Skip to content

Commit ff36118

Browse files
author
AbhishekMallick01
committed
PE updates
1 parent 0ccff61 commit ff36118

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,8 @@ This article describes how the [enhanced capabilities of private endpoints](#key
2828

2929
- You can create private endpoints for new Recovery Services vaults that don't have any items registered/protected to the vault, only.
3030

31-
- You can't create private endpoints using static IP.
31+
>[!Note]
32+
>You can't create private endpoints using static IP.
3233
3334
- You can't upgrade vaults (that contains private endpoints) created using the classic experience to the new experience. You can delete all existing private endpoints, and then create new private endpoints with the v2 experience.
3435

@@ -42,6 +43,8 @@ This article describes how the [enhanced capabilities of private endpoints](#key
4243

4344
- [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.
4445

46+
- You can create DNS across subscriptions.
47+
4548
## Recommended and supported scenarios
4649

4750
While private endpoints are enabled for the vault, they're used for backup and restore of SQL and SAP HANA workloads in an Azure VM, MARS agent backup and DPM only. You can use the vault for backup of other workloads as well (they won't require private endpoints though). In addition to backup of SQL and SAP HANA workloads and backup using the MARS agent, private endpoints are also used to perform file recovery for Azure VM backup.

0 commit comments

Comments
 (0)