Subscription shows "not eligible for Brand and Campaign registration" despite meeting MCA + PAYG + US billing criteria.

Question

Subscription shows "not eligible for Brand and Campaign registration" despite meeting MCA + PAYG + US billing criteria.

Michael Dako 20

I'm trying to complete 10DLC Brand and Campaign registration for SMS on our Communication Services resource (acs-acscaller-prod, Local US number, application type = Brand). Opening the "Create a new regulatory documents application" wizard shows:

"Your subscription is not eligible for Brand and Campaign registration."

The Application Type dropdown is disabled and we can't proceed past Country/Region + Phone number type.

Per the subscription eligibility docs, Local/Toll-Free 10DLC registration requires a Modern Customer Agreement (MCA), Modern Partner Agreement (CSP), Enterprise Agreement, or Pay-As-You-Go subscription, billed to a US (excl. Puerto Rico) or Canada address. As far as I can tell, our subscription meets this:

Billing account agreement type: MicrosoftCustomerAgreement, active since 2023
Billing relationship: Direct (not Indirect — no CSP/reseller shown via the Billing API)
Subscription quota: PayAsYouGo_2014-09-01
Billing/sold-to address: United States

I can't find a documented reason this subscription would be excluded. A couple of questions for anyone who's hit this before or from the product team:

What specific eligibility check is failing here, beyond the documented MCA/PAYG/US criteria?
Could a prior CSP/reseller relationship on this billing account (even after transitioning to a direct MCA) leave a stale flag that blocks 10DLC eligibility? Our Microsoft 365 licensing is still managed by a reseller, though the Azure billing account itself shows as Direct with no active delegated admin (GDAP) relationship on the tenant.
Is this the same issue reported in these other threads with an identical symptom (MCA + US billing, still flagged ineligible)?
- https://learn.microsoft.com/en-us/answers/questions/5858184/
  - https://learn.microsoft.com/en-us/answers/questions/5812196/
    - https://learn.microsoft.com/en-us/answers/questions/5859720/
      - https://learn.microsoft.com/en-nz/answers/questions/5889295/

Any pointers on what to check or fix next would be appreciated — happy to share more detail via DM/private channel if that's easier for anyone from the ACS team to look at the account directly.I'm trying to complete 10DLC Brand and Campaign registration for SMS on our Communication Services resource (acs-acscaller-prod, Local US number, application type = Brand). Opening the "Create a new regulatory documents application" wizard shows:

"Your subscription is not eligible for Brand and Campaign registration."

The Application Type dropdown is disabled and we can't proceed past Country/Region + Phone number type.

Per the subscription eligibility docs, Local/Toll-Free 10DLC registration requires a Modern Customer Agreement (MCA), Modern Partner Agreement (CSP), Enterprise Agreement, or Pay-As-You-Go subscription, billed to a US (excl. Puerto Rico) or Canada address. As far as I can tell, our subscription meets this:

Billing account agreement type: MicrosoftCustomerAgreement, active since 2023
Billing relationship: Direct (not Indirect — no CSP/reseller shown via the Billing API)
Subscription quota: PayAsYouGo_2014-09-01
Billing/sold-to address: United States

I can't find a documented reason this subscription would be excluded. A couple of questions for anyone who's hit this before or from the product team:

What specific eligibility check is failing here, beyond the documented MCA/PAYG/US criteria?
Could a prior CSP/reseller relationship on this billing account (even after transitioning to a direct MCA) leave a stale flag that blocks 10DLC eligibility? Our Microsoft 365 licensing is still managed by a reseller, though the Azure billing account itself shows as Direct with no active delegated admin (GDAP) relationship on the tenant.
Is this the same issue reported in these other threads with an identical symptom (MCA + US billing, still flagged ineligible)?
- https://learn.microsoft.com/en-us/answers/questions/5858184/
  - https://learn.microsoft.com/en-us/answers/questions/5812196/
    - https://learn.microsoft.com/en-us/answers/questions/5859720/
      - https://learn.microsoft.com/en-nz/answers/questions/5889295/

Any pointers on what to check or fix next would be appreciated — happy to share more detail via DM/private channel if that's easier for anyone from the ACS team to look at the account directly.

0 comments

Answer accepted by question author

Allan Solomon Mejia 6,240

Hello @Michael Dako

If your Azure subscription is showing "Not eligible" for Brand and Campaigns, it's typically due to one or more eligibility requirements not being met rather than an issue with the subscription itself.

A few things to verify:

Confirm that you're using a supported subscription type. Some benefit programs (such as Azure Sponsorship, trial, or certain promotional subscriptions) may not be eligible for all marketplace or marketing benefits.
Ensure you're signed in with the same Microsoft account and Microsoft Entra tenant associated with the subscription and the program enrollment.
Verify that your subscription is active and doesn't have any billing or enrollment issues.
If this benefit is tied to a specific program (for example, Microsoft for Startups or Marketplace Rewards), check that all enrollment requirements have been completed and that the benefit has been provisioned successfully.

If everything appears to be configured correctly and the subscription still shows as Not eligible, this usually requires Microsoft to verify the backend eligibility status. I'd recommend opening a support request through the program portal (such as Founders Hub or Marketplace Rewards, depending on where you're accessing the benefit) so they can confirm why the subscription isn't qualifying.

If you can share:

the subscription offer type (for example, Pay-As-You-Go, Azure Sponsorship, Enterprise Agreement, etc.),
the program you're trying to use (Microsoft for Startups, Marketplace Rewards, ISV Success, etc.), and
a screenshot of the "Not eligible" message,

the community can help narrow down the exact cause.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

0 comments

1 additional answer

Your answer

Answer 1

Short answer: nothing is wrong with your billing setup, and nothing you enter in the wizard can clear that banner.

That message comes from a per-subscription eligibility/tier flag that the ACS backend evaluates before the wizard renders. When the flag is off, the Application Type dropdown is disabled by design — which matches exactly what you're seeing. So MicrosoftCustomerAgreement + Direct + PayAsYouGo_2014-09-01 + US sold-to are all necessary, but they are not sufficient on their own.

The reason is that US 10DLC Brand and Campaign registration is still in Public Preview and is currently enabled on an allow-list basis rather than being open to all eligible subscriptions. You can see the status documented here: https://learn.microsoft.com/azure/communication-services/concepts/sms/sms-number-types (10DLC — Availability: United States, Status: Public Preview)

On your question 2 — a prior CSP/reseller relationship: I have not seen any documented "stale reseller flag" that blocks 10DLC, and M365 licensing managed by a reseller does not feed the ACS eligibility check. Since your Azure billing account already reports Direct with an active MCA, I would not spend more time down that path.

On your question 3 — yes, those threads are the same symptom and the same underlying cause. I've seen this resolved exactly two ways: the backend team flips the subscription's tier to SMS-enabled, or the request is declined on preview-allow-list grounds and the customer is pointed at toll-free instead. I have not seen a single case fixed by the customer changing anything in the form.

What to do next:

Ask for the enablement explicitly rather than retrying the wizard. Have the following ready, because this is exactly the payload the backend team needs:
- Subscription ID
  - Resource ID of the ACS resource
    - Immutable Resource ID and Data Location
      - Number type (Local) and desired area code
        
        Estimated monthly message volume
        
        Written description of your SMS use case and opt-in wording
        
        You can pull the immutable resource ID and data location with: az communication show --name acs-acscaller-prod --resource-group <YOUR_RESOURCE_GROUP> --query "{immutableResourceId:immutableResourceId, dataLocation:dataLocation, location:location}" -o json
        
        In parallel, check whether Toll Free behaves differently on the same blade. Open the same wizard, select United States and Toll-Free instead of Local, and see whether Application Type becomes selectable. This is a useful discriminator — in past cases toll-free was fully unblocked on the exact same resource while 10DLC stayed refused. If toll-free works and you need to send now, toll-free verification is the practical unblock while the 10DLC request is pending.
        
        Capture the banner with the request ID. Reproduce it with browser DevTools open (F12, Network tab), then grab the failing request's x-ms-request-id response header along with a screenshot and the UTC timestamp. That ID lets the ACS team trace the exact eligibility evaluation for your subscription.
        
        If you do get enabled, budget for these (from https://learn.microsoft.com/azure/communication-services/concepts/pricing — SMS section): Brand Registration $4 one-time, Standard Brand Vetting $40 one-time (generally required for brands not in the Russell 3000), and campaign registration monthly by use case (Low Volume $1.50/mo, Sole Proprietor $2/mo, Charity $3/mo, Emergency $5/mo, Franchises $30/mo). Typical timelines are 2–3 business days for brand approval and 3–5 business days for campaign approval. Note that in the US and Puerto Rico, Azure Prepayment and prepaid credits cannot be used for 10DLC products.

If you can post the output of the az communication show command above plus the x-ms-request-id from the banner, I can line it up against the eligibility check and tell you whether you're looking at the preview allow-list or something specific to your subscription.

Thanks