Merge pull request #312581 from msangapu-msft/patch-26

Fix NFS port number in troubleshooting section

Author: prmerger-automator[bot]

articles/app-service/includes/configure-azure-storage/azure-storage-linux-container-pivot.md

@@ -268,7 +268,7 @@ You can customize health‑check behavior by using the following app settings.
 ### Troubleshooting
 
 - The mount directory in the custom container should be empty. Any content stored at this path is deleted when the Azure Storage is mounted, if you specify a directory under */home*, for example. If you migrate files for an existing app, make a backup of the app and its content before you begin.
-- When mounting an NFS share, you need to ensure that Secure Transfer Required is disabled on the storage account. App Service doesn't support mounting NFS shares when this setting is enabled. It uses port 2409 and virtual network integration and private endpoints as the security measure.
+- When mounting an NFS share, you need to ensure that Secure Transfer Required is disabled on the storage account. App Service doesn't support mounting NFS shares when this setting is enabled. It uses port 2049 and virtual network integration and private endpoints as the security measure.
 - If you delete an Azure Storage account, container, or share, remove the corresponding storage mount configuration in the app to avoid possible error scenarios.
 - Don't use storage mounts for local databases, such as SQLite, or for any other applications and components that rely on file handles and locks.
 - Ensure the following ports are open when using virtual network integration: Azure Files: 80 and 445. Azure Blobs: 80 and 443.