Flamingo Raises $4.5M Seed Round

Skip to content

Software license audit: get ahead of the letter

Best Practices
MSP
IT Operations
Conrad LunderstedtConrad Lunderstedt
September 28, 2026
1,123 views
Software license audit: get ahead of the letter

A software license audit guide for MSPs and IT teams: the 5-step prep, a per-client checklist, the records that prove compliance, what Microsoft, SPLA, VMware, IBM and Oracle audits check in 2026, the first 30 days after a letter, and a worked penalty example.


Updated: November 2026

A software license audit checks what an organization installs and uses against the licenses it can prove it owns. Vendors like Microsoft, Oracle, Broadcom and IBM run them under the audit clauses in their contracts, and a gap you find yourself costs less than one Microsoft bills back at 125% of the current price. This guide covers how to prepare, the checklist and records that prove compliance, what each vendor checks in 2026, and the first 30 days after a letter.

TL;DR

  • Definition. A software license audit checks every installed or assigned license against what the organization legally owns.
  • Frequency. Flexera's 2026 report says 48% of organizations were audited in the past year.
  • Penalty. Under Microsoft's customer agreement, 5% or more unlicensed use means 125% pricing plus audit costs.
  • Clock. Autodesk gives 15 days to respond, Microsoft 30 days' notice, Oracle 45.
  • Proof. Agreements, invoices, vendor portal entitlements and dated tool exports, kept per product and per legal entity.
  • 2026 watch list. Microsoft tenants, Oracle Java's per-employee count, VMware usage reporting every 180 days, IBM sub-capacity reports and SPLA monthly reporting.
  • Opportunity. An MSP that audits first saves the client the penalty and gets a billable service.

What is a software license audit?

A software license audit checks every piece of software installed, assigned or used in an organization against the licenses it owns. A vendor can run it through an auditor it appoints, or you can run it on yourself. The output is a gap: what you use without a license, and what you pay for and don't use.

Vendors don't always call it an audit. A "license review," a "SAM engagement" or a friendly spreadsheet request from Adobe or Oracle can turn contractual fast, so treat any of them as the start of one.

A software license assessment or license review runs the same comparison without the audit clause behind it. Your own team, a reseller or a SAM partner does the counting, and the results stay with you. In a license audit, the vendor's auditor collects the data and every finding comes with a price, so run the assessment first and audit your software licenses on your own schedule.

Flexera's 2026 report (512 respondents, June 2026) found 48% of organizations were audited in the last year, yet only 36% have full visibility of their IT estate. Microsoft tops the list, with 64% audited by Microsoft in the past three years. Oracle's share jumped from 24% to 38% in a year, and Adobe's from 24% to 32%.

Why audit letters land on MSP desks now

The last 18 months have been busy. In May 2025, Broadcom sent cease-and-desist letters to VMware perpetual-license holders whose support had lapsed. The letters told them to remove every patch installed after support ended and warned of audits. Dean Colpitts, CTO of Canadian MSP Members IT Group, said one of his clients got its letter six days after its support contract expired.

The lawsuits followed. VMware sued Siemens in March 2025 over a Siemens list of 23,000 US deployments, per Network World's timeline. Tesco has a UK High Court claim of at least £100M against Broadcom, VMware and Computacenter.

Then Broadcom went further. VMware Cloud Foundation 9 licensing requires a license usage file sent to Broadcom at least every 180 days. Miss it, and VMware's licensing overview says running workloads keep going but disconnect from management, and no new workloads can be created. Broadcom has built the audit into the product.

Oracle is on a similar path with Java. Its Java SE Universal Subscription counts every employee, plus the staff of contractors and outsourcers who support the business, whether or not they run Java. The October 8, 2026 price list sells smaller organizations annual bands, $1,000 a year for up to 100 employees and $10,000 for up to 500, plus $147.20 a year for each employee from 501 to 2,999. From 3,000 employees it's $10.50 per employee per month.

A Dimensional Research survey reported by The Register found 73% of Oracle Java users had been audited in three years. The survey was commissioned by the ITAM Forum and Azul, which sells Java alternatives, so read it with that in mind.

The MSP angle shows up in the details. Vendor telemetry doesn't care whose laptop is running the software. In January 2026, Autodesk contacted an MSP's client with a list of the MSP's own staff usernames, software versions and days of use, then asked the client for the MSP's contact details.

The comments add more: a fully licensed shop flagged after a domain migration left licenses tied to old accounts, and an MSP that paid Malwarebytes after techs ran the free version on client machines. Your tooling habits end up in your client's audit.

What triggers a software license compliance audit?

Vendors pick audit targets from signals they can see from their side of the contract. A software license compliance audit follows one of the signals below, so they also tell you where to look first.

TriggerWhat the vendor seesWhat to check first
Renewal or true-upYour counts versus last year'sHeadcount growth, new sites, new servers
Support lapses or downgradesA customer still running the product without payingPatches installed after the support end date (Broadcom's letter targeted exactly this)
Merger, acquisition or new legal entityLicenses tied to an entity that changedWhich entity signed the agreement, and whether licenses transfer
Product telemetryInstalls, usernames, days of useFree or trial versions on work machines, installs on the wrong domain
Usage reportingA usage file or monthly report that's late, missing or lower than last timeVMware usage file dates, SPLA monthly reports, IBM sub-capacity reports
Tenant signalsOne license unlocking a feature for everyonePremium identity features like Conditional Access used tenant-wide
Spend dropA customer who cut the budget but not the usageDowngraded tiers, cancelled SKUs still deployed

The tenant-signal row is the one closest to MSPs, because it lives in the systems you administer. A single Entra ID P1 license in a tenant doesn't license every user for P1 features. Microsoft can see that from its side.

Software license audits to expect in 2026

Flexera's survey and the vendors' own contract changes point to the same short list for 2026. Here's what each vendor counts and how long you get.

Vendor2026 signalWhat it countsContract clock
Microsoft64% of Flexera respondents audited in three yearsUsers, devices and server cores, plus premium features against premium licenses30 days' notice, 125% pricing over 5%
Oracle (Java)Audit share up from 24% to 38% in a yearEvery employee for Java SE Universal Subscription45 days' notice, 30 days to fix
AdobeAudit share up from 24% to 32%Named users, shared or generic accounts30 days to hand over data
Broadcom (VMware)Usage file every 180 days on VCF 9Physical cores, at least 16 per CPU, and raw vSAN TiBLicenses treated as expired when usage goes unreported
IBMSub-capacity reporting through ILMTPVU or VPC capacity of the virtual machines IBM software runs onFull-capacity charges when reporting is missing
AutodeskProduct telemetry with usernamesNamed users, versions, days of use15 days to submit results

Microsoft, VMware and IBM need the deepest technical prep on an MSP's side, so they get their own sections below. SPLA, where the MSP itself is the one audited, sits in the MSP risk section further down.

Microsoft software license audit process

A Microsoft software license audit follows the same arc under every agreement. A letter announces the review and names the auditor, an NDA and a kickoff call set scope and dates, and your team hands over usage data. The auditor sends a draft report, you challenge it line by line, and the final report goes to Microsoft for the commercial settlement. Under the Microsoft Business and Services Agreement you then have 30 days to buy what's missing, and under the Microsoft Customer Agreement unlicensed use over 5% also carries Microsoft's audit costs.

No single Microsoft tool produces an audit-ready position. Tenant licenses and assignments come from the Microsoft 365 admin center, and classic volume licensing agreements sit on its Volume licensing pages since the Volume Licensing Service Center was retired in April 2024. CSP subscriptions come from Partner Center, and server installs, editions and core counts come from your RMM inventory, so match all four sources before the auditor does.

VMware license audit checklist

Broadcom's licensing changes turned VMware into a standing audit risk for every client still on vSphere. Run this checklist per client before the next renewal conversation with Broadcom.

  • Support dates against patch dates. List each host's support end date and every patch installed after it. Broadcom's May 2025 letters targeted exactly that.
  • Core counts. Count physical cores per host, with a minimum of 16 per CPU, and raw vSAN capacity in TiB. Broadcom's KB 313548 includes a script that does the count.
  • Usage reporting. On VCF 9, check the date of the last license usage file. VCF 9.1 sends usage every 24 hours in connected mode, and disconnected sites still send it by hand every 180 days.
  • Keys and entitlements. Match every license key or license file in use to a current subscription or a perpetual entitlement, and record which entity holds it.
  • Hosting partner status. If a cloud provider hosts the client's VMware, confirm Broadcom still authorizes that provider.

If the count makes a migration cheaper than a renewal, our guide to virtualization and the VMware exit covers the hypervisor options.

IBM software license audit

An IBM software license audit checks sub-capacity licensing closely, because that's where the price can jump. Sub-capacity lets a client license IBM software for the virtual machines it runs on instead of the whole physical server. The condition is reporting: IBM's sub-capacity rules require the IBM License Metric Tool (ILMT) or an approved alternative, such as HCL BigFix Inventory or Flexera One with IBM Observability. Without it, IBM charges full capacity for every physical core activated on the server.

For an MSP, the risk is a Db2 or WebSphere install on a client VM with no ILMT coverage, or an ILMT server nobody updated after a host migration. Add IBM products to the inventory step, check that ILMT reports every server, and keep its reports with the audit pack. Estates under 5,000 virtual machines can use IBM's pre-approved ILMT Lite configuration with a disconnected scanner.

How to prepare for a software license audit in 5 steps

Preparing for a software license audit means running one on yourself first. The internal audit uses the same five steps as the vendor's, on your schedule. Run it per client, once a year at minimum, and before any renewal of a major agreement.

  1. Scope it. List every vendor, contract and legal entity in play, and the audit clause of each. Evidence: the agreements themselves, including which entity signed.
  2. Inventory what's installed and used. Pull installed software per device from your RMM agent or a network discovery scan, user accounts per tenant, and SaaS sign-ins from your identity provider. Evidence: tool-generated reports with a date, not hand-built spreadsheets.
  3. Gather what's owned. Collect reseller invoices, Microsoft reseller (CSP) subscriptions, volume agreements, license keys and PDFs from vendor portals. Evidence: proof of entitlement for every product in scope.
  4. Reconcile. Match step 2 against step 3, product by product and version by version. Evidence: a gap list with an owner and a cost for each line.
  5. Fix and document. Buy what's missing, remove what shouldn't be there, reclaim what's idle, and file the evidence. Evidence: an audit pack you could hand to an auditor tomorrow.

Step 2 is where the time goes. Pulling installed software from 300 endpoints by hand is a day nobody wants. This is where an IT asset lifecycle view pays off, and where your RMM data does the heavy lifting.

OpenFrame's device inventory reads installed software from live endpoints, so a tech can ask Mingo, OpenFrame's AI agent, what's installed on which devices and get the answer from the machines themselves. Flamingo's published pricing puts a software inventory audit at 30 minutes and $24 by hand, against about a minute and $0.05 with Mingo. Matching installs to licenses in step 4 is still your job. OpenFrame doesn't track license entitlements.

For clients who want a dedicated asset register, Snipe-IT is the open-source option we've reviewed. It holds licenses, seats and assignments, so step 3 and step 4 live in one place.

Don't skip SaaS. Tools bought on a credit card never show up in an endpoint scan. Check SSO logs, OAuth grants and expense reports, the same places you'd look for shadow IT.

Software license compliance audit checklist

Copy this per client. The owner column matters more than it looks. If nobody owns a line, nobody will have the evidence when an auditor asks for it.

ItemOwnerEvidenceDone
All vendor agreements and audit clauses on fileMSP account managerSigned agreements, entity names☐
Microsoft customer agreement acceptance recordedMSP (if you're the reseller)Attestation date and signatory in Partner Center☐
Installed software per deviceMSP techDated inventory export☐
Users and licenses per tenantMSP techTenant license report☐
Premium features versus premium licensesMSP techConditional Access and security feature usage versus P1/P2 counts☐
SaaS apps outside IT's approvalMSP tech + client financeSSO logs, OAuth grants, card statements☐
Server, virtualization and database licensingMSP engineerCore counts, host lists, VMware support dates☐
License usage reports sent to vendorsMSP engineerVMware usage file dates, SPLA monthly reports, IBM ILMT reports☐
Java installs and versionsMSP techScan for Oracle JDK versus OpenJDK☐
Named-user products (Adobe, Autodesk)Client adminUser list, no shared or generic accounts☐
Commercial fontsClient marketingFont license records against installed fonts☐
Leavers still holding licensesClient HR + MSPOffboarding tickets matched to license reclaim☐
Open-source licenses in client-built softwareClient dev leadDependency scan or SBOM☐
Who owns compliance in the MSAMSP ownerThe signed MSA clause☐

The leavers line is a quiet cost. Licenses tied to people who left months ago are pure waste. Build license return into your client offboarding checklist and the problem shrinks every month.

Which records prove software license compliance

An auditor accepts records that tie a product, a quantity and a licensed entity together. Licenses bought after the letter arrives don't erase the unlicensed use the auditor finds, so the proof has to predate the letter.

RecordWhat it provesWhere it lives
Signed agreements and order formsThe licensed entity, the terms and the audit clauseContract files, vendor portals
Reseller invoicesSKU, quantity, term and buyerFinance system, reseller portal
Vendor portal entitlementsWhat the vendor itself records as ownedMicrosoft 365 admin center, Partner Center, IBM Passport Advantage, Adobe Admin Console, Autodesk Account
OEM proofLicenses that came preinstalled on hardwareThe device's purchase invoice
Dated inventory exportsWhat was installed or assigned, and whenRMM, discovery tools, tenant license reports
Usage reportsWhat you reported to the vendorVCF usage files, SPLA monthly reports, ILMT reports
Change recordsLicenses reclaimed, transferred or retiredOffboarding tickets, M&A transfer paperwork

Keep the pack per client and per legal entity, and refresh it every quarter. If you resell through CSP, the Microsoft Partner Agreement adds record-keeping of its own, covered in the MSP risk section below.

The first 30 days after an audit letter

A letter has arrived. Before anyone replies, pull the contract and find the audit clause. Every deadline that matters is in there, and they're shorter than you'd expect.

Here's what the vendors' own terms say. Microsoft's customer agreement gives 30 days' notice. Oracle's master agreement gives 45 days' written notice, then 30 days to fix any shortfall, and Oracle pays none of your costs. Adobe's 2025 terms give 30 days to hand over data. Autodesk's March 2026 terms give 15 calendar days to submit results, including machine IDs and Windows usernames.

WhenWhat to doWhy
Days 0-2Confirm the letter is a contractual audit, not a sales email. Find the agreement, the signing entity and the audit clauseSales outreach can be dressed as compliance. The clause sets your deadlines
Days 0-2Tell the client's leadership. Name one point of contactMixed messages to an auditor cost you later
Days 3-7Bring in legal counsel. Sign an NDA with the auditorMicrosoft's MBSA gives 14 days to complete the auditor NDA
Days 3-10Negotiate scope and timeline at the kickoff callScope is easiest to limit before any data leaves the building
Days 5-20Run your own inventory and reconciliation firstYou want to know the answer before the auditor tells you
Days 10-30Hand over tool-generated data, within scope onlyVolunteering out-of-scope data widens the audit
After findingsCheck every count and formula. Don't accept findings in writing until reviewedThe auditor's first number is an opening position

That last point comes from SAMexpert, an independent Microsoft licensing consultancy. Their August 2026 session walks through the full Microsoft process, including why the audit is won or lost in the data-collection phase and why SAM tool dashboards don't hold up against the auditor's counting method. It's long, but the first 15 minutes cover what to do in the first 48 hours.

One more thing about ignoring a letter. Oracle's clause lets it terminate support, licenses or the whole master agreement if you don't fix a shortfall in 30 days. Autodesk requires you to buy immediately. Silence only runs out your clock.

A worked example of what an audit finding costs

The penalty math is in the contract, so you can work it out before an auditor does. Here's a hypothetical to show the shape of it.

Take a client with 60 Microsoft 365 Business Standard licenses, at the $14 per user per month list price that took effect in July 2026 (The Register). An audit finds 62 people using the suite. Six of the 60 licenses still sit with people who left, and 8 current staff have been working without a license of their own for 12 months. That's 8 unlicensed users out of 62, or 13%, well past Microsoft's 5% threshold.

Under the Microsoft Customer Agreement, the client must "acquire sufficient licenses to cover its unlicensed use at 125% of the then-current Customer price." Because the gap is over 5%, it also reimburses Microsoft's verification costs.

Line (hypothetical)MathCost
Back-licensing 8 users for 12 months at 125%8 × $14 × 12 × 1.25$1,680
Microsoft's audit costsOver the 5% threshold, so the client paysNot published, varies by audit
Going forward, buying 8 new licenses8 × $14 × 12$1,344 per year
Going forward, reassigning the 6 leavers' licenses and buying 22 × $14 × 12$336 per year

Two things jump out. First, the penalty itself is survivable at this size. What hurts is the audit cost on top, plus the hours your team spends answering an auditor instead of closing tickets.

Second, the gap and the fix were sitting in the same tenant. Six idle licenses covered six of the eight missing seats, and reclaiming them saves $1,008 a year against buying fresh. An internal audit a year earlier would have caught both sides and skipped the penalty entirely.

This pattern isn't limited to small tenants. Zylo's 2026 index puts unused SaaS licenses at 36% on average across its customers. Zylo's customers are larger than an MSP's small-business clients, but idle seats show up at every size.

Now swap the vendor. Autodesk's terms have no 5% threshold. Any shortfall means buying at least its full value plus Autodesk's audit costs. Run the same exercise on an Autodesk shortfall and there's no margin to absorb even one unlicensed seat.

Software spend audit

A software spend audit runs the same reconciliation from the money side. Start from invoices, reseller bills and card statements, list every subscription with an owner and a renewal date, and match each one to sign-in data from the identity provider. Anything without an owner or recent sign-ins gets cut or downsized before it renews. Our IT cost audit worksheet covers the rest of the IT budget the same way.

Where MSPs carry license risk

Here's the part the generic audit guides skip. An MSP sits in the middle of the licensing chain, and part of that chain carries your name.

Start with what the Microsoft Partner Agreement says, and what it doesn't. If you resell through CSP, you must secure the client's acceptance of the Microsoft Customer Agreement and record it, with the date and signatory. Since October 7, 2025, partners who attested before April 2023 and haven't re-attested are blocked from new purchases and license changes. You also keep licensing records for five years, including after you leave the program. What the agreement doesn't contain is a clause making you liable when a client deploys more than it bought. Your exposure is your own records, your attestations and your contract with the client.

If you host, SPLA puts the reporting on you directly. You self-report usage every month, and an SPLA audit checks every one of those months, as the SPLA section at the end of this part shows.

Costs are moving too. Microsoft adds a 5% uplift to annual-term CSP software subscriptions billed monthly from October 1, 2026, covering Windows Server, SQL Server, System Center and CALs.

VMware hosting changed even more. In January 2026, Broadcom told VMware cloud service providers outside its invite-only program that their authorization would not be renewed, and to close open deals by March 31. If you host VMware for clients, your licensing path has changed twice in a year.

Then there's the client relationship, which no contract fully protects. In this r/msp thread, an MSP with 80 client tenants describes Microsoft sending a license letter to nearly every client. The shortcut is a familiar one: a single Entra ID P1 license bought on a vendor's advice, then Conditional Access used across every tenant. Clients got 90 days to true up. Two of them left.

The lesson is simple. One license that unlocks a feature isn't the same as licensing everyone who uses it. Check the feature against the license, not just the license against the invoice.

Your MSA should say who owns compliance. MSP lawyers publish three patterns. In the first, the client guarantees its own licensing and indemnifies you, and Rob Scott of Scott & Scott publishes sample wording for it. In the second, each side covers its own mistakes, matched to your professional liability insurance. In the third, vendor license terms pass straight to the client, and the MSP states it isn't the client's compliance officer. CompassMSP's MSA, updated March 2026, uses that exact phrasing. Which one fits is a question for your lawyer, not a blog post. Have your MSA reviewed if it's silent on licensing.

Microsoft SPLA license audit

An SPLA audit starts with an email from Microsoft's License Contract and Compliance team selecting you for a formal license compliance review. SAMexpert's SPLA guide (February 2026) lays out what follows. Microsoft appoints an independent auditor, and the firms the guide names are EY, PwC, KPMG and Deloitte. Your first conversation with the auditors happens within 30 days of the notice.

The difference from a customer audit is time. The auditor builds a licensing position for every past month, and a month without solid data gets extrapolated from the months that have it. SPLA presumes unreported use began when each end-customer relationship started, unless you can show otherwise, so keep historical usage data and change records.

The auditor also checks contract terms: that every end customer signed the SPLA End User License Terms, and that you reported contact details for customers spending more than $1,000 a month on Microsoft licensing. Under-reporting costs 125% of list price, you pay the audit costs over 5% non-compliance, and Microsoft can audit up to two years after the agreement ends. SAMexpert describes the first draft report as an Excel worksheet, so check every assumption and formula in it before you sign off.

Open-source licenses count too

Commercial vendors aren't the only licensors. Open-source licenses come with obligations, and copyleft licenses like the GPL and AGPL come with the strictest ones. If a client builds and ships software, or gets acquired, those obligations get checked.

Black Duck's 2026 OSSRA report audited 947 commercial codebases between November 2024 and October 2025, 197 of them in M&A transactions. 68% had license conflicts, up from 56% the year before. Black Duck called it "the largest single-year jump we've recorded." A further 8% of components had no license detected at all.

For MSPs, the relevant cases are a client's own software team and the self-hosted open-source tools in your stack. AGPL matters most when you modify a tool and offer it over a network. We went through the AGPLv3 question in our Grafana Loki review. Add a dependency scan to the checklist for any client that ships code.

Open-source license audits in acquisitions

When a client buys or sells a company, the buyer's auditors scan the target's code for every open-source component, its license and the conflicts between licenses. Black Duck warns that a GPL violation found in due diligence can derail an acquisition. Its 2026 report also flags the 11% of components with custom or modified licenses, which need a lawyer's review one by one, and recommends including AI-generated code in license audits because dependency manifests don't show it.

If a client with a development team is heading into a deal, ask who runs the code audit and when. A software bill of materials (SBOM) from the client's own scanner, produced before due diligence starts, gives them the answer first.

Turning license audits into a service

Every step above takes skill, and clients will pay for skill. Steven Kelley, founder of Software Licensing Advisors and now with Directions on Microsoft, put it plainly in ChannelE2E in March 2026: "Microsoft has commoditized the transaction. It hasn't commoditized the expertise." He reports partners charging $10,000 to $25,000 for Enterprise Agreement management.

Your clients are smaller than EA customers, but the logic scales down. Software license audit services come in three shapes. You can bundle a license review into a premium QBR or vCIO package. You can charge a fixed quarterly fee for larger tenants. Or you can run the first audit, show the savings, and price the ongoing review against the value found.

The third one sells itself. In the worked example above, reclaiming idle seats saves the client $1,008 a year before you've charged a cent. That's an easy conversation at a QBR.

Building a software license compliance audit program

A software license compliance audit program turns these steps into a recurring service with an owner. The toolkit is short:

  • Owner. One named person at the MSP per client, and one approver on the client side.
  • Scope register. Every vendor and agreement, with its audit clause, notice period and renewal date.
  • Cadence. A license reconciliation every quarter, and a full audit once a year and before each major renewal.
  • Tools. Inventory from your RMM or discovery scans, an entitlement store, and sign-in data from the identity provider.
  • Report. One page per quarter with gaps, idle seats, renewal dates and risk flags.
  • Evidence. The audit pack, refreshed every cycle and stored where the next tech can find it.

If you already run an MSP stack audit on your own tools, you have the template. Point it at the client.

The client gets a smaller bill and a clean answer when the letter comes. You get recurring revenue and a reason to be in the room before renewals. Your techs get fewer fire drills.

License audit software and tools

License audit software falls into three groups, plus the vendors' own counting tools. Pick by the gap in your stack.

Discovery and inventory tools answer "what's installed where." Lansweeper comes up in r/sysadmin threads about Oracle Java audits. Open-source options like Snipe-IT and the tools in our open-source inventory roundup cover the basics without a license bill of their own. Your RMM agent data belongs in this group too.

Software asset management (SAM) platforms do the reconciliation. Flexera, Snow (now part of Flexera) and USU match entitlements to usage and model vendor-specific rules like Oracle processor licensing. They're built for enterprises, and priced like it.

SaaS management platforms like Zylo and Tropic track seat usage in cloud apps, which endpoint scans miss. They make sense once a client's SaaS spend is large enough to justify another subscription.

Vendor counting tools cover single products. Broadcom's KB 313548 script counts VMware cores and vSAN TiB, and IBM's License Metric Tool produces the sub-capacity reports IBM asks for.

For an MSP, the cheapest combination is the inventory you already have plus a disciplined quarterly reconciliation. OpenFrame covers the inventory half. It's open, AI-native infrastructure for IT and security, priced at $1 per device per month with 10 million AI tokens included, or $0.80 per device on annual billing with 25 million, after a 14-day free trial. The reconciliation half is the checklist above and a tech who owns it.

Get ahead of the letter

Vendor audits aren't slowing down. Broadcom built usage reporting into VMware, Oracle's audit share jumped in Flexera's survey, and Microsoft is writing to tenants over premium features used without premium licenses. The letter is coming either way. The difference is whether you've already run the numbers when it lands.

Start with one client this month. Run the five steps, fill in the checklist, and bring the idle-seat number to the next QBR. If the inventory step is the one eating your week, see how OpenFrame pulls it from live endpoints.

For the tools side, our roundup of free IT asset management software is the next read.

Conrad Lunderstedt

Conrad Lunderstedt

Solution Architect

I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.

Related Content

Frequently Asked Questions

/blog/software-license-audit

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions