{
"title": "Azure Communication Services Adds Two-Way SMS in 100+ Countries Through Infobip Integration",
"content": "Microsoft’s Azure Communication Services (ACS) has dramatically expanded its global SMS footprint. On September 8, 2025, Infobip announced that its carrier-grade messaging platform is now integrated with ACS through Microsoft’s new Messaging Connect partner model, enabling two-way SMS and local number provisioning in more than 100 additional countries. For enterprises that rely on Azure for customer communications, this integration promises to reduce the complexity of reaching users worldwide—but it comes with important caveats around preview status, per-country variability, and contractual obligations.

This integration marks the first implementation of Messaging Connect, a program designed to let vetted third-party communications platforms route SMS on behalf of Azure tenants when native ACS coverage falls short. By keeping application logic, authorization, and observability within Azure while offloading telco routing and regulatory compliance to Infobip, it offers a compelling hybrid model for global enterprises.

How Messaging Connect Changes the Game for Developers

The architectural beauty of Messaging Connect is that it demands almost no changes to existing ACS implementations. Developers continue to call the familiar ACS SMS API, using the same SDKs in C#, JavaScript, or other supported languages. The only addition is a small configuration object—a MessagingConnect block that specifies the partner (Infobip) and the necessary credentials. From that point, ACS forwards the message to Infobip’s global delivery network, while delivery receipts, inbound messages, and opt-out events are still pushed back to Azure Event Grid and Log Analytics. This preserves the unified telemetry pipeline that many IT teams have built around Azure Functions, Logic Apps, and monitoring dashboards.

Crucially, number provisioning and compliance paperwork are handled through Infobip but surfaced inside the Azure portal. When a developer requests a phone number for a country not covered natively by ACS, the portal redirects to Infobip’s provisioning interface. There, teams can acquire local long codes, submit regulatory documentation, and manage sender registrations. Once approved, those numbers appear as usable ACS resources, ready to send and receive messages.

A common scenario: a developer building an Azure-hosted web application needs to send a text message to a user in a country where ACS doesn't have native SMS coverage. Previously, the developer would have to integrate a separate CPaaS SDK, manage a different set of credentials, and build custom logic to reconcile delivery receipts. With Messaging Connect, the developer simply adds a MessagingConnect options object to the existing ACS SMS send call. The SDK handles the rest, routing the message through Infobip’s network while returning delivery events to the same Event Grid topics already in use. This seamless extension is what makes the integration so attractive for teams already invested in the Microsoft ecosystem.

What Capabilities Are Included—and What's Still Coming

In this preview phase, the integration supports two primary sender types: long codes (also called virtual local numbers) for two-way messaging, and dynamic alphanumeric sender IDs for one-way branded messages in countries that allow them. Short codes, often used for high-volume marketing or alerts, are listed as “coming soon” and are not universally available during the preview.

Infobip’s network spans over 800 direct operator connections and reaches more than 200 countries and territories, but the practical takeaway is that two-way SMS—arguably the most important capability for conversational support and authentication—is now accessible in over 100 additional markets through ACS. This includes many regions in Asia, Africa, and Latin America where native ACS coverage was previously thin or nonexistent.

Why Global Enterprises Should Pay Attention

For organizations that use SMS for time-sensitive authentication, multi-factor authentication (MFA), emergency alerts, or customer support, this expansion removes a major barrier to global consistency. Instead of stitching together multiple CPaaS providers or negotiating direct operator deals country by country, teams can now manage nearly their entire SMS estate from within Azure. This reduces vendor sprawl, simplifies procurement, and cuts the engineering time required to onboard new countries from weeks to hours in many cases.

Other tangible benefits include:

  • Faster regulatory onboarding: Infobip handles local sender registrations, template approvals, and opt-out compliance, which is especially valuable in markets with complex telecommunications regulations.
  • Preserved automation: Existing Event Grid subscriptions for delivery receipts and inbound messages continue to work, so automated workflows for chatbots, ticketing systems, and Copilot notifications remain intact.
  • Operational visibility: Because events flow into Azure Log Analytics, teams can set alerts on delivery rates, monitor latency, and build dashboards without integrating yet another monitoring tool.

Validating the Numbers: What to Trust and What to Test

Both Microsoft and Infobip have made bold claims about reach. Infobip says it enables two-way SMS in “100+ additional countries,” while Microsoft frames Messaging Connect as providing access to “190+ countries” through partner networks. However, these figures are marketing measurements, not contractual guarantees. The distinction between one-way deliverability (via alphanumeric IDs) and full two-way local number support is critical. Not every country that appears on a coverage map will permit inbound SMS on a local long code, and some may require lengthy registration processes or impose content restrictions.

Enterprises should treat these numbers as starting points for validation. During procurement, demand a detailed, per-country list of supported sender types, provisioning timelines, and expected delivery latencies. Conduct real-world pilots by sending test messages to actual numbers in each target market and measuring both outbound and inbound delivery. Only then can you confirm whether the integration meets your service-level objectives.

The Strengths That Make This Integration Stand Out

Despite the need for due diligence, the partnership between Infobip and Microsoft offers genuine advantages that many Azure-centric organizations will find hard to ignore:

  • Unified billing and management: While billing can be partner-directed (meaning you may pay Infobip directly), the ability to see and manage numbers in the Azure portal reduces administrative friction.
  • Developer continuity: Teams don’t need to learn a new SDK or rewrite message-handling logic; the changes are minimal and backward-compatible with existing ACS code.
  • Compliance at scale: Infobip’s experience with global telecom regulations means that enterprises can offload much of the legal and administrative burden, lowering the risk of accidental non-compliance.
  • Time-to-market acceleration: For companies entering new markets, the weeks or months typically spent on operator negotiations and local registrations can be compressed into days, giving them a competitive edge.
For Windows administrators, the ability to monitor SMS delivery through familiar tools like Azure Monitor and Log Analytics means that no new monitoring infrastructure is needed. PowerShell scripts or Azure CLI commands can be used to query delivery metrics, and alerts can be configured through Action Groups to notify on-call teams if delivery rates drop below a threshold.

However, the integration is not without significant risks. The most glaring is that Messaging Connect, as of the announcement, is still in public preview. This means Microsoft provides no service-level agreement (SLA), and the APIs, SDKs, and features may change before general availability. Running production-critical workloads—such as MFA or emergency alerts—on a preview service without a contingency plan is a recipe for disaster. Organizations should either wait for general availability or build robust fallback mechanisms.

Other concerns include:

  • Per-country unpredictability: Even with Infobip’s broad network, message delivery latency, throughput limits, and inbound support vary by country and operator. A pilot that works flawlessly in India might encounter delays in Brazil or regulatory snags in the EU.
  • Partner dependency: Relying on a single CPaaS provider for global SMS creates a single point of failure. If Infobip experiences an outage or a contractual dispute arises, your communication channel could be crippled. A multi-vendor strategy with native ACS fallbacks (where available) is strongly advised.
  • Data privacy and residency: Message metadata and content may transit through Infobip’s infrastructure, potentially crossing borders. Enterprises must verify that data handling practices comply with GDPR, local data residency laws, and internal security policies.
  • Cost unpredictability: Per-message fees, number lease charges, and registration costs can add up quickly. Without careful modeling, total cost of ownership (TCO) may exceed expectations, especially for high-volume use cases.
  • Message filtering by operators: Even if Infobip successfully delivers a message to a foreign network, that network might still block or filter messages based on content, sender type, or volume. Enterprises should test a representative sample of message content to ensure high deliverability.

A Practical Roadmap for Adoption

For Windows and Azure teams considering this integration, a staged approach is essential. Here’s a practical checklist:

  1. Audit your current ACS SMS usage: Map out which countries you already cover natively and where gaps exist. Identify the sender types (long codes vs. alphanumeric) you need in each market.
  2. Verify preview status: Check the official Microsoft documentation for the latest API versions and the Messaging Connect public preview terms. Do not assume it has moved to general availability without explicit confirmation.
  3. Pilot in a low-risk environment: Select two or three target countries that are critical but not mission-critical. Provision numbers through the Infobip flow, then send test messages and measure deliverability, latency, and inbound functionality over at least a week.
  4. Negotiate hard SLAs: If you plan to use the service for production workloads before general availability, negotiate custom SLAs with Infobip covering delivery latency, success rates, and support response times. Ensure these SLAs have teeth through financial penalties or support credits.
  5. Design failover routing: Implement logic in your application that can dynamically switch to native ACS (if available) or an alternate SMS provider when Messaging Connect experiences issues. Use Azure Event Grid metrics to trigger automatic failover.
  6. Lock down compliance: Request documentation from Infobip detailing message flow, data processing locations, and opt-out handling. Work with your legal team to ensure alignment with regulations like GDPR, HIPAA (if applicable), and country-specific telecom laws.
  7. Monitor everything: Stream delivery receipts and inbound events to Azure Log Analytics. Create dashboards and alerts for delivery rates, latency spikes, and unusual error patterns. Treat Messaging Connect like any other critical Azure service.
  8. Automate provisioning and testing: Use Azure DevOps pipelines or GitHub Actions to automatically provision new numbers through the Messaging Connect flow (where API support exists) and run automated test suites that send and receive messages in target countries. This ensures that coverage remains valid over time as regulations change.

The Bigger Picture: A Smart Architectural Pattern

The Infobip integration exemplifies a growing trend in cloud services: platform providers focusing on orchestration and developer experience while partnering with domain specialists for hard-to-reach capabilities. For Microsoft, this avoids the massive investment required to build direct operator relationships in every corner of the globe. For enterprises, it offers a pragmatic way to fill coverage gaps without fragmenting their technology stack.

Yet the success of this model hinges on execution. During the preview phase, the burden is on IT teams to validate performance and push for accountability. Those that move thoughtfully will gain a scalable, Azure-native pathway to global SMS that is easier to manage and faster to deploy than anything available before. Those that rush in without testing or contractual safeguards may find themselves struggling with unreliable delivery, compliance headaches, or unexpected costs just when they need communication channels the most.

In the coming months, as Messaging Connect moves