Stay organized with collections
Save and categorize content based on your preferences.
This page explains the considerations for adding or updating the Virtual Private Cloud
(VPC) networks used by your Managed Service for Microsoft Active Directory
domain.
When you add or update the VPC networks used by your Managed Microsoft AD
domain, you should consider the following factors:
You can only add a VPC network from the project in
which you create the domain.
You can only add up to a total of five VPC networks to your
Managed Microsoft AD domain as authorized networks.
CIDR range considerations apply across all VPC networks in a
Managed Microsoft AD domain. For more information, see
Select IP address ranges.
Adding authorized networks to your Managed Microsoft AD domain does not
provide transitive connectivity. This means that a VM on one of the authorized
networks is not automatically able to reach a VM on another authorized network.
If you need connectivity between authorized networks, you must manually create
VPC peering between them. For more information, see
VPC peering.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Select VPC networks\n\nThis page explains the considerations for adding or updating the Virtual Private Cloud\n(VPC) networks used by your Managed Service for Microsoft Active Directory\ndomain.\n\nWhen you add or update the VPC networks used by your Managed Microsoft AD\ndomain, you should consider the following factors:\n\n- You can only add a VPC network from the project in\n which you create the domain.\n\n- You can only add up to a total of five VPC networks to your\n Managed Microsoft AD domain as authorized networks.\n\n- CIDR range considerations apply across all VPC networks in a\n Managed Microsoft AD domain. For more information, see\n [Select IP address ranges](/managed-microsoft-ad/docs/selecting-ip-address-ranges).\n\n- Adding authorized networks to your Managed Microsoft AD domain does not\n provide transitive connectivity. This means that a VM on one of the authorized\n networks is not automatically able to reach a VM on another authorized network.\n If you need connectivity between authorized networks, you must manually create\n VPC peering between them. For more information, see\n [VPC peering](/vpc/docs/using-vpc-peering).\n\n- Standard [VPC quotas and limits](/vpc/docs/quota) apply to these\n networks.\n\nWhat's next\n-----------\n\n- [Create a domain](/managed-microsoft-ad/docs/create-domain)\n- [Manage authorized networks](/managed-microsoft-ad/docs/managing-authorized-networks)"]]
