ACS 10DLC Brand/Campaign registration - subscription not eligible message

Question

I'm trying to enable SMS for Local numbers using an Azure Communication Service. When I go to start the brand/campaign registration in my communication service, I get a message saying, "Your subscription is not eligible for Brand and Campaign registration."

Currently:

• Subscription is pay-as-you-go
• Billing country is United States
• Communication Service is active
• Microsoft.Communication resource provider is registered
• Issue persists across computers/users
• When attempting to purchase a local phone number for this communication service, I get the message "To enable SMS functionality for local numbers, you need to submit a brand and ensure your campaign is approved first. Click here to submit your brand"
• Created a new resource group and communication service to ensure the subscription wasn't free/trial at any time

I can provide more information if needed.

Answer 1

Hello @Akshaya Ramanan

Thank you for the follow-up and for sharing the screenshots — that helps a lot.

You're right that the 10DLC documentation shows "Local" as the phone number type. However, this "Local" option specifically refers to US 10DLC numbers (A2P SMS-capable 10-digit local numbers), not the standard geographic local numbers that are available for purchase directly in the Azure portal.

Quick Clarification:

• Standard Local numbers in ACS > Voice calls only (no SMS support by design).
• 10DLC numbers >Local-looking 10-digit numbers that do support SMS, but they require Brand + Campaign registration through TCR first.

This is why you're seeing the "Your subscription is not eligible for Brand and Campaign registration" message — the system is currently treating it under the standard local number path.

How to proceed:

1. Go to your Azure Communication Services resource > Telephony and SMS > Regulatory documents (or Brands & Campaigns).
2. Create a new application and select:

• Country or region: United States of America
• Phone number type: Local
• Application type: Brand

3.Complete the Brand registration with your company details.

Once the Brand is approved, you can create a Campaign and then provision a 10DLC number that supports SMS.

If you still receive the "subscription not eligible" error after selecting Local correctly, this is a known situation where the subscription needs a backend capability flag enabled. In that case, I recommend opening a support ticket directly from your ACS resource with the details (subscription ID, resource ID, and screenshots). Support can usually enable the 10DLC capability quickly.

Reference :

https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/sms/apply-for-ten-digit-long-code

https://learn.microsoft.com/en-us/azure/communication-services/concepts/numbers/phone-number-management-for-united-states

https://learn.microsoft.com/en-us/azure/communication-services/concepts/sms/sms-number-types

If the answer is helpful,  Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you

 

Answer 2

Hello @Akshaya Ramanan
Thank you for the detailed information. The Microsoft Learn documentation reflects the standard experience for subscriptions that are already eligible for 10DLC onboarding, where the Phone number type = Local option is available during Brand and Campaign registration. Since your portal displays “Your subscription is not eligible for Brand and Campaign registration”, the Local option will not appear until the subscription passes the required eligibility checks. This indicates the issue is related to the subscription or billing profile configuration rather than the Azure Communication Services resource itself. Even with a Pay-As-You-Go subscription and United States billing country, additional backend validation may still be required. We recommend opening an Azure Support request so the subscription can be reviewed for 10DLC enablement, billing account type, account verification status, and any internal restrictions preventing registration. Once the subscription is confirmed eligible, the Local option should become available and you will be able to proceed with Brand registration and Campaign approval for SMS-enabled local numbers.
https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/sms/apply-for-ten-digit-long-code
Let me know if you have any further assistance needed.

Answer 3

The error occurs because 10DLC brand and campaign registration is only available when both the subscription type and billing location meet the eligibility rules for US/Canada local SMS numbers.

From the documented rules:

1. To acquire and use US or Canada local numbers with SMS (via 10DLC), the subscription must be a paid Azure subscription of an eligible agreement type.
2. For United States and Canada, eligible agreement types for local (geographic) numbers include:
   • Modern Customer Agreement (Field and Customer Led)
   • Modern Partner Agreement (CSP)
   • Enterprise Agreement
   • Pay-As-You-Go
3. 10DLC SMS availability is further restricted by subscription billing location:
   • For US 10DLC SMS: the Azure subscription billing location must be United States (excluding Puerto Rico) or Canada.
   • For Canada 10DLC SMS: the Azure subscription billing location must be Canada or United States.

Given that the subscription is Pay-As-You-Go and the billing country is United States, the most common reasons for the “subscription not eligible for Brand and Campaign registration” message are:

• The subscription, while Pay-As-You-Go, is not one of the supported Azure agreement types for 10DLC (for example, legacy or special contract types that are not in the supported list).
• The billing location recorded for the subscription does not exactly match the supported locations (for example, a US territory such as Puerto Rico, which is explicitly excluded for US 10DLC SMS).

To resolve:

1. Confirm the Azure agreement type and billing location for the subscription match the supported combinations listed in:
   • “Subscription eligibility” in the US phone number management article.
   • “Subscription eligibility” in the Canada phone number management article.
2. If the subscription is not one of the supported agreement types or the billing location is a non‑supported region (for example, Puerto Rico), move the Azure Communication Services workload to a subscription that:
   • Is Pay-As-You-Go, Modern Customer Agreement, Modern Partner Agreement (CSP), or Enterprise Agreement, and
   • Has a billing location of United States (excluding Puerto Rico) or Canada.
3. After using an eligible subscription, purchase a local number and then follow the 10DLC registration flow (brand registration first, then campaign registration) as described in the 10DLC registration guidelines and SMS FAQ.

If the subscription clearly meets the documented eligibility (agreement type and billing location) and the portal still shows “not eligible,” the next step is to open an Azure support request for the subscription so support can correct the eligibility flag on the backend.

---

References:

• Phone number management for United States
• Phone number management for Canada
• Phone number management for Australia
• Phone number management for United Kingdom
• SMS FAQ
• 10DLC registration guidelines
• Quickstart: Get and manage phone numbers (platform-azp-new)