Skip to content

Commit d7941f4

Browse files
authored
Update DNS zone group limitations in documentation
Clarified limitations on DNS zone groups for private endpoints.
1 parent 881044b commit d7941f4

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

articles/private-link/private-endpoint-dns-integration.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -212,6 +212,7 @@ In a hub-and-spoke topology, a common scenario allows the creation of private DN
212212

213213
> [!NOTE]
214214
> - Each DNS zone group can support up to five DNS zones.
215+
> - Each DNS zone group can include only one private DNS zone per DNS zone name. For example, you can't associate more than one private DNS zone resource for `privatelink.blob.core.windows.net` to the same DNS zone group.
215216
> - Adding multiple DNS zone groups to a single Private Endpoint isn't supported.
216217
> - Delete and update operations for DNS records can be seen performed by **Azure Traffic Manager and DNS.** This is a normal platform operation necessary for managing your DNS Records.
217218

0 commit comments

Comments
 (0)