You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/files/storage-how-to-use-files-windows.md
+24-11Lines changed: 24 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,23 @@ description: Learn to use Azure file shares with Windows and Windows Server. Use
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: how-to
7
-
ms.date: 05/02/2023
7
+
ms.date: 01/05/2024
8
8
ms.author: kendownie
9
9
ms.custom: ai-video-demo
10
10
ai-usage: ai-assisted
11
11
---
12
12
13
13
# Mount SMB Azure file share on Windows
14
-
[Azure Files](storage-files-introduction.md) is Microsoft's easy-to-use cloud file system. Azure file shares can be seamlessly used in Windows and Windows Server. This article discusses the considerations for using an Azure file share with Windows and Windows Server.
14
+
15
+
[Azure Files](storage-files-introduction.md) is Microsoft's easy-to-use cloud file system. Azure file shares can be seamlessly used in Windows and Windows Server. This article shows you how to use an Azure file share with Windows and Windows Server.
16
+
17
+
## Applies to
18
+
19
+
| File share type | SMB | NFS |
20
+
|-|:-:|:-:|
21
+
| Standard file shares (GPv2), LRS/ZRS |||
22
+
| Standard file shares (GPv2), GRS/GZRS |||
Ensure port 445 is open: The SMB protocol requires TCP port 445 to be open. Connections will fail if port 445 is blocked. You can check if your firewall or ISP is blocking port 445 by using the `Test-NetConnection` cmdlet. See [Port 445 is blocked](/troubleshoot/azure/azure-storage/files-troubleshoot-smb-connectivity?toc=/azure/storage/files/toc.json#cause-1-port-445-is-blocked).
60
63
61
64
## Using an Azure file share with Windows
65
+
62
66
To use an Azure file share with Windows, you must either mount it, which means assigning it a drive letter or mount point path, or [access it via its UNC path](#access-an-azure-file-share-via-its-unc-path).
63
67
64
-
This article uses the storage account key to access the file share. A storage account key is an administrator key for a storage account, including administrator permissions to all files and folders within the file share you're accessing, and for all file shares and other storage resources (blobs, queues, tables, etc.) contained within your storage account. If this isn't sufficient for your workload, you can use [Azure File Sync](../file-sync/file-sync-planning.md) or [identity-based authentication over SMB](storage-files-active-directory-overview.md).
68
+
This article uses the storage account key to access the file share. A storage account key is an administrator key for a storage account, including administrator permissions to all files and folders within the file share you're accessing, and for all file shares and other storage resources (blobs, queues, tables, etc.) contained within your storage account. If this isn't sufficient for your workload, you can use [Azure File Sync](../file-sync/file-sync-planning.md) or [identity-based authentication over SMB](storage-files-active-directory-overview.md). Shared access signature (SAS) tokens aren't currently supported for mounting Azure file shares.
65
69
66
70
A common pattern for lifting and shifting line-of-business (LOB) applications that expect an SMB file share to Azure is to use an Azure file share as an alternative for running a dedicated Windows file server in an Azure VM. One important consideration for successfully migrating an LOB application to use an Azure file share is that many applications run under the context of a dedicated service account with limited system permissions rather than the VM's administrative account. Therefore, you must ensure that you mount/save the credentials for the Azure file share from the context of the service account rather than your administrative account.
67
71
68
72
### Mount the Azure file share
69
73
70
-
The Azure portal provides a script that you can use to mount your file share directly to a host. We recommend using this provided script.
74
+
The Azure portal provides a script that you can use to mount your file share directly to a host using the storage account key. We recommend using this provided script.
71
75
72
76
To get this script:
73
77
@@ -92,6 +96,7 @@ To get this script:
92
96
You have now mounted your Azure file share.
93
97
94
98
### Mount the Azure file share with File Explorer
99
+
95
100
> [!Note]
96
101
> Note that the following instructions are shown on Windows 10 and may differ slightly on older releases.
97
102
@@ -116,6 +121,7 @@ You have now mounted your Azure file share.
116
121
1. When you're ready to dismount the Azure file share, right-click on the entry for the share under the **Network locations** in File Explorer and select **Disconnect**.
117
122
118
123
### Access an Azure file share via its UNC path
124
+
119
125
You don't need to mount the Azure file share to a particular drive letter to use it. You can directly access your Azure file share using the [UNC path](/windows/win32/fileio/naming-a-file) by entering the following into File Explorer. Be sure to replace *storageaccountname* with your storage account name and *myfileshare* with your file share name:
If you've taken a share snapshot, either manually or automatically through a script or service like Azure Backup, you can view previous versions of a share, a directory, or a particular file from a file share on Windows. You can take a share snapshot using the [Azure portal](storage-files-quick-create-use-windows.md#create-a-share-snapshot), [Azure PowerShell](/powershell/module/az.storage/new-azrmstorageshare), or [Azure CLI](/cli/azure/storage/share#az-storage-share-snapshot).
133
140
134
141
#### List previous versions
142
+
135
143
Browse to the item or parent item that needs to be restored. Double-click to go to the desired directory. Right-click and select **Properties** from the menu.
136
144
137
145
@@ -145,14 +153,17 @@ You can select **Open** to open a particular snapshot.
Select **Restore** to copy the contents of the entire directory recursively at the share snapshot creation time to the original location.
149
158
150
159
151
160
152
161
## Enable SMB Multichannel
162
+
153
163
Support for SMB Multichannel in Azure Files requires ensuring Windows has all the relevant patches applied to be up-to-date. Several older Windows versions, including Windows Server 2016, Windows 10 version 1607, and Windows 10 version 1507, require additional registry keys to be set for all relevant SMB Multichannel fixes to be applied on fully patched installations. If you're running a version of Windows that is newer than these three versions, no additional action is required.
154
164
155
165
### Windows Server 2016 and Windows 10 version 1607
166
+
156
167
To enable all SMB Multichannel fixes for Windows Server 2016 and Windows 10 version 1607, run the following PowerShell command:
157
168
158
169
```PowerShell
@@ -164,6 +175,7 @@ Set-ItemProperty `
164
175
```
165
176
166
177
### Windows 10 version 1507
178
+
167
179
To enable all SMB Multichannel fixes for Windows 10 version 1507, run the following PowerShell command:
168
180
169
181
```PowerShell
@@ -175,6 +187,7 @@ Set-ItemProperty `
175
187
```
176
188
177
189
## Next steps
190
+
178
191
See these links for more information about Azure Files:
179
192
-[Planning for an Azure Files deployment](storage-files-planning.md)
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments