Microsoft's Azure Communication Services just got a massive global SMS upgrade. On September 8, 2025, Infobip became the inaugural partner in the new Messaging Connect program, unlocking carrier-grade SMS—with two-way messaging and locally provisioned numbers—for ACS customers in over 100 additional markets. The integration keeps the same Azure APIs and observability tooling while offloading the messy, hyper-local telecom legwork to Infobip. But there's a catch: it's all in preview, with no production SLA, and the headline numbers demand careful scrutiny.

For years, enterprises building on Azure faced a frustrating gap. Azure Communication Services offered a clean, cloud-native SMS API, but native number provisioning topped out in a few dozen countries. To cover the rest, teams had to juggle separate CPaaS contracts, custom integrations, and fragmented monitoring. Messaging Connect changes the game architecturally. A small MessagingConnect options block in the send request tells ACS to route a message via a vetted partner, while the partner handles number leasing, local compliance, and operator peering. The developer keeps coding against the same ACS SDK, and delivery receipts flow back into Azure Event Grid as always.

Infobip, a global communications platform with direct operator connections in 190+ countries, steps in as the first partner. That means ACS users can now provision virtual long numbers (VLNs), dynamic alphanumeric sender IDs, and—soon—short codes in markets that previously showed up as unsupported in the Azure portal. Infobip’s announcement boasts two-way SMS availability in 100+ countries under this arrangement. That’s a leap from largely one-way coverage in many regions, opening doors for customer service chatbots, appointment confirmations, and interactive alerts.

How Messaging Connect Works Under the Hood

The architecture is elegantly simple. Application code calls the standard ACS SMS send method—either REST API or SDK—and adds a messagingConnect block containing the partner identifier and authentication credentials. ACS then forwards the message via a secure bridge to Infobip’s platform, which handles everything from carrier routing to handset delivery. Responses, delivery reports, and inbound messages are relayed back to ACS and surfaced through the familiar Event Grid topics.

Provisioning follows a similar handshake. When a developer tries to acquire a number in a country where ACS has no native inventory, the portal presents a “Messaging Connect” option. Selecting it redirects to Infobip’s interface, where the team completes KYC, uploads regulatory docs, and leases numbers. Once approved—a process that can take minutes in some countries and weeks in others—the number appears in the Azure portal as a first-class ACS phone number resource. From that point, it behaves identically to a native number, albeit with partner-dependent delivery characteristics.

The preview API version is 2025-05-29-preview. Microsoft has published preview SDKs for C# and JavaScript, with Python and Java promised later. Preview features, of course, come without service level agreements and may change before general availability. For production flows—especially authentication OTPs—that’s a non-trivial risk.

What Infobip Brings to the Table

Infobip’s integration isn’t just about filling potholes. It adds capabilities that many ACS users have requested for years:

  • Expanded geographic reach: Infobip claims to enable SMS numbers in 100+ additional countries where ACS had no presence. Combined with ACS native coverage, the program’s total footprint stretches toward 190+ countries for outbound messaging.
  • Multiple sender types: Virtual long numbers (also called long codes) support two-way flows and are the bread-and-butter for conversational SMS. Dynamic alphanumeric sender IDs—common in Europe and Asia—let brands send messages that appear from a name like YourBank instead of a number. Short codes, often used for high-volume marketing, are on the roadmap.
  • Two‑way messaging: Critically, Infobip enables inbound messaging on local numbers in over 100 countries. That means customers can reply to alerts, participate in surveys, or interact with support bots—all without leaving Azure’s event pipeline.
  • Platform parity: Infobip-provisioned numbers surface in Azure portal, support Event Grid, and integrate with Log Analytics. No separate console for basic monitoring.

However, those 100+ countries are not a uniform promise. Two‑way support depends on operator agreements and local regulations, which vary widely. Alphanumeric sender IDs, for instance, often work only one‑way and may require pre‑registration in markets like India or Saudi Arabia. Short codes involve lengthy approval processes and carrier contracts. The “100+” figure is best read as the number of countries where Infobip can enable at least one sender type with some form of inbound capability—not a blanket guarantee of full two‑way service.

The Developer and Operator Experience

For teams already using ACS, the workflow is nearly unchanged. The biggest lift is adding the partner credentials to your application’s configuration. Sample code from Microsoft’s documentation shows a straightforward send:

var smsSendOptions = new SmsSendOptions
{
    EnableDeliveryReport = true,
    MessagingConnect = new MessagingConnectOptions
    {
        PartnerId = "infobip",
        Credentials = new MessagingConnectCredentials
        {
            ApiKey = "your-infobip-api-key"
        }
    }
};

No new endpoint URLs, no separate SDKs. The C# and JavaScript preview libraries handle the rest. Delivery reports and incoming messages appear in the same event streams as native ACS messages, keeping your monitoring and response logic unchanged.

Number provisioning, though, introduces a new step. The Azure portal redirects to Infobip’s site for KYC and documentation upload. This is where the “outsourced compliance” model takes hold. Infobip’s team verifies business registrations, obtains local approvals, and manages opt‑out handling according to local law. For enterprises accustomed to navigating these waters alone, it’s a significant time saver. But legal teams must still vet contractual terms, data residency, and audit rights. Just because Infobip handles the paperwork doesn’t mean the enterprise is off the hook for GDPR, CCPA, or other obligations.

Separating Coverage Hype from Reality

Microsoft markets Messaging Connect as a route to 190+ countries. Infobip’s press release highlights 100+ additional countries with two‑way SMS. Those numbers measure different things. Microsoft’s 190+ includes one‑way alphanumeric sender IDs in markets where a simple delivery path exists, even if no local number is provisioned. Infobip’s 100+ typically refers to countries where a VLN or long code can be leased and used for inbound traffic. Some overlap, but many edge cases exist.

A few real‑world implications:

  • In Brazil, alphanumeric senders are widely used for one‑way notifications, but two‑way requires a local number with strict registration. Infobip can provide that path now via ACS.
  • In Saudi Arabia, sender ID pre‑registration can take weeks, and certain content is blocked. The integration doesn’t bypass those rules; it just puts Infobip on the front line to handle them.
  • In China, SMS delivery involves state‑owned carriers and unique compliance hurdles. Coverage claims must be verified per province and sender type.

The bottom line: before building a global campaign, teams must run an availability matrix directly in the Azure portal (or Infobip’s provisioning UI) and note expected provisioning timelines. Broad marketing figures are a starting point, not a guarantee.

Regulatory, Security, and Deliverability Concerns

The division of labor is clear: Microsoft retains the API, authorization, and telemetry; Infobip handles the telco layer. But that doesn’t simplify the compliance stack—it redistributes it.

Data protection: Message content and metadata may pass through Infobip’s systems and, in some cases, third‑party jurisdictions. A Data Protection Impact Assessment is essential, especially for healthcare, finance, or EU‑facing applications. Confirm where logs are stored, who can access them, and how long they persist.

Security: The integration doesn’t alter the inherent risks of SMS. SIM swapping, SS7 interception, and social engineering remain threats. For authentication, enterprises should layer additional signals—device fingerprinting, behavioral analysis, or push‑based second factors—rather than relying solely on SMS OTPs. The partner model merely adds another hop; it doesn’t make the channel more secure.

Deliverability: Partner routing introduces new variables. Infobip’s carrier connections are generally high‑quality, but local network conditions vary. Teams should instrument delivery rates, latency, and failover patterns via Event Grid and Log Analytics. Maintain a backup route—whether an alternative CPaaS or a direct operator connection—for mission‑critical messages until the partner’s performance is proven in each market.

Opt‑out and abuse: Infobip manages opt‑out keywords and rate limiting. But the enterprise remains responsible for honoring those opt‑outs and preventing spam. Ensure your ACS logic correctly respects the opt‑out status Infobip reports back.

Commercial Reality: Pricing, Lock‑in, and Multi‑Partner Strategy

Pricing for Messaging Connect will likely follow a partner‑direct model. Expect variable per‑message fees that differ by country and sender type, plus monthly number leases and one‑time registration costs. These aren’t listed on any public price sheet yet—you’ll need to negotiate directly with Infobip. Factor all components into your TCO: a campaign that looks cheap on a per‑message basis could become expensive once number leases and regulatory fees hit.

Vendor concentration is another concern. With Infobip as the sole partner at launch, any service disruption or pricing change hits you directly. Microsoft hints at future partners; a multi‑partner strategy would let teams route based on cost, performance, or regional strengths. Until then, have a contingency plan. Contractual SLAs with Infobip should cover availability, latency, and support responsiveness.

What This Means for Windows and Azure Shops

For organizations that live inside the Azure ecosystem, Messaging Connect is a watershed. It eliminates the need to stitch together standalone CPaaS APIs for international SMS, bringing everything under the Azure portal, SDKs, and security model. For Windows‑focused teams that already use Azure Monitor, Event Grid, and PowerShell for automation, adding global SMS via Infobip feels natural.

The preview status, however, demands caution. Rolling out a global two‑factor auth SMS flow on a preview API is asking for trouble. Pilot with low‑risk notification traffic first. Test delivery in each target country, validate inbound handling, and monitor consistently for weeks before switching critical paths.

A structured adoption checklist:

  1. Audit your SMS footprint: List every country and sender type you need today. Separate one‑way notifications from two‑way conversations.
  2. Verify coverage: Using the Messaging Connect blade or Infobip’s UI, confirm that your required countries and sender types are truly available. Record provisioning lead times.
  3. Negotiate commercial terms: Get itemized quotes for messages, numbers, and registration fees. Lock in SLAs for uptime and latency.
  4. Architect your fallback: Keep a secondary provider or native ACS route for high‑priority OTP traffic until the Infobip route proves itself.
  5. Deploy monitoring: Wire delivery events, failures, and inbound messages into your existing Azure dashboards. Compare performance against your current CPaaS.
  6. Legal and DPIAs: Map data flows, confirm storage locations, and secure the right to audit Infobip’s handling of your message content.
  7. Pilot, then scale: Start small, measure, and expand gradually.

Bottom Line

Infobip’s integration with Azure Communication Services through Messaging Connect is a pragmatic, long‑overdue fix for the global SMS gap in ACS. It lets developers stay inside their Azure comfort zone while tapping Infobip’s direct‑to‑carrier network. The immediate availability of two‑way SMS in over 100 new countries opens real‑time customer interactions that were previously impractical.

But the preview flag matters. This isn’t a GA service, and the lack of an SLA makes it a gamble for production authentication or transactional alerts. The lofty coverage figures require per‑country validation, and the single‑partner model introduces concentration risk. Smart teams will pilot now, negotiate aggressively, and keep the eject button ready with a fallback CPaaS. When Messaging Connect matures to GA and adds more partners, it could become the default SMS backbone for Azure‑centric enterprises. Until then, it’s a powerful tool for those who use it with eyes wide open.