Managed Microsoft Active Directory (AD) support is available in preview. During this preview, connecting Cloud Volumes Service and Managed AD is a manual, multi-step process.
Both Cloud Volumes Service and Managed AD are peered to your user VPC network. Because Google Cloud VPC networks don't allow transitive routing, Cloud Volumes Service can't access Managed AD through your user VPC network.
Managed AD deployment architecture
The following diagram shows the architecture for the required three-way peering:
Peering from Managed AD to your VPC network occurs when you set up Managed AD.
Peering from Cloud Volumes Service to your VPC network occurs during the Cloud Volumes Service onboarding process.
Connecting Cloud Volumes Service with Managed AD isn't automated through the web-based user interface. You can connect Cloud Volumes Service with Managed AD by using API calls to Managed AD and Cloud Volumes Service. NetApp can assist you with this process.
Place resources like the Cloud Volumes Services SMB server in the correct
organizational unit (OU) when configuring an AD connection.
Managed AD organizes resources under the organizational unit OU=Cloud by
default.
Using AD sites, as described in Manage DC selection using AD sites, is recommended for all service types. You must provision Managed AD to the respective regions and place the region's domain controllers into a region-specific AD site.
To complete three-way peering by connecting Cloud Volumes Service with Managed AD, you must contact Cloud Customer Care. For more information, see Obtain support for NetApp Cloud Volumes Service.