You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: infrastructure/infrastructure-setup-bicep/15-private-network-standard-agent-setup/README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,6 +117,7 @@ To use an existing VNet and subnets, set the existingVnetResourceId parameter to
117
117
- param agentSubnetPrefix string = '192.168.0.0/24' //optional, default is '192.168.0.0/24'
118
118
- param peSubnetName string = 'pe-subnet' //optional, default is 'pe-subnet'
119
119
- param peSubnetPrefix string = '192.168.1.0/24' //optional, default is '192.168.1.0/24'
120
+
- param dnsZonesSubscriptionId string = '' //optional, leave empty to use current subscription, or set to a subscription ID if DNS zones are in a different subscription
120
121
- param existingDnsZones = {
121
122
122
123
'privatelink.services.ai.azure.com': 'privzoneRG' //add resource group name where your private DNS zone is located
@@ -125,6 +126,10 @@ To use an existing VNet and subnets, set the existingVnetResourceId parameter to
125
126
126
127
💡 If subnets information is provided then make sure it exist within the specified VNet to avoid deployment errors. If subnet information is not provided, the template will create subnets with the default address space.
127
128
129
+
💡 **Cross-Subscription DNS Zones**: All DNS zones specified in `existingDnsZones` will be referenced from the subscription specified in `dnsZonesSubscriptionId`. Leave this parameter empty (default) to use the current deployment subscription, or set it to a subscription ID if your DNS zones are located in a different subscription.
130
+
131
+
⚠️ **Important**: When `dnsZonesSubscriptionId` is set to a different subscription, ALL DNS zones in `existingDnsZones` must have resource groups specified (non-empty values). The template does not support creating new DNS zones in a different subscription. Empty resource groups are only allowed when creating zones in the current deployment subscription.
Copy file name to clipboardExpand all lines: infrastructure/infrastructure-setup-bicep/15-private-network-standard-agent-setup/modules-network-secured/private-endpoint-and-dns.bicep
Copy file name to clipboardExpand all lines: infrastructure/infrastructure-setup-bicep/15-private-network-standard-agent-setup/modules-network-secured/validate-existing-resources.bicep
0 commit comments