You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/sms/messaging-connect.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ The following table summarizes capabilities available when using Messaging Conne
72
72
| Java SDK | ❌ (coming soon) |
73
73
| Automatic Country Sender selection (partner-managed) | Infobip ✔️ |
74
74
75
-
> **Note**: Future updates will include support for more SDKs, sender types, and additional partners.
75
+
76
76
77
77
### Authentication: Secure Access with Azure Identity
78
78
@@ -269,22 +269,22 @@ Let's go step-by-step:
269
269
270
270
In the Azure portal, in your Communication Services resource, go to the **Messaging Connect** blade and choose a partner from the list. Accept the terms. You're redirected to the partner’s website to complete the number acquisition.
To purchase the number, follow the prompts provided by the Messaging Connect partner. Depending on the country, you may need to upload supporting documents or complete identity verification. Once approved, the number is assigned to your partner account.
Once the partner confirms that your numbers are provisioned, they trigger the sync with Azure Communication Services. After the sync is complete, the numbers automatically appear in your ACS resource—ready to use with the ACS SMS API, just like any number provisioned directly through Azure Communication Services. No extra setup is needed on your side.
> The Messaging Connect partner sets the approval and activation timeline, which varies by country and number type. Messaging Connect doesn't currently support instant provisioning, and Microsoft isn't involved in the vetting or approval process.
0 commit comments