Should I move my office server to the cloud
This article outlines the process of retiring physical on-premise servers and migrating business workloads to Microsoft 365 and Azure. It covers the financial and operational risks associated with maintaining office hardware, including power consumption, cooling, UPS maintenance, and warranty renewals. The content explains how Australian small businesses can move file storage, identity management, email, and applications to the cloud to reduce hardware headaches and improve accessibility for remote staff.
Understanding the true cost of your office server
Deciding whether to retire your physical office server and move to the cloud is a significant decision for any Australian small business. While keeping hardware on-site can feel more tangible and secure, the hidden running costs and maintenance requirements often outweigh the perceived benefits. Moving your workloads to Microsoft 365 and Azure removes the burden of managing physical hardware, reduces power and cooling expenses, and provides secure access to files and applications for staff working remotely or from home offices across Australia.
Physical hardware expenses
- Power consumption: Servers run 24 hours a day, seven days a week, contributing significantly to your office electricity bill.
- Cooling and air conditioning: Servers generate heat and require climate control to prevent overheating and hardware failure.
- Uninterruptible Power Supply (UPS): UPS units protect against power surges and outages, but batteries degrade over time and require periodic replacement.
- Warranty renewals and replacement parts: As hardware ages, warranty renewals become more expensive, and sourcing replacement components for older servers can be difficult and costly.
- Physical space: Dedicated server rack space or a secure cupboard takes up valuable office real estate.
Australian data residency and connectivity requirements
Before migrating, confirm that your data will remain within Australian borders. Microsoft Azure offers two regions in Australia that support data sovereignty requirements for Australian organisations:
- Australia East (New South Wales)
- Australia Southeast (Victoria)
When provisioning Azure resources, select one of these regions in the Azure portal to keep your data within Australia.
Cloud migration places additional demand on your internet connection. For a small business moving file shares, email, and applications to the cloud, we recommend:
- NBN business-grade service: NBN Enterprise Ethernet or NBN Business fibre where available, with a service level agreement (SLA) that suits your operating hours.
- Upload speed: Minimum 50 Mbps upload for a small office, though higher speeds are recommended if multiple staff will sync large files or access hosted applications simultaneously.
- Redundancy: A secondary connection such as 4G/5G failover to minimise disruption if your primary NBN service experiences an outage.
Run a speed test during peak business hours to verify actual upload performance before scheduling your migration.
Workloads you can move to the cloud
Most small business workloads traditionally hosted on an office server can be migrated to Microsoft 365 and Azure. This reduces reliance on physical hardware while improving accessibility for remote staff.
Email migration: Exchange to Exchange Online
Migrate your on-premise Exchange mailboxes to Exchange Online as part of Microsoft 365.
- Sign in to the Microsoft 365 admin center.
- Navigate to Setup > Email migration.
- Select Exchange as the source email system.
- Enter the administrator credentials for your on-premise Exchange server.
- Create a migration batch and select the mailboxes to migrate.
- Start the sync and monitor progress in the Recipients > Migration page.
- Once synced, update your public DNS MX record to point to Microsoft 365 so new mail is delivered to Exchange Online.
- Assign the appropriate Microsoft 365 licence to each user so they can access their mailbox.
File storage
Replace local file shares with cloud storage solutions such as OneDrive for Business and SharePoint. Files are stored securely in Microsoft data centres and can be accessed from any device with an internet connection. Version history and recycle bin features help protect against accidental deletion or ransomware.
Identity management
Move user accounts and authentication from an on-premise Active Directory to Microsoft Entra ID (formerly Azure Active Directory). Staff can use a single set of credentials to sign in to Windows, Microsoft 365, and business applications. Conditional Access policies add an extra layer of security by requiring multi-factor authentication for sign-ins from unfamiliar locations.
Applications
Host line-of-business applications on Azure Virtual Machines or migrate them to Software as a Service (SaaS) equivalents. This removes the need to manage application servers, install patches, or maintain local SQL instances.
Microsoft 365 and Azure licensing recommendations
Select licences based on the features your staff require:
| Licence | Best suited for | Key features |
|---|---|---|
| Microsoft 365 Business Basic | Staff who primarily need email and web versions of Office apps | Exchange Online, OneDrive for Business, SharePoint, Teams, web and mobile Office apps |
| Microsoft 365 Business Standard | Staff who need desktop Office applications | All Business Basic features plus desktop versions of Word, Excel, PowerPoint, and Outlook |
| Microsoft 365 Business Premium | Staff handling sensitive data or requiring advanced security | All Business Standard features plus Microsoft Entra ID P1, Intune, Azure Information Protection, and advanced threat protection |
For Azure workloads such as virtual machines, create resources in the Azure portal under Virtual machines > Create and select Australia East or Australia Southeast as the region.
Planning your migration
- Audit your current environment: Document all roles performed by your office server, including file sharing, DHCP, DNS, printing, and application hosting.
- Identify dependencies: Determine which applications rely on the server and whether cloud alternatives exist.
- Assess internet connectivity: Ensure your business has a reliable business-grade NBN connection with sufficient upload speed to support cloud workloads.
- Choose your cloud services: Select the appropriate Microsoft 365 and Azure services based on your storage, identity, email, and application requirements.
- Plan the migration timeline: Schedule the move outside of peak business hours to minimise disruption to staff.
- Migrate data in stages: Move non-critical data first, test access and permissions, then migrate production files and user mailboxes.
- Decommission the physical server: Once you have verified that all workloads are running in the cloud and backups are in place, safely retire the on-premise hardware.
Backup strategy
Cloud native features such as the Microsoft 365 recycle bin and OneDrive version history are not a complete backup strategy. We recommend implementing a dedicated third-party Microsoft 365 backup solution to protect Exchange Online, SharePoint, OneDrive, and Teams data against accidental deletion, ransomware, and retention gaps.
For Azure Virtual Machines, use Azure Backup to create recovery points and configure backup policies directly in the Azure portal under Virtual machines > Backup > Enable backup.
Security and access considerations
Moving files off a physical server in your office can cause anxiety, but cloud platforms offer enterprise-grade security controls that are difficult and expensive to replicate on-premise.
- Encryption: Data is encrypted at rest and in transit using industry-standard protocols.
- Multi-factor authentication: Require a second form of verification in addition to a password for all user accounts.
- Conditional Access: Block sign-ins from high-risk locations or require compliant devices before granting access to corporate resources.
- Device management: Use Microsoft Intune to manage and secure laptops and mobile devices that access business data.
Ongoing management
Once your server workloads are in the cloud, your IT provider handles patching, hardware maintenance, and infrastructure updates. Your internal team can focus on supporting users rather than replacing UPS batteries or monitoring server room temperatures. Regular reviews of Azure usage and Microsoft 365 licensing ensure you are not paying for services you no longer need.
Troubleshooting common migration issues
DNS propagation delays after MX record update
If external email is not arriving in Exchange Online after you update your MX record, the change may not have propagated across Australian ISPs.
- Use an online DNS lookup tool to verify the MX record points to
yourdomain-com.mail.protection.outlook.com. - Wait up to 72 hours for full propagation, though most changes appear within a few hours.
- Contact your domain registrar if the record does not update after 72 hours.
Permission errors accessing migrated files
Users may report they cannot open files after migration to SharePoint or OneDrive.
- Sign in to the Microsoft 365 admin center.
- Navigate to Users > Active users.
- Select the affected user and verify they have the correct licence assigned.
- Check SharePoint site permissions under SharePoint admin center > Active sites > Permissions.
Azure AD Connect sync failures
If on-premise Active Directory changes are not reflecting in Microsoft Entra ID, the sync service may have stopped.
- Open the Azure AD Connect application on your on-premise sync server.
- Check the Synchronization Service Manager for stopped or failed sync cycles.
- Run a manual delta sync and review the event logs for error codes.
- Verify the service account has the required permissions in Active Directory.
If you would like assistance assessing your current server environment or planning a migration to Microsoft 365 and Azure, please Open a Ticket.