move AD topic in sidebar

Author: b-ahibbard

articles/azure-netapp-files/TOC.yml

@@ -41,6 +41,8 @@
             href: nfs-access-control-lists.md
       - name: Understand dual-protocol security style and permission behaviors
         href: dual-protocol-permission-behaviors.md
+      - name: Understand guidelines for Active Directory Domain Services
+        href: understand-guidelines-active-directory-domain-service-site.md
       - name: Understand the use of LDAP
         href: lightweight-directory-access-protocol.md
       - name: Understand NFS group memberships and supplemental groups
@@ -201,8 +203,6 @@
       href: request-region-access.md
   - name: Manage Active Directory 
     items:
-    - name: Understand guidelines for Active Directory Domain Services
-      href: understand-guidelines-active-directory-domain-service-site.md
     - name: Create and manage Active Directory connections
       href: create-active-directory-connections.md
     - name: Modify Active Directory connections

articles/azure-netapp-files/create-active-directory-connections.md

@@ -19,7 +19,8 @@ Several features of Azure NetApp Files require that you have an Active Directory
 
 > [!IMPORTANT]
 > You must follow guidelines described in [Understand guidelines for Active Directory Domain Services site design and planning for Azure NetApp Files](understand-guidelines-active-directory-domain-service-site.md) for Active Directory Domain Services (AD DS) or Microsoft Entra Domain Services used with Azure NetApp Files. 
-> In addition, before creating the AD connection, review [Modify Active Directory connections for Azure NetApp Files](modify-active-directory-connections.md) to understand the impact of making changes to the AD connection configuration options after the AD connection has been created. Changes to the AD connection configuration options are disruptive to client access and some options cannot be changed at all.
+>
+> Before creating the AD connection, review [Modify Active Directory connections for Azure NetApp Files](modify-active-directory-connections.md) to understand the impact of making changes to the AD connection configuration options after the AD connection has been created. Changes to the AD connection configuration options are disruptive to client access and some options cannot be changed at all.
 
 * An Azure NetApp Files account must be created in the region where the Azure NetApp Files volumes are deployed.
 

articles/azure-netapp-files/modify-active-directory-connections.md

@@ -13,6 +13,8 @@ ms.author: anfdocs
 
 Once you've [created an Active Directory connection](create-active-directory-connections.md) in Azure NetApp Files, you can modify it. When you're modifying an Active Directory connection, not all configurations are modifiable.
 
+For more information, see [Understand guidelines for Active Directory Domain Services site design and planning for Azure NetApp Files](understand-guidelines-active-directory-domain-service-site.md).
+
 ## Modify Active Directory connections
 
 1. Select **Active Directory connections**. Then, select **Edit** to edit an existing AD connection. 

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

@@ -34,7 +34,6 @@ Azure NetApp Files supports identity-based authentication over SMB through the f
 * **Microsoft Entra Kerberos for hybrid identities**: Using Microsoft Entra ID for authenticating [hybrid user identities](../active-directory/hybrid/whatis-hybrid-identity.md) allows Microsoft Entra users to access Azure NetApp Files file shares using Kerberos authentication. This means your end users can access Azure NetApp Files file shares without requiring a line-of-sight to domain controllers from Microsoft Entra hybrid joined and Microsoft Entra joined Windows or Linux virtual machines. *Cloud-only identities aren't currently supported.*
 * **AD Kerberos authentication for Linux clients**: Linux clients can use Kerberos authentication over SMB for Azure NetApp Files using AD DS.
 
-
 ### <a name="network-requirements"></a>Network requirements 
 
 Azure NetApp Files SMB, dual-protocol, and Kerberos NFSv4.1 volumes require reliable and low-latency network connectivity (less than 10 ms RTT) to AD DS domain controllers. Poor network connectivity or high network latency between Azure NetApp Files and AD DS domain controllers can cause client access interruptions or client timeouts.