Merge pull request #208971 from b-ahibbard/anf-jira-updates-24aug

new considerations: security faq & standard networking

Author: prmerger-automator[bot]

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 08/11/2022
+ms.date: 08/22/2022
 ms.author: ramakk
 ---
 # Guidelines for Azure NetApp Files network planning
@@ -33,7 +33,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
 
 ### Supported regions 
 
-Azure NetApp Files standard network features are supported for the following regions:
+Azure NetApp Files Standard network features are supported for the following regions:
 
 *   Australia Central
 *   Australia Central 2
@@ -80,7 +80,10 @@ The following table describes what’s supported for each network features confi
 |     Dual stack (IPv4 and   IPv6) VNet    |     No <br> (IPv4 only   supported)    |     No <br> (IPv4 only supported)    |
 
 > [!IMPORTANT]
-> Upgrade from basic to standard network feature is not currently supported.
+> Upgrade from Basic to Standard network feature is not currently supported.
+
+> [!IMPORTANT]
+> Conversion between Basic and Standard networking features is not currently supported.
 
 ### Supported network topologies
 
@@ -158,7 +161,7 @@ The following diagram illustrates an Azure-native environment with cross-region
 
 :::image type="content" source="../media/azure-netapp-files/azure-native-cross-region-peering.png" alt-text="Diagram depicting Azure native environment setup with cross-region VNet peering." lightbox="../media/azure-netapp-files/azure-native-cross-region-peering.png":::
 
-With the standard network feature, VMs are able to connect to volumes in another region via global or cross-region VNet peering. The above diagram adds a second region to the configuration in the [local VNet peering section](#vnet-peering). For VNet 4 in this diagram, an Azure NetApp Files volume is created in a delegated subnet and can be mounted on VM5 in the application subnet.
+With Standard network features, VMs are able to connect to volumes in another region via global or cross-region VNet peering. The above diagram adds a second region to the configuration in the [local VNet peering section](#vnet-peering). For VNet 4 in this diagram, an Azure NetApp Files volume is created in a delegated subnet and can be mounted on VM5 in the application subnet.
 
 In the diagram, VM2 in Region 1 can connect to Volume 3 in Region 2. VM5 in Region 2 can connect to Volume 2 in Region 1 via VNet peering between Region 1 and Region 2.
 

articles/azure-netapp-files/faq-smb.md

@@ -6,7 +6,7 @@ ms.workload: storage
 ms.topic: conceptual
 author: b-hchen
 ms.author: anfdocs
-ms.date: 04/21/2022
+ms.date: 08/24/2022
 ---
 # SMB FAQs for Azure NetApp Files
 
@@ -30,7 +30,7 @@ However, you can map multiple NetApp accounts that are under the same subscripti
 
 Both [Azure Active Directory (AD) Domain Services](../active-directory-domain-services/overview.md) and [Active Directory Domain Services (AD DS)](/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview) are supported. You can use existing Active Directory domain controllers with Azure NetApp Files. Domain controllers can reside in Azure as virtual machines, or on premises via ExpressRoute or S2S VPN. Azure NetApp Files doesn't support AD join for [Azure Active Directory](https://azure.microsoft.com/resources/videos/azure-active-directory-overview/) at this time.
 
-If you are using Azure NetApp Files with Azure Active Directory Domain Services, the organizational unit path is `OU=AADDC Computers` when you configure Active Directory for your NetApp account.
+If you're using Azure NetApp Files with Azure Active Directory Domain Services, the organizational unit path is `OU=AADDC Computers` when you configure Active Directory for your NetApp account.
 
 ## What versions of Windows Server Active Directory are supported?
 
@@ -75,6 +75,10 @@ Azure NetApp Files supports [`CHANGE_NOTIFY` response](/openspecs/windows_protoc
 
 Azure NetApp Files also supports [`LOCK` response](/openspecs/windows_protocols/ms-smb2/e215700a-102c-450a-a598-7ec2a99cd82c). This response is for the client’s request that comes in the form of a [`LOCK` request](/openspecs/windows_protocols/ms-smb2/6178b960-48b6-4999-b589-669f88e9017d).  
 
+## What network authentication methods are supported for SMB volumes in Azure NetApp Files?
+
+NTLMv2 and Kerberos network authentication methods are supported with SMB volumes in Azure NetApp Files. NTLMv1 and LanManager are disabled and are not supported.
+
 ## What is the password rotation policy for the Active Directory machine account for SMB volumes?
 
 The Azure NetApp Files service has a policy that automatically updates the password on the Active Directory machine account that is created for SMB volumes. This policy has the following properties: