Merge pull request #312972 from khdownie/kendownie031026-2

prmerger-automator[bot] · web-flow · commit 8fbea102b159 · 2026-03-11T00:01:43.000Z
standardize applies to lines part one
diff --git a/articles/storage/files/authorize-data-operations-portal.md b/articles/storage/files/authorize-data-operations-portal.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Choose how to authorize access to file data in the Azure portal
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 When you access file data by using the [Azure portal](https://portal.azure.com?azure-portal=true), the portal makes requests to the Azure Files service behind the scenes. You can authorize these requests by using either your Microsoft Entra account (preferred) or the storage account access key (less secure). The portal shows which method you're using and enables you to switch between the two methods if you have the appropriate permissions. By default, the portal uses whichever method you're already using to authorize all file shares, but you can change this setting for individual file share operations.
 
diff --git a/articles/storage/files/authorize-oauth-rest.md b/articles/storage/files/authorize-oauth-rest.md
@@ -15,7 +15,7 @@ ms.custom:
 
 # Access Azure file shares using Microsoft Entra ID with Azure Files OAuth over REST
 
-:heavy_check_mark: **Applies to:** Classic file shares created with the Microsoft.Storage resource provider
+:heavy_check_mark: **Applies to:** Classic SMB and NFS file shares created with the Microsoft.Storage resource provider
 
 :heavy_multiplication_x: **Doesn't apply to:** File shares created with the Microsoft.FileShares resource provider (preview)
 
diff --git a/articles/storage/files/change-identity-source.md b/articles/storage/files/change-identity-source.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Change the identity source for Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Azure Files supports only one identity source per storage account for identity-based authentication over SMB. If you want to switch from one identity source to another, you must first disable the current identity source and then enable the new one.
 
diff --git a/articles/storage/files/create-classic-file-share.md b/articles/storage/files/create-classic-file-share.md
@@ -13,7 +13,7 @@ ms.custom: devx-track-azurecli, references_regions, devx-track-azurepowershell
 
 # Create an Azure classic file share
 
-:heavy_check_mark: **Applies to:** SMB and NFS Azure classic file shares (Microsoft.Storage)
+:heavy_check_mark: **Applies to:** Classic SMB and NFS file shares created with the Microsoft.Storage resource provider
 
 :heavy_multiplication_x: **Doesn't apply to:** File shares created with the Microsoft.FileShares resource provider (preview)
 
diff --git a/articles/storage/files/files-managed-identities.md b/articles/storage/files/files-managed-identities.md
@@ -13,7 +13,7 @@ ms.custom:
 
 # Access SMB Azure file shares by using managed identities with Microsoft Entra ID (preview)
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 This article explains how you can use [managed identities](/entra/identity/managed-identities-azure-resources/overview) to allow Windows and Linux virtual machines (VMs) to access SMB Azure file shares by using identity-based authentication with Microsoft Entra ID (preview).
 
diff --git a/articles/storage/files/files-nfs-protocol.md b/articles/storage/files/files-nfs-protocol.md
@@ -12,7 +12,7 @@ ms.custom: references_regions
 
 # NFS Azure file shares
 
-**Applies to:** :heavy_check_mark: NFS Azure file shares
+**Applies to:** :heavy_check_mark: NFS file shares
 
 Azure Files offers two industry-standard file system protocols for mounting Azure file shares: the [Server Message Block (SMB)](/windows/win32/fileio/microsoft-smb-protocol-and-cifs-protocol-overview) protocol and the [Network File System (NFS)](https://en.wikipedia.org/wiki/Network_File_System) protocol, allowing you to pick the protocol that is the best fit for your workload. Azure file shares don't support accessing an individual Azure file share with both the SMB and NFS protocols, although you can create SMB and NFS file shares within the same FileStorage storage account. Azure Files offers enterprise-grade file shares that can scale up to meet your storage needs and can be accessed concurrently by thousands of clients.
 
diff --git a/articles/storage/files/files-smb-protocol.md b/articles/storage/files/files-smb-protocol.md
@@ -12,7 +12,7 @@ ms.custom: devx-track-azurepowershell
 
 # SMB Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Azure Files offers two industry-standard protocols for mounting Azure file share: the [Server Message Block (SMB)](/windows/win32/fileio/microsoft-smb-protocol-and-cifs-protocol-overview) protocol and the [Network File System (NFS)](https://en.wikipedia.org/wiki/Network_File_System) protocol. Azure Files enables you to pick the file system protocol that is the best fit for your workload. Azure file shares don't support accessing an individual Azure file share with both the SMB and NFS protocols, although you can create SMB and NFS file shares within the same storage account. For all file shares, Azure Files offers enterprise-grade file shares that can scale up to meet your storage needs and can be accessed concurrently by thousands of clients.
 
diff --git a/articles/storage/files/migrate-files-storage-mover.md b/articles/storage/files/migrate-files-storage-mover.md
@@ -11,7 +11,7 @@ author: khdownie
 
 # Use Azure Storage Mover to migrate to Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB and NFS Azure file shares
+**Applies to:** :heavy_check_mark: Classic SMB and NFS file shares created with the Microsoft.Storage resource provider
 
 This migration guide describes how to migrate on-premises files to Azure file shares with full fidelity using [Azure Storage Mover](../../storage-mover/service-overview.md), a fully managed migration service. You can use Storage Mover to migrate from SMB or NFS source shares, including Windows Server, Linux, or NAS. Storage Mover uses the FileREST API to move the data.
 
diff --git a/articles/storage/files/modify-file-share.md b/articles/storage/files/modify-file-share.md
@@ -13,7 +13,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell
 
 # How to modify an Azure file share
 
-:heavy_check_mark: **Applies to:** SMB and NFS Azure classic file shares (Microsoft.Storage)
+:heavy_check_mark: **Applies to:** Classic SMB and NFS file shares created with the Microsoft.Storage resource provider
 
 :heavy_check_mark: **Applies to:** File shares created with the Microsoft.FileShares resource provider (preview)
 
diff --git a/articles/storage/files/storage-files-active-directory-overview.md b/articles/storage/files/storage-files-active-directory-overview.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Overview of Azure Files identity-based authentication for SMB access
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 This article explains how you can use identity-based authentication, either on-premises or in Azure, to enable identity-based access to Azure Files over Server Message Block (SMB) protocol. Just like Windows file servers, you can grant permissions to an identity at the share, directory, or file level. There's no extra service charge to enable identity-based authentication on your storage account.
 
diff --git a/articles/storage/files/storage-files-authorization-overview.md b/articles/storage/files/storage-files-authorization-overview.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Overview of Azure Files authorization and access control
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Regardless of which identity source you choose for [identity-based authentication](storage-files-active-directory-overview.md) on your storage account, you need to configure authorization and access control. Azure Files enforces authorization on user access at both the share level and the directory/file level.
 
diff --git a/articles/storage/files/storage-files-configure-p2s-vpn-windows.md b/articles/storage/files/storage-files-configure-p2s-vpn-windows.md
@@ -1,6 +1,6 @@
 ---
 title: Configure a Point-to-Site VPN on Windows for Azure Files
-description: How to configure a point-to-site (P2S) VPN on Windows for use with SMB Azure file shares to mount your Azure file shares over SMB from outside of Azure without opening up port 445.
+description: How to configure a point-to-site VPN on Windows for use with SMB Azure file shares to mount your Azure file shares over SMB from outside of Azure without opening up port 445.
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: how-to
@@ -12,11 +12,11 @@ ms.custom:
 # Customer intent: "As an IT administrator, I want to configure a point-to-site VPN on Windows for Azure file shares, so that I can securely access and mount file shares from on-premises without compromising network security."
 ---
 
-# Configure a point-to-site (P2S) VPN on Windows for use with Azure Files
+# Configure a point-to-site VPN on Windows for use with Azure Files
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
-You can use a point-to-site (P2S) VPN connection to mount your Azure file shares over SMB from outside of Azure, without opening up port 445. A point-to-site VPN connection is a VPN connection between Azure and an individual client. To use a P2S VPN connection with Azure Files, you must configure a VPN connection for each client that wants to connect. If you have many clients that need to connect to your Azure file shares from your on-premises network, you can use a site-to-site (S2S) VPN connection instead of a point-to-site connection for each client. To learn more, see [Configure a site-to-site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md).
+You can use a point-to-site VPN connection to mount your Azure file shares over SMB from outside of Azure, without opening up port 445. A point-to-site VPN connection is a VPN connection between Azure and an individual client. To use a point-to-site VPN connection with Azure Files, you must configure a VPN connection for each client that wants to connect. If you have many clients that need to connect to your Azure file shares from your on-premises network, you can use a site-to-site VPN connection instead of a point-to-site connection for each client. To learn more, see [Configure a site-to-site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md).
 
 We strongly recommend that you read [Networking considerations for direct Azure file share access](storage-files-networking-overview.md) before continuing with this how-to article for a complete discussion of the networking options available for Azure Files.
 
@@ -567,7 +567,7 @@ Add-AzVpnClientRootCertificate @vpnClientRootCertParams
 
 ## See also
 
-- [Configure server settings for P2S VPN Gateway connections](../../vpn-gateway/point-to-site-certificate-gateway.md)
+- [Configure server settings for point-to-site VPN Gateway connections](../../vpn-gateway/point-to-site-certificate-gateway.md)
 - [Networking considerations for direct Azure file share access](storage-files-networking-overview.md)
-- [Configure a point-to-site (P2S) VPN on Linux for use with Azure Files](storage-files-configure-p2s-vpn-linux.md)
-- [Configure a site-to-site (S2S) VPN for use with Azure Files](storage-files-configure-s2s-vpn.md)
+- [Configure a point-to-site VPN on Linux for use with Azure Files](storage-files-configure-p2s-vpn-linux.md)
+- [Configure a site-to-site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md)
diff --git a/articles/storage/files/storage-files-how-to-mount-nfs-shares.md b/articles/storage/files/storage-files-how-to-mount-nfs-shares.md
@@ -14,7 +14,6 @@ ms.author: kendownie
 
 :heavy_check_mark: **Applies to:** Classic NFS file shares created with the Microsoft.Storage resource provider
 
-
 :heavy_check_mark: **Applies to:** File shares created with the Microsoft.FileShares resource provider (preview)
 
 Azure file shares can be mounted in Linux distributions using either the Server Message Block (SMB) protocol or the Network File System (NFS) protocol. This article is focused on mounting with NFS. For details on mounting SMB file shares, see [Use Azure Files with Linux](storage-how-to-use-files-linux.md). For details on each of the available protocols, see [Azure file share protocols](storage-files-planning.md#available-protocols).
diff --git a/articles/storage/files/storage-files-identity-ad-ds-enable.md b/articles/storage/files/storage-files-identity-ad-ds-enable.md
@@ -12,7 +12,7 @@ ms.custom: devx-track-azurepowershell
 
 # Enable Active Directory Domain Services authentication for Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 This article explains how to enable Active Directory Domain Services (AD DS) authentication on your storage account so you can use on-premises Active Directory (AD) credentials to authenticate to Azure file shares.
 
diff --git a/articles/storage/files/storage-files-identity-ad-ds-overview.md b/articles/storage/files/storage-files-identity-ad-ds-overview.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Overview: On-premises Active Directory Domain Services authentication over SMB for Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 [!INCLUDE [storage-files-aad-auth-include](../../../includes/storage-files-aad-auth-include.md)]
 
diff --git a/articles/storage/files/storage-files-identity-ad-ds-update-password.md b/articles/storage/files/storage-files-identity-ad-ds-update-password.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Update the password for your storage account identity in AD DS
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 When you domain join your storage account in your Active Directory Domain Services (AD DS), you create an AD principal, either a computer account or service account, with a password. The password for the AD principal is one of the Kerberos keys for the storage account. Depending on the password policy of the organizational unit for the AD principal, you must periodically rotate the password to avoid authentication problems. If you don't change the password before it expires, you lose Kerberos authentication to your Azure file shares. Some AD environments also delete AD principals with expired passwords by using an automated cleanup script.
 
diff --git a/articles/storage/files/storage-files-identity-assign-share-level-permissions.md b/articles/storage/files/storage-files-identity-assign-share-level-permissions.md
@@ -13,7 +13,7 @@ ms.devlang: azurecli
 
 # Assign share-level permissions for Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 After you enable an identity source for your storage account, you must configure share-level permissions to access your file share. You can assign share-level permissions in two ways: to [specific Microsoft Entra users or groups](#share-level-permissions-for-specific-azure-ad-users-or-groups), or to all authenticated identities as a [default share-level permission](#share-level-permissions-for-all-authenticated-identities).
 
diff --git a/articles/storage/files/storage-files-identity-auth-domain-services-enable.md b/articles/storage/files/storage-files-identity-auth-domain-services-enable.md
@@ -12,7 +12,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell
 
 # Enable Microsoft Entra Domain Services authentication on Azure Files
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 [!INCLUDE [storage-files-aad-auth-include](../../../includes/storage-files-aad-auth-include.md)]
 
diff --git a/articles/storage/files/storage-files-identity-auth-hybrid-cloud-trust.md b/articles/storage/files/storage-files-identity-auth-hybrid-cloud-trust.md
@@ -12,7 +12,7 @@ ms.custom: sfi-ga-nochange
 
 # Configure a cloud trust between on-premises AD DS and Microsoft Entra ID for accessing Azure Files
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Many organizations want to use identity-based authentication for SMB Azure file shares in environments that span both on-premises Active Directory Domain Services (AD DS) and Microsoft Entra ID ([formerly Azure Active Directory](/entra/fundamentals/new-name)), but don't meet the necessary [operating system or domain prerequisites](storage-files-identity-auth-hybrid-identities-enable.md#operating-system-and-domain-prerequisites).
 
diff --git a/articles/storage/files/storage-files-identity-auth-hybrid-identities-enable.md b/articles/storage/files/storage-files-identity-auth-hybrid-identities-enable.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Enable Microsoft Entra Kerberos authentication for hybrid and cloud-only identities (preview) on Azure Files
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 This article explains how to enable and configure Microsoft Entra ID (formerly Azure AD) for authenticating [hybrid](/entra/identity/hybrid/whatis-hybrid-identity) or cloud-only identities (preview).
 
diff --git a/articles/storage/files/storage-files-identity-auth-linux-kerberos-enable.md b/articles/storage/files/storage-files-identity-auth-linux-kerberos-enable.md
@@ -12,7 +12,7 @@ ms.author: kendownie
 
 # Enable Active Directory authentication over SMB for Linux clients accessing Azure Files
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 For more information on supported options and considerations, see [Overview of Azure Files identity-based authentication options for SMB access](storage-files-active-directory-overview.md).
 
diff --git a/articles/storage/files/storage-files-identity-configure-file-level-permissions.md b/articles/storage/files/storage-files-identity-configure-file-level-permissions.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Configure directory and file-level permissions for Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Before you can configure directory and file-level permissions, you must [assign share-level permissions to an identity](storage-files-identity-assign-share-level-permissions.md) with Azure role-based access control (RBAC). After the share-level permissions propagate, you can configure Windows access control lists (ACLs), also known as NTFS permissions, at the root, directory, or file level.
 
diff --git a/articles/storage/files/storage-files-identity-multiple-forests.md b/articles/storage/files/storage-files-identity-multiple-forests.md
@@ -12,7 +12,7 @@ ms.custom: sfi-image-nochange
 
 # Use Azure Files with multiple Active Directory forests
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Many organizations want to use identity-based authentication for SMB Azure file shares in environments that have multiple on-premises Active Directory Domain Services (AD DS) forests. This is a common IT scenario, especially following mergers and acquisitions, where the acquired company's AD forests are isolated from the parent company's AD forests. This article explains how forest trust relationships work and provides step-by-step instructions for multi-forest setup and validation.
 
diff --git a/articles/storage/files/storage-files-migration-robocopy.md b/articles/storage/files/storage-files-migration-robocopy.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Use RoboCopy to migrate to Azure file shares
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 This migration article describes the use of RoboCopy to move or migrate files to an SMB Azure file share. RoboCopy is a trusted and well-known file copy utility with a feature set that makes it well suited for migrations. It uses the SMB protocol, which makes it broadly applicable to any source and target combination that supports SMB.
 
diff --git a/articles/storage/files/storage-how-to-use-files-linux.md b/articles/storage/files/storage-how-to-use-files-linux.md
@@ -15,7 +15,7 @@ ms.custom:
 
 # Mount SMB Azure file shares on Linux clients
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 Azure file shares can be mounted in Linux distributions using the [SMB kernel client](https://wiki.samba.org/index.php/LinuxCIFS).
 
diff --git a/articles/storage/files/storage-how-to-use-files-mac.md b/articles/storage/files/storage-how-to-use-files-mac.md
@@ -11,7 +11,7 @@ ms.author: kendownie
 
 # Mount an Azure file share on macOS
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 [Azure Files](storage-files-introduction.md) is Microsoft's easy-to-use cloud file system. Azure file shares can be mounted with the industry standard SMB 3 protocol by macOS High Sierra 10.13+.
 
diff --git a/articles/storage/files/storage-how-to-use-files-windows.md b/articles/storage/files/storage-how-to-use-files-windows.md
@@ -13,7 +13,7 @@ ms.custom:
 
 # Mount SMB Azure file share on Windows
 
-**Applies to:** :heavy_check_mark: SMB Azure file shares
+**Applies to:** :heavy_check_mark: SMB file shares
 
 [Azure Files](storage-files-introduction.md) is Microsoft's easy-to-use cloud file system. This article shows you how to mount an SMB Azure file share on Windows and Windows Server.
 
diff --git a/articles/storage/files/windows-server-to-azure-files.md b/articles/storage/files/windows-server-to-azure-files.md
