Skip to content

Commit 7ef740e

Browse files
committed
acrolinx
1 parent b57583a commit 7ef740e

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/azure-netapp-files/understand-guidelines-active-directory-domain-service-site.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ Incorrect or incomplete AD DS site topology or configuration can result in volum
161161
>[!IMPORTANT]
162162
>The AD Site Name field is required to create an Azure NetApp Files AD connection. The AD DS site defined must exist and be properly configured.
163163
164-
Azure NetApp Files uses the AD DS Site to discover the domain controllers and subnets assigned to the AD DS Site defined in the AD Site Name. All domain controllers assigned to the AD DS Site must have good network connectivity from the Azure virtual network interfaces used by ANF and be reachable. AD DS domain controller VMs assigned to the AD DS Site that are used by Azure NetApp Files must be excluded from cost management policies that shut down VMs.
164+
Azure NetApp Files uses the AD DS Site to discover the domain controllers and subnets assigned to the AD DS Site defined in the AD Site Name. All domain controllers assigned to the AD DS Site must have good network connectivity from the Azure virtual network interfaces used by ANF and be reachable. AD DS domain controller VMs assigned to the AD DS Site used by Azure NetApp Files must be excluded from cost management policies that shut down VMs.
165165

166166
If Azure NetApp Files is not able to reach any domain controllers assigned to the AD DS site, the domain controller discovery process will query the AD DS domain for a list of all domain controllers. The list of domain controllers returned from this query is an unordered list. As a result, Azure NetApp Files may try to use domain controllers that are not reachable or well-connected, which can cause volume creation failures, problems with client queries, authentication failures, and failures to modify Azure NetApp Files AD connections.
167167

articles/operational-excellence/relocation-netapp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to relocate an Azure NetApp Files volume to another regio
44
author: anaharris-ms
55
ms.author: anaharris
66
ms.reviewer: anaharris
7-
ms.date: 08/14/2024
7+
ms.date: 09/04/2024
88
ms.service: azure-netapp-files
99
ms.topic: how-to
1010
ms.custom:
@@ -26,7 +26,7 @@ Before you begin the relocation planning stage, review the following prerequisit
2626
- Source and target regions must be paired regions. To see if they're paired, see [Supported cross-region replication pairs](../azure-netapp-files/cross-region-replication-introduction.md?#supported-region-pairs).
2727

2828
- Understand all dependent resources. Some of the resources could be:
29-
- [Microsoft Entra ID](../azure-netapp-files/understand-guidelines-active-directory-domain-service-site)
29+
- [Microsoft Entra ID](../azure-netapp-files/understand-guidelines-active-directory-domain-service-site.md)
3030
- [Virtual Network](./relocation-virtual-network.md)
3131
- Azure DNS
3232
- [Storage services](./relocation-storage-account.md)

0 commit comments

Comments
 (0)