連線至 Managed Service for Microsoft Active Directory
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁說明如何連線至 Managed Service for Microsoft Active Directory。
NetApp Volumes 支援受管理 Microsoft AD。
受管理 Microsoft AD 會使用私人服務存取權連線至消費者專案,與 NetApp Volumes 類似。私人服務存取權使用虛擬私有雲 (VPC) 對等互連,可阻擋 VPC 之間的遞移流量。NetApp Volumes 無法透過消費者 VPC 與 Managed Microsoft AD 通訊,因此您需要網域對等互連來建立這項連線。
如果是 Flex 服務層級,請在政策中使用 169.254.169.254 做為 DNS 伺服器 IP 位址。
如要使用 Standard、Premium 和 Extreme 服務等級,請按照「使用 IP 位址進行 DNS 解析」一文中的操作說明進行。您會在 Active Directory 政策中使用 Cloud DNS 建立的進入點 IP 位址。
機構單位 (OU):Managed Microsoft AD 會預設將所有物件放入 OU=cloud。您必須為環境指定正確的組織單位參數。舉例來說,如果您有名為「engineering.example.com」engineering.example.com的 Windows 網域,要指定的預設機構單位就是 CN=Computers,OU=Cloud,DC=engineering,DC=example,DC=com。
將 Active Directory 政策附加至要使用的儲存空間集區。
如為 Flex 服務等級,請建立使用 Active Directory 的磁碟區,測試 Active Directory 政策連線。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Connect to Managed Service for Microsoft Active Directory\n\nThis page provides instructions for how to connect to Managed Service for Microsoft Active Directory.\n\nNetApp Volumes supports Managed Microsoft AD.\n\nManaged Microsoft AD uses private services access to connect to consumer\nprojects, similar to NetApp Volumes. Private services access\nuses Virtual Private Cloud (VPC) peering, which blocks transitive traffic between\nVPCs. NetApp Volumes can't communicate with\nManaged Microsoft AD through a consumer VPC, so you\nneed a [domain peering](/managed-microsoft-ad/docs/quickstart-domain-peering) to\nestablish this connection.\n\nBefore you begin\n----------------\n\nMake sure you meet the prerequisites mentioned in\n[Managed Microsoft AD - Before you begin](/managed-microsoft-ad/docs/quickstart-domain-peering#before-you-begin).\n\nEstablish a domain peering\n--------------------------\n\nUse the following instructions to establish a domain peering:\n\n1. Identify the project name of the NetApp Volumes tenant project\n that owns your NetApp Volumes resources:\n\n ```\n gcloud compute networks peerings list --project=project_owning_NetAppVolumes --flatten=peerings --filter=\"peerings.name=sn-netapp-prod\"\n ```\n\n The `PEER_PROJECT` parameter shows the name of the NetApp Volumes\n tenant project. The `PEER_NETWORK` parameter shows the tenant project VPC\n name, which should be *netapp-prod-network*.\n2. Follow the instructions in\n [Configure domain peering](/managed-microsoft-ad/docs/quickstart-domain-peering#configure_domain_peering)\n to create a domain peering from Managed Microsoft AD to\n NetApp Volumes, using the tenant project ID and network you\n identified from the previous step.\n\n Note that you can only establish the peering from the domain resource project\n to the NetApp Volumes tenant project. The reverse peering\n from the VPC resource project\n (NetApp Volumes tenant project) to the domain resource project\n requires a support case with\n [Google Cloud Customer Care](https://cloud.google.com/support-hub/).\n3. Open a support case with\n [Google Cloud Customer Care](https://cloud.google.com/support-hub/) to establish\n the reverse peering from NetApp Volumes to Managed Microsoft AD.\n Provide the output of the following command to Google Cloud Customer Care to\n identify which peering to accept.\n\n ```\n gcloud active-directory peerings list --project=project_owning_ManagedAD\n ```\n4. After Google Cloud Customer Care establishes the two-way peering, the status of\n your peering shows **CONNECTED**. Verify the peering status:\n\n ```\n gcloud active-directory peerings list --project=project_owning_ManagedAD\n ```\n5. [Create an Active Directory policy](/netapp/volumes/docs/configure-and-use/active-directory/create-ad-policy)\n in the same region where you plan to create volumes using Managed Microsoft AD.\n You need to specify the following parameters:\n\n - **DNS servers** IP address:\n\n - For the Flex service level, use `169.254.169.254` for the DNS servers IP\n address in the policy.\n\n - For Standard, Premium, and Extreme service levels, follow the\n instructions in [Using IP address for DNS resolution](/managed-microsoft-ad/docs/connect-to-active-directory-domain#using_ip_address_for_dns_resolution).\n You will use the entry point IP addresses created by Cloud DNS in\n your Active Directory policy.\n\n - **Organizational Unit** (OU): Managed Microsoft AD puts all objects\n into `OU=cloud` by [default](/managed-microsoft-ad/docs/objects). You need\n to specify a correct organizational unit parameter for your environment.\n For example, if you have a Windows domain called\n *engineering.example.com* , the default organizational unit to\n specify would be `CN=Computers,OU=Cloud,DC=engineering,DC=example,DC=com`.\n\n6. Attach the Active Directory policy to the storage pool to be used.\n\n For the Flex service level, test Active Directory policy connection by\n creating a volume which uses the Active Directory.\n\n For Standard, Premium, and Extreme service levels, test\n [Active Directory policy connection](/netapp/volumes/docs/configure-and-use/active-directory/test-ad-policy-connection)\n before creating a volume.\n\nWhat's next\n-----------\n\n[Manage customer-managed encryption key policies](/netapp/volumes/docs/configure-and-use/cmek/cmek-overview)."]]