type: Guide collections: BCM, Software title: Azure File Sync Setup (Access DB Cloud Migration) description: A step-by-step guide to configuring Azure File Sync for migrating and accessing an Access database in the cloud while maintaining legacy front-end compatibility. tags: [bcm, software, windows]

Azure File Sync Setup (Access DB Cloud Migration)

Use this checklist to configure Azure File Sync for migrating the Access database to the cloud, while keeping compatibility with legacy Access front-ends.

✅ Prerequisites

• [ ] Ensure on-prem server is running Windows Server 2016 or later.
• [ ] Confirm on-prem server is domain-joined and online.
• [ ] Confirm outbound internet access to Azure is unrestricted.
• [ ] Confirm port 445 is open for SMB traffic.
• [ ] Sign in to the Azure Portal.

🔧 Step 1 – Create Azure Storage Account

• [ ] Go to Azure Portal → Storage Accounts.
• [ ] Click Create, then select:
• Performance: Standard
• Redundancy: Locally Redundant Storage (LRS)
• Region: UK South
• [ ] Name the account (e.g., bcmfilesync).
• [ ] Create a new resource group (e.g., BCM-FileSync).

📂 Step 2 – Create File Share

• [ ] Inside your Storage Account, go to File shares.
• [ ] Click + File share, name it (e.g., accessdb).
• [ ] Set access tier to Hot.
• [ ] Click Create (no need to configure backup now).

🔁 Step 3 – Deploy Azure File Sync Service

• [ ] In the Azure portal, search for Azure File Sync.
• [ ] Create a Sync Group and associate it with:
• The file share you just created (accessdb)
• [ ] Install the Azure File Sync agent on the on-prem server.
• [ ] Register the on-prem server with the sync group.
• [ ] Configure sync to match existing folder name and drive letter (e.g., Z:\AccessDB).

🧪 Step 4 – Testing and Access

• [ ] Confirm database is syncing successfully between on-prem and Azure.
• [ ] Install sync agent on other machines that need local access.
• [ ] Ensure Access front-ends open and save without issue.
• [ ] Confirm shared drive/folder mapping works as expected.

📝 Notes

• Legacy Access DBs may rely on specific file paths.
• You can preserve folder names and drive letters to prevent breaking links.
• This setup allows you to retain a local copy while using Azure as authoritative storage.

⠀

#bcm #work