Cost and licensing

Completed

Before implementing Dynamics 365 Contact Center, you need a clear picture of what drives costs and how to structure licensing conversations with business stakeholders. Contact center licensing combines user-based licenses for named users with consumption-based charges for AI and telephony usage. Understanding both dimensions is essential for accurate cost planning.

The product portfolio

Dynamics 365 Contact Center offers several licensing options depending on whether the organization needs CCaaS only, CRM only, or both:

Product Best for
Service agent Copilot assistance in Outlook and Teams for users with any CRM—doesn't include CCaaS channels
Dynamics 365 Customer Service Enterprise CRM and case management for organizations retaining their existing CCaaS infrastructure
Dynamics 365 Contact Center CCaaS for organizations with an existing CRM (Salesforce, ServiceNow, or custom)
Contact Center Add-on Add CCaaS capabilities to existing Dynamics 365 Customer Service Enterprise licenses
Dynamics 365 Customer Service Premium Full CRM and CCaaS bundle; cost-effective compared to purchasing both separately

Tip

IVR and transcription usage beyond the included entitlements is available as a capacity add-on. Plan for these overages when estimating costs for high-volume contact centers.

For current licensing prices, see Dynamics 365 Contact Center pricing on the Microsoft website.

Copilot Credits: AI consumption currency

AI agent usage across Dynamics 365 Contact Center and Copilot Studio is measured in Copilot Credits. Every generative AI response from a Copilot Studio agent consumes credits. Classical, rule-based topic responses don't consume credits and are included in the license.

Three purchasing models are available:

Model Best for Purchase via
Pay-as-you-go (PAYG) Low or unpredictable usage volumes Azure portal, billed monthly
Capacity Packs Steady, predictable usage (sold in fixed credit bundles) Microsoft 365 Admin Center
Pre-purchase plan Larger or variable demand, with volume discount tiers Azure portal (one-time upfront purchase)

When organizations estimate Copilot Credit consumption, factor in the expected number of self-service interactions per month, the percentage of those that use generative answers, and the escalation rate to human agents.

For current Copilot Credit pricing, see Copilot Studio licensing on Microsoft Learn.

Teams Phone licensing

If the organization uses Microsoft Teams as the telephony backbone, other licensing considerations apply:

  • Each service phone number requires a Teams Resource Account license (free—one per number per environment)
  • The Dynamics 365 Contact Center license includes Teams Phone System entitlements for contact center agents—no separate Teams Phone license is needed for agents whose voice usage is limited to contact center interactions
  • If agents also need personal Teams calling features such as peer-to-peer calls or meetings, a separate Teams Phone license may be required
  • PSTN connectivity options include Microsoft Calling Plans (Microsoft as the operator), Operator Connect (qualified partner operators), or Direct Routing (customer-managed Session Border Controller infrastructure)

Independent research validates significant ROI for organizations integrating Teams Phone with Dynamics 365 Contact Center, including measurable savings from retiring legacy telephony infrastructure.

Evaluating total cost of ownership

The total cost of owning a contact center extends beyond license fees. When building a TCO analysis, consider both the costs reduced and the value generated.

Infrastructure costs you can reduce

Replacing a fragmented point-solution stack with a unified cloud-native platform eliminates several categories of infrastructure cost:

  • On-premises telephony hardware and maintenance: Moving to a cloud-native CCaaS platform eliminates the capital expenditure and ongoing operational costs associated with PBX systems, session border controllers, and the staff required to maintain them.
  • Point-solution licenses: A unified platform consolidates capabilities that organizations typically purchase separately—standalone IVR systems, workforce management tools, quality monitoring software, and analytics platforms—into a single license structure.
  • Integration development and maintenance: Fragmented stacks require custom integrations between each point solution. A unified platform with a shared Dataverse data model reduces or eliminates these integration layers and the engineering effort required to keep them running.

Value generated by AI-driven improvements

The Contact Center benefit framework identifies four measurable levers:

Lever How value is created
Reduce case volume AI self-service shifts interactions away from human agents
Reduce case handling time AI summaries, suggested replies, and case automation reduce average handle time
Improve employee experience Shorter agent onboarding, lower attrition from AI assistance
Improve quality outcomes Higher CSAT and retention from better-matched, better-assisted interactions

The provisioning journey

Licensing and provisioning follow a defined sequence for new customers:

  1. Start a 30-day free trial to explore the platform with demo data
  2. Purchase licenses through the Microsoft 365 Admin Center
  3. Assign Dynamics 365 Contact Center licenses to users
  4. Create a Power Platform environment with Dataverse in the Power Platform Admin Center
  5. Provision the Dynamics 365 Contact Center instance
  6. Enable channels in the Contact Center Admin Center
  7. Configure channels according to business requirements

Note

A trial environment can't be used for production. A separate production instance must be provisioned before go-live.

For accelerated implementations, the Contact Center Accelerate Program offers a Microsoft go-to-market program with five-year contracts, predictable pricing, and a committed go-live timeline of 240 days or fewer. The program includes AI-first features, omnichannel channels, core integrations, and delivery through Microsoft-preferred partners.