Question

You are designing a Copilot Studio agent for a healthcare provider that queries patient appointment data stored in a Dataverse environment governed by row-level security. Regulatory rules require that each user only ever see records they are individually authorized to access, and every data access must be attributable to the requesting individual for audit purposes. When configuring how the agent authenticates to the Dataverse connector, which approach best satisfies these governance and compliance requirements?

Accepted Answer

Configure the connector to authenticate on behalf of the signed-in user so Dataverse enforces the individual's row-level security and each access is attributed to that user

Answer

Configure the connector to use a single service principal (application) identity with broad Dataverse read access, and filter results in the agent's topic logic based on the user's identity

Answer

Use a shared connection reference tied to the maker's account so all agent queries run under the maker's elevated permissions for consistent behavior

Answer

Store each user's credentials in an environment variable and pass them to the connector at runtime to impersonate the correct identity