In the previous post we talked about Azure File Sync technology and the scenarios this can be useful.

Now it’s time to implement it: the service is still in preview, it means that some functionalities can be changed or added before the General Availability and it could not be present in all Azure regions.

The Scenario

The test scenarios we will use is the following:

We have two different file servers joined to the same Active Directory domain: these servers will be our Registered Servers hosting different Server Endpoints of the same Cloud Endpoint. All the servers will be tiering enabled.

The first server will already contains some contents before the implementation of the Azure File Sync, the second one will be added later in the Sync Group: the idea is to show how the previous contents are synced with Azure File Share and how a new server will handle it.

The Action Plan

the high level list of activities will be the following split in 3 different posts:

  1. Create an Azure File Share and a Storage Account (Part 2)
  2. Enable File Sync (Part 2)
  3. Create and Configure Sync Group (Part 2)
  4. Configuring the First Server Endpoint (Part 3)
  5. Configuring the Second Server Endpoint (Part 4)
  6. Verify the functionalities (Part 4)
  7. Secure your Azure File Sync (Part 5)

Ready to start? Let’s go!


Create an Azure File Share and a Storage Account

Log in to the Azure Portal, in Create a resource, type Storage, and select Storage Account – blob, file. table, queue

Fill all the info required:

  • Name: unique name to identify the Storage account (this is the external URL to reach it)
  • Account kind: let’s work with Storage (general purpose v1)
  • Replication: Geo-redundant Storage (I want my file be safe even if the region goes down)
  • Performance: Standard (I want cheap storage as performance are not required because file will be cached on-prem if used)
  • Secure Transfer required: Yes (I don’t think an explanation is required here..)
  • Resource Group: create a new one but it depends of your Governance rules.

After storage account created, click the storage account and then click Files

Inside the file service, click create file share plus icon, fill the file share name and the capacity (remember that the maximum capacity is 5TB). Click OK to create the file share.

Now the Storage account and the file share is completed.


Enable File Sync

Log in to the Azure Portal, in Create a resource, type Azure File Sync

Fill all the info required:

  • Name: the name of the Azure File Sync service
  • Resource Group: use the same you created before for the storage account
  • Location: keep the same of the storage account for performance reasons

Now the service is created. you can find it in the azure portal under the name Storage Sync Service (this is a bit confusing, I know..)


Create and Configure Sync Group

Now it’s time to configure the Sync Group

Login to the Azure portal and open the previously created Storage Sync Service and click on Create Sync Group icon

On sync group blade, type a name for the sync group and select the previously created Storage Account and Azure File Share

Done! the Azure side is now completed.


Now let’s move to the on-prem side to create the server endpoints in Part 3.

Comments are closed.