PL-400 · Question #369
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 h
The correct answer is B. No. Publishing a custom connector to AppSource makes it publicly available globally, directly contradicting the requirement for it to be visible and accessible only to users in a specific tenant.
Question
Options
- AYes
- BNo
How the community answered
(45 responses)- A20% (9)
- B80% (36)
Why each option
Publishing a custom connector to AppSource makes it publicly available globally, directly contradicting the requirement for it to be visible and accessible only to users in a specific tenant.
Publishing to AppSource makes the connector public, not tenant-specific.
Publishing a custom connector to AppSource makes it publicly available to all Power Apps and Power Automate users globally, which directly violates the requirement that the connector must be visible and accessible only to users in the specific tenant. AppSource is designed for public distribution, not private tenant-specific use.
Concept tested: Custom connector distribution and scope
Source: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/share-custom-connector#submit-your-connector-for-microsoft-certification
Community Discussion
No community discussion yet for this question.