Microsoft’s Azure Communication Services (ACS) now delivers two-way SMS in more than 100 additional countries, thanks to a new integration with cloud communications platform Infobip. The move, announced on September 8, 2025, marks the debut of Messaging Connect, a public preview program that lets trusted partners provision phone numbers, navigate local regulations, and route SMS on behalf of Azure tenants—all while preserving the native ACS developer experience and observability stack.

Enterprises running global authentication, transactional alerts, or customer support over SMS have long struggled with fragmented vendor contracts and per-country compliance hurdles. Messaging Connect aims to collapse that complexity into a single Azure workflow. Developers keep using the same ACS SMS API, Event Grid telemetry, and Log Analytics; behind the scenes, a partner like Infobip manages carrier connectivity, number leasing, and regulatory onboarding.

From Alpha to Global: The Messaging Connect Architecture

Messaging Connect is effectively an orchestration layer within Azure Communication Services. When an ACS resource lacks native coverage for a country or sender type, a new “Messaging Connect” option appears in the Azure portal’s number provisioning blade. Selecting it redirects administrators to Infobip’s interface, where they complete the required business verifications and acquire local long codes, virtual long numbers (VLNs), or alphanumeric sender IDs. Once approved, those numbers surface inside the Azure portal and behave like any other ACS resource.

On the wire, developers add a MessagingConnect object to their SMS send options. A snippet of C# code might look like:

var sendOptions = new SmsSendOptions {
    MessagingConnect = new MessagingConnectOptions {
        Partner = "infobip",
        ApiKey = "<partner-key>"
    }
};
await smsClient.SendAsync(from, to, message, sendOptions);

The API version powering this preview is 2025-05-29-preview, with SDK support initially limited to C# and JavaScript. Python and Java libraries are on the roadmap. Microsoft explicitly warns that preview features carry no SLA and may change; organizations should not divert mission-critical traffic without a fallback path.

What makes this architecture notable is the clean separation of concerns. Azure handles authentication (existing ACS tokens), orchestration, and telemetry, while Infobip—with over 800 direct operator connections—tackles the hyper-local telco realities. Delivery receipts, inbound messages, and opt-out events all flow back into Azure Event Grid, so existing monitoring and automation pipelines remain untouched.

190+ Countries vs. 100+ New Two-Way Markets

The numbers can cause confusion. Microsoft frames Messaging Connect as enabling ACS reach across a partner network spanning more than 190 countries for SMS delivery overall. That figure includes one-way delivery via alphanumeric sender IDs and long codes through partners. Infobip’s specific claim—100+ additional countries for two-way SMS—refers to markets where local long numbers can now receive inbound messages, a capability that often requires pre-registration and operator approval.

Both figures are vendor statements and must be validated per country and per sender type. Local laws, operator filtering, and registration timelines vary significantly. For example, a country listed as “supported” might still require a separate business license or template pre-approval that can take weeks.

Enterprise Benefits: Unifying SMS without Uprooting Toolchains

The integration promises several concrete advantages:

  • Unified developer experience: Teams stay within the ACS SDK, Azure Event Grid, and existing automation, cutting development overhead when expanding SMS reach.
  • Reduced vendor fragmentation: Instead of juggling multiple CPaaS contracts or local telco relationships, organizations lease and manage numbers via Infobip inside Azure.
  • Partner-managed compliance: Local sender registration, template approvals, and opt-out enforcement are handled by Infobip, centralizing regulatory workflows and reducing legal bottlenecks.
  • Faster time to market: Where Infobip already has direct operator connections, provisioning can be quicker than building a bespoke integration.
  • Enterprise-grade redundancy: Infobip’s 800+ direct operator links and Microsoft’s cloud orchestration offer multiple routing options, improving deliverability resilience.

What Enterprises Can Now Do

With two-way SMS available in markets previously unreachable via native ACS, several use cases become immediately practical:

  • Time-sensitive OTP and MFA delivery to global users without fallback to less secure channels.
  • Transactional notifications—banking alerts, delivery updates—sent from branded alphanumeric IDs where regulators allow.
  • International conversational support using local long numbers that customers can reply to, enabling a true two-way dialogue.
  • AI/Copilot-triggered notifications that rely on SMS as a reliable, out-of-band channel when internet connectivity is spotty.

Veselin Vuković, Chief Alliances Officer at Infobip, framed the collaboration in terms of AI-era engagement: “Integrating Infobip’s SMS channels through the Messaging Connect Integration underscores our commitment to empowering cloud platforms with truly global, reliable, and high-quality communication capabilities. In today’s era of AI and automation, we are not only connecting businesses and customers, but we are also enabling conversations that drive impact.”

