Why publishing a custom connector to AppSource does not deploy it

PL-400 By islever Editorial Last updated

Create custom connectors

Short answer

B Publishing to AppSource puts the connector in a public marketplace and does not deploy it into the tenant's production environment, so it fails the goal.

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: Publish the custom connector to AppSource. Does the solution meet the goal?
  1. Yes
  2. No Correct Answer

Key Takeaways

AppSource is Microsoft's public app marketplace for distribution to customers, not an environment-to-environment deployment mechanism. A tenant-scoped connector is deployed via solutions, never by publishing to AppSource.

The connector must move to the tenant's production environment and stay visible only to tenant users. Publishing to AppSource puts the connector in a public marketplace, which is unrelated to deploying it into a specific Power Platform environment, so the solution does not meet the goal.

Common mistake: Confusing 'publish' (making something publicly available on AppSource) with 'deploy' (moving a component into a specific environment via a solution). They are entirely different operations.

Expert Analysis

Why the Answer Is Correct

AppSource is a public marketplace for commercially distributing apps and connectors to external customers. Publishing there makes the connector publicly available; it does not import the connector into the company's production Power Platform environment, nor does it keep it restricted to tenant users. Therefore it does not meet the deployment goal.

Why the Other Options Are Wrong

The only other offered option is A (Yes), which is wrong because AppSource publication is not an environment deployment path. The supported path remains solution export/import.

Community Comment Notes

rrustick (likes=5) explains AppSource is a marketplace and not the correct way to deploy a tenant-restricted connector to production. Juan0414 (likes=1) reinforces that AppSource does not satisfy the tenant-only, production-environment requirement.

Official Reference

https://learn.microsoft.com/en-us/connectors/custom-connectors/

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

Community Votes

B
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

  1. rrustick 👍 5
    B. No Explanation: Publishing the custom connector to AppSource is not the correct solution for deploying it to a production environment accessible only to users in the tenant. AppSource is a marketplace for distributing and discovering business applications, add-ins, and connectors for Microsoft products like Dynamics 365, Office 365, and Power BI. Publishing to AppSource makes the connector available to a broader audience beyond the company's tenant. To deploy the custom connector to a production environment accessible only to users in the tenant, the appropriate steps would involve configuring and deploying the connector within the company's environment, such as deploying it to Microsoft Power Platform or Azure, and managing access controls to ensure it's visible and accessible only to users within the tenant.
  2. Masaan 👍 2
    someone please tell us what is the right answer,,, I'm not saying anything here to avoid confusion
  3. Juan0414 👍 1 Answered B
    "The connector must be visible and accessible only to users in the tenant."
  4. HeWhoTakesExams 👍 1
    Scam-artist-tier trickery in these questions. Shoutouts to Microsoft

Reader comments & corrections

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

Log in to comment, report an error, or add a note about this question.

Diagnosing the 'remote name could not be resolved' 404 for the Northwind Web API connector

S-grade

Solution for Long-Running Transactional Dataverse Operations

S-grade

Why exporting a custom connector directly from the maker portal fails to deploy it

S-grade

Preventing plug-in timeouts when calling a slow external web service

S-grade

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