Azure Communication Services Alphanumeric Sender ID is disabled for Sweden on an active Azure Plan

Hossein Shokri Ghadikolaei 0 Reputation points
2026-09-04T19:44:31.23+00:00

We need one-way SMS from Azure Communication Services to Swedish recipients using a dynamic alphanumeric sender ID such as Tandvy or a clinic name. We do not want to acquire or display a phone number, and we do not need inbound SMS.

Microsoft's Sweden capability page lists Alphanumeric Sender ID as Generally Available for sending SMS and unsupported for receiving SMS, which matches this use case.

What we have verified:

  • The destination is Sweden.
  • The Azure Communication Services resource uses the Europe data location.
  • The subscription is active, is shown in Azure billing as a Microsoft Azure Plan, and belongs to an active Microsoft Customer Agreement billing account.
  • The signed-in user is Owner of the subscription.
  • In Communication Services > Alphanumeric Sender ID > Dynamic, the Enable Alphanumeric Sender ID button is disabled.
  • An SDK send authenticated with the resource connection string, using a valid short alphanumeric sender and an authorized Swedish test recipient, returns Unauthorized with no provider message ID.
  • No SMS was sent and no Azure phone number is involved.

The Azure CLI support-ticket API also returned InvalidSupportPlan because the account has the Developer support plan. The portal troubleshooting flow does identify Assistance with SMS > Issues with enabling Alphanumeric Sender ID, but has not completed the entitlement change.

Is this a tenant-level entitlement that Microsoft must enable manually? If so, what is the supported free request path for a Developer support-plan customer when the subscription and country are eligible? We can provide the full subscription ID, tenant ID, ACS resource ID, screenshot, and failed request details privately to Microsoft staff.

Use case: consented, transactional dental appointment and service notifications. Testing is recipient-allowlisted, sender IDs are limited to valid 3-11 character values, and the application does not subscribe to SMSReceived events.

Azure Communication Services

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Divyesh Govaerdhanan 11,725 Reputation points MVP Volunteer Moderator
    2026-09-04T20:33:22.6566667+00:00

    Hello Hossein Shokri Ghadikolaei,

    Welcome to Microsoft Q&A,

    Sweden is officially listed for Dynamic Alphanumeric Sender ID (marked General Availability), so your prerequisites are correct and you're not missing a config step.

    What you're hitting is expected behavior, not a bug on your end. The "Enable Alphanumeric Sender ID" button being disabled even when every documented eligibility criteria is met (country, data location, subscription, permissions) means Microsoft needs to manually activate this feature at the tenant level for your subscription. It's a backend provisioning step, not something togglable purely from the portal. That also explains the Unauthorized SDK response, the SDK is correctly rejecting the send because the entitlement genuinely isn't active on your tenant yet, not because of a code or auth issue on your side.

    The good part: you don't need a paid support plan for this specific request. The InvalidSupportPlan error you hit is because a regular Technical support ticket requires Standard support minimum, but enabling this capability goes through a Quota request instead, which is free on any plan, including Developer.

    You need to need to create support request.

    1. Check your Azure subscription's billing address is in a supported location (Sweden is eligible).
    2. In Azure portal > Your ACS resource > Alphanumeric Sender ID >Dynamic tab > Click Enable Alphanumeric Sender ID.
    3. If button is unavailable/grayed out > Create a support ticket Request Microsoft to enable Alphanumeric Sender ID for your tenant

    You can create free Quota request and then on Additional details tab explain that you need Alphanumeric Sender ID capability enabled for your ACS. Normally you would create Technical support request for this, however, that requires minimum Standard support plan. Please follow my instructions below to avoid getting stuck in endless loop:

    1. Navigate to this link to start the process:

    https://portal.azure.com/#create/Microsoft.Support

    2. Enter quota in the box and click Go

    User's image

    3. Select Others / Service and subscription limits (quotas) and click Next

    User's image

    4. Click Create a support request button, as shown

    User's image

    5. Select Issue type: Service and subscription limits (quotas), Quota type: Other Requests, click Next

    User's image

    6. On Additional details tab, Enter description for your request

    User's image

    7. Finish filling out Additional details tab, click Next, review and click Create. You should receive an automated email within a few minutes.

    Please Upvote and accept the answer if it helps!!

    Was this answer helpful?

    1 person found this answer 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.