Diego Basantes, Senior Product Manager for Messaging Connect at Microsoft, added: “This new integration between Microsoft Azure Communication Services and Infobip marks a step forward for the next generation of cloud-based customer engagement solutions. We are creating new opportunities for businesses to connect with customers in simpler ways, helping them deliver seamless interactions.”

The Risks: Preview Status, Vendor Concentration, and Compliance Pitfalls

Despite its promise, Messaging Connect introduces complexities that IT leaders must address.

1. Preview means no SLA.
Preview APIs can change or break across versions. Routing high-value authentication or compliance messages through an unsupported pipeline without a backup invites operational risk. Enterprises should maintain a secondary delivery path until the feature reaches general availability.

2. Single-partner dependency.
Infobip is the inaugural—and currently only—Messaging Connect partner. While additional partners are on the roadmap, organizations relying solely on this integration today face concentration risk for carrier routing, pricing, and dispute resolution. Contractual failover clauses are essential.

3. Per-country variability.
The “100+ countries” figure doesn’t mean uniform service. Some markets permit only alphanumeric sender IDs, others require outright business registration. Provisioning timelines can stretch from hours to weeks. A market-by-market audit is non-negotiable before committing to launch dates.

4. Pricing opacity.
Messaging Connect enables partner-directed billing, which can mix per-message fees, monthly number leasing, regulatory surcharges, and support add-ons. Total cost per message may vary dramatically by destination. Procurement teams should request detailed rate cards and model costs under realistic volume assumptions.

5. Security and data residency.
While ACS authenticates API calls with its own tokens, partner API keys must be stored securely and rotated. Data residency expectations for inbound messages and delivery reports need clear contractual language, especially in regulated industries.

6. Delivery performance isn’t guaranteed.
Operator filtering, spam detection, and local greylisting can still cause inconsistent delivery. Robust monitoring of delivery receipts, complaint metrics, and inbound traffic is critical to quickly surface regional problems.

Pricing and Procurement: What to Watch

Because Infobip bills separately through the Azure Marketplace or directly, the total cost of ownership includes:

  • Monthly number leasing (varies by country and type)
  • Per-message send fees (destination-dependent)
  • One-time or recurring regulatory registration charges
  • Optional SLA and support tiers

Procurement teams should negotiate volume discounts and include a transition clause to move traffic to another partner if pricing or quality degrades. Contracts should also define penalties for missed provisioning timelines and delivery performance targets.

A Practical Rollout Checklist

The Azure community discussion outlined a sensible adoption path:

  1. Pilot in a low-risk region with a defined message template to measure latency, throughput, and complaint rates.
  2. Verify per-country sender type support—check whether long codes, short codes, or alphanumeric IDs are allowed and estimate registration timelines.
  3. Maintain redundancy: keep an alternate CPaaS or direct-operator connection for critical flows until Messaging Connect is GA.
  4. Integrate telemetry early: feed delivery receipts, opt-out events, and inbound messages into your SIEM or Azure Monitor to detect deliverability issues.
  5. Align legal and privacy teams: prepare know-your-business documents, use-case justifications, and message templates upfront.
  6. Harden secrets management: store partner API keys in Azure Key Vault, enable rotation, and audit provisioning activities.

What’s Next: Short Codes, More Partners, GA

Microsoft’s documentation signals that short codes—the highly recognizable 5–6 digit numbers used for high-throughput campaigns—are “coming soon” to Messaging Connect. Expanded SDK language support (Python, Java) is also planned. As the program matures toward general availability, additional messaging partners will likely join, introducing competitive pricing and geographic redundancy.

Tighter integration with Azure’s AI and automation ecosystem—Copilot Studio, Power Automate, Logic Apps—is a natural progression. SMS will become an even more seamless notification endpoint for AI-driven workflows, reducing the need for custom connectors.

Strategic Bottom Line

Infobip’s integration with Azure Communication Services via Messaging Connect is more than a feature launch; it’s an architectural statement. By decoupling developer orchestration from local telecom complexities, Microsoft and Infobip are lowering the barrier to genuine global SMS. For Azure-centric enterprises, this can shrink development cycles, cut compliance overhead, and accelerate time-to-market for critical messaging workloads. The caveats are real—preview instability, single-partner risk, and per-country fragmentation—but with disciplined governance and a phased rollout, Messaging Connect could become the default path for international SMS on Azure.