An organization is implementing a client-side Single Page Application (SPA) named ClientConnect. The application must authenticate users using Microsoft Entra ID and access a secure downstream web API named DataAPI on behalf of the signed-in user. The DataAPI exposes a custom scope named Data.Write.
You register both ClientConnect and DataAPI in Microsoft Entra ID.
Which two configuration steps should you perform in Microsoft Entra ID to implement the required permissions and consent? Select two.
- In the App Registration for ClientConnect, add the custom scope Data.Write from DataAPI as a Delegated permission.Cevap
- In the App Registration for DataAPI, define the custom scope Data.Write under the Expose an API section.Cevap
- CGenerate a Shared Access Signature (SAS) token with write permissions and configure ClientConnect to include it in requests to DataAPI.
- DIn the App Registration for ClientConnect, add the custom scope Data.Write from DataAPI as an Application permission.
Cevap
In the App Registration for ClientConnect, add the custom scope Data.Write from DataAPI as a Delegated permission; and in the App Registration for DataAPI, define the custom scope Data.Write under the Expose an API section.
To access the custom downstream web API on behalf of a signed-in user, two configurations must be met: First, the target web API (DataAPI) must expose the scope by defining it in the Expose an API section. Second, the client application (ClientConnect) must request access by adding that scope as a Delegated permission. This maintains the user context flow.
Adım Adım Çözüm
Anahtar Kavram
Delegated permissions and custom API scopes in Microsoft Entra ID