Skip to content

Commit eebef4e

Browse files
Merge pull request #303400 from dbasantes/main
Update messaging-connect.md
2 parents 297588b + 90cb03a commit eebef4e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communication-services/concepts/sms/messaging-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ During Public Preview, you can acquire and use two types of sender identities fr
168168

169169
When you search for a country and number type in the Azure portal, you're offered Messaging Connect as an option if Azure Communication Services doesn’t support that configuration directly. You then complete the provisioning process through the partner’s portal.
170170

171-
🌐 The Messaging Connect partner determines country availability. The Messaging Connect partner (for example, Infobip) handles number types, compliance requirements, and onboarding steps, which vary by country.
171+
🌐 The Messaging Connect partner determines country availability. The Messaging Connect partner (for example, Infobip) handles number types, compliance requirements, and onboarding steps, which vary by country. See [Infobip SMS Coverage](https://www.infobip.com/docs/essentials/getting-started/sms-coverage-and-connectivity).
172172

173173
📌 Short codes aren't yet supported in Public Preview but are planned for General Availability.
174174

0 commit comments

Comments
 (0)