Skip to content

Commit 5b5c919

Browse files
authored
Merge pull request #173781 from v-amallick/master
Horizontal content Azure RBAC doc updates
2 parents 7874b40 + 0c57539 commit 5b5c919

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

articles/backup/backup-azure-database-postgresql-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: About Azure Database for PostgreSQL backup
33
description: An overview on Azure Database for PostgreSQL backup (preview)
44
ms.topic: conceptual
5-
ms.date: 09/22/2021
5+
ms.date: 09/28/2021
66
ms.custom: references_regions
77
---
88

@@ -107,10 +107,10 @@ To grant all the access permissions needed by Azure Backup, refer to the followi
107107

108108
1. Set Backup vault’s MSI **Key Vault Secrets User** (or **get**, **list** secrets) access on the Azure key vault. To assign permissions, you can use role assignments or access policies. It’s not required to add the permission using both the options as it doesn’t help.
109109

110-
- Using RBAC authorization (that is, Permission model is set to Azure role-based access control):
110+
- Using Azure role-based access control (Azure RBAC) authorization (that is, Permission model is set to Azure role-based access control):
111111

112112
- Under Access control, grant the backup vault’s MSI _Key Vault Secrets User_ access on the key vault. Bearers of that role will be able to read secrets.
113-
- [Grant permission to applications to access an Azure key vault using Azure RBAC](/azure/key-vault/general/rbac-guide?tabs=azure-cli)
113+
- [Grant permission to applications to access an Azure key vault using Azure RBAC](/azure/key-vault/general/rbac-guide?tabs=azure-cli).
114114

115115
:::image type="content" source="./media/backup-azure-database-postgresql-overview/key-vault-secrets-user-access-inline.png" alt-text="Screenshot showing the option to provide secret user access." lightbox="./media/backup-azure-database-postgresql-overview/key-vault-secrets-user-access-expanded.png":::
116116

articles/backup/blob-backup-configure-manage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configure operational backup for Azure Blobs
33
description: Learn how to configure and manage operational backup for Azure Blobs.
44
ms.topic: conceptual
5-
ms.date: 08/06/2021
5+
ms.date: 09/28/2021
66

77
---
88

@@ -135,7 +135,7 @@ To start configuring backup:
135135

136136
1. Select **Review + create** to create the backup policy.
137137

138-
1. Choose the required storage accounts for configuring protection of blobs. You can choose multiple storage accounts at once and choose Select.<br></br>However, ensure that the vault you have chosen has the required RBAC role assigned to configure backup on storage accounts. Learn more about [Grant permissions to the Backup vault on storage accounts](#grant-permissions-to-the-backup-vault-on-storage-accounts).<br></br>If the role is not assigned, you can still assign the role while configuring backup. See step 7.
138+
1. Choose the required storage accounts for configuring protection of blobs. You can choose multiple storage accounts at once and choose Select.<br></br>However, ensure that the vault you have chosen has the required Azure role-based access control (Azure RBAC) role assigned to configure backup on storage accounts. Learn more about [Grant permissions to the Backup vault on storage accounts](#grant-permissions-to-the-backup-vault-on-storage-accounts).<br></br>If the role is not assigned, you can still assign the role while configuring backup. See step 7.
139139

140140
![Verify permissions of the vault](./media/blob-backup-configure-manage/verify-vault-permissions.png)
141141

articles/backup/private-endpoints-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Private endpoints overview
33
description: Understand the use of private endpoints for Azure Backup and the scenarios where using private endpoints helps maintain the security of your resources.
44
ms.topic: conceptual
5-
ms.date: 08/19/2021
5+
ms.date: 09/28/2021
66
ms.custom: devx-track-azurepowershell
77
---
88

@@ -23,7 +23,7 @@ This article will help you understand how private endpoints for Azure Backup wor
2323
- Virtual networks with Network Policies aren't supported for Private Endpoints. You'll need to [disable Network Polices](../private-link/disable-private-endpoint-network-policy.md) before continuing.
2424
- You need to re-register the Recovery Services resource provider with the subscription if you registered it before May 1 2020. To re-register the provider, go to your subscription in the Azure portal, navigate to **Resource provider** on the left navigation bar, then select **Microsoft.RecoveryServices** and select **Re-register**.
2525
- [Cross-region restore](backup-create-rs-vault.md#set-cross-region-restore) for SQL and SAP HANA database backups aren't supported if the vault has private endpoints enabled.
26-
- When you move a Recovery Services vault already using private endpoints to a new tenant, you'll need to update the Recovery Services vault to recreate and reconfigure the vault’s managed identity and create new private endpoints as needed (which should be in the new tenant). If this isn't done, the backup and restore operations will start failing. Also, any role-based access control (RBAC) permissions set up within the subscription will need to be reconfigured.
26+
- When you move a Recovery Services vault already using private endpoints to a new tenant, you'll need to update the Recovery Services vault to recreate and reconfigure the vault’s managed identity and create new private endpoints as needed (which should be in the new tenant). If this isn't done, the backup and restore operations will start failing. Also, any Azure role-based access control (Azure RBAC) permissions set up within the subscription will need to be reconfigured.
2727

2828
## Recommended and supported scenarios
2929

@@ -116,4 +116,4 @@ The following diagram shows how the name resolution works for storage accounts u
116116

117117
## Next steps
118118

119-
- [Create and use private endpoints](private-endpoints.md)
119+
- [Create and use private endpoints](private-endpoints.md).

0 commit comments

Comments
 (0)