A development team is planning an agent that needs to store customer ticket data collected during conversations and allow other Power Apps to read that data. Which storage solution should they use to align with Power Platform best practices?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Dataverse is Power Platform's native data backbone — it speaks the same language as Copilot Studio, Power Apps, and Power Automate, with built-in security, relationships, and zero glue code. Answer: B.
Full explanation below image
Full Explanation
Microsoft Dataverse is the recommended data store for Power Platform solutions because it integrates natively with all Power Platform components without custom connectors or middleware.
Option B is correct. Dataverse provides: role-based access control via security roles that integrate with Entra ID, table relationships that the agent can traverse, native connectors in Power Automate and Power Apps (no custom connector required), and auditing/change history out of the box. Copilot Studio actions can write to and read from Dataverse directly using the Dataverse connector in Power Automate.
Option A is incorrect. While SharePoint lists work for simple scenarios, they have limitations: 5,000-item view thresholds, limited relationship modeling, no proper row-level security comparable to Dataverse, and poor support for complex data structures. For ticket management data that other apps need to read, SharePoint is the wrong tool.
Option C is incorrect. Azure Blob Storage is appropriate for file/binary data, not structured relational data like customer tickets. Building a REST API wrapper for Power Apps to read blob storage adds significant complexity that Dataverse eliminates.
Option D is incorrect. SQL Server with a custom connector is viable but adds unnecessary infrastructure, licensing costs (SQL Server), and custom connector maintenance. Dataverse provides equivalent capability natively within the Power Platform tenant.