Download blank audit templates: SaaS License Audit Workbook (.xlsx) · CSV Worksheet (.csv)

Software subscription sprawl rarely happens in one bad purchase order. A department manager puts a project tool on a company card, an employee leaves in the spring while their CRM and Adobe seats stay assigned on an annual plan, or every new hire gets top-tier enterprise licensing by default regardless of what their job actually involves. Wait until the renewal invoice hits accounts payable and it is usually too late to adjust anything. Most annual B2B contracts require 30 to 90 days of written notice before you can drop seats.

So how do you get ahead of that cycle without taking away tools people actually use? Pair the downloadable worksheets above with a quarterly review across your accounting ledger, your identity provider's sign-in logs, and your contract notice calendar. (Any sample rows in the downloaded files are illustrative formatting examples; replace them with exports from your own ledger and tenant.)

Start in Accounts Payable Rather Than the SSO Portal

When teams decide to audit software spend, the first instinct is usually to ask IT for an export of applications wired into single sign-on. That list helps, though it is not sufficient on its own. Your identity provider has no idea about departmental subscriptions charged straight to corporate credit cards or reimbursed every month on employee expense reports.

Pull a trailing 12-month export from your accounting ledger, corporate card feeds, and expense system filtered for software, cloud, telecom, and subscription vendors. Grouping a full year of charges by merchant turns up both the quiet monthly creep and the annual renewals that bill once every twelve months and vanish from memory in between.

Cross-Checking Paid Seats Against HR and Sign-In Logs

Once you know what the company pays for, compare assigned seats in your largest platforms (Microsoft 365 or Google Workspace, Salesforce or HubSpot, Slack, Zoom, Adobe, GitHub, Jira, DocuSign) against your active HR roster and 90 days of authentication logs. In Microsoft Graph PowerShell, a single query exports every licensed Entra ID user right next to their most recent sign-in timestamp:

# Export licensed Microsoft Entra ID users with last sign-in activity (requires AuditLog.Read.All, User.Read.All)
Connect-MgGraph -Scopes "User.Read.All","AuditLog.Read.All"

Get-MgUser -All -Property DisplayName,UserPrincipalName,AccountEnabled,AssignedLicenses,SignInActivity |
  Where-Object { $_.AssignedLicenses.Count -gt 0 } |
  Select-Object DisplayName,
                UserPrincipalName,
                AccountEnabled,
                @{Name="LicenseCount";Expression={$_.AssignedLicenses.Count}},
                @{Name="LastInteractiveSignIn";Expression={$_.SignInActivity.LastSignInDateTime}} |
  Export-Csv -Path "./m365-licensed-users-audit.csv" -NoTypeInformation

Sorting that CSV next to your HR roster almost always surfaces the same handful of habits. Disabled accounts from past offboardings sit near the top. Blocking sign-in when someone leaves protects access, yet Microsoft keeps billing for the license every month until an admin converts the Exchange mailbox (when under 50 GB and free of special retention requirements) to a shared mailbox and removes the paid SKU. Service accounts show up right beside them: copiers, scanners, and alerting scripts assigned full desktop Office bundles when a mail-flow connector or app registration would do the job.

Active employees accumulate quiet overlap too. Look for standalone Audio Conferencing, Defender, or Entra ID P1 add-ons still attached to staff whose base bundle already includes those exact entitlements. Then check specialty tools such as Visio, Project, Power BI Pro, Creative Cloud, and paid CRM seats with zero logins over 90 days. Moving dormant seats to free viewer tiers or assigning licenses on request trims recurring cost before you ever touch anyone's daily workflow.

Matching Microsoft 365 Tiers to Real Job Duties

Maybe the bigger question on a Microsoft 365 agreement isn't how many seats are idle, but why every employee sits on the same SKU in the first place? It is not unheard of for companies under 300 employees to place the entire staff onto enterprise E3 or E5 plans, even though Microsoft 365 Business Premium covers up to 300 seats with desktop Office apps, Intune device management, Conditional Access, and Defender for Business. Compare published US commercial annual-commitment list rates below (and verify current Microsoft and CSP pricing as of late 2026 before changing agreements):

Microsoft 365 Plan (Reference List Rate) Tenant Cap Key Included Capabilities Typical Role Fit
Business Basic (~$6 / user / mo annual) 300 seats Web/mobile Office, 50 GB Exchange mailbox, Teams, SharePoint; no desktop apps or Intune Frontline, warehouse, seasonal, or kiosk staff working exclusively in a browser
Business Premium (~$22 / user / mo annual) 300 seats Desktop Office apps, Intune MDM, Entra ID P1 (Conditional Access), Defender for Business Primary tier for knowledge workers in organizations under the 300-seat limit
Microsoft 365 E3 (~$36 / user / mo annual) Unlimited Desktop Office, 100 GB mailbox, auto-expanding archive, Intune P1, Entra ID P1, Windows Enterprise Organizations above 300 seats or roles needing 100 GB+ compliance mailboxes
Microsoft 365 E5 (~$57 / user / mo annual) Unlimited Adds Entra ID P2, Defender XDR suite, Teams Phone System, Power BI Pro, Purview eDiscovery Premium Targeted security administrators, Power BI authors, or regulated compliance roles

Consider how the math looks on a 120-person company at those reference list rates. Putting all 120 employees uniformly onto Microsoft 365 E5 comes out to $82,080 per year. Assigning 100 standard office staff to Business Premium ($22/mo), 15 frontline staff to Business Basic ($6/mo), 5 administrators and compliance leads to E5 ($57/mo), and 10 standalone Power BI Pro add-ons ($10/mo) brings the modeled total down to $32,100 per year—provided none of the reassigned Business Premium users rely on E5-only features like Teams Phone, 100 GB mailboxes, or Purview eDiscovery Premium. Check active mailbox sizes, retention holds, and security dependencies before downgrading any seat.

Balancing Annual and Monthly Microsoft NCE Commitments

Under Microsoft's New Commerce Experience (NCE), annual-commitment subscriptions lock in your minimum seat count for a full 12 months once a brief 7-day cancellation and reduction window closes. Putting all of your peak seasonal or contractor headcount onto annual NCE leaves you paying for empty seats long after the busy stretch ends.

Does paying the ~20% monthly rate premium on monthly-term NCE SKUs sting a little? Per month, sure. Compared to paying twelve months for seasonal or project seats you only needed for four, splitting your tenant—steady baseline headcount on annual commitments, variable and transitional seats on monthly NCE—almost always comes out cheaper.

Tracking Notice Deadlines Instead of Expiration Dates

Calendar reminders set on a contract's expiration date fire too late to help. Because most B2B SaaS agreements auto-renew for another 12-month term unless written notice arrives 30, 60, or 90 days ahead of renewal, record both the renewal date and the contractual notice window in your audit workbook. Set your review reminder 30 days ahead of the notice deadline itself, such as October 1 for a December 31 contract carrying a 60-day notice clause.

Pairing this check with your quarterly user access review makes sure revoked accounts release their paid licenses right away, and our software licensing and procurement page explains how we put together written quotes you can compare straight against vendor retail pricing.