Skip to content

Commit e168154

Browse files
author
AbhishekMallick01
committed
PE doc updates
1 parent 6205b09 commit e168154

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

articles/backup/backup-azure-private-endpoints-concept.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,13 @@ In addition to the Azure Backup cloud services, the workload extension and agent
145145

146146
As a pre-requisite, Recovery Services vault requires permissions for creating additional private endpoints in the same Resource Group. We also recommend providing the Recovery Services vault the permissions to create DNS entries in the private DNS zones (`privatelink.blob.core.windows.net`, `privatelink.queue.core.windows.net`). Recovery Services vault searches for private DNS zones in the resource groups where VNet and private endpoint are created. If it has the permissions to add DNS entries in these zones, they’ll be created by the vault; otherwise, you must create them manually.
147147

148+
>[!Note]
149+
>Integration with private DNS zone present in different subscriptions is unsupported in this experience.
150+
151+
The following diagram shows how the name resolution works for storage accounts using a private DNS zone.
152+
153+
:::image type="content" source="./media/private-endpoints-overview/name-resolution-works-for-storage-accounts-using-private-dns-zone-inline.png" alt-text="Diagram showing how the name resolution works for storage accounts using a private DNS zone." lightbox="./media/private-endpoints-overview/name-resolution-works-for-storage-accounts-using-private-dns-zone-expanded.png":::
154+
148155
## Next steps
149156

150157
- Learn [how to configure and manage private endpoints for Azure Backup](backup-azure-private-endpoints-configure-manage.md).

0 commit comments

Comments
 (0)