The fastest Microsoft 365 cost optimization wins come from four moves: reclaiming inactive licenses, rightsizing seats to actual usage, converting departed employees' mailboxes before they renew, and gating Copilot before it generates surprise charges. Most teams see measurable savings within a few months from unassigning and converting alone, with rightsizing and renewal prep adding more savings over time. The rest of this guide walks through the evidence, tools, and governance that make those savings stick.
TL;DR:
- Flag accounts with no activity for 60 days, then verify employment status and role needs before removal; activity reports can miss virtual desktop use.
- Convert departed employees’ mailboxes to shared mailboxes when access must continue; deleting accounts frees licenses immediately, but Exchange data is retained for only 30 days.
- Match E5 to advanced security, compliance, or voice needs, E3 to desktop app users, and E1 or Business tiers to browser app users; review quarterly.
- Copilot connectors and custom extensions can trigger usage billing through Copilot Credits beyond the base license, so restrict access, pilot features, and set alerts.
- Existing customers keep current pricing until renewal; request a quote at least 90 days beforehand and bring SKU counts, usage evidence, and planned packaging changes.
Table of Contents
- Quick savings checklist: what to run in the next 30-90 days
- Audit and evidence: how to use Microsoft 365 reports to find license waste
- Rightsizing and license lifecycle: match users to the right SKU
- Copilot and add-on cost control: prevent consumption surprises
- Renewal and negotiation playbook for 2026 packaging changes
- Governance and ops: making the savings stick
- Practitioner perspective: when to DIY and when to bring in help
- How we support your license cleanup
- FAQ
- Sources
Quick savings checklist: what to run in the next 30-90 days
Start with the moves that cost nothing but admin time, then layer in rightsizing and renewal prep as you gather usage evidence.
- Week 1-2: IT admin pulls the Active Users report and flags accounts with no sign-in activity in 60+ days.
- Week 2-3: HR confirms which flagged accounts belong to departed or transferred employees.
- Week 3-4: Admin unassigns licenses for confirmed departures and converts their mailboxes to shared mailboxes where access is still needed.
- Week 4-6: Procurement and IT jointly review SKU assignments against role requirements and downgrade or upgrade as needed.
- Week 6-12: IT rolls out group-based licensing policies and sets a recurring review cadence.
A few actions require no purchase at all and deliver savings immediately:
- Unassigning licenses from accounts with zero sign-ins in the last billing cycle.
- Converting a departed employee's mailbox to a shared mailbox instead of keeping a full license active.
- Revoking unused add-ons (Visio, Power BI Pro, Copilot seats) assigned to accounts that never opened the app.
Pro Tip: Before unassigning anything, export a snapshot of current license assignments to a dated CSV so you have a rollback reference if someone disputes a removal.
Audit and evidence: how to use Microsoft 365 reports to find license waste
Guesswork is the single biggest reason rightsizing projects stall or get reversed. The Microsoft 365 admin center usage reports give you the raw signal: Active Users, Microsoft 365 Apps Activations, and mailbox storage reports can all be exported to CSV directly from the Reports section of the admin center.
Usage data by itself is not proof of waste. A user who never opens Excel on their laptop might be running it daily through a virtual desktop, and a sales rep who looks "inactive" in Teams might be living in Outlook. Cross-reference every flagged account against HR data and role expectations before you touch a license assignment.
A pragmatic first pass costs almost nothing: unassign clearly inactive accounts, convert departed employees' mailboxes, then run a 60-90 day pilot collecting usage data before making larger rightsizing calls across the organization.
A minimal data model keeps this process honest:
- User identity: name, department, manager, and employment status.
- Role expectations: what tools the job actually requires (Teams, Excel, Power BI, Copilot).
- Last activity: sign-in date and app-level activation data.
- Current SKU: which license and add-ons are assigned today.
- Recommendation: keep, observe, or rightsize.
For organizations with more than a few hundred seats, manual CSV review becomes impractical. PowerShell scripts and Microsoft Graph API calls can automate the export and scoring, pulling license assignment and activity data on a schedule rather than a one-time pull.
One retention warning matters here: deleting a user account and unassigning a license are different operations with different consequences. According to Microsoft's license assignment guidance, deleting a user frees the license immediately but Exchange mailbox data is only retained for 30 days afterward, so a straight deletion without an export or archive plan can mean permanent data loss.
Rightsizing and license lifecycle: match users to the right SKU
Rightsizing is not about buying the cheapest plan available. It's about matching the SKU to what the role actually requires, then removing everything else.
- E5 makes sense for users who need advanced security, compliance, or voice features built in, not for users who simply "might need them someday."
- E3 covers the bulk of knowledge workers who need full desktop apps, Exchange, and SharePoint without the advanced compliance stack.
- E1 or Business Basic/Standard fits users who live mostly in browser-based apps and Teams, with no need for desktop Office installs.
Departed employees need a lifecycle decision, not a default deletion. Converting a mailbox to a shared mailbox, as described in SendSync's overview of shared mailbox behavior, keeps the content accessible to a team without paying for a full license, though it requires manual conversion steps and ongoing access management. Where legal or compliance holds apply, an archived mailbox with a retention policy is often safer than either option.
Group-based licensing, assigning licenses to a security group rather than individual users, removes a large share of manual assignment errors and makes offboarding automatic when someone is removed from the group.
The 2026 Microsoft 365 packaging and pricing updates change the calculus here. Existing customers stay on current pricing until their renewal date, but packaging changes rolling out from June 2026 mean the SKU that made sense last year may bundle differently going forward. Treat your next renewal as a checkpoint to re-verify every tier assignment rather than auto-renewing the same mix.
Pro Tip: Run rightsizing changes in a test security group first and monitor help desk tickets for two weeks before applying the same change tenant-wide.
Copilot and add-on cost control: prevent consumption surprises
Copilot licensing is not a flat per-seat cost in every scenario. According to Microsoft's cost considerations for Copilot extensibility, certain actions, particularly connectors that pull in shared tenant data or custom extensibility features, can trigger usage-based billing through Copilot Credits on top of the base license.
Before rolling Copilot out broadly, put controls in place:
- Restrict who can enable connectors to a small admin group rather than leaving it open to all users.
- Run new Copilot features as scoped pilots with a fixed group of users before a tenant-wide rollout.
- Set up consumption alerts so finance and IT see usage-based charges building before the invoice arrives.
- Understand the difference between declarative agents, which are generally lighter weight and cheaper to run, and custom engine agents, which often carry separate hosting and consumption costs.
Teams running Copilot extensions on Azure infrastructure should also look at how those hosting costs interact with the base Microsoft 365 spend. Our Azure cost optimization runbook covers the hosting side of that equation in more depth.
Renewal and negotiation playbook for 2026 packaging changes
Your current Microsoft 365 agreement does not change automatically when pricing updates are announced. Per Microsoft's own 2026 packaging and pricing announcement, existing customers remain on their current pricing until renewal, which means the real work is making sure you walk into that renewal with evidence, not assumptions.
Build a negotiation dossier well before the renewal date:
- Pull exact seat counts by SKU, including how many seats have been unassigned or converted in the past 12 months.
- Attach usage evidence from your audit, showing which SKUs are genuinely needed versus overprovisioned.
- Document any pilots already running (Copilot, add-ons) and what scope you expect to request at renewal.
- List desired packaging changes, including any SKUs you want to drop, add, or swap under the new packaging structure.
- Identify your negotiation levers: phased seat commitments, scoped pilot pricing, or multi-year terms in exchange for rate protection.
For larger agreements, a Software Asset Management (SAM) function or a trusted advisor becomes valuable at this stage, particularly when Enterprise Agreement terms or true-up clauses are involved. Smaller organizations on monthly or annual Business plans typically have simpler decisions to make but still benefit from going into the conversation with real usage numbers rather than guesses.
Pro Tip: Request your renewal quote at least 90 days out so you have time to run a final usage audit and adjust seat counts before the new terms lock in.
Governance and ops: making the savings stick
A one-time cleanup drifts back to waste within a year without a governance model behind it. Set a recurring cadence: a monthly check on new hires and departures, and a quarterly full license audit against the usage data model described earlier.
Tie license assignment directly to your onboarding and offboarding workflow. When HR marks an employee as terminated, that event should trigger license removal or mailbox conversion automatically rather than waiting for someone to remember. Our Entra ID governance guide covers how group-based licensing and identity policies support this kind of automation.
- Automate license reclamation with Microsoft Graph or PowerShell scripts rather than manual admin center clicks.
- Integrate license data with your CMDB or SAM tooling so cost tracking lives alongside asset tracking.
- Track a small set of KPIs: unused license count, average days-to-reclaim after departure, and Copilot consumption trend.
| Action | Primary owner | Expected impact |
|---|---|---|
| Monthly inactive-user review | IT admin | Prevents license waste from accumulating |
| Quarterly SKU rightsizing audit | IT and procurement | Keeps spend matched to actual usage |
| Offboarding automation | IT and HR | Removes delay between departure and reclamation |
| Copilot consumption review | IT admin and finance | Catches usage-based billing before it compounds |
Practitioner perspective: when to DIY and when to bring in help
Most of this playbook is within reach for a lean IT team with basic PowerShell skills and under a few hundred seats. The calculus changes with Enterprise Agreement complexity, multi-tenant Copilot extensibility, or compliance-driven retention tradeoffs, situations where a mistake costs more than a consultant's time. If your renewal involves true-up clauses or your Copilot rollout touches shared tenant data, bringing in outside expertise before you negotiate or deploy is usually the cheaper path.
— jaras
How we support your license cleanup
Running the audit, rightsizing, and governance steps above takes real hours that a lean IT team may not have free, especially alongside a renewal deadline. Our Enterprise Intelligence Assessment starts with a free review of your current license assignments, usage patterns, and renewal timing, and produces a prioritized, plain-language plan you own regardless of what you do next.
From there, the engagement model depends on what your team needs:
- Fractional CTO engagements for organizations that want ongoing strategic oversight of licensing, security, and cloud spend without a full-time hire.
- Cloud & Training support to help your internal team run the automation and governance processes described in this guide.
- Custom Apps development when your license tracking needs integration with internal HR or CMDB systems beyond what off-the-shelf tools cover.
If your next renewal is within 90 days, start with the Enterprise Intelligence Assessment to get a documented baseline before you talk to Microsoft or your reseller.
FAQ
What's the cheapest way to buy Microsoft 365?
The lowest-cost path is usually matching each user to the smallest SKU that covers their actual role requirements, then adding group-based licensing so seats are never left assigned to inactive accounts. Volume licensing or an Enterprise Agreement can lower per-seat rates for larger organizations, but only after usage data confirms the seat count is accurate.
Why does Microsoft 365 cost so much?
Costs climb mainly from license sprawl: unused seats, departed employees still holding full licenses, and add-ons like Copilot or Power BI Pro assigned but never opened. The 2026 packaging and pricing updates also change feature bundling, which makes periodic SKU review more important at renewal time.
How to get 50% off Microsoft 365?
Organizations that document usage evidence before renewing typically have stronger negotiating positions than those renewing their existing seat count by default.
Is there a cheaper option for Microsoft 365?
Lower-tier SKUs like Business Basic or E1 cost less than E3 or E5 and fit users who don't need desktop app installs or advanced compliance tools. The cheaper option for most organizations is not switching platforms but rightsizing the mix of SKUs already in use based on the Active Users and apps activation reports.
Sources
- Microsoft 365 Packaging and pricing updates (2026) — Microsoft Licensing
- Microsoft 365 admin center usage reports — Microsoft Learn