Home › Knowledgebase › KB-1289

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.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

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:

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:

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:

  1. Is the server primarily used for file storage, or does it host specialised line-of-business applications?
  2. How many staff members access server resources daily, and do any work remotely?
  3. What is the current age of the server, and when is the warranty due to expire?
  4. Are backups automated, tested, and stored offsite?
  5. 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:

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:

  1. Open your backup management console and confirm the most recent backup completed successfully.
  2. Perform a test restore of a random selection of files and folders to a temporary location.
  3. Open the restored files to ensure they are not corrupted and contain the expected data.
  4. Document the backup date, time, and the specific data sets verified.
  5. 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

  1. Sign in to the Microsoft 365 admin center at admin.microsoft.com.
  2. Navigate to Settings > Domains.
  3. Select Add domain and enter your business domain name (for example, yourbusiness.com.au).
  4. Choose Use this domain and select Add a TXT record to your domain's DNS records for verification.
  5. Copy the TXT record value provided by Microsoft.
  6. Log in to your domain registrar's DNS management portal and add the TXT record.
  7. 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

  1. In the Microsoft 365 admin center, navigate to Users > Active users.
  2. Select Add a user or select an existing user from the list.
  3. On the user details page, select the Licences and apps tab.
  4. Toggle the appropriate licence (for example, Microsoft 365 Business Standard) to On.
  5. Select Save changes.

3. Email migration considerations

If you are migrating from Exchange on-premise to Exchange Online, plan the following:

4. DNS changes and MX records

Once mailboxes are migrated, update your DNS records to direct email to Microsoft 365:

  1. In the Microsoft 365 admin center, go to Settings > Domains > select your domain > DNS records.
  2. Copy the MX record value provided (typically pointing to yourdomain-com-au.mail.protection.outlook.com).
  3. Log in to your DNS hosting provider and update the MX record for your domain.
  4. Set the MX record priority to 0 or the value specified by Microsoft.
  5. Add any required SPF, DKIM, and DMARC records to prevent email spoofing and improve deliverability.
  6. Allow up to 72 hours for DNS propagation, though changes often take effect within a few hours.

5. Azure portal setup for virtual machines

  1. Sign in to the Azure portal at portal.azure.com.
  2. Select Create a resource > Virtual machine.
  3. Choose your subscription, resource group, and virtual machine name.
  4. Select an Australian region (such as Australia East or Australia Southeast) for data sovereignty.
  5. Choose an image (for example, Windows Server 2022 Datacenter) and size based on your workload requirements.
  6. Configure administrator account credentials and inbound port rules (RDP port 3389 if remote access is required).
  7. 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:

  1. Download Azure AD Connect from the Microsoft download centre.
  2. Run the installer on a domain-joined server with local administrator rights.
  3. Select Express settings for a standard synchronisation between on-premise Active Directory and Microsoft Entra ID.
  4. Provide enterprise administrator credentials for your on-premise forest.
  5. Provide global administrator credentials for your Microsoft 365 tenant.
  6. 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: