10DLC Brand/Campaign registration - subscription not eligible despite Microsoft Customer Agreement + US billing

Hi Nicholas,

The "Your subscription is not eligible for Brand and Campaign registration" banner you're seeing fires from an upfront backend eligibility check that runs before the wizard renders any fields — which is why your MCA (Azure Plan) with US billing doesn't get you past it. The published eligibility table (agreement type + billing location) is necessary but not sufficient; there's a separate telephony/SMS capability tier on the subscription that also has to be set.

Concretely, on Aug 23, 2026 the ACS backend team stated through a moderator that 10DLC is currently in preview and available only to select enterprise customers, with Toll-Free recommended as the interim path. On the other hand, one customer in the same situation was unblocked on Aug 17, 2026 after the backend team applied a tier upgrade to their tenant/subscription. So this is worth pursuing — it's just not something you can fix from the portal.

Here's what I'd do, in order:

1. Rule out the documented criteria in 60 seconds. Go to Subscription > Overview/Properties and Cost Management + Billing, and confirm: paid (no Azure free credits or Azure Prepayment funding the purchase), agreement type is MCA / Modern Partner (CSP) / EA / Pay-As-You-Go, and Sold-to country is United States excluding Puerto Rico (or Canada) — for 10DLC SMS specifically, only those two billing locations qualify. ✔ To verify: your sold-to country and agreement type match the tables in "Phone number management for United States." Also check whether the subscription ever carried a free-tier/trial promotion — another customer found the legacy freetier flag persisted in subscription metadata even after the promotion expired, and it kept blocking 10DLC.
2. Check the SMS capability state on the resource. ACS resource > Telephony and SMS > Phone numbers. If SMS shows**"None"** for US, that's the backend flag being unset — the same signature another customer confirmed on their thread. ✔ To verify: SMS status reads "None" rather than an eligible/enabled state.
3. Request backend 10DLC enablement. This is the actual unblock. Raise it against the ACS resource (Help + Support > Create a support request > Azure Communication Services) and, in parallel, email acstns@microsoft.com with the subject "Request to enable SMS/10DLC capabilities — Subscription not eligible for 10DLC Brand Registration." Include: subscription ID, tenant ID, ACS immutable resource ID + region, billing agreement type and sold-to country, a screenshot of the exact error, a screenshot of Telephony and SMS > Phone numbers showing the SMS state, and your use case (transactional vs marketing, consent model, expected volume). Ask explicitly for a backend 10DLC eligibility/tier review, referencing that a tier upgrade resolved this for another subscription in August 2026. ✔ To verify: you receive confirmation the tier upgrade was applied, then retry Regulatory Documents > Add > United States > Local > Brand and confirm the Application type field is now selectable. If the portal support flow auto-resolves and won't let you create a ticket (several people hit this), go to https://portal.azure.com/#create/Microsoft.Support, type quota, choose Other / Service and subscription limits (quotas), then Issue type: Other request — that path surfaces the Create button when the technical path won't.
4. Unblock messaging now with Toll-Free — this is what the ACS backend team recommended as the alternative while 10DLC remains gated. Acquire a Toll-Free number with SMS enabled and submit Toll-Free verification on the same resource. ✔ To verify: the Toll-Free number shows SMS enabled and the verification application reaches Verified.

This is a workaround, not a permanent fix — Toll-Free doesn't give you a local-presence 10DLC number, and Microsoft has said only that it is "actively working toward making 10DLC broadly available." I haven't seen a public GA date, so I won't quote one.

One thing to plan for: brand and campaign registrations are per ACS resource — they can't be reused or linked across resources or subscriptions, so if you're standing up multiple ACS resources, budget for a registration in each.

References:

• https://learn.microsoft.com/azure/communication-services/concepts/numbers/phone-number-management-for-united-states
• https://learn.microsoft.com/azure/communication-services/quickstarts/sms/apply-for-ten-digit-long-code
• https://learn.microsoft.com/en-us/answers/questions/5972395/your-subscription-is-not-eligible-for-brand-and-ca
• https://learn.microsoft.com/en-us/answers/questions/5967477/acs-10dlc-brand-campaign-registration-subscription

If Step 2 shows SMS as "None," post that back here along with the ACS region and whether Toll-Free verification works on this same resource — that combination tells us immediately whether it's the tier flag or something narrower on the billing profile.

I hope this helps clarify the available options.

Kindly let us know if the above helps or you need further assistance on this issue. 

Hi @Nicholas Bieghler

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?