ACS 10DLC brand/campaign registration says subscription is not eligible despite MCA + U.S. billing

Question

I’m trying to enable SMS for Local, US Azure Communication Services phone numbers through 10DLC brand/campaign registration.

The Azure portal says Local, US numbers require Brand and Campaign registration before SMS can be enabled. However, when I go to Regulatory Documents and try to start the Brand/Campaign process, the portal says:

“Your subscription is not eligible for Brand and Campaign registration.”

Verified facts:

• Subscription is active and paid
• Billing agreement type: Microsoft Customer Agreement
• Billing / sold-to country: United States
• ACS resource name: telephony-main-4
• Local, US phone numbers are already provisioned and active
• The error appears before any brand details are entered
• Under Phone numbers, SMS is not enabled and the portal says Brand/Campaign registration is required first

Based on the official Azure documentation for U.S. phone numbers and 10DLC SMS, this subscription appears to meet the published requirements.

Can a Microsoft engineer please verify whether ACS SMS / telecom capabilities are correctly provisioned on this subscription and tenant? This looks like a backend eligibility/provisioning issue rather than a form-entry issue.

If needed, I can provide:

• subscription ID privately
• screenshots of the portal error
• screenshots of the Phone numbers page
• billing/account screenshots showing MCA + U.S. billing

Answer 1

Hi @Kurt

Thanks for the detailed information.

The behavior you are seeing is expected when using standard Local (geographic) ACS phone numbers. While your subscription (MCA, U.S. billing, paid) is valid, standard Local numbers do not support SMS in Azure Communication Services, so Brand/Campaign registration is not applicable for them.

Because SMS is not supported on these numbers, the portal surfaces the message*“Your subscription is not eligible for Brand and Campaign registration”* during the registration flow. This can appear misleading but is by design.

To send SMS using ACS, Microsoft supports only:

• 10DLC numbers (US only) – require Brand & Campaign registration
• Toll‑Free numbers – require Toll‑Free verification

References:

• Phone number capabilities & eligibility : https://learn.microsoft.com/en-us/azure/communication-services/concepts/numbers/sub-eligibility-number-capability
• Apply for 10DLC Brand & Campaign registration : 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

Recommended next step is to acquire 10DLC numbers (after Brand/Campaign approval) or use Toll‑Free numbers for SMS.

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

The documented eligibility requirements for 10DLC SMS on Azure Communication Services are:

1. A paid Azure subscription (no free credits)
2. An eligible agreement type (Modern Customer Agreement / Microsoft Customer Agreement, Modern Partner Agreement, Enterprise Agreement, or Pay-As-You-Go)
3. Azure subscription billing location in a supported country/region
4. For U.S. 10DLC SMS, the subscription billing location must be United States or Canada

From the provided details:

• Billing agreement type is Microsoft Customer Agreement (eligible)
• Billing / sold-to country is United States (eligible for U.S. 10DLC SMS)
• Local U.S. numbers are already provisioned and active (supported number type)

The portal message “Your subscription is not eligible for Brand and Campaign registration” despite meeting the published criteria strongly indicates a backend eligibility or provisioning issue rather than anything related to brand/campaign form data.

Because subscription-level eligibility and backend provisioning cannot be changed from the portal when this condition occurs, this scenario requires direct Microsoft support intervention to:

• Validate that 10DLC SMS capabilities are correctly enabled for the subscription and tenant
• Correct any misconfiguration in the ACS/telecom backend for that subscription

Next steps:

1. Confirm subscription type and billing location
   • Ensure the subscription in use for the ACS resource is indeed the MCA subscription with U.S. billing (not a different subscription in the tenant).
   • Confirm that the ACS resource is deployed in a region that supports U.S. 10DLC SMS.
2. Open a support case with Microsoft
   • Since this is a subscription/eligibility provisioning issue, it must be handled by Microsoft support or the ACS engineering team.
   • Provide in the ticket:
     • Subscription ID
     • ACS resource name and region
     • Screenshots of:
       • The “Your subscription is not eligible for Brand and Campaign registration” message in Regulatory Documents
       • Phone numbers blade showing Local U.S. numbers and SMS disabled with the 10DLC requirement message
       • Billing page showing Microsoft Customer Agreement and U.S. billing/sold-to country
3. Ask support to explicitly verify ACS telecom/10DLC flags
   • Request that support/engineering verify that:
     • The subscription is marked as eligible for U.S. 10DLC SMS
     • The ACS resource is correctly associated with that subscription and eligibility
     • Any internal feature flags or backend configurations required for 10DLC brand/campaign registration are enabled for the subscription and tenant

Given that the subscription meets the documented requirements, resolution will be on Microsoft’s side by correcting the eligibility/provisioning state so that the Brand and Campaign registration wizard can be started under Regulatory Documents.

---

References:

• Phone number management for United States
• Apply for 10DLC brand registration and campaign registration
• 10DLC registration guidelines
• SMS FAQ
• 10 Digit Long Code (10DLC) pricing