TECHNICAL REFERENCE

Microsoft Stack for Australian NFPs — Reference

Technical reference for what's actually in the Microsoft cloud-for-nonprofit stack and how it fits together. For IT leads, technical evaluators, and CTOs assessing whether to build on Microsoft. Not a sales page — the sales angle lives on the NFP industry page and crmfornfp.com.au.

Stack Components

What each layer does, the SKU it lives under, and what it's for in an NFP context.

Component SKU / product NFP use
CRM coreDynamics 365 Customer ServiceCase management, intake, knowledge base, multi-channel.
Marketing / journeysCustomer Insights – JourneysConsent-managed comms, segmentation, member journeys. Mailchimp-replacement.
Customer 360 dataCustomer Insights – DataStakeholder unification across systems. Different SKU from Journeys — check what you need.
Self-service portalPower PagesClient and member portals. Shares CRM security model.
Workflow automationPower AutomateApproval flows, integrations, scheduled jobs. Per-flow or per-user licensing.
Custom appsPower Apps (model-driven & canvas)Field worker apps, intake forms, internal tools.
AnalyticsPower BIBoard reporting, funder dashboards, operational KPIs.
ProductivityMicrosoft 365Email, Teams, SharePoint, OneDrive. NFP grants commonly cover up to 300 users.
Common data modelMicrosoft Cloud for NonprofitAdds NFP-specific entities (constituents, fundraising, program delivery) on top of Dataverse.

NFP Licensing Reference

What's available to eligible Australian NFPs registered with the ACNC. Always verify current rates with Microsoft — this is reference only, not a quote.

Microsoft 365 grants

Grant licensing for up to 300 users for eligible NFPs. Covers email, Teams, SharePoint, OneDrive (Business Standard / Business Premium tiers).

Dynamics 365 discounts

Up to ~60% discount on Dynamics 365 licensing for eligible NFPs (current at time of writing; always reconfirm).

Azure credits

Annual Azure credit grants are available for eligible NFPs — useful for hosting Power Pages portals and custom integrations.

Eligibility

Registered with the ACNC; must align with Microsoft's anti-discrimination policy. Verification handled via TechSoup or Microsoft directly.

Architecture Choices to Make Early

The decisions that hurt to reverse later. Worth thinking about before any implementation kicks off.

Microsoft Cloud for Nonprofit: yes or no?

Adds NFP-specific entities but locks you into Microsoft's NFP data model. Useful if your work fits it; constraining if not.

Customer Insights — Data or Journeys?

Two separate SKUs. "Data" is the CDP. "Journeys" is the marketing automation. Don't buy both unless you actually need both.

Power Pages identity model

Power Pages can use Microsoft Entra (Azure AD), local accounts, or external providers. Choose with future SSO requirements in mind.

Region: Australia East or Southeast?

Default to Australia East (Sydney) unless you have specific Melbourne-DR or latency reasons. Cross-region replication available.

For the productised version: crmfornfp.com.au

If you'd rather not assemble the stack yourself, our MNFP product is the Dynamics 365 + Microsoft Cloud for Nonprofit configuration packaged for Australian NFPs — same Microsoft components, configured and supported.

Visit crmfornfp.com.au

Also relevant

Microsoft Cloud for Nonprofit (blog)

Practical guide to the nonprofit cloud licensing programme.

Read the guide

Power Platform licensing (blog)

The licensing gotchas everyone hits with Power Apps and Power Automate.

Read the guide

NFP CRM for government-funded NFPs

The compliance-focused angle — DEX, CHSP, NDIS.

View compliance page

Want to talk to an Australian Microsoft partner?

Book a 30-minute discovery call. No pitch deck. Practical conversation about whether we're a fit.