Home › Knowledgebase › KB-1211

How to reduce office server power and cooling costs

Summary

This guide helps you troubleshoot and resolve: How to reduce office server power and cooling costs. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

How to reduce office server power and cooling costs

Many small businesses across Australia continue to rely on physical servers stored in office cupboards to host files and line-of-business applications. While familiar, these on-premise systems incur ongoing costs for electricity, air conditioning, uninterruptible power supply (UPS) battery replacements, hardware warranty renewals, and physical security. Migrating file storage and identity services to Microsoft 365 and Azure eliminates these hardware overheads, reduces single points of failure, and enables staff to access business data securely from any location without maintaining a server on site.

Understanding the true cost of an office server

A physical server sitting in a cupboard or server rack consumes power 24 hours a day, seven days a week. Beyond the electricity drawn by the server itself, the equipment generates heat that requires air conditioning or dedicated ventilation to prevent overheating. Over time, these running costs add up alongside less obvious expenses such as:

  • Uninterruptible power supply (UPS) battery replacements every few years
  • Hardware warranty renewals and extended support contracts
  • Physical security measures to protect the server room or cupboard
  • Replacement parts when components fail out of warranty
  • Downtime costs when a single point of failure takes the system offline

For a small business, these costs are often hidden within general overheads, but they represent a significant drain on cash flow compared with cloud-based alternatives.

Cost comparison: On-premise server vs. Microsoft 365 and Azure

Expense item On-premise server Microsoft 365 and Azure
Electricity and cooling Ongoing 24/7 power and air conditioning costs Included in cloud subscription
Hardware warranty and renewals Annual support contracts and replacement parts None; managed by Microsoft
UPS battery replacement Every few years None
Physical security Locked cupboard or server room access controls None required on site
Licensing Windows Server and Client Access Licences Microsoft 365 and Azure user licences
Data residency Stored on site Australian Azure regions available

Cloud subscription costs vary by user count and licence type. Contact your IT provider for a detailed quotation based on your organisation’s requirements.

Data sovereignty and Australian data centres

Australian businesses must consider where their data is stored. Microsoft Azure operates data centres in Australian regions, including the Australia East (New South Wales) and Australia Southeast (Victoria) regions. Storing business data in these regions helps meet Australian data residency expectations and keeps data within Australian jurisdiction.

When configuring Microsoft 365 and Azure, verify that your tenant is provisioned in an Australian region to support local data sovereignty requirements.

Step 1: Audit your current server usage

Before making changes, identify what your on-premise server is actually doing. Most small businesses use a local server for one or more of the following:

  • File shares and shared folders for staff
  • Active Directory for user logins and passwords
  • Print server management
  • Hosting a line-of-business application or database
  • Local backups of business data

Make a list of the applications and services that depend on the server, and note how many staff members access them daily. This inventory will help you determine which workloads can move to the cloud and which may need a different approach.

Step 2: Move file storage to Microsoft 365

Microsoft 365 provides cloud-based file storage that removes the need for an on-premise file server. Staff can access documents from any device with an internet connection, and you no longer need to power and cool hardware to keep files available.

  1. Assess the total size of your current file shares and identify redundant or obsolete data.
  2. In a web browser, sign in to the SharePoint admin centre at https://admin.microsoft.com/sharepoint.
  3. Select Active sites, then select Create to set up SharePoint team sites for departmental files.
  4. Instruct users to sign in to OneDrive at https://onedrive.live.com and select Add new to create folders for individual files.
  5. Download and install the SharePoint Migration Tool from the Microsoft Download Centre.
  6. Open the SharePoint Migration Tool, select Start, then choose SharePoint as the destination.
  7. Map your existing on-premise folders to the corresponding SharePoint team sites and OneDrive accounts.
  8. Select Migrate to begin transferring files and permissions.
  9. Train staff on saving files to SharePoint and OneDrive instead of local mapped drives.
  10. Verify all data has migrated successfully before decommissioning the file server role.

Step 3: Move identity services to Azure

If your office server runs Active Directory to manage user accounts and computer logins, you can reduce reliance on that hardware by moving identity services to Azure. Azure AD (Microsoft Entra ID) provides cloud-based authentication that integrates with Microsoft 365 and many other business applications.

  1. Review your current Active Directory structure, including user accounts, groups, and group policies.
  2. Sign in to the Microsoft Entra admin centre at https://entra.microsoft.com.
  3. Select Identity, then Overview to create or connect an Azure AD tenant for your organisation.
  4. Download Microsoft Entra Connect from the Microsoft Download Centre.
  5. Run the installer and select Express settings to synchronise on-premise user accounts to Azure AD, or create cloud-only accounts for a clean break.
  6. Open Settings on a Windows device, select Accounts, then Access work or school.
  7. Select Connect and enter the user’s cloud credentials to join the device to Azure AD or hybrid Azure AD.
  8. In the Microsoft Entra admin centre, select Protection, then Authentication methods, and enable self-service password reset.

