An Azure communication platform for deploying applications across devices and platforms.
Hi Nicholas Bieghler & thx for join me at Q&A platform,
this error is usually raised before the Brand/Campaign workflow even starts, so it points to a subscription or ACS eligibility gate rather than anything in the brand details. An active Microsoft Customer Agreement with US billing is necessary, but it doesn’t automatically guarantee that 10DLC registration is enabled for the subscription. ACS applies additional eligibility checks for SMS and regulatory registration, and those checks can be tied to the subscription, billing profile, or the Communication Services resource itself. Because the portal stops you before you can enter the brand information, I’d ask Microsoft to verify the backend 10DLC/SMS eligibility flags for both the subscription and the ACS resource. Changing the brand data, recreating the registration form, or retrying in another browser won’t help if the subscription is being rejected at that stage.
Open or update the Azure Communication Services support case with the subscription ID, ACS resource name, region/data location, billing country, exact UTC timestamp of a failed attempt, and any correlation/request ID from the portal. Ask specifically whether the subscription is eligible for US Local Number 10DLC Brand/Campaign registration and whether an internal SMS provisioning restriction is blocking it.
If Microsoft confirms that the subscription is otherwise valid but not provisioned for 10DLC, only the ACS backend team can enable or clear that state.
rgds,
Alex