Home › Knowledgebase › KB-1387

Do I Need A Server In My Office Cupboard?

Summary

This guide helps you troubleshoot and resolve: Do I Need A Server In My Office Cupboard?. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Many small businesses across Australia still rely on a physical server sitting in an office cupboard or spare room to store files, host applications, and manage user logins. While this setup may have made sense years ago, the reality of maintaining legacy on-premise hardware has changed. Power consumption, cooling requirements, uninterruptible power supply (UPS) battery replacement, warranty renewals, and replacement parts all add up to significant ongoing costs. More importantly, a single hardware failure can bring your entire operation to a standstill. This article examines the hidden expenses of keeping a server on site and explains how moving your workloads to Microsoft 365 and Azure cloud tiers can improve reliability, security, and accessibility for staff working from multiple locations.

The Real Cost Of An Office Server

Keeping a physical server in the office involves more than the initial purchase price. Over the lifespan of the hardware, you will encounter several recurring expenses that are easy to overlook until something breaks.

Power And Cooling

A server runs 24 hours a day, 7 days a week. That constant draw adds a noticeable amount to your quarterly electricity bill. Servers also generate significant heat, which means your office air conditioning must work harder to keep the room temperature stable. In summer, a poorly ventilated cupboard can become a heat trap, increasing the risk of thermal throttling or unexpected shutdowns.

UPS Battery Replacement

An uninterruptible power supply protects your server from power spikes and outages, but UPS batteries degrade over time. Most batteries need replacement every three to five years. If a battery fails during a blackout, your server will shut down abruptly, risking data corruption and extended downtime while you source a replacement.

Warranty Renewals And Replacement Parts

Hardware warranties typically expire after three or five years. Once out of warranty, a failed hard drive, power supply, or motherboard means sourcing parts yourself, often at a premium for older equipment. Downtime while waiting for parts can stretch to days, leaving staff without access to files, email, or line-of-business applications.

Security And Backup Risks

An on-premise server requires manual patching, antivirus updates, and regular backup verification. If backups are stored on a local drive or USB disk in the same cupboard, a fire, flood, or theft could destroy both your live data and your backups simultaneously. Physical access to the server also presents a security risk if the cupboard is not locked or monitored.

Data Sovereignty And Australian Compliance

When moving to the cloud, it is important to understand where your data is physically stored. Microsoft Azure operates data centres in Australian regions, including the Australia East (New South Wales) and Australia Southeast (Victoria) regions. Storing your data in these regions helps your organisation meet Australian Privacy Principles (APPs) and local data sovereignty requirements. When provisioning resources in the Azure portal, select Australia East or Australia Southeast as the region to ensure your data remains within Australian borders.

Moving To Microsoft 365 And Azure

Cloud platforms remove the need to manage physical hardware in your office. Microsoft 365 and Azure provide enterprise-grade infrastructure with built-in redundancy, automatic security updates, and access from any internet connection.

Internet Bandwidth Requirements

Before migrating, assess your internet connection. Cloud workloads require a reliable business-grade connection. We recommend a minimum upload speed of 10 Mbps for small teams performing file synchronisation, and 50 Mbps or higher for larger organisations or those migrating significant volumes of data. Low upload speeds will slow down the initial sync to OneDrive and SharePoint and can cause timeouts during large file transfers.

File Storage With OneDrive And SharePoint

Replace shared folders on a local server with OneDrive for personal files and SharePoint team sites for departmental documents. Files sync to desktops and laptops, remain accessible offline, and are protected by version history and recycle bin retention. Staff can access documents from home, a client site, or while travelling without needing a VPN connection back to the office.

To migrate files using the SharePoint Migration Tool:

  1. Download and install the SharePoint Migration Tool from the Microsoft Download Centre.
  2. Open the tool and select Upload.
  3. Choose SharePoint as the destination.
  4. Sign in with your Microsoft 365 global administrator account.
  5. Select the source folder on your file server and the destination SharePoint document library.
  6. Click Start to begin the migration and monitor progress in the tool dashboard.

Identity And Access With Microsoft Entra ID

Move user accounts and sign-in credentials from an on-premise Active Directory domain controller to Microsoft Entra ID (formerly Azure Active Directory). Conditional Access policies let you require multi-factor authentication and block sign-ins from untrusted locations or devices, improving security without managing certificates or VPN tunnels.

To configure Conditional Access:

  1. Sign in to the Microsoft Entra admin centre.
  2. Navigate to Protection > Conditional Access.
  3. Click New policy.
  4. Under Assignments, select users or groups and cloud apps or actions.
  5. Under Access controls > Grant, select Require multi-factor authentication.
  6. Set Enable policy to On and click Create.

Email Migration From On-Premise Exchange To Exchange Online

If you run Microsoft Exchange on your local server, you can migrate mailboxes to Exchange Online as part of Microsoft 365. A cutover migration is suitable for small organisations with fewer than 150 mailboxes.

To perform a cutover migration:

  1. Sign in to the Exchange admin centre.
  2. Navigate to Recipients > Migration.
  3. Click + Add a migration and select Cutover.
  4. Enter your on-premise Exchange server details and administrator credentials.
  5. Create a migration batch and select the mailboxes to migrate.
  6. Start the batch and monitor synchronisation status in the migration dashboard.
  7. Once synchronisation is complete, update your public DNS MX records to point to Exchange Online.
  8. Finalise the migration batch to complete mailbox delivery.

Application Hosting With Azure

If you run legacy line-of-business applications on a local server, Azure virtual machines or Azure App Service can host those workloads in a secure data centre. You pay only for the resources you use, and you can scale compute power up or down as your business needs change. Azure Site Recovery and Azure Backup provide automated protection against hardware failure and ransomware.

Not all legacy applications are compatible with Azure. Applications that rely on specific hardware dongles, outdated operating systems, or local network broadcasts may require refactoring, replacement with a SaaS alternative, or continued operation on a dedicated virtual machine. Test application functionality thoroughly in Azure before decommissioning your on-premise server.

To deploy an Azure virtual machine:

  1. Sign in to the Azure portal.
  2. Click + Create a resource.
  3. Select Virtual machine.
  4. Choose Australia East or Australia Southeast as the region.
  5. Select the operating system image, size, and authentication method.
  6. Configure networking and disk settings, then click Review + create and Create.

Planning Your Migration

  1. Audit your current server usage. Identify which files, folders, and applications are actively used and which can be archived or decommissioned.
  2. Assess your internet connection. Confirm you meet the minimum upload speed recommendations for cloud synchronisation.
  3. Choose your Microsoft 365 and Azure subscription tiers based on user count, storage requirements, and application needs.
  4. Set up Microsoft Entra ID and synchronise or recreate user accounts. Assign appropriate licenses and security groups.
  5. Migrate email from on-premise Exchange to Exchange Online using the Exchange admin centre.
  6. Migrate file shares to SharePoint or OneDrive using the SharePoint Migration Tool or a third-party migration service.
  7. Test application functionality in Azure before decommissioning the on-premise server.
  8. Train staff on accessing files through the web browser, desktop sync client, or mobile apps.
  9. Decommission the physical server securely. Wipe all drives and dispose of hardware through a certified e-waste recycler.
Keep your existing server running in parallel during the migration. Do not decommission hardware until you have verified that all critical data has been successfully transferred and staff can access it from the cloud.
Do not delete local files until you have confirmed that cloud backups are working and that you can restore a sample file from the cloud. Data loss during migration is irreversible if local copies are removed prematurely.

Cost Comparison Guidance

Compare the total cost of ownership between maintaining an on-premise server and subscribing to cloud services. On-premise costs include hardware purchase, electricity, cooling, UPS maintenance, warranty renewals, and replacement parts. Cloud costs are typically recurring subscription fees based on user count and consumption.

Common Microsoft 365 tiers for small business include:

Azure costs vary based on virtual machine size, storage tier, and data transfer. Use the Azure pricing calculator in the Azure portal to estimate monthly expenditure for your specific workload. Factor in potential savings from reduced power consumption, eliminated hardware refresh cycles, and reduced IT maintenance hours.

Rollback Plan

Prepare a rollback plan in case the migration encounters critical issues that cannot be resolved within an acceptable timeframe.

  1. Keep the on-premise server powered on and network-connected until the cloud environment is fully validated.
  2. Maintain recent backups of all on-premise data, including file shares, Exchange databases, and application data.
  3. Document DNS settings, IP addresses, and firewall rules so you can restore internal access quickly if needed.
  4. If file synchronisation fails, keep local file shares available and redirect users back to the on-premise server while troubleshooting SharePoint or OneDrive issues.
  5. If email delivery fails after updating MX records, revert DNS MX records to point back to your on-premise Exchange server.
  6. If an Azure-hosted application is unstable, redeploy the application on the original on-premise hardware or restore from the most recent backup.
  7. Only decommission the physical server after all users have confirmed access to cloud resources and a successful test restoration has been completed.

Benefits For Distributed Teams

Removing the server from the office cupboard means staff are no longer tied to a single physical location. Employees working from home, a co-working space, or a client office can open the same files and applications with consistent performance. IT updates and security patches happen automatically in the cloud, reducing the maintenance burden on your internal team or external support provider.

Troubleshooting Common Migration Issues

Sync Conflicts In OneDrive And SharePoint

Sync conflicts occur when the same file is edited in multiple locations before synchronisation completes. OneDrive creates duplicate files with conflict suffixes to preserve both versions.

Permission Errors After Migration

Users may find they cannot access migrated folders or files due to missing or incorrect permissions.

Connectivity Problems

Users may experience slow performance or inability to connect to cloud services.

Exchange Mailbox Migration Delays

Mailbox migration batches may stall or take longer than expected.

Conclusion

Moving from an office cupboard server to Microsoft 365 and Azure removes the burden of hardware maintenance, improves security, and gives your staff flexible access from anywhere. By planning for bandwidth, data sovereignty, application compatibility, and potential rollback scenarios, your organisation can transition with confidence and minimise disruption.

If you would like assistance assessing your current server environment or planning a move to Microsoft 365 and Azure, Open a Ticket and our team can help you review your options.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket