Should i replace my physical server with cloud services
Summary
This guide helps you troubleshoot and resolve: Should i replace my physical server with cloud services. Follow the steps below to fix the issue.
Common Causes
Should I replace my physical server with cloud services?
Many small businesses across Australia continue to rely on a physical server tucked away in an office cupboard or spare room. While this setup may have served your business well for years, hardware eventually reaches the end of its useful life. Deciding whether to refresh your on-premise server or migrate to cloud services such as Microsoft 365 and Azure requires a clear look at your total cost of ownership and operational risk.
Understand the hidden costs of an on-premise server
A physical server costs more than the initial purchase price. Over a typical three-to-five-year lifespan, several recurring expenses add up:
- Power consumption: Servers run 24 hours a day, drawing electricity even when usage is low.
- Cooling and ventilation: Server rooms require adequate airflow and temperature control to prevent overheating.
- Uninterruptible power supply (UPS): Batteries must be tested regularly and replaced every few years to protect against power spikes and outages.
- Hardware refresh cycles: Components such as hard drives, power supplies, and motherboards fail over time and require replacement.
- Maintenance and support: Firmware updates, security patching, and physical repairs consume internal or external IT resources.
- Physical security: On-site hardware is exposed to theft, fire, flood, and accidental damage.
For a small business, these costs are often overlooked because they are spread across utility bills and occasional repair invoices rather than appearing as a single line item.
Compare cloud alternatives
Moving file and identity services to the cloud shifts the burden of infrastructure management from your business to the service provider. Common options for small businesses include:
- Microsoft 365: Replaces on-premise file shares with OneDrive and SharePoint, while Microsoft Entra ID (formerly Azure Active Directory) handles user identities and single sign-on.
- Azure: Hosts virtual machines, databases, and line-of-business applications without requiring physical hardware in your office.
With cloud services, you typically pay a predictable monthly subscription based on usage. The provider manages power, cooling, hardware refreshes, and physical security. Your internal team or MSP can focus on supporting users rather than maintaining servers.
Evaluate your current server usage
Before making a decision, document what your physical server actually does for your business. Consider the following questions:
- Is the server primarily used for file storage, or does it host specialised line-of-business applications?
- How many staff members access server resources daily, and do any work remotely?
- What is the current age of the server, and when is the warranty due to expire?
- Are backups automated, tested, and stored offsite?
- How much time does your team spend troubleshooting server-related issues each month?
If your server is mostly serving files and managing user logins, a migration to Microsoft 365 and Azure is often straightforward. If you run legacy software that requires a local server, a hybrid approach may be more appropriate.
Licensing requirements and user subscription planning
Before starting migration, determine the correct Microsoft 365 licences for your workforce. Review the following common plans:
- Microsoft 365 Business Basic: Suitable for users who need email and web/mobile Office apps.
- Microsoft 365 Business Standard: Required for users who need desktop versions of Office applications.
- Microsoft 365 Business Premium: Includes advanced security, device management, and Azure AD Premium P1 features.
Create a user inventory spreadsheet listing every staff member, their current email address, and the applications they use daily. Assign licences based on role requirements to avoid paying for unused features.
Pre-migration backup verification
Verify that all server data is backed up and recoverable before initiating any migration. Follow these steps:
- Open your backup management console and confirm the most recent backup completed successfully.
- Perform a test restore of a random selection of files and folders to a temporary location.
- Open the restored files to ensure they are not corrupted and contain the expected data.
- Document the backup date, time, and the specific data sets verified.
- Ensure backups include server system state, Active Directory (if applicable), and all shared folders.
Warning: Do not proceed with migration until you have verified that backups are current and test restores are successful.
Step-by-step migration instructions
1. Domain verification in Microsoft 365
- Sign in to the Microsoft 365 admin center at
admin.microsoft.com. - Navigate to Settings > Domains.
- Select Add domain and enter your business domain name (for example,
yourbusiness.com.au). - Choose Use this domain and select Add a TXT record to your domain's DNS records for verification.
- Copy the TXT record value provided by Microsoft.
- Log in to your domain registrar's DNS management portal and add the TXT record.
- Return to the Microsoft 365 admin center and select Verify. Verification may take up to 72 hours but usually completes within minutes.
2. Assign user licences
- In the Microsoft 365 admin center, navigate to Users > Active users.
- Select Add a user or select an existing user from the list.
- On the user details page, select the Licences and apps tab.
- Toggle the appropriate licence (for example, Microsoft 365 Business Standard) to On.
- Select Save changes.
3. Email migration considerations
If you are migrating from Exchange on-premise to Exchange Online, plan the following:
- Determine whether to use cutover, staged, or hybrid migration based on your mailbox count and bandwidth.
- Export mailboxes from your on-premise Exchange server using the Exchange admin center or PowerShell.
- Import mailboxes to Exchange Online using the Microsoft 365 admin center migration tools.
- Notify users of their new email credentials and Outlook profile configuration steps.
4. DNS changes and MX records
Once mailboxes are migrated, update your DNS records to direct email to Microsoft 365:
- In the Microsoft 365 admin center, go to Settings > Domains > select your domain > DNS records.
- Copy the MX record value provided (typically pointing to
yourdomain-com-au.mail.protection.outlook.com). - Log in to your DNS hosting provider and update the MX record for your domain.
- Set the MX record priority to 0 or the value specified by Microsoft.
- Add any required SPF, DKIM, and DMARC records to prevent email spoofing and improve deliverability.
- Allow up to 72 hours for DNS propagation, though changes often take effect within a few hours.
5. Azure portal setup for virtual machines
- Sign in to the Azure portal at
portal.azure.com. - Select Create a resource > Virtual machine.
- Choose your subscription, resource group, and virtual machine name.
- Select an Australian region (such as Australia East or Australia Southeast) for data sovereignty.
- Choose an image (for example, Windows Server 2022 Datacenter) and size based on your workload requirements.
- Configure administrator account credentials and inbound port rules (RDP port 3389 if remote access is required).
- Review and select Create to deploy the virtual machine.
6. Hybrid identity with Azure AD Connect
If your organisation maintains on-premise Active Directory and wants to synchronise identities with Microsoft Entra ID, install Azure AD Connect:
- Download Azure AD Connect from the Microsoft download centre.
- Run the installer on a domain-joined server with local administrator rights.
- Select Express settings for a standard synchronisation between on-premise Active Directory and Microsoft Entra ID.
- Provide enterprise administrator credentials for your on-premise forest.
- Provide global administrator credentials for your Microsoft 365 tenant.
- Complete the configuration and verify synchronisation status in the Synchronisation Service Manager.
Tip: Azure AD Connect is recommended for businesses with complex identity needs, such as existing on-premise group policies or legacy applications that rely on local Active Directory.
Internet bandwidth requirements and downtime warnings
Warning: Cloud services depend entirely on your internet connection. Before migrating, review your business broadband plan. A business-grade connection with a service level agreement is strongly recommended if staff will rely solely on cloud access for files, email, and applications.
Estimate your bandwidth needs by multiplying the number of concurrent users by the expected usage per user. For example, video conferencing, large file uploads to SharePoint, and synchronized OneDrive folders can consume significant bandwidth. Schedule large data transfers outside peak business hours to minimise impact on daily operations.
Warning: Expect potential downtime during email migration and DNS propagation. Users may experience temporary email delivery delays or inability to access on-premise file shares during the cutover. Communicate the migration schedule to all staff in advance.
Create a migration framework
Use this framework to compare your options:
1. Assess total cost of ownership
Calculate the annual cost of keeping your current server, including electricity, cooling, UPS maintenance, anticipated repairs, and IT support time. Compare this against the annual subscription cost of equivalent cloud services.
2. Identify business-critical workloads
List every application and data store running on your server. Determine which can move to the cloud and which may require refactoring or replacement.
3. Plan for connectivity
Cloud services rely on a stable internet connection. Review your current business broadband plan and consider upgrading to a business-grade connection with a service level agreement if your staff will depend entirely on cloud access.
4. Schedule the migration
Plan the move outside peak business hours to minimise disruption. Migrate user identities and file data in stages, testing access and permissions at each step.
5. Decommission the old hardware
Once data has been verified in the cloud, securely wipe and dispose of the physical server. Ensure any sensitive data is destroyed in accordance with Australian privacy obligations.
Pilot migration checklist
Before migrating the entire organisation, complete a pilot with a small group of users:
- Select 3 to 5 non-critical users or a single department for the pilot.
- Migrate their mailboxes, files, and user identities to Microsoft 365.
- Verify that users can log in, access email, and open shared files.
- Test printing, application access, and mobile device connectivity.
- Collect feedback from pilot users on performance and usability.
- Document any issues and resolve them before proceeding with the full migration.
- Announce the migration timeline and expected benefits at least two weeks in advance.
- Provide training on Microsoft 365 applications, including Outlook, OneDrive, SharePoint, and Teams.
- Create quick-reference guides for common tasks, such as accessing SharePoint files or sharing documents via OneDrive.
- Designate internal champions or power users who can assist colleagues during the transition.
- Schedule a support window immediately after migration to address login and access issues quickly.
Change management and user training
Technical migration is only one part of the project. Prepare your staff for the change:
Troubleshooting common migration issues
| Issue | Possible cause | Resolution |
|---|---|---|
| Domain verification fails | TXT record not propagated or entered incorrectly | Double-check the TXT record value in your DNS provider's portal. Wait up to 72 hours for propagation, then retry verification in the Microsoft 365 admin center. |
| Users cannot log in after migration | Licence not assigned or password sync issue | Verify the user has an active licence in the Microsoft 365 admin center. Reset the user password and instruct them to sign in again. |
| Email not flowing after MX record change | DNS propagation delay or incorrect MX record priority | Confirm the MX record points to the correct Microsoft 365 endpoint and has the correct priority. Use an online DNS lookup tool to verify the record is public. |
| Slow file access in SharePoint or OneDrive | Insufficient internet bandwidth or Wi-Fi signal | Run a speed test from the affected workstation. If bandwidth is low, schedule large uploads overnight or upgrade your business broadband plan. |
| Azure AD Connect synchronisation errors | Credential mismatch or firewall blocking required ports | Check the Synchronisation Service Manager for error codes. Ensure the server can communicate with Microsoft Entra ID endpoints over port 443. |
Consider the risks of staying on-premise
Keeping an ageing server introduces operational risk. Hardware failure can lead to extended downtime, and restoring from backup may take hours or days. Cloud services offer built-in redundancy and geo-replication, which can improve resilience for small businesses without an on-site IT team.
There are also compliance considerations. Storing data in reputable Australian cloud regions can help meet data sovereignty requirements while benefiting from enterprise-grade security controls.
Tip: Start with a pilot migration. Move a small group of users or a non-critical data set to the cloud first to validate performance and user experience before migrating the entire business.
Warning: Do not decommission your physical server until you have confirmed that all data has been successfully migrated, tested, and backed up in the cloud environment.
Replacing a physical server with cloud services is not just a technology decision; it is a business decision about cost, risk, and flexibility. By reviewing your total cost of ownership and mapping your workloads to Microsoft 365 and Azure, you can determine whether your office server is still an asset or a liability.
If you would like assistance assessing your current infrastructure or planning a migration, Open a Ticket.
Still Having Issues?
💻 Open a Ticket