Why adding a custom connector to a managed solution breaks deployment

PL-400 By islever Editorial Last updated Sep 25, 2026

Create custom connectors Implement application lifecycle management (ALM)

Short answer

B Components cannot be added to a managed solution; add the connector to an unmanaged solution, export it, and import it, so the managed-solution approach fails.

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than once correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. A company develops a new custom connector for a Microsoft Entra ID-protected Azure Function that was created as a single tenant app. The custom connector must be moved to a production environment. The connector must be visible and accessible only to users in the tenant. You need to deploy the custom connector. Solution: Add the custom connector to a managed solution, export the managed solution, and then import the managed solution into the production environment. Does the solution meet the goal?

Yes
No Correct Answer

Key Takeaways

Managed solutions are sealed; you cannot add, edit, or remove components in them. The correct deployment is to add the connector to an unmanaged solution, then export that solution (as managed for production) and import it.

The same connector must move to production and stay tenant-scoped. The proposed solution adds the custom connector to a managed solution, exports it, and imports it. But components cannot be added to a managed solution — only to unmanaged solutions — so the approach does not work.

Common mistake: Believing you can 'add a component to a managed solution.' Managed solutions are read-only containers used for distribution; all composition happens in unmanaged solutions first.

Expert Analysis

Why the Answer Is Correct

A managed solution is a sealed, deployed artifact — you cannot add new components to it. To deploy the custom connector you must first add it to an unmanaged solution, then export that solution (choosing managed for the production target) and import it. Because the proposed solution tries to add the connector to a managed solution, it cannot be executed and does not meet the goal.

Why the Other Options Are Wrong

The alternative option A (Yes) is incorrect because the premise — adding to a managed solution — is invalid. The correct variant of this series uses an unmanaged solution, not a managed one.

Community Comment Notes

Panda01 (likes=5) states plainly that you cannot add components to a managed solution, only to unmanaged solutions. Juan0414 (likes=1) reinforces that adding to a managed solution is not possible.

Official Reference

https://learn.microsoft.com/en-us/power-platform/alm/overview-alm

This link opens the official vendor documentation in a new tab.

Community Votes

100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

Panda01 👍 5 Answered B

B: No You can't add components to a managed solution, only unmanaged solutions.
DevInProgress 👍 1

The answer is A. The proposed solution meets the objective of moving the custom connector to a production environment, as the process of adding the custom connector to a managed solution, exporting the managed solution, and then importing it into the production environment is the proper flow for moving solutions between environments in Power Platform. This ensures that the connector remains a managed solution and is restricted to a specific environment, fulfilling the need for it to be visible and accessible only to tenant users. In addition, a managed solution ensures that the connector remains protected and accessible only to users in the relevant production environment, as required by the question.
loftuscheek 👍 1 Answered A

its correct ( they mean by the question to add to new solution and export as managed )
Juan0414 👍 1 Answered B

You can not add components to managed solutions.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Practice All PL-400 Questions

Access 85 questions with complete answers and detailed explanations.

View Full PL-400 Practice Test →

← Back to PL-400 Study Guide