Most of a Dynamics 365 Customer Service implementation is decided before anyone builds anything. The licence tier, the channels, the routing model and the scope of the data migration each lock in architecture and effort, and each is expensive to reverse once configuration has started.
Deferring one of those decisions and reopening it mid-build is one of the more expensive ways for a project to slip. This article sets out the eight decisions that set the timeline, in the order to take them, what each one locks in, and which can safely wait for a second phase. What the implementation costs is a separate question, covered in our Dynamics CRM implementation pricing article.
1. The licence tier is an architecture decision
Customer Service comes in three tiers at Microsoft’s list prices: Professional at $50, Enterprise at $105 and Premium at $195 per user per month, paid yearly. It is tempting to treat this as purchasing. It is the first architecture decision of the project, because the tier decides which application your representatives use and whether routing exists at all.
According to the Dynamics 365 Licensing Guide, Professional has no unified routing, no multisession experience and no Copilot in Customer Service, and it caps queues at 15. Professional organisations stay on Customer Service Hub. New Enterprise organisations no longer get Customer Service Hub at all, and Microsoft’s unified routing documentation states that representatives “must use the Copilot Service workspace app only to be assigned work through unified routing”. So the tier chooses the workspace, and the workspace shapes every form, view and process the team builds.
It also decides how many environments you run. The Licensing Guide states that “Enterprise and Professional users may not be deployed in the same environment.” A design that gives some teams Professional to save money has quietly committed to a second environment and to keeping data synchronised between them.
And it decides what Copilot can do. Service Agent in Microsoft 365 Copilot needs a Customer Service Enterprise or Premium licence to work with case data. Representatives on Professional cannot use it against their own cases, however many Copilot licences the organisation holds.
2. Channels, and when voice arrives
Premium “includes Customer Service Enterprise and Contact Center (Digital + Voice)”. Enterprise users can instead buy Contact Center add-ons. Either way, voice is a different kind of workstream. It is “powered by Azure Communication Services and priced separately”, which means telephony procurement, number porting or a carrier connection, IVR design and its own test regime.
A published example shows how much sits in that path. Kotsovolos, a Greek technology retailer with 400 agents handling about five million calls a year, deployed Dynamics 365 Contact Center in February 2026 with Azure Communication Services for telephony, Omilia’s AI-powered IVR and AudioCodes as a secure voice gateway, according to Technology Record. That is three components beyond Dynamics 365 in the voice path alone, each with its own configuration and testing, which is the practical case for planning voice as a workstream of its own.
That makes channel scope the second decision. Case management, email and routing can go live without voice. Voice cannot go live without them. The sequencing question is whether voice is in phase one or phase two, and the honest answer depends on how soon it is needed: at list price, Premium is $20 a user cheaper than Enterprise plus the full Contact Center, so if voice is due within the year, licensing for it from day one may cost less even if it is configured later.
3. Routing, and how much of it you have
Unified routing is the recommended model, and Microsoft’s basic routing documentation is blunt about the alternative: without unified routing, “one routing ruleset only can be active at a time”, and queue and user mappings are “not solution-aware data”, so they have to be re-mapped by hand in every environment.
Unified routing has a capacity attached. Enterprise “includes unified routing with 50 record routes/user/month”, pooled across the tenant. Twenty Enterprise users therefore route about 1,000 records a month between them before an add-on is needed. For a busy email-to-case desk that limit can arrive sooner than expected, and it is far easier to size before go-live than to discover in the first month.
Routing configuration also has to move between environments in a fixed sequence, using solutions and the Configuration Migration tool. Microsoft’s migration guidance says “You must perform the steps in the order they’re listed.” That belongs in the deployment plan from the start, not in the week before cutover.
4. SLAs and entitlements belong to the business
Microsoft has replaced standard SLAs with enhanced SLAs, and the setup order is fixed: prerequisites, SLA KPIs, SLAs, then applying them. One default matters more than the rest. If no working-hours schedule is set, “the work hours are considered to be all day, every day.”
That default is how a business-hours service desk ends up reporting breaches overnight. Working hours, holiday calendars and pause states are business decisions, and they need an owner on the business side before the first sprint, not a configurator guessing at them. Entitlements follow the same rule: terms defined by hours or by number of cases, per channel, can block case creation once they are used up, which is a commercial decision dressed as configuration.
5. Knowledge before Copilot
Knowledge management is available in every tier, and Copilot can summarise cases and draft knowledge articles from them. What Copilot cannot do is answer well from a knowledge base that does not exist. Summaries and suggested answers generated over an empty or stale knowledge base teach representatives, in the first week, that Copilot is not worth reading.
So knowledge readiness is a go-live criterion for Copilot, not a nice-to-have. Who owns the knowledge base, what state it is in at kickoff, and who reviews articles before they are published are questions for Discover.
6. Migrate open work, not closed history
Microsoft’s implementation guidance lists “Don’t migrate data” as a legitimate migration method, with the instruction to “Consider the value of the data versus the quality, volume, time, and cost of moving it.” It also notes that Power Automate and Logic Apps “aren’t meant to do large data migration jobs”.
For a service desk, the case for moving years of closed cases is usually weaker than it looks. Open cases, active customers, entitlements and the knowledge base have to move. Closed history can often stay in the old system, read-only, or be archived. Every year of history moved adds mapping, transformation, validation and rehearsal time to the cutover, and the cutover is where timelines slip. The storage consequences of that choice are covered in the pricing article.
7. Integrations
Customer Service rarely stands alone. It needs customer and order data from ERP, identity from Entra ID, and often a telephony or messaging platform. Whether each integration copies data into Dataverse or connects to it in place is a design decision with long consequences, and it is the subject of Gaurav’s Dynamics 365 integration patterns. The sequencing point here is only that copy-or-connect has to be settled before migration design, because it decides what gets migrated at all.
8. FastTrack and the design review
Customer Service is eligible for Microsoft’s FastTrack programme, subject to a minimum spend Microsoft does not publish and a partner meeting its criteria. Whether or not a project qualifies, Microsoft’s Success by Design method puts the Solution Blueprint Review in the first phase: “The Solution Blueprint Review (SBR) begins in the Discover phase.” That is the right place for the seven decisions above, in any Dynamics 365 Customer Service implementation. A design review held after build starts reviews decisions that have already been made.
Our position: decide the tier in Discover, and land voice second
In our view the licence tier should be decided in Discover, per population, before any design work, because it determines the workspace, the routing engine, the number of environments and what Copilot can reach. Treating it as a procurement line to be optimised later is the most expensive deferral in a Customer Service project, because reversing it means redesigning the application the representatives live in.
The corollary is about sequencing. Our recommended default, where voice is not central to the business objective, is to land cases, email, routing and SLAs first, and bring voice in a second phase once the case model is stable. Telephony brings its own procurement, carrier, configuration and test regime, and tying go-live to it ties the whole project to the slowest workstream. Where voice is fundamental to the operating model, it belongs in phase one.
That is why, in any Dynamics 365 Customer Service implementation, the requirements of each user population should be written down before the architecture and the implementation plan are finalised.
Where to start
- Decide the tier per population, and write down which workspace, routing model and environments that implies.
- Decide whether voice is phase one or two, and license for it accordingly.
- Size routing against your monthly case volume before go-live.
- Name the business owner of SLAs and working hours, and of the knowledge base.
- Agree what migrates: open work and active customers first, closed history only if it earns its place.
Veratas runs Dynamics 365 CRM implementations, including Customer Service, and what happens after go-live is covered in our managed service versus project delivery article. If you are planning a Customer Service implementation, talk to our team.
Frequently asked questions
Which Dynamics 365 Customer Service tier do we need? It depends on routing and Copilot. Professional has no unified routing, no multisession experience and no Copilot in Customer Service. Enterprise adds them. Premium adds Contact Center digital and voice channels on top of Enterprise.
Can Professional and Enterprise users share an environment? No. Microsoft’s Licensing Guide states they may not be deployed in the same environment, so mixing tiers means running separate environments.
Does Service Agent in Microsoft 365 Copilot work with Customer Service Professional? Not against case data. Microsoft requires a Customer Service Enterprise or Premium licence for Service Agent to work with cases, knowledge and service workflows.
Should we migrate our closed case history? Often not all of it. Microsoft lists not migrating data as a valid option where the value does not justify the cost. Open cases, active customers, entitlements and knowledge must move; closed history can usually stay read-only in the old system.
When should voice go live? Usually in a second phase, after cases, email, routing and SLAs are stable, unless voice is the reason for the project. If voice is due within the year, licensing Premium from the start can cost less at list price than adding Contact Center later.
Operations head with 20 years of experience delivering business intelligence, ERP and AI programmes across healthcare, finance and manufacturing. Focus areas include Power Platform adoption and governance, delivery models, and managed services.