PL-400 · Question #368
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. Adding a custom connector to a managed solution facilitates deployment, but it doesn't inherently control its visibility or access exclusively to users within a specific tenant.
Question
Options
- AYes
- BNo
How the community answered
(41 responses)- A20% (8)
- B80% (33)
Why each option
Adding a custom connector to a managed solution facilitates deployment, but it doesn't inherently control its visibility or access exclusively to users within a specific tenant.
Adding to a managed solution is a deployment mechanism, not an access control mechanism for tenant visibility.
Adding a custom connector to a managed solution facilitates its deployment and lifecycle management across environments, but it does not inherently guarantee or enforce that the connector will only be visible and accessible to users within a specific tenant. The single-tenant restriction is primarily determined by the Azure Function's Microsoft Entra ID application registration and the custom connector's authentication configuration.
Concept tested: Custom connector deployment and tenant access
Source: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/share-custom-connector
Community Discussion
No community discussion yet for this question.