A company has a Microsoft 365 tenant in Canada and multiple Microsoft Power Platform environments in Canada and the United States. The company plans to deploy a Microsoft Copilot Studio agent to the Canadian environment that will use:
* Microsoft Dataverse data stored in Canada
* A connector that connects to an Azure OpenAI instance in the United States
You need to ensure that the agent adheres to data residency and data movement policies before being deployed. What should you do?
The key issue is that the agent will run in a Canadian environment and use:
Dataverse data stored in Canada
a connector to Azure OpenAI in the United States
That means data may need to move across regions. Before deployment, the organization must make sure this cross-region use is explicitly allowed under the platform's data movement and residency controls.
That makes C the correct answer.
Why C is correct:
It directly addresses the fact that the solution uses services in different geographic regions
It ensures the environment and its connector dependencies are configured to allow that movement in line with platform policy
It is the most specific action tied to data residency and data movement compliance before deployment
Why the other options are not correct:
A . Ensure that the data processed by Azure OpenAI is stored in the United States. This does not address whether the cross-region movement itself is permitted.
B . From the Microsoft Purview portal, validate the Data loss prevention settings. DLP helps govern connector usage and data exfiltration, but the question is specifically about data residency and cross-region data movement.
D . Migrate the tenant to the United States. This is unnecessary and does not align with the stated Canadian deployment requirement.
Currently there are no comments in this discussion, be the first to comment!