SOFTWARE AND SUBSCRIPTIONS · QUICKBOOKS ONLINE & XERO
How to Categorize Microsoft 365 and Azure in QuickBooks and Xero
Last Updated: October 5, 2026Microsoft bills the same business through completely different channels, and they do not belong in the same account. Microsoft 365 is per-seat software that tracks headcount and barely moves. Azure is metered infrastructure that can double because someone left a test environment running. A single MICROSOFT rule puts a volatile cost inside a stable line, which is exactly where nobody notices it growing.
The Short Answer
| What the charge actually is | Microsoft 365 (per-seat), Azure (consumption-based infrastructure), Microsoft Store (hardware or apps), or a Dynamics licence. |
| Where each belongs | 365 → software subscriptions. Azure → hosting or infrastructure, separately. Hardware → equipment, possibly an asset. |
| QuickBooks Online default | Office Expenses or a custom Software and Subscriptions; a custom Hosting account for Azure. |
| Xero default | Subscriptions; a custom Cloud Services account for Azure. |
| Expense or balance sheet | Monthly billing is an expense. An annual commitment paid up front is a prepayment, and so is Azure reserved capacity bought for a year. |
| Bank feed descriptor | Commonly MICROSOFT or MSFT with a product reference; Azure usually carries an Azure or subscription identifier. |
Azure Does Not Belong in Your Software Line
Microsoft 365 is stable: it tracks headcount and changes slowly. Azure is metered consumption, and it moves with usage, mistakes and growth.
Put both in one account and a fluctuating infrastructure cost is averaged into a stable software figure, so nobody reviews either. The month Azure doubles, the combined line looks only mildly higher and the cause is invisible.
Separate accounts make this manageable: software tracks headcount, infrastructure tracks usage, and an unexpected jump in the second has a visible cause. For any business with meaningful Azure spend this is among the highest-value splits in the whole chart of accounts.
Licence Count Versus Headcount
Microsoft 365 bills per seat, usually on an annual commitment. Seats are added when people join and almost never removed when they leave — and because an annual commitment would not refund the difference anyway, there is no feedback at all.
The control is a quarterly comparison of licences billed to people employed. It takes minutes and needs no tooling, and on Microsoft it routinely finds seats nobody uses. The same check applies to every per-seat tool you buy.
Microsoft 365 and Azure Categorisation FAQs
Should Azure and Microsoft 365 be in the same expense account?
No. Microsoft 365 is per-seat software that barely moves; Azure is metered consumption that can jump sharply. Combining them hides the jump inside a stable-looking line. Separating them means an unexpected increase in infrastructure has a visible cause, which is the point of having accounts at all.
Is an annual Microsoft 365 payment a prepayment?
Largely, yes — most of it relates to future months. If the amount is material to your monthly figures, record it as a prepaid asset and release a twelfth each month; expensing it all on payment makes one month look bad and eleven look good. For small amounts the entry may not be worth making.
This page is about where the transaction belongs in your books. Whether a cost is deductible, and how it is treated on a return, is a question for your CPA — and consistent categorisation is what lets them answer it without guessing. Dedicated bookkeepers from $75/month, extra hours at $15/hour, wholesale $10/hour for CPA firms, with a 100% money-back guarantee on your 1st retainer, refundable on the unused balance.
Related Resources
Stop Deciding This Every Month
A dedicated bookkeeper who codes Microsoft 365 and Azure the same way every time — from $75/month with a 100% money-back guarantee on your 1st retainer, refundable on the unused balance.