In this guest blog post, Lukasz Strzelecki, Distinguished Engineer at Infobip, explores migrations involving messaging architecture and how Infobip's unified API for omnichannel communication can help organizations affected by the retirement of Azure Communication Services messaging.
When a messaging provider changes, the obvious question is where to move your messaging traffic next. The less obvious question is what else in your application depends on that provider.
Modern messaging integrations rarely stop at an API call. Applications might rely on sender identities, delivery events, inbound messages, webhooks, authentication, and business logic built around these capabilities. Because of that, replacing a messaging provider can affect much more than the endpoint used to send a message.
This is particularly relevant for organizations using Azure Communication Services (ACS), as Microsoft has announced the retirement of ACS messaging, with the process starting on September 23, 2026. Teams planning their next step must determine what needs to change in the existing messaging architecture and what can remain in place.
A messaging migration does not necessarily mean rebuilding the messaging layer from scratch. Depending on the capabilities supported by the replacement provider, much of the existing application logic can remain in place.
What changes when changing messaging providers?
It’s not simply a matter of replacing one API endpoint with another. Developers need to understand which parts of the integration are specific to the current provider and which represent application logic that can remain unchanged.
Four areas are particularly important:
Sender identity includes the phone numbers, sender IDs, and other identities customers already recognize. Changing these unnecessarily can affect established customer communication flows.
API connectivity determines how the application sends messages and interacts with the provider. The amount of code that needs to change depends on how closely the replacement provider supports existing integration patterns.
Messaging events include delivery reports and other status updates that can trigger processes elsewhere in the application.
Inbound messaging covers messages coming back from customers. For two-way communication, moving inbound traffic without disrupting existing processing can be just as important as moving outbound traffic.
Looking at these areas separately helps teams distinguish between what actually needs to be migrated and what can stay in place.
Compatibility can matter more than starting from scratch
When a messaging service is retired, teams can redesign their integration or look for a migration path that preserves existing application components. For established production systems, minimizing unnecessary changes can reduce engineering effort and migration risk. Compatibility therefore becomes an important consideration.
API compatibility can reduce the amount of application code that needs to change, but the surrounding messaging architecture also needs to fit the new provider.
This is the approach Infobip has taken for supported ACS messaging scenarios.
Infobip Communication Services, available in Microsoft Marketplace, includes APIs that support the ACS messaging scenarios covered by its migration path, including SMS and email. This allows applications to retain much of their existing integration while changing the underlying messaging provider.
For example, an existing application using the ACS SMS SDK can continue to use the same SDK while pointing its connection string to an Infobip endpoint:
from azure.communication.sms import SmsClient
CONNECTION_STRING = (
"endpoint=https://acsdemo.api-us.infobip.com/;"
"accesskey=<YOUR_INFOBIP_ACCESS_KEY>"
)
FROM_NUMBER = "+11234567890"
TO_NUMBER = "+18768768760"
MESSAGE = "Hello from ACS SDK"
client = SmsClient.from_connection_string(CONNECTION_STRING)
responses = client.send(
from_=FROM_NUMBER,
to=[TO_NUMBER],
message=MESSAGE,
enable_delivery_report=True,
)
This example illustrates the principle rather than a complete solution. Sender configuration, authentication, delivery reporting, inbound messaging, and other production requirements still need to be validated for the specific use case.
The value of this approach is developers can focus changes on the provider-specific parts of the integration rather than rewriting application logic that already works.
Sender identity and events are part of the architecture
One of the easiest parts of a messaging migration to underestimate is the sender itself.
For an application, a sender number may look like a configuration. For a customer, it can be part of the identity of the service they interact with, particularly when it is used for notifications, authentication, support, or ongoing conversations.
Depending on the use case and geography, organizations moving to Infobip can obtain new numbers or reuse numbers already associated with Infobip through MessagingConnect. They can also initiate a process to migrate existing ACS numbers where number portability is supported.
Sending a message is only one part of a production workflow. Delivery reports can update customer records, trigger retries, or determine what happens next in an automated process. If customers can reply, inbound messages may feed directly into existing business logic.
A migration that successfully moves outbound messages but breaks these event flows can still disrupt the application.
Infobip supports webhook-based delivery of messaging events, which can be routed to existing infrastructure, such as an Azure Event Grid instance. Inbound messages can similarly be routed into the application's existing processing architecture.
This means teams can change the provider responsible for messaging while keeping more of the downstream processing intact.
Change what you need, nothing more
A messaging provider can be replaced without necessarily rebuilding the application around it. The key is understanding which parts of the integration are provider-specific and which are part of the application's existing business logic.
For organizations affected by the ACS messaging retirement, that distinction can help define a more contained migration: Update the provider-specific components, validate the surrounding workflows, and keep the application logic that already works.
If your organization is considering an ACS migration, visit our website to explore your options.