A solution architect at Kestrel Healthcare is designing a Copilot Studio agent that will use custom Power Platform connectors built by the integration team. The integration team maintains these connectors in a development environment (Dev), while the business wants the agent deployed in the production environment (Prod). The architect proposes connecting the agent in Prod directly to the connectors in Dev to avoid duplication. Why will this proposal fail, and what is the correct approach?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Power Platform environments are isolated containers — a Copilot Studio agent in Prod can't reach into Dev to grab a connector any more than you can use a library card from a different city. The connectors must be in the same environment, migrated via ALM (solution export/import or pipelines). Answer: D.
Full explanation below image
Full Explanation
Power Platform environments are fully isolated administrative boundaries. All resources — agents, connectors, flows, Dataverse tables, and environment variables — are scoped to the environment in which they were created. Cross-environment references are not supported for runtime execution.
Option D is correct because it accurately identifies both the root cause (environment isolation prevents cross-environment connector discovery) and the correct remedy (ALM-based migration). Microsoft's recommended approach uses Power Platform solutions to package the custom connector definitions, then export the solution from Dev and import it into Prod using the managed solution format. Alternatively, organizations can configure Power Platform Pipelines or Azure DevOps-based deployment pipelines to automate this promotion process.
Option A is incorrect because the environment isolation issue has nothing to do with Azure subscriptions. A Power Platform environment can be linked to an Azure subscription for capacity, but connector availability is governed by the Power Platform environment boundary, not by the Azure subscription configuration.
Option B is incorrect. While Dataverse-enabled environments do unlock additional capabilities, cross-environment connector references are not supported regardless of license tier. The isolation boundary is architectural, not a licensing restriction that can be lifted by purchasing a higher tier.
Option C is incorrect in its approach description. While it correctly identifies the import/export mechanism, it uses the term 'export the connector solution' loosely without mentioning the proper ALM (Application Lifecycle Management) process. More importantly, option D is more complete and precise — it names the correct migration methodology (solution-based ALM) and mentions both the export/import path and pipeline automation options.
Exam tip: Environment isolation is a foundational Power Platform concept. For AB-620, remember: agent + connector + flow must all be in the same environment at runtime. Moving resources between environments requires solutions and ALM pipelines — not direct cross-environment references.