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

Michael Dako 20 Reputation points
2026-08-05T19:08:21.5533333+00:00

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:

  1. What specific eligibility check is failing here, beyond the documented MCA/PAYG/US criteria?
  2. 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.
  3. Is this the same issue reported in these other threads with an identical symptom (MCA + US billing, still flagged ineligible)?

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:

  1. What specific eligibility check is failing here, beyond the documented MCA/PAYG/US criteria?
  2. 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.
  3. Is this the same issue reported in these other threads with an identical symptom (MCA + US billing, still flagged ineligible)?

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.

Azure Communication Services
0 comments No comments

Answer accepted by question author
Allan Solomon Mejia 3,510 Reputation points
2026-08-06T03:32:32.0733333+00:00

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.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.