Disable dbo schema fallback when table doesn't exist in default schema
In a word, no this is not possible.

I've struggled to find an official line on this, but the name resolution algorithm in SQL Server is something like the following, as defined by Bob Beauchemin in Dude, Where's my table?

If batch or dynamic SQL:


Look in 'sys' schema for system objects
Look in user's default schema
Look in dbo schema


If procedural code: 


Look in 'sys' schema for system objects
Look in procedure schema
Look in dbo schema


In your case, SQL Server is failing to find an MS Shipped object firstly, then failing to find the object in the user schema (DataTeamSchema), and finally it finds the object in the dbo schema.

One way around this would be to change the original object to a schema other than dbo, as the dbo schema is a special case in terms of object-name resolution.

There does not appear to be a documented way to avoid this behaviour.