Skip to content

Commit 28cc736

Browse files
Update for correctness
1 parent 9f320b2 commit 28cc736

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

articles/azure-app-configuration/quickstart-deployment-overview.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,22 +13,28 @@ ms.custom: subject-armqs, mode-arm, devx-track-bicep
1313
# Deployment
1414

1515
Azure App Configuration supports following methods to read and manage your configuration for deployment:
16+
1617
- [ARM template](./quickstart-resource-manager.md)
1718
- [Bicep](./quickstart-bicep.md)
1819
- Terraform
1920

2021
## Manage Azure App Configuration resources in deployment
21-
### Authorization
22+
23+
### Azure Resource Manager Authorization
24+
2225
You must have permissions to manage Azure App Configuration resources. Azure role-based access control (Azure RBAC) roles that provide these permissions include the Microsoft.AppConfiguration/configurationStores/write or Microsoft.AppConfiguration/configurationStores/* action. Built-in roles with this action include:
26+
2327
- The Azure Resource Manager Owner role
2428
- The Azure Resource Manager Contributor role
2529

2630
To learn more about Azure RBAC and Microsoft Entra ID, see [Authorize access to Azure App Configuration using Microsoft Entra ID](./concetp-enable-rbac.md).
2731

2832
## Manage Azure App Configuration data in deployment
33+
2934
Azure App Configuration data, such as key-values and snapshots, can be managed in deployment. It is recommended to configure **Pass-through** ARM authentication mode to require proper Azure App Configuration data plane authorization.
3035

3136
### ARM authentication mode
37+
3238
# [Azure portal](#tab/portal)
3339

3440
To configure ARM authentication mode of Azure App Configuration resource in the Azure portal, follow these steps:
@@ -47,14 +53,17 @@ To configure ARM authentication mode of Azure App Configuration resource in the
4753
> [!NOTE]
4854
> Local authentication mode is for backward compatibility and has several limitations. It does not support proper auditing for accessing data in deployment. Under local authentication mode, key-value data access inside an ARM template/Bicep/Terraform is disabled if [access key authentication is disabled](./howto-disable-access-key-authentication.md#limitations). Azure App Configuration data plane permissions are not required for accessing data under local authentication mode.
4955
50-
### Authorization
56+
### Azure App Configuration Authorization
57+
5158
In addition to the permissions required for managing Azure App Configuration resource, you must have data plane permissions to read and manage Azure App Configuration data in deployment under pass-through mode. Azure App Configuration data plane permissions include Microsoft.AppConfiguration/configurationStores/keyValues/read and Microsoft.AppConfiguration/configurationStores/snapshots/read. Built-in roles with this action include:
59+
5260
- App Configuration Data Owner
5361
- App Configuration Data Reader
5462

5563
To learn more about Azure RBAC and Microsoft Entra ID, see [Authorize access to Azure App Configuration using Microsoft Entra ID](./concetp-enable-rbac.md).
5664

5765
### ARM private access
66+
5867
[Azure Resource Management Private Link](../../includes/resource-manager-create-rmpl.md) can be set up to restrict access for managing resources in your virtual network. Azure App Configuration supports ARM Private Link access to the App Configuration data under pass-through authentication mode and ARM private access enabled.
5968

6069
# [Azure portal](#tab/portal)

0 commit comments

Comments
 (0)