A contact center migration becomes dangerous when the first question is “Which replacement should we buy?” The first question should be simpler. Which live customer paths still depend on Azure Communication Services?
Microsoft says certain standalone Azure Communication Services capabilities used by Dynamics 365 Contact Center will reach end of service on 30 September 2028. Affected configurations include voice, SMS, and WhatsApp through Azure Communication Services. Teams Phone extensibility, SMS through Twilio or Infobip, and WhatsApp through Twilio are not affected in the same way. The practical answer is to inventory each channel, choose its supported destination, preserve the number and routing evidence, run both paths in parallel, and disconnect the old path only after an end to end test passes.
This is not a one day switch. It is a controlled channel migration.
Check whether your channels are affected
Start from the running configuration, not a vendor list. Two Dynamics 365 environments can show the same channel name while using different providers underneath. Record every production voice line, SMS number, and WhatsApp number. For each one, capture the Azure resource, current provider, routing rules, queues, templates, automations, recording or transcription dependencies, reporting feeds, and named owner.
- 1Map the live pathProve the provider, number, routing, automation, reporting and owner for every channel.
- 2Protect the numberConfirm ownership, portability, contracts and local requirements before procurement.
- 3Choose by channelSelect the supported voice, SMS or WhatsApp destination for the actual configuration.
- 4Prove in parallelTest both directions, routing, handoff, failure and reporting while the old path remains.
- 5Retire after observationDisconnect the old service only after the pilot, rollback rehearsal and live watch pass.
The current Microsoft migration guide separates the affected and unaffected paths. Voice through Azure Communication Services Direct Offer or Direct Routing is in scope. SMS and WhatsApp configured through Azure Communication Services are in scope. A voice configuration already using Teams Phone extensibility is not.
Do not infer the provider from a phone number or from what an agent sees. Ask an administrator to prove the connection in the service configuration. If evidence is missing, mark the channel unknown. Unknown is a work item, not permission to cut over.
Protect the number before choosing a target
A familiar number is part of the customer journey. It may appear on invoices, ads, appointment reminders, saved contacts, QR codes, and old support emails. Losing it can create more damage than changing the application behind it.
Build a number record before procurement. Include legal owner, carrier, country, number type, current porting status, emergency calling obligations for voice, the WhatsApp business account, approved templates, SMS sender rules, and any contractual restriction. Microsoft says portability depends on the destination service, carrier, geography, and local regulation. That means “we expect to keep it” is not evidence.
This is also the point to decide whether the move is only a provider change or a wider workflow change. If customer history or ownership will move too, use a separate conversation migration control. Do not bury a data migration inside a telephony cutover.
Choose a destination per channel
One deadline does not create one replacement. Voice, SMS, and WhatsApp have different supported destinations and different failure modes.
| Current Dynamics 365 path | Supported destination in Microsoft guidance | Proof needed before approval |
|---|---|---|
| Voice through Azure Communication Services | Microsoft Teams Phone extensibility | Carrier fit, number plan, emergency requirements, recording, routing, inbound and outbound calls |
| SMS through Azure Communication Services | SMS through Twilio or Infobip | Country coverage, sender and number portability, consent handling, inbound replies, delivery events |
| WhatsApp through Azure Communication Services | Meta Direct or WhatsApp through Twilio | Number ownership, template access, inbound and outbound messages, webhooks, routing, reply ownership |
| Teams Phone extensibility, supported SMS providers, or WhatsApp through Twilio | No retirement migration for this specific dependency | Evidence that the live configuration really uses the unaffected path |
Treat this table as a triage map, not a purchasing recommendation. Commercial terms, geographic coverage, compliance, support, and existing provider relationships still matter. A team assessing WhatsApp operations should not assume the same provider decision will fit business SMS or AI calling.
Build a migration receipt before touching production
A useful migration plan names what must remain true for the customer. For each channel, freeze a small but representative test set. Include an inbound contact, an outbound contact, a transfer, a queue assignment, a reply after handoff, a failure path, and the reporting event that closes the interaction. For WhatsApp, add approved template and customer initiated cases. For SMS, add opt out and reply handling. For voice, add caller identity, recording, and any required emergency behavior.
Record the expected result, actual result, evidence location, reviewer, and rollback trigger. This becomes the migration receipt. It prevents a green dashboard from replacing real proof.
The owner should also define stop conditions. Examples include a number that cannot be ported, missing templates, inbound replies that bypass the queue, recording gaps, wrong caller identity, a broken webhook, or reports that count the same interaction twice. Any one of these should pause the cutover.
Cut over one channel at a time
Configure the destination without removing the working path. Run a limited pilot where the architecture allows it. Test at ordinary and peak periods. Rehearse the rollback while the old service still exists.
On cutover day, use a named commander, a channel owner, and a customer owner. Watch inbound and outbound success, queue acceptance, transfers, abandoned contacts, duplicate records, and unresolved conversations. Do not declare success because one test call connected.
Keep the old path available until the agreed observation period ends. Then remove obsolete routing deliberately, revoke unnecessary access, update runbooks, and preserve the receipt. The same discipline applies when leaving another retired channel, as shown in the Apple Messages for Business migration guide.
Use the deadline without wasting it
September 2028 sounds distant. The useful work starts now because contracts, number portability, security review, procurement, and peak-season calendars move more slowly than configuration screens. Early planning also lets a team combine necessary retirement work with a cleaner support operating model instead of reproducing every old exception.
Do not rush every channel into production this quarter. Finish discovery, name owners, test the hardest number first, and schedule a reversible pilot. The deadline should create order, not panic.
Frequently Asked Questions
Does Dynamics 365 Contact Center stop working in September 2028?
No. Microsoft says Dynamics 365 Contact Center continues to operate, but voice, SMS, or WhatsApp configurations that still depend on retired Azure Communication Services capabilities will stop working.
Must every WhatsApp number move?
No. The scope depends on the current provider path. WhatsApp through Azure Communication Services is affected. Microsoft says WhatsApp through Twilio is not affected by this retirement. Verify the live configuration before deciding.
Can we keep our existing phone numbers?
Often, but not automatically. Portability depends on the destination provider, carrier, country, number type, and local rules. Obtain written confirmation and test the plan before announcing a date.
What should be tested after migration?
Test inbound and outbound contact, routing, ownership, transfers, templates or sender rules, recording where relevant, delivery and webhook events, reporting, failure handling, and rollback. A working connection alone is not enough.
If the migration creates an opportunity to simplify how teams own conversations across channels, inspect the evidence in a shared customer inbox before changing the live customer path.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