Moving identity to the cloud removes the need to maintain a local domain controller, reducing power, cooling, and hardware replacement costs.

Step 4: Evaluate line-of-business applications

Some small businesses keep a server solely to host a specialised application or database. Before retaining hardware for this purpose, check whether the vendor offers a cloud-hosted or Software as a Service (SaaS) version. Many Australian business applications now run in Azure or through a web browser, removing the need for an on-site server entirely.

If a cloud version is not available, consider hosting the application on Azure virtual machines rather than in your office. This still removes the power and cooling burden from your premises while keeping the application accessible to staff.

Step 5: Address print server migration

If your office server manages printers, you have several options to move printing to the cloud:

  • Use Azure Virtual Desktop to host print workloads in Azure and provide staff with remote access to network printers.
  • Evaluate cloud print solutions that allow users to print directly from Microsoft 365 applications without a local print server.
  • Replace shared network printers with Wi-Fi or Ethernet-connected printers that support direct printing from Windows, macOS, iOS, and Android devices.

Test all printer queues and driver installations before decommissioning the print server role.

Step 6: Plan for decommissioning

Warning: Before decommissioning your office server, verify that you have a current backup of all business data. Confirm data integrity by opening migrated files and testing user logins without the on-premise server. Do not switch off or dispose of the server until migration is fully verified.

Once file storage, identity, applications, and printing have moved to the cloud, you can plan to switch off the office server. Follow these steps to avoid disruption:

  1. Confirm all business data has been migrated and is accessible to staff.
  2. Test user logins and application access without the on-premise server.
  3. Export or archive any remaining local backups to cloud storage.
  4. Schedule a shutdown outside business hours and monitor for issues.
  5. Arrange secure disposal or recycling of the server hardware through a certified e-waste provider.

Removing the server also eliminates the need for UPS battery replacements and reduces the heat load on your office air conditioning.

Hybrid considerations

Some businesses may need to keep a local domain controller for certain applications, such as legacy line-of-business software that requires on-premise Active Directory authentication. If this applies to your organisation, plan a hybrid configuration where the local server remains for authentication while file storage and other workloads move to Microsoft 365 and Azure.

Security and access considerations

Moving to the cloud does not mean compromising security. Microsoft 365 and Azure include features such as multi-factor authentication, conditional access policies, and device compliance rules that help protect business data. Staff can work securely from the office, home, or while travelling, without needing a VPN connection back to an on-site server.

Ensure that all user accounts have strong passwords and multi-factor authentication enabled before decommissioning local servers.

Important warnings

Internet bandwidth: Moving file storage and identity to the cloud increases reliance on your internet connection. Ensure your business has sufficient upload and download bandwidth to support staff accessing SharePoint, OneDrive, and Azure AD during business hours.
Connectivity dependency: Cloud services require an active internet connection. If your internet service is interrupted, staff may be unable to access files or log in to devices joined to Azure AD.
Migration downtime: Schedule data migration and cutover outside normal business hours to minimise disruption. Inform staff in advance of any expected downtime.

Troubleshooting common migration issues

Issue Possible cause Resolution
Files fail to migrate to SharePoint File path too long or invalid characters in file name Shorten file paths or rename files before running the SharePoint Migration Tool again.
User cannot sign in with cloud credentials Device not joined to Azure AD or password not synchronised Go to Settings > Accounts > Access work or school and select Connect to rejoin the device to Azure AD.
OneDrive files not syncing OneDrive client not signed in or storage quota exceeded Sign in to OneDrive at https://onedrive.live.com and check available storage. Restart the OneDrive sync client.
Multi-factor authentication not prompting MFA not enabled for the user account In the Microsoft Entra admin centre, go to Protection > Authentication methods and verify MFA is enabled for the user.
Slow access to cloud files Insufficient internet bandwidth or Wi-Fi signal Run a speed test and consider upgrading your business internet plan or switching to a wired Ethernet connection.

Next steps

Reducing on-premise server hardware lowers your ongoing power, cooling, and maintenance costs while improving access and reliability for your team. Migrating to Microsoft 365 and Azure supports a modern workplace where staff can collaborate and work securely from any location.

If you need assistance planning your migration from an office server to Microsoft 365 and Azure, Open a Ticket.

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