problem at Creating resource Communication Service, get error: Validation failed. Required information is missing or not valid.

Question

problem at Creating resource Communication Service, get error: Validation failed. Required information is missing or not valid.

Bowei Tong 0

User's image

my Subscription "Pay-As-You-Go" and Resource group "cb" is active and works well for creating/hosting other services like app service,logic-app and so on. but problem when create Communication Service. the resource name "cb-sms" is not conflict with all other resources under my "Pay-As-You-Go" Subscription.

2 answers

Your answer

Answer 1

Hi @Bowei Tong,

This error typically occurs due to one or more of the following:

Azure Communication Services are not available in all regions. If you’re trying to deploy in a region where it’s unsupported, you’ll get this validation error, even if everything else is correct.
Sometimes, subtle missing fields (like not choosing a correct data location or billing type) can trigger this error.
While “Pay-As-You-Go” is generally supported, certain legacy or special types of subscriptions may lack required permissions or policies for communication services. It's rare but can happen.

Please follow these steps carefully:

Azure Communication Services are only supported in specific regions. Make sure you’re selecting one of the supported regions, like East US, West Europe, North Europe, West US 2 (See the full list here)
Ensure that you're selecting a valid and supported region and the resource name meets requirements between 1-80 characters, only alphanumeric and hyphens, and doesn't start or end with a hyphen. Make sure you’ve filled all required fields during the resource creation wizard. Create an Azure Communication Services resource
Sometimes, using the Azure Portal hides the exact error message. Using CLI can give clearer diagnostics:

az communication create --name cb-sms --resource-group cb --location "East US"

If this also fails, the CLI output will give a more detailed validation message. Azure CLI for Communication Services

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Let me know if you have any further Queries.

Bowei Tong 0 Reputation points

2025-06-11T11:08:52.1666667+00:00

thanks for quick reply, I tried Azure CLI by following your suggest. it said "Interactive authentication is needed" butwhen i do login, it said I was already login, i am using my current login subcription.
Bhargavi Naragani 4,560 Reputation points Microsoft External Staff Moderator

2025-06-11T11:43:47.66+00:00

Hi @Bowei Tong,

From the message:

“Timeout waiting for token from portal. Audience: https://management.core.windows.net” and “Interactive authentication is needed”

It looks like you’re encountering a Cloud Shell token timeout or stale session issue. Even though Cloud Shell says you're already signed in, the session might have expired or lost access to the token required for creating a new resource like Communication Services, which has stricter authentication checks. This happens occasionally in Cloud Shell, especially if the session has been idle for a while, a cached or stale authentication token is being reused, and the target resource requires elevated permissions or user re-authentication

Even if you're technically signed in, the CLI is requesting a fresh login token for security-sensitive operations. Please run:

az login --use-device-code

Then open https://microsoft.com/devicelogin in your browser, enter the code shown, and complete the sign-in process. This will force a new login flow and refresh your access token with the right scopes. az login documentation

After the device login succeeds, retry your command with a supported region (avoid "norwayeast" if you're unsure it’s supported):

az communication create --name cb-sms --resource-group cb --location "eastus"

Hope this information helps, let me know if you still face the issue.

Answer 2

Bowei Tong 0

it maybe caused by: subscription must explicitly register the providers for the services you want to use.

The Microsoft.Communication is not registered in my subscription yet.

Share via

problem at Creating resource Communication Service, get error: Validation failed. Required information is missing or not valid.

2 answers

Your answer