A compost-vendor app must create user accounts in its own directory when staff are assigned in Microsoft Entra ID. Which enterprise-application capability addresses that requirement, as distinct from OAuth permission grants?
Select an answer to reveal the explanation.
Short Explanation
Provisioning is the conveyor that creates users in the vendor’s directory when you assign them in Entra. OAuth grants are a different blade—those let the app call APIs, not mint accounts in the SaaS side.
Full Explanation
Enterprise applications can enable automated user provisioning to create, update, and disable accounts in the SaaS directory based on Entra assignments, typically via SCIM or an app-specific connector. OAuth permission grants authorize API calls such as Microsoft Graph and do not themselves provision vendor-directory users. Application Proxy publishes on-premises web apps. Azure AD Connect addresses hybrid directory sync, not the enterprise-app provisioning blade for this SaaS scenario.