— MICROSOFT 365 • AI + INTRANET READINESS

Microsoft Copilot Credits vs. Licenses Calculator

This calculator helps provide better clarity on what you might expect to pay for credits if not everyone is being licensed.

Not ready to turn on Copilot licenses for everyone? You can still give your employees access to some of Copilot’s powerful AI features like Chatbots built on organizational knowledge — without granting everyone licenses with PAYG credits.

Copilot Licensing Calculator — StitchDX
01

How big is the organization?

This sets the ceiling for how many seats you'd need if you licensed everyone.

Qualifies for Copilot Enterprise — $30/user/month.
02

What share would get a Copilot seat?

Drag to model licensing everyone down to a small pilot group.

0% 60% 100%
Licensed300
Unlicensed200
Copilot Business is capped at 300 seats per tenant. Seats beyond 300 are priced at the Enterprise rate ($30) in this estimate.
03

What are you actually building?

Pick the experiences you're planning. Unlicensed employees using these still cost something — licensed employees using the chatbot don't.

Free for licensed employees. Costs credits for everyone else.
Planning ranges — estimates, not a published benchmark (see note below)
No vendor publishes chatbot questions-per-employee data. The closest proxy — formal IT ticket volume — runs about 1/employee/month industry-wide, but a chatbot has near-zero filing friction compared to a ticket, so real usage for the same underlying need typically runs well above that. Treat these as a reasoning starting point, not a citation.
Metered regardless of who's licensed — multi-step agents always draw credits.
Planning ranges, scaled to your headcount above
0% — all invoked 0% 100% — all autonomous
Invoked = a person submits a form, an event fires, someone asks a question. Autonomous = the agent wakes itself up on a schedule or polls something with no one prompting it — e.g. checking a shared inbox every 15 minutes. Every autonomous check costs a flat 25-credit trigger fee before it does any work, even on runs where it finds nothing to act on. A mostly event-driven workflow should stay near 0%; a polling or monitoring agent belongs closer to 100%.
Always metered — no employee license covers external traffic.
Planning ranges — driven by site/customer traffic, not headcount
04

How are you buying credits?

Applies to every metered interaction above.

Estimated monthly cost
License everyone
$0
License the subset
$0

—

Monthly line itemEveryoneSubset
What this doesn't include: your existing base M365 subscription cost (assumed already in place either way), Azure OpenAI charges for custom agents calling outside models, and Microsoft's undefined "fair use" ceiling on licensed employees' agent usage. Build in a buffer before committing to a headcount.

What this is actually answering: whether it's cheaper to give someone a seat or pay per chatbot question. It does not weigh the value of full Copilot in Word, Excel, and Outlook — the reasons most companies buy a seat in the first place. A low chatbot volume doesn't mean nobody needs Copilot; it means the chatbot alone isn't the business case for licensing that person. See the companion calculator — is a seat worth it beyond the chatbot? — for that side of it.

Questions about your numbers?

Have a digital workplace specialist reach out to you about Copilot readiness.

— FREQUENTLY ASKED QUESTIONS
A Microsoft 365 intranet consultant designs and implements the digital workplace environment inside Microsoft 365 — including SharePoint architecture, information structure, governance policies, and AI readiness. StitchDX goes further: we treat the intranet as the control surface for AI, building the knowledge foundation that makes tools like Copilot reliable and trustworthy.
Copilot readiness starts with knowledge architecture — not licensing. Before rolling out Copilot, your organization needs clean information architecture, governed content, appropriate metadata, and clear ownership policies in SharePoint. Without this foundation, Copilot surfaces whatever exists in your tenant, including outdated, duplicate, or unstructured content. We call this AI readiness work, and it’s the most important thing you can do before expanding your Copilot investment.
Most StitchDX intranet implementations run 60–90 days from initial discovery to launch, depending on organizational complexity and platform (Powell, Omnia, or native SharePoint). We follow a structured process:
Discovery → Information Architecture Design → Configuration & Build → Governance Setup → Training & Launch.
Timelines compress significantly when governance decisions are made early.
Native SharePoint is the underlying platform — powerful, but requires significant configuration and IT expertise to become a true intranet experience. Powell and Omnia layer purpose-built intranet features on top of SharePoint: branded templates, navigation, governance tools, and employee experience capabilities.
StitchDX is a premiere implementation partner for both in North America, and helps organizations choose the right fit based on their requirements.
StitchDX serves mid-market and enterprise organizations across a variety of industries include manufacturing, healthcare and life sciences, professional services (including law firms and tax advisories), retail (including franchise and multi-branded environments), financial services, and nonprofits.
Our work spans every sector where knowledge management and employee communication are operationally critical — and where AI adoption is a strategic priority.