Ask three people what a Dynamics 365 Contact Center costs and you get three answers and a shrug. Customer Service Premium or Enterprise plus the Contact Center add-on? What happens to Copilot credits when you switch on the AI agents? And what does the bill look like two years after go-live, when the project team is long gone?
I have had that conversation more times than I can count. The honest answer is usually "it depends", followed by a spreadsheet only one person understands. That is not cost transparency, and it makes it hard for you to plan, budget or push back on a quote.
So I built the Dynamics CCaaS Cost Calculator. It is free, it runs in your browser without a server, and it exports to Excel and PDF.
- Use it here: Dynamics CCaaS Cost Calculator
- Source on GitHub: peterruiter/d365-contactcenter-estimator-powerpete
Why licences are only half the story
Most calculators stop at "users × list price". That number is fine for a first ballpark and useless for a budget. A contact center generates cost every time a call lands, a bot answers, a recording is stored or an AI agent classifies an email. Those are runtime costs, and they can move the total by a lot.
The calculator therefore splits your Dynamics 365 Contact Center cost into four buckets:
| Bucket | What sits in it |
|---|---|
| Licences | Per-user Microsoft licences: CS Premium, CS Enterprise, Contact Center digital / voice / both, Team Member |
| Consumption | Telephony minutes, Copilot credit overage, Dataverse capacity, add-on SKUs, Azure resources |
| Implementation | Phases, roles, integrations, contingency (illustrative in the public version) |
| Run | Support team, other monthly run costs (illustrative in the public version) |
The public version puts licences and consumption up front. Those are the numbers you can validate against a Microsoft price list. Implementation and run stay in as an indication of shape, not as a quote.
What the calculator does
Licensing per user type. You enter agents (voice, digital or both), supervisors, back-office case workers and read-only users. The tool picks the cheapest path between Customer Service Premium and Enterprise plus the Contact Center add-on, or Contact Center standalone if you run a third-party CRM. Existing Enterprise seats are taken into account. All list prices are editable defaults in USD, EUR or GBP.
Telephony. Choose Microsoft as carrier through Azure Communication Services, Teams Phone with a Calling Plan, or Teams Phone with Operator Connect or Direct Routing. The tool needs minutes and numbers, and a wizard turns calls, handling time and containment into those minutes.
Copilot Studio credits. Self-service in Copilot Studio is billed in credits: one for a classic answer, two for a generative one, five per action, ten when you ground on Microsoft 365 tenant data. Premium users bring 1,000 credits per month into a shared pool. The calculator nets your need against that pool and prices the overage in packs or pay-as-you-go, whichever is cheaper.
The Dynamics 365 AI agents. This is the part I care about most. The prebuilt agents in Customer Service and Contact Center draw from the same credit pool:
- Customer Intent Agent
- Case Management Agent
- Customer Knowledge Management Agent
- Quality Assurance Agent
- Customer Assist Agent (premium generative voice, 75 credits per minute)
The calculator uses Microsoft's own agent usage estimator formulas. You answer operational questions, such as how many assisted conversations per month, how many messages per conversation, what share triggers a knowledge suggestion, and it converts that into credits and money. Try it with realistic volumes before you promise anyone that "AI is included".
Dataverse capacity. Voice recordings, transcripts, cases and attachments land in Dataverse. A wizard estimates database, file and log gigabytes at steady state from your volumes and retention periods, then prices the overage above what your licences include.
Multi-year view. Licences ramp per go-live wave, run costs start after hypercare, and you get a month-by-month chart plus a cost-by-year table for the horizon you choose.
Wizards instead of raw numbers
Almost nobody knows their "credits per session" off the top of their head. So most sections have a wizard: a short set of questions in plain operational language that end up as the raw inputs. Users, Copilot credits, AI agents, telephony, Dataverse, integrations, add-on SKUs, support team, Azure footprint. Your answers are saved with the estimate and printed in the Excel and PDF export, so anyone reviewing the numbers can see the reasoning.
Three things I learned building it
- Premium usually wins on list price. Enterprise plus the Contact Center add-on only makes sense when you already own Enterprise seats.
- Recordings drive Dataverse file capacity. Your retention policy is a cost decision, not just a compliance one.
- AI agent consumption can exceed the licence cost. The Customer Intent Agent on a busy contact center is a real line item. Model it early.
What it is not
It is not a quote. Microsoft list prices change, your agreement will differ, and the implementation and run figures in the public version use generic roles with average market day rates. Validate everything with Microsoft or your CSP before you sign.
If you find a formula you disagree with, open an issue or send a pull request on GitHub. I would rather fix it in the open than have people carry a wrong number into a business case.
Need a real estimate?
The public calculator gives you the licensing and consumption picture. A real implementation and run estimate depends on your integrations, countries, languages and rollout plan. That is my day job as Global Microsoft Dynamics 365 Contact Center lead at Capgemini. Get in touch and we will size it properly.
Comments