Skip to content

Commit d02b5ac

Browse files
authored
Merge pull request #97982 from benperk/patch-4
Move Limitation from "code-windows" tab
2 parents 424a3b1 + aa0fdbe commit d02b5ac

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/app-service/configure-connect-to-azure-storage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,6 @@ The following features are supported for Linux containers:
106106
- Mapping `/mounts`, `mounts/foo/bar`, `/`, and `/mounts/foo.bar/` to custom-mounted storage is not supported (you can only use /mounts/pathname for mounting custom storage to your web app.)
107107
- Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
108108
- Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts.
109-
- Only Azure Files [SMB](../storage/files/files-smb-protocol.md) are supported. Azure Files [NFS](../storage/files/files-nfs-protocol.md) is not currently supported for Linux App Services.
110109

111110
::: zone-end
112111

@@ -118,7 +117,7 @@ The following features are supported for Linux containers:
118117
- FTP/FTPS access to mounted storage not supported (use [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/)).
119118
- Mapping `[C-Z]:\`, `[C-Z]:\home`, `/`, and `/home` to custom-mounted storage is not supported.
120119
- Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
121-
- Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts.
120+
- Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts.
122121

123122
> [!NOTE]
124123
> Ensure ports 80 and 445 are open when using Azure Files with VNET integration.
@@ -134,6 +133,7 @@ The following features are supported for Linux containers:
134133
- Don't map the custom storage mount to `/tmp` or its subdirectories as this may cause timeout during app startup.
135134
- Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
136135
- Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts.
136+
- Only Azure Files [SMB](../storage/files/files-smb-protocol.md) are supported. Azure Files [NFS](../storage/files/files-nfs-protocol.md) is not currently supported for Linux App Services.
137137

138138
> [!NOTE]
139139
> When VNET integration is used, ensure the following ports are open:
@@ -343,4 +343,4 @@ To validate that the Azure Storage is mounted successfully for the app:
343343
- [Configure a custom container](configure-custom-container.md?pivots=platform-linux).
344344
- [Video: How to mount Azure Storage as a local share](https://www.youtube.com/watch?v=OJkvpWYr57Y).
345345

346-
::: zone-end
346+
::: zone-end

0 commit comments

Comments
 (0)