@itsmelmon
Its actually a separate Dataverse environment (Dataverse is the recent brand new name for what was formerly called Common Data Service environment or CDS environment) .
Dataverse for Teams is the type, and it is a new, very specific, and very special type of environment.
The Table might be called Area Inspection that has some of the records to check, but you'd need to check for the Table you want.
A good sign is if the Dataverse has these Tables in it (partial list from A-Z):
Keep in mind, that this special Teams Dataverse environment is actually separate from any others. Any Apps in any other Dataverse environments, have their own separate Tables whose data and records are not shared with this environment. So make sure when you go and make the Flow, from https://us.flow.microsoft.com/ that you switch to this environment specifically before you create it. Careful, it may be hard to tell as the name of the environment may be very similar to another Dataverse environment that is not the Dataverse for Teams one. You may need to cross reference the Environment GUID's showing in the URL bar with the right environment ID's as seen from the Power Platform Admin Center
Although technically a more refined and detailed explanation might be more accurate, we believe this specific functionality you are inquiring about is either the main essential point of the notorious new release known as Project Oakdale or even if it is something separate, it is something very strongly associated with that wave of releases. Essentially the main point is that having the Dataverse in the same exact database as Teams was something not previously possible before just a few months ago actually before this new powerful feature set was introduced. That unique way the Canvas Apps like the Teams Inspection app just run so directly in Teams itself like that and on the exact same database using even the Dataverse capabilities directly on the same underlying backend. Essentially Teams just being on Dataverse itself is a pretty recently released and potentially very powerful capability, and it could possibly help even replace some specific implementation cases where before it required manual Office 365 development of highly custom apps that required advanced coding, with hard coded Graph API calls and complicated synchronizations, etc. that could previously possibly only be done using complex code only and requiring full initialization of a full stack Office 365 Development, even for simple Teams apps previously (depends on the specific case).
Check if this above helps @itsmelmon
