Tutorial: Extend Windows file servers with Azure File Sync
The article demonstrates the basic steps for extending the storage capacity of a Windows server by using Azure File Sync. Although the tutorial features Windows Server as an Azure virtual machine (VM), you would typically do this process for your on-premises servers. You can find instructions for deploying Azure File Sync in your own environment in the Deploy Azure File Sync article.
- Deploy the Storage Sync Service
- Prepare Windows Server to use with Azure File Sync
- Install the Azure File Sync agent
- Register Windows Server with the Storage Sync Service
- Create a sync group and a cloud endpoint
- Create a server endpoint
If you don't have an Azure subscription, create a free account before you begin.
This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. For Az module installation instructions, see Install Azure PowerShell.
Sign in to Azure
Sign in to the Azure portal.
Prepare your environment
For this tutorial, you need to do the following before you can deploy Azure File Sync:
- Create an Azure storage account and file share
- Set up a Windows Server 2016 Datacenter VM
- Prepare the Windows Server VM for Azure File Sync
Create a folder and .txt file
On your local computer, create a new folder named FilesToSync and add a text file named mytestdoc.txt. You'll upload that file to the file share later in this tutorial.
Create a storage account
To create a general-purpose v2 storage account in the Azure portal, follow these steps:
On the Azure portal menu, select All services. In the list of resources, type Storage Accounts. As you begin typing, the list filters based on your input. Select Storage Accounts.
On the Storage Accounts window that appears, choose Add.
Select the subscription in which to create the storage account.
Under the Resource group field, select Create new. Enter a name for your new resource group, as shown in the following image.
Next, enter a name for your storage account. The name you choose must be unique across Azure. The name also must be between 3 and 24 characters in length, and can include numbers and lowercase letters only.
Select a location for your storage account, or use the default location.
Leave these fields set to their default values:
Field Value Deployment model Resource Manager Performance Standard Account kind StorageV2 (general-purpose v2) Replication Read-access geo-redundant storage (RA-GRS) Access tier Hot
If you plan to use Azure Data Lake Storage, choose the Advanced tab, and then set Hierarchical namespace to Enabled.
Select Review + Create to review your storage account settings and create the account.
For more information about types of storage accounts and other storage account settings, see Azure storage account overview. For more information on resource groups, see Azure Resource Manager overview.
Create a file share
After you deploy an Azure storage account, you create a file share.
In the Azure portal, select Go to resource.
Select Files from the storage account pane.
Select + File Share.
Name the new file share afsfileshare. Enter "1" for the Quota, and then select Create. The quota can be a maximum of 5 TiB, but you only need 1 GB for this tutorial.
Select the new file share. On the file share location, select Upload.
Browse to the FilesToSync folder where you created your .txt file, select mytestdoc.txt and select Upload.
At this point, you've created a storage account and a file share with one file in it. Next, you deploy an Azure VM with Windows Server 2016 Datacenter to represent the on-premises server in this tutorial.
Deploy a VM and attach a data disk
Go to the Azure portal and expand the menu on the left. Choose Create a resource in the upper left-hand corner.
In the search box above the list of Azure Marketplace resources, search for Windows Server 2016 Datacenter and select it in the results. Choose Create.
Go to the Basics tab. Under Project details, select the resource group you created for this tutorial.
Under Instance details, provide a VM name. For example, use myVM.
Don't change the default settings for Region, Availability options, Image, and Size.
Under Administrator account, provide a Username and Password for the VM.
Under Inbound port rules, choose Allow selected ports and then select RDP (3389) and HTTP from the drop-down menu.
Before you create the VM, you need to create a data disk.
On the Disks tab, under Disk options, leave the defaults.
Under DATA DISKS, select Create and attach a new disk.
Use the default settings except for Size (GiB), which you can change to 1 GB for this tutorial.
Select Review + create.
You can select the Notifications icon to watch the Deployment progress. Creating a new VM might take a few minutes to complete.
After your VM deployment is complete, select Go to resource.
At this point, you've created a new virtual machine and attached a data disk. Next you connect to the VM.
Connect to your VM
In the Azure portal, select Connect on the virtual machine properties page.
On the Connect to virtual machine page, keep the default options to connect by IP address over port 3389. Select Download RDP file.
Open the downloaded RDP file and select Connect when prompted.
In the Windows Security window, select More choices and then Use a different account. Type the username as localhost\username, enter the password you created for the virtual machine, and then select OK.
You might receive a certificate warning during the sign-in process. Select Yes or Continue to create the connection.
Prepare the Windows server
For the Windows Server 2016 Datacenter server, disable Internet Explorer Enhanced Security Configuration. This step is required only for initial server registration. You can re-enable it after the server has been registered.
In the Windows Server 2016 Datacenter VM, Server Manager opens automatically. If Server Manager doesn't open by default, search for it in File Explorer.
In Server Manager, select Local Server.
On the Properties pane, select the link for IE Enhanced Security Configuration.
In the Internet Explorer Enhanced Security Configuration dialog box, select Off for Administrators and Users.
Now you can add the data disk to the VM.
Add the data disk
While still in the Windows Server 2016 Datacenter VM, select Files and storage services > Volumes > Disks.
Right-click the 1 GB disk named Msft Virtual Disk and select New volume.
Complete the wizard. Use the default settings and make note of the assigned drive letter.
At this point, you've brought the disk online and created a volume. Open File Explorer in the Windows Server VM to confirm the presence of the recently added data disk.
In File Explorer in the VM, expand This PC and open the new drive. It's the F: drive in this example.
Right-click and select New > Folder. Name the folder FilesToSync.
Open the FilesToSync folder.
Right-click and select New > Text Document. Name the text file MyTestFile.
Close File Explorer and Server Manager.
Download the Azure PowerShell module
Next, in the Windows Server 2016 Datacenter VM, install the Azure PowerShell module on the server.
In the VM, open an elevated PowerShell window.
Run the following command:
Install-Module -Name Az
If you have a NuGet version that is older than 188.8.131.52, you're prompted to download and install the latest version of NuGet.
By default, the PowerShell gallery isn't configured as a trusted repository for PowerShellGet. The first time you use the PSGallery, you see the following prompt:
Untrusted repository You are installing the modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet. Are you sure you want to install the modules from 'PSGallery'? [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"):
Answer Yes or Yes to All to continue with the installation.
Az module is a rollup module for the Azure PowerShell cmdlets. Installing it downloads all the available Azure Resource Manager modules and makes their cmdlets available for use.
At this point, you've set up your environment for the tutorial. You're ready to deploy the Storage Sync Service.
Deploy the service
To deploy Azure File Sync, you first place a Storage Sync Service resource into a resource group for your selected subscription. The Storage Sync Service inherits access permissions from its subscription and resource group.
In the Azure portal, select Create a resource and then search for Azure File Sync.
In the search results, select Azure File Sync.
Select Create to open the Deploy Storage Sync tab.
On the pane that opens, enter the following information:
Value Description Name A unique name (per subscription) for the Storage Sync Service.
Use afssyncservice02 for this tutorial.
Subscription The Azure subscription you use for this tutorial. Resource group The resource group that contains the Storage Sync Service.
Use afsresgroup101918 for this tutorial.
Location East US
When you're finished, select Create to deploy the Storage Sync Service.
Select the Notifications tab > Go to resource.
Install the agent
The Azure File Sync agent is a downloadable package that enables Windows Server to be synced with an Azure file share.
In the Windows Server 2016 Datacenter VM, open Internet Explorer.
Go to the Microsoft Download Center. Scroll down to the Azure File Sync Agent section and select Download.
Select the check box for StorageSyncAgent_V3_WS2016.EXE and select Next.
Select Allow once > Run > Open.
If you haven't already done so, close the PowerShell window.
Accept the defaults in the Storage Sync Agent Setup Wizard.
You've deployed the Azure Sync Service and installed the agent on the Windows Server 2016 Datacenter VM. Now you need to register the VM with the Storage Sync Service.
Register Windows Server
Registering your Windows server with a Storage Sync Service establishes a trust relationship between your server (or cluster) and the Storage Sync Service. A server can only be registered to one Storage Sync Service. It can sync with other servers and Azure file shares that are associated with that Storage Sync Service.
The Server Registration UI should open automatically after you install the Azure File Sync agent. If it doesn't, you can open it manually from its file location:
When the Server Registration UI opens in the VM, select OK.
Select Sign-in to begin.
Sign in with your Azure account credentials and select Sign-in.
Provide the following information:
Value Description Azure Subscription The subscription that contains the Storage Sync Service for this tutorial. Resource Group The resource group that contains the Storage Sync Service. Use afsresgroup101918 for this tutorial. Storage Sync Service The name of the Storage Sync Service. Use afssyncservice02 for this tutorial.
Select Register to complete the server registration.
As part of the registration process, you're prompted for an additional sign-in. Sign in and select Next.
Create a sync group
A sync group defines the sync topology for a set of files. A sync group must contain one cloud endpoint, which represents an Azure file share. A sync group also must contain one or more server endpoints. A server endpoint represents a path on a registered server. To create a sync group:
In the Azure portal, select + Sync group from the Storage Sync Service. Use afssyncservice02 for this tutorial.
Enter the following information to create a sync group with a cloud endpoint:
Value Description Sync group name This name must be unique within the Storage Sync Service, but can be any name that is logical for you. Use afssyncgroup for this tutorial. Subscription The subscription where you deployed the Storage Sync Service for this tutorial. Storage account Choose Select storage account. On the pane that appears, select the storage account that has the Azure file share you created. Use afsstoracct101918 for this tutorial. Azure file share The name of the Azure file share you created. Use afsfileshare for this tutorial.
If you select your sync group, you can see that you now have one cloud endpoint.
Add a server endpoint
A server endpoint represents a specific location on a registered server. For example, a folder on a server volume. To add a server endpoint:
Select the newly created sync group and then select Add server endpoint.
On the Add server endpoint pane, enter the following information to create a server endpoint:
Value Description Registered server The name of the server you created. Use afsvm101918 for this tutorial. Path The Windows Server path to the drive you created. Use f:\filestosync in this tutorial. Cloud Tiering Leave disabled for this tutorial. Volume Free Space Leave blank for this tutorial.
Your files are now in sync across your Azure file share and Windows Server.
Clean up resources
When you're done, you can delete the resource group. Deleting the resource group deletes the storage account, the Azure file share, and any other resources that you deployed inside the resource group.
- In the left menu, select Resource groups.
- Right-click the resource group, and then select Delete resource group. A window opens and displays a warning about the resources that will be deleted with the resource group.
- Enter the name of the resource group, and then select Delete.
In this tutorial, you learned the basic steps to extend the storage capacity of a Windows server by using Azure File Sync. For a more thorough look at planning for an Azure File Sync deployment, see: