update metadata for Azure Files includes

khdownie · khdownie · commit 19251ccc6f1f · 2023-08-15T10:22:02.000-07:00
diff --git a/includes/files-nfs-limitations.md b/includes/files-nfs-limitations.md
@@ -3,7 +3,7 @@ title: "include file"
 description: "include file"
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: "include"
 ms.date: 10/18/2022
 ms.author: kendownie
@@ -13,4 +13,3 @@ Currently, only NFS version 4.1 is supported. NFS 4.1 shares are only supported
 
 NFS Azure file shares support most features from the 4.1 protocol specification. Some features such as delegations and callback of all kinds, Kerberos authentication, and encryption-in-transit aren't supported.
 
-The nconnect mount option is currently in preview and isn't recommended for production use.
diff --git a/includes/files-nfs-regional-availability.md b/includes/files-nfs-regional-availability.md
@@ -3,7 +3,7 @@ title: "include file"
 description: "include file"
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: "include"
 ms.date: 06/04/2021
 ms.author: kendownie
diff --git a/includes/storage-file-sync-cost-categories.md b/includes/storage-file-sync-cost-categories.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 04/17/2022
  ms.author: kendownie
diff --git a/includes/storage-files-aad-auth-include.md b/includes/storage-files-aad-auth-include.md
@@ -3,14 +3,14 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 11/07/2022
  ms.author: kendownie
  ms.custom: include file
 ---
 
-Azure Files supports identity-based authentication for Windows file shares over Server Message Block (SMB) using the Kerberos authentication protocol through the following three methods:
+Azure Files supports identity-based authentication for Windows file shares over Server Message Block (SMB) using the Kerberos authentication protocol through the following methods:
 
 - On-premises Active Directory Domain Services (AD DS)
 - Azure Active Directory Domain Services (Azure AD DS)
diff --git a/includes/storage-files-aad-permissions-and-mounting.md b/includes/storage-files-aad-permissions-and-mounting.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 01/24/2023
  ms.author: kendownie
diff --git a/includes/storage-files-clean-up-portal.md b/includes/storage-files-clean-up-portal.md
@@ -2,11 +2,11 @@
  title: storage-files-create-clean-up-portal
  description: Clean up after Azure Files quickstarts and tutorials.
  services: storage
- author: wmgries
- ms.service: azure-storage
+ author: khdownie
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 07/18/2022
- ms.author: wgries
+ ms.author: kendownie
  ms.custom: include file
 ---
 When you're done, delete the resource group. Deleting the resource group deletes the storage account, the Azure file share, and any other resources deployed inside the resource group.
diff --git a/includes/storage-files-condition-headers.md b/includes/storage-files-condition-headers.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 09/04/2019
  ms.author: kendownie
@@ -12,13 +12,13 @@
 
 ## Error ConditionHeadersNotSupported from a Web Application using Azure Files from Browser
 
-The ConditionHeadersNotSupported error occurs when accessing content hosted in Azure Files through an application that makes use of conditional headers, such as a web browser, access fails. The error states that condition headers are not supported.
+The ConditionHeadersNotSupported error occurs when accessing content hosted in Azure Files through an application that makes use of conditional headers, such as a web browser, access fails. The error states that condition headers aren't supported.
 
 ![Azure Files conditional headers error](media/storage-files-condition-headers/conditionalerror.png)
 
 ### Cause
 
-Conditional headers are not yet supported. Applications implementing them will need to request the full file every time the file is accessed.
+Conditional headers aren't currently supported. Applications implementing them will need to request the full file every time the file is accessed.
 
 ### Workaround
 
diff --git a/includes/storage-files-encryption-at-rest.md b/includes/storage-files-encryption-at-rest.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 12/27/2019
  ms.author: kendownie
diff --git a/includes/storage-files-file-share-management-concepts.md b/includes/storage-files-file-share-management-concepts.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 12/26/2019
  ms.author: kendownie
diff --git a/includes/storage-files-migration-configure-sync.md b/includes/storage-files-migration-configure-sync.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 2/20/2020
 ms.author: kendownie
diff --git a/includes/storage-files-migration-deploy-azure-file-sync-agent.md b/includes/storage-files-migration-deploy-azure-file-sync-agent.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 2/20/2020
 ms.author: kendownie
diff --git a/includes/storage-files-migration-deploy-azure-file-sync-storage-sync-service.md b/includes/storage-files-migration-deploy-azure-file-sync-storage-sync-service.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 2/20/2020
 ms.author: kendownie
diff --git a/includes/storage-files-migration-generate-key.md b/includes/storage-files-migration-generate-key.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 2/20/2020
 ms.author: kendownie
diff --git a/includes/storage-files-migration-namespace-mapping.md b/includes/storage-files-migration-namespace-mapping.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 01/19/2023
 ms.author: kendownie
diff --git a/includes/storage-files-migration-provision-azure-file-share.md b/includes/storage-files-migration-provision-azure-file-share.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 2/20/2020
 ms.author: kendownie
@@ -27,7 +27,7 @@ In the previous phase, you determined the appropriate number of shares. In this
 Make sure the region of each of your storage accounts is the same and matches the region of the Storage Sync Service resource you've already deployed.
 
 > [!CAUTION]
-> If you create an Azure file share that has a 100 TiB limit, that share can use only locally redundant storage or zone-redundant storage redundancy options. Consider your storage redundancy needs before using 100-TiB file shares.
+> If you create an Azure file share that has a 100 TiB limit, that share can use only locally redundant storage or zone-redundant storage redundancy options. Consider your storage redundancy needs before using 100 TiB file shares.
 
 Azure file shares are still created with a 5 TiB limit by default. Follow the steps in [Create an Azure file share](../articles/storage/files/storage-how-to-create-file-share.md) to create a large file share.
 
diff --git a/includes/storage-files-migration-robocopy-optimize.md b/includes/storage-files-migration-robocopy-optimize.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 06/22/2022
 ms.author: kendownie
diff --git a/includes/storage-files-migration-robocopy.md b/includes/storage-files-migration-robocopy.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 9/12/2021
 ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-private-cli.md b/includes/storage-files-networking-endpoints-private-cli.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 5/11/2020
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-private-portal.md b/includes/storage-files-networking-endpoints-private-portal.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 08/03/2022
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-private-powershell.md b/includes/storage-files-networking-endpoints-private-powershell.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 5/11/2020
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-public-disable-cli.md b/includes/storage-files-networking-endpoints-public-disable-cli.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 6/2/2020
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-public-disable-portal.md b/includes/storage-files-networking-endpoints-public-disable-portal.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 11/01/2022
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-public-disable-powershell.md b/includes/storage-files-networking-endpoints-public-disable-powershell.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 6/2/2020
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-public-restrict-cli.md b/includes/storage-files-networking-endpoints-public-restrict-cli.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 6/2/2020
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-public-restrict-portal.md b/includes/storage-files-networking-endpoints-public-restrict-portal.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 11/01/2022
  ms.author: kendownie
diff --git a/includes/storage-files-networking-endpoints-public-restrict-powershell.md b/includes/storage-files-networking-endpoints-public-restrict-powershell.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 6/2/2020
  ms.author: kendownie
diff --git a/includes/storage-files-redundancy-overview.md b/includes/storage-files-redundancy-overview.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 06/09/2023
  ms.author: kendownie
diff --git a/includes/storage-files-redundancy-premium-zrs.md b/includes/storage-files-redundancy-premium-zrs.md
@@ -1,9 +1,9 @@
 ---
-author: tamram
-ms.service: azure-storage
+author: khdownie
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 05/12/2022
-ms.author: tamram
+ms.author: kendownie
 ---
 
 ZRS for premium file shares is available for a subset of Azure regions:
diff --git a/includes/storage-files-sync-create-server-endpoint.md b/includes/storage-files-sync-create-server-endpoint.md
@@ -3,7 +3,7 @@ title: include file
 description: include file
 services: storage
 author: khdownie
-ms.service: azure-storage
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 04/26/2023
 ms.author: kendownie
diff --git a/includes/storage-files-tiers-large-file-share-availability.md b/includes/storage-files-tiers-large-file-share-availability.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 06/06/2023
  ms.author: kendownie
diff --git a/includes/storage-files-tiers-overview.md b/includes/storage-files-tiers-overview.md
@@ -3,7 +3,7 @@
  description: include file
  services: storage
  author: khdownie
- ms.service: azure-storage
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 06/02/2022
  ms.author: kendownie
diff --git a/includes/storage-sync-files-agent-update-policy.md b/includes/storage-sync-files-agent-update-policy.md
@@ -1,9 +1,9 @@
 ---
-author: roygara
-ms.service: azure-storage
+author: khdownie
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 5/13/2022
-ms.author: rogarana
+ms.author: kendownie
 ---
 The Azure File Sync agent is updated on a regular basis to add new functionality and to address issues. We recommend updating the Azure File Sync agent as new versions are available.
 
diff --git a/includes/storage-sync-files-bad-connection.md b/includes/storage-sync-files-bad-connection.md
@@ -2,11 +2,11 @@
  title: include file
  description: include file
  services: storage
- author: roygara
- ms.service: azure-storage
+ author: khdownie
+ ms.service: azure-file-storage
  ms.topic: include
  ms.date: 07/08/2018
- ms.author: rogarana
+ ms.author: kendownie
  ms.custom: include file
 ---
 This error can occur whenever the Azure File Sync service is inaccessible from the server. You can troubleshoot this error by working through the following steps:
diff --git a/includes/storage-sync-files-change-detection.md b/includes/storage-sync-files-change-detection.md
@@ -1,9 +1,9 @@
 ---
-author: roygara
-ms.service: azure-storage
+author: khdownie
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 7/20/2022
-ms.author: rogarana
+ms.author: kendownie
 ---
 Changes made to the Azure file share by using the Azure portal or SMB are not immediately detected and replicated like changes to the server endpoint. Azure Files does not yet have change notifications or journaling, so there's no way to automatically initiate a sync session when files are changed. On Windows Server, Azure File Sync uses [Windows USN journaling](/windows/win32/fileio/change-journals) to automatically initiate a sync session when files change.
 
diff --git a/includes/storage-sync-files-remove-server-endpoint.md b/includes/storage-sync-files-remove-server-endpoint.md
@@ -2,11 +2,11 @@
 title: "include file"
 description: "include file"
 services: storage
-author: roygara
-ms.service: azure-storage
+author: khdownie
+ms.service: azure-file-storage
 ms.topic: include
 ms.date: 05/31/2018
-ms.author: rogarana
+ms.author: kendownie
 ms.custom: include file
 ---
-No: removing a server endpoint isn't like rebooting a server! Removing and recreating the server endpoint is almost never an appropriate solution to fixing issues with sync, cloud tiering, or other aspects of Azure File Sync. Removing a server endpoint is a destructive operation. It may result in data loss in the case that tiered files exist outside of the server endpoint namespace. For more information, see [why do tiered files exist outside of the server endpoint namespace](../articles/storage/files/storage-files-faq.md#afs-tiered-files-out-of-endpoint) for more information. Or it may result in inaccessible files for tiered files that exist within the server endpoint namespace. These issues won't resolve when the server endpoint is recreated. Tiered files may exist within your server endpoint namespace even if you never had cloud tiering enabled. That's why we recommend that you don't remove the server endpoint unless you would like to stop using Azure File Sync with this particular folder or have been explicitly instructed to do so by a Microsoft engineer. For more information on remove server endpoints, see [Remove a server endpoint](../articles/storage/file-sync/file-sync-server-endpoint-delete.md).
+No: removing a server endpoint isn't like rebooting a server! Removing and recreating the server endpoint is almost never an appropriate solution to fixing issues with sync, cloud tiering, or other aspects of Azure File Sync. Removing a server endpoint is a destructive operation. It might result in data loss in the case that tiered files exist outside of the server endpoint namespace. For more information, see [why do tiered files exist outside of the server endpoint namespace](../articles/storage/files/storage-files-faq.md#afs-tiered-files-out-of-endpoint) for more information. Or it might result in inaccessible files for tiered files that exist within the server endpoint namespace. These issues won't resolve when the server endpoint is recreated. Tiered files may exist within your server endpoint namespace even if you never had cloud tiering enabled. That's why we recommend that you don't remove the server endpoint unless you would like to stop using Azure File Sync with this particular folder or have been explicitly instructed to do so by a Microsoft engineer. For more information on remove server endpoints, see [Remove a server endpoint](../articles/storage/file-sync/file-sync-server-endpoint-delete.md).
