What is Microsoft Azure and why does it matter for not-for-profits?
Microsoft Azure is Microsoft's cloud platform — the infrastructure layer that sits underneath Microsoft 365. Where Microsoft 365 covers email, files and collaboration, Azure covers everything else an organisation's IT environment needs: servers, databases, line-of-business applications, backup, disaster recovery and identity services.
For Australian not-for-profits, Azure matters because it changes the economics of IT. Instead of buying physical servers every five years, paying for a server room, and carrying the risk of hardware failure, an NFP can run its entire server environment in Microsoft's Australian data centres and pay only for what it uses. Combined with Microsoft's not-for-profit donation and credit programs, Azure is often cheaper than the on-premises environment it replaces — before you count the reduction in risk.
The shift also matters for compliance. Funders, auditors and cyber insurers increasingly ask where data is stored, how it is backed up, and who can access it. Azure gives an NFP enterprise-grade answers to those questions: data residency in Australian regions, geo-redundant backup options, and identity controls through Microsoft Entra ID that small organisations could never afford to build themselves.
What Azure credits and donations are available to Australian NFPs?
Microsoft provides Azure benefits to eligible not-for-profits through its Tech for Social Impact program, administered in Australia through Connecting Up. The headline benefit is an annual Azure credit — currently US$2,000 per year for eligible organisations — which can be applied against most Azure services including virtual machines, storage, backup and databases.
Beyond the credit, Microsoft offers discounted pricing on many Azure services for NFPs, and donated or heavily discounted licences for the surrounding stack: Microsoft 365 Business Premium is donated for the first ten users, and Entra ID (the identity platform that secures Azure) is included with Microsoft 365 at no extra cost.
Eligibility requires registration with Connecting Up and validation of your organisation's charitable status — ACNC-registered charities and equivalent bodies qualify. The credit renews annually but does not roll over, so it pays to plan workloads that use it fully: backup and disaster recovery are the most common starting points because they deliver immediate risk reduction for a predictable cost.
A practical note: the US$2,000 credit covers a modest workload — typically backup for a small server environment, or a couple of lightly used virtual machines. Organisations running larger environments should treat the credit as a subsidy on top of a properly budgeted Azure spend, not as the whole funding model.
Which workloads should an NFP move to Azure first?
Not everything belongs in the cloud, and the order matters. Based on the migrations we run for Australian NFPs, this is the sequence that delivers value fastest:
Backup and disaster recovery first. Azure Backup and Azure Site Recovery replace tape drives, USB disks and the hope that the server room never floods. This is usually the cheapest workload to move, uses the donation credit efficiently, and immediately answers the funder question "what happens if your systems fail?".
File servers second. Most NFP file servers are better served by SharePoint and OneDrive (already included in Microsoft 365) than by an Azure virtual machine. Where a genuine file server is still needed — large CAD files, legacy applications that require a mapped drive — Azure Files or a Windows Server VM in Azure fills the gap.
Line-of-business applications third. Case management systems, CRMs and finance packages that currently run on a server under someone's desk are the highest-risk workloads in most NFPs. Moving them to Azure — or better, to the vendor's hosted version if one exists — removes the single point of failure.
Identity throughout. Microsoft Entra ID should underpin every stage: conditional access, multi-factor authentication and single sign-on apply equally to cloud and remaining on-premises resources, and they are the controls cyber insurers ask about first.
How does Azure pricing work for a small NFP?
Azure uses consumption pricing: you pay for what you run, per hour or per gigabyte. That is a different budgeting model from a server purchase, and it catches some organisations out — a virtual machine left running at full size around the clock costs more than the same machine sized correctly and shut down outside business hours.
For a typical small NFP (10–50 staff) the monthly Azure bill after migration usually lands between $150 and $600 AUD, covering one or two virtual machines, backup, and storage — partially offset by the annual credit. The variables that move the number are VM size, storage volume, backup retention, and whether any SQL Server licences are required.
Three disciplines keep costs predictable. First, right-size: most on-premises servers are over-specified, and the Azure equivalent is usually a smaller VM than expected. Second, use reservations: committing to a one- or three-year term on a VM that runs permanently cuts its cost by up to 40 percent. Third, set budget alerts: Azure can email you when spend crosses a threshold, so there are no invoice surprises.
A managed service provider with NFP experience will model this before migration and commit to a fixed monthly figure, which converts an unpredictable consumption bill into a line item a board can approve.
What security and compliance controls does Azure give an NFP?
Azure's Australian data centres (Sydney, Melbourne and Canberra) carry certifications that no NFP could achieve in its own server room: ISO 27001, IRAP assessment against the Australian Government's Information Security Manual, and PCI DSS among others. Data stored in Australian regions stays in Australia, which answers the data residency question most funders and some legislation now ask.
On top of the platform, the controls that matter most for NFPs are the ones you configure. Multi-factor authentication and conditional access through Entra ID. Encryption of data at rest and in transit, on by default. Role-based access control so volunteers and contractors see only what they need. Immutable backup copies that ransomware cannot encrypt. Audit logging through Microsoft Purview that records who accessed which client record and when.
For NFPs handling sensitive client information — family services, health data, case notes — these controls map directly onto the Australian Privacy Principles and the Notifiable Data Breaches scheme. Azure provides the capability; the obligation to configure it correctly stays with the organisation, which is where a governance review before migration pays for itself.
How does Mycelium 365 help not-for-profits move to Azure?
We start with an assessment of the current environment: what servers exist, what applications run on them, what the data residency and privacy obligations are, and what the funder and insurer questionnaires are asking. That produces a migration plan with a fixed monthly cost model the board can approve before anything moves.
The migration itself is staged: backup first so there is a safety net from day one, then files, then applications, with identity controls configured throughout. We handle the Connecting Up registration and the Azure credit application as part of the engagement, and we monitor consumption monthly so the bill never surprises you.
After migration, the environment is managed under the same agreement as your Microsoft 365 tenancy: patching, backup verification, security monitoring and helpdesk, with a named team rather than a shared queue. If your NFP is running ageing servers or preparing for a funder audit, contact us for an Azure readiness assessment.