The unused Copilot licence problem: enterprise IT's quietest waste line
Companies in the US and India pay for Microsoft 365 and Copilot seats that sales teams barely touch. The gap isn't the model's fault — it's that generic assistants don't speak the language of quota.
The short answer
Enterprises frequently pay for Microsoft 365 and Copilot licences that sales teams under-use, because a general-purpose assistant doesn't answer the questions reps actually have — price at this quantity, stock, lead time, last quote. Closing the gap means connecting the licences already paid for to sales-specific data, not buying more seats.
Somewhere in your Microsoft 365 bill is a line most CFOs have stopped reading: AI seats, purchased in an optimistic quarter, renewed on autopilot. IT rolled Copilot out. The launch email went to everyone. And in the sales organisation — the function with the clearest dollar case for AI — weekly active usage quietly settled somewhere between “tried it once” and “what’s Copilot?”
This is the unused-licence problem, and it is becoming enterprise IT’s quietest waste line in both the US and India.
Why did adoption stall exactly where the ROI case was strongest?
Because a general-purpose assistant answers general-purpose questions. Copilot out of the box is genuinely useful for summarising a thread or drafting a document. But listen to what a rep actually needs answered on a Tuesday: What’s the price at this quantity with this discount tier? Is it in stock or made to order? What’s the lead time on this configuration? What did we quote this customer last time?
Those answers live in the ERP, the pricing sheets, the CRM and a folder of spec PDFs — systems the assistant, unconnected, cannot see. So the rep asks twice, gets a fluent non-answer, and returns to the old workflow: call the product team, ping a colleague, promise to “check and get back to you.” The licence keeps billing either way.
What does the waste actually look like?
Run the numbers the way a utilisation review would. A 200-rep organisation with AI seats at list price is committing six figures annually in dollars — and in India, where mid-market firms bought M365 broadly but pay for add-ons in dollar-linked pricing, the rupee line item draws CFO attention even faster. Against that spend, the admin dashboards tell the real story: sales-function weekly actives a fraction of marketing’s, prompts per user in single digits, and no measurable movement in quote speed or CRM freshness.
The waste isn’t only the fee. It’s the option cost: the org believes it “did AI,” so the budget and the appetite for fixing the actual sales bottleneck are gone for a cycle.
What separates the teams getting value?
The pattern among teams that turned the line item into output is consistent — and it is not “more training.”
They connected the licence to sales data. Whether through Copilot extensions and Graph connectors, Copilot Studio agents, or specialised layers that sit on top of M365, the winning move was making the assistant answer sales questions: price, stock, compatibility, account history, with sources. The moment the tool answers something a colleague would have taken an hour to answer, adoption stops needing a mandate.
They put it where reps already work. Inside Teams and Outlook — not in another tab. India adds WhatsApp to that list for field teams; the US adds the inbox. Surface beats feature list.
They measured a sales metric, not a usage metric. Quote turnaround time, same-day CRM updates, “let me check” moments per call. Prompts-per-user is a vanity number; minutes-to-quote is a budget line.
What should leaders do this quarter?
Three moves, in order. Audit utilisation by function against spend — the M365 admin reports take an afternoon. Decide the connection strategy for the sales stack: extend Copilot to your CRM/ERP data, build a scoped agent, or evaluate a connecting layer — the wrong answer is a second disconnected assistant. Re-negotiate or redeploy seats that fail the review; unused AI licences are the easiest savings conversation of 2026, in dollars or rupees.
The licence you already pay for is not the problem. Paying for it to sit disconnected from the revenue workflow is.
Was this useful?
Questions leaders are asking
Why do sales teams under-use Microsoft Copilot? +
Because out of the box it knows documents and email, not the sales stack. A rep's urgent questions — current lead time, discount tier, whether stock exists, what was quoted last time — live in the ERP, price lists and CRM. If the assistant can't reach those, reps try it twice, get generic answers, and go back to calling a colleague.
How can companies measure Copilot licence utilisation? +
Microsoft 365 admin reports show active usage per app and per user, and Copilot dashboards report feature-level engagement. The revealing cut is by function: compare sales-team weekly active use against departments like marketing or finance, and against the licence line item in the M365 bill.
Is the answer more AI licences or better-connected ones? +
For most sales orgs, better-connected. The marginal value of a second assistant subscription is low while the first one can't see pricing, inventory or account history. Connecting existing licences to sales data — via Copilot extensions, Graph connectors or specialised layers — attacks the actual bottleneck.
Does this apply to Indian enterprises too? +
Yes, with sharper price sensitivity. Indian mid-market firms adopted M365 broadly, and per-seat AI add-ons priced in dollars get real CFO scrutiny in rupees. Utilisation reviews tend to happen faster in India; the underlying fix — make the licence do sales work — is the same in both markets.
Sources
- Microsoft — Copilot for Microsoft 365 documentation learn.microsoft.com
- Microsoft — Microsoft 365 usage analytics learn.microsoft.com
- Gartner — Generative AI spending and value research gartner.com
Published by
Independent news and analysis on AI for the people who run revenue in industrial and enterprise businesses — in India and the US.