Proposed Pull Request Change

title description author ms.author ms.service ms.topic ms.date
Azure App Configuration REST API - Microsoft Entra authorization Use Microsoft Entra ID for authorization against Azure App Configuration by using the REST API maud-lv malev azure-app-configuration reference 08/17/2020
📄 Document Links
GitHub View on GitHub Microsoft Learn View on Microsoft Learn
Content Truncation Detected
The generated rewrite appears to be incomplete.
Original lines: -
Output lines: -
Ratio: -
Raw New Markdown
Generating updated version of doc...
Rendered New Markdown
Generating updated version of doc...
+0 -0
+0 -0
--- title: Azure App Configuration REST API - Microsoft Entra authorization description: Use Microsoft Entra ID for authorization against Azure App Configuration by using the REST API author: maud-lv ms.author: malev ms.service: azure-app-configuration ms.topic: reference ms.date: 08/17/2020 --- # Microsoft Entra authorization - REST API reference When you use Microsoft Entra authentication, authorization is handled by role-based access control (RBAC). RBAC requires users to be assigned to roles in order to grant access to resources. Each role contains a set of actions that users assigned to the role are able to perform. ## Roles The following roles are available in Azure subscriptions by default: - **Azure App Configuration Data Owner**: This role provides full access to all operations. It permits the following actions: * Microsoft.AppConfiguration/configurationStores/*/read * Microsoft.AppConfiguration/configurationStores/*/write * Microsoft.AppConfiguration/configurationStores/*/delete * Microsoft.AppConfiguration/configurationStores/*/action - **Azure App Configuration Data Reader**: This role enables read operations. It permits the following actions: * Microsoft.AppConfiguration/configurationStores/*/read ## Actions Roles contain a list of actions that users assigned to that role can perform. Azure App Configuration supports the following actions: - `Microsoft.AppConfiguration/configurationStores/keyValues/read`: This action allows read access to App Configuration key-value resources, such as /kv and /labels. - `Microsoft.AppConfiguration/configurationStores/keyValues/write`: This action allows write access to App Configuration key-value resources. - `Microsoft.AppConfiguration/configurationStores/keyValues/delete`: This action allows App Configuration key-value resources to be deleted. Note that deleting a resource returns the key-value that was deleted. - `Microsoft.AppConfiguration/configurationStores/snapshots/read`: This action allows read access to App Configuration snapshot resources, as well as any key-values contained within snapshots. - `Microsoft.AppConfiguration/configurationStores/snapshots/write`: This action allows write access to App Configuration snapshot resources. - `Microsoft.AppConfiguration/configurationStores/snapshots/archive/action`: This action allows access to archive and recover App Configuration snapshot resources. ## Error ```http HTTP/1.1 403 Forbidden ``` **Reason:** The principal making the request doesn't have the required permissions to perform the requested operation. **Solution:** Assign the role required to perform the requested operation to the principal making the request. ## Managing role assignments You can manage role assignments by using [Azure RBAC procedures](../role-based-access-control/overview.md) that are standard across all Azure services. You can do this through the Azure CLI, PowerShell, and the Azure portal. For more information, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
Success! Branch created successfully. Create Pull Request on GitHub
Error: