A community bank wants its branch staff to build a small loan-referral app, an approval flow, and a question-answering agent that all read and write the same set of records, with staff working inside Microsoft Teams. Which built-in component provides the shared low-code data platform that the app, the flow, and the agent all draw on?
- AThe Power Platform admin center, the unified portal administrators use to manage environments and settings across Power Platform services
- BThe Power Apps tab for Teams, which embeds a canvas or model-driven app as a tab inside a Teams channel
- CMicrosoft Dataverse for Teams, the built-in low-code data platform that Power Apps, Power Automate, and Copilot Studio all build against Correct
- DA custom connector, which lets a Power Platform service reach an external data source through a defined interface
Why A is wrong: Tempting because it is the one cross-service surface named in the grounding, but the admin center is a management portal for administrators, not the data platform that apps, flows, and agents read and write records against.
Why B is wrong: The Power Apps tab is a way to surface an app inside Teams, not the shared data store; it embeds an app but does not itself hold the records the flow and agent also use.
Why C is correct: Correct. Dataverse for Teams is described as the built-in, low-code data platform that empowers users to build custom apps, agents, and flows using Power Apps, Copilot Studio, and Power Automate, so all three services act on the same shared records inside Teams.
Why D is wrong: Custom connectors reach out to external systems; they do not provide the built-in internal data platform that the in-Teams app, flow, and agent share, so this misses the integrated shared-data point.