Some domains could not be retrieved in Communication Service

Question

Some domains could not be retrieved in Communication Service

Fabian Fischer 25

I have a communication service setup in Azure. In the Azure Portal, when I navigate to the communication service -> email -> domains, I get the following error (actual IDs masked). Any clues on what could cause this?

The service is working so this is just something that happens in Azure Portal, but it prevents me from configuring the domains.

Some domains could not be retrieved. Error fetching /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Communication/emailServices/xxx/domains/AzureManagedDomain: An unknown error occured,Error fetching /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Communication/emailServices/xxx/domains/xxx.se: An unknown error occured

Shree Hima Bindu Maganti 5,165 Reputation points Microsoft External Staff Moderator

2025-05-13T15:11:30.89+00:00

Hi @Fabian Fischer
The error you are experiencing while retrieving domains in the Azure Communication Service may be due to several factors. Although the service is operational, issues in the Azure Portal can result from temporary backend problems, permission issues, or misconfigurations in resource setup.

Azure services may occasionally experience temporary outages or issues. Check the Azure status page for any ongoing incidents affecting the Communication Services.

Verify that your account has the necessary permissions to access domains within the Azure Communication Service. Inadequate permissions can lead to errors when fetching resources.

Review the configuration of your Azure Communication Service and associated domains. Ensure that the domains are correctly set up and there are no conflicts or misconfigurations.

If this is a transient error, waiting and retrying later may resolve the issue.
Add Azure Managed Domains to Email Communication Service (platform-azp)

Troubleshooting domain configuration issues
https://azure.status.microsoft/status
Let me know if you have any further assistances needed.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-05-14T10:20:16.21+00:00

Hi Fabian Fischer,

Thank you for raising this. the issue seems related to how the Azure Portal loads domain metadata while the service backend works, the portal may fail to display some domains due to internal timeouts or retrieval errors.

Our internal team is currently investigating this behavior. In the meantime, you can still manage domains using Azure CLI or ARM templates as a workaround. please provide the details which I have shared in the private chat.

Accepted answer

1 additional answer

Your answer

Shree Hima Bindu Maganti 5,165 Reputation points Microsoft External Staff Moderator

2025-05-13T15:11:30.89+00:00

Hi @Fabian Fischer
The error you are experiencing while retrieving domains in the Azure Communication Service may be due to several factors. Although the service is operational, issues in the Azure Portal can result from temporary backend problems, permission issues, or misconfigurations in resource setup.

Azure services may occasionally experience temporary outages or issues. Check the Azure status page for any ongoing incidents affecting the Communication Services.

Verify that your account has the necessary permissions to access domains within the Azure Communication Service. Inadequate permissions can lead to errors when fetching resources.

Review the configuration of your Azure Communication Service and associated domains. Ensure that the domains are correctly set up and there are no conflicts or misconfigurations.

If this is a transient error, waiting and retrying later may resolve the issue.
Add Azure Managed Domains to Email Communication Service (platform-azp)

Troubleshooting domain configuration issues
https://azure.status.microsoft/status
Let me know if you have any further assistances needed.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-05-14T10:20:16.21+00:00

Hi Fabian Fischer,

Thank you for raising this. the issue seems related to how the Azure Portal loads domain metadata while the service backend works, the portal may fail to display some domains due to internal timeouts or retrieval errors.

Our internal team is currently investigating this behavior. In the meantime, you can still manage domains using Azure CLI or ARM templates as a workaround. please provide the details which I have shared in the private chat.

Answer 1

Suresh Chikkam 2,135 Microsoft External Staff Moderator

Fabian Fischer, I know how irritating it is when the portal simply refuses to show domains that are actually there. What’s happening under the covers is a brief timeout or hiccup in the portal’s domain-metadata API especially for AzureManagedDomain or any custom domain still completing DNS validation. The good news is your email flow isn’t broken, it’s just the UI.

To unblock yourself right now, switch to the CLI so you can see and fix whatever’s stuck. First, list everything on your Email Communication resource.

az communication email domain list \
  --resource-group YourResourceGroup \
  --email-service-name YourEmailService

If one of your domains shows a provisioningState of Pending or Failed, kick off a fresh DNS.

az communication email domain initiate-verification \
  --resource-group YourResourceGroup \
  --email-service-name YourEmailService \
  --domain-name contoso.com

Wait for that command to report “Succeeded,” then reload the portal. If the portal still errors after you see Succeeded everywhere, try an incognito window or clear your browser cache—those stale tokens sometimes hang onto old errors. Once the CLI tells you all domains are green, the portal will finally reflect that state. If it doesn’t, you can always fall back on the same CLI commands (or ARM templates) to manage domains reliably until the UI issue is fully resolved.

Hope it helps!

Please do not forget to click "Accept the answer” and Yes wherever the information provided helps you, this can be beneficial to other community members.

Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-06-02T06:49:39.05+00:00

Hi Fabian Fischer,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further query do let us know.
Fabian Fischer 25 Reputation points

2025-06-02T11:19:59.08+00:00

Sorry for the late reply, when I run the email domain list command in Azure CLI I get the error "(ParentResourceNotFound) Failed to perform 'read' on resource(s) of type 'EmailServices/Domains', because the parent resource '/subscriptions/xxx/resourceGroups/yyy/providers/Microsoft.Communication/EmailServices/zzz' could not be found.

Code: ParentResourceNotFound.

Any clues?
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-06-03T06:38:20.66+00:00
First, update the Azure CLI and the Communication extension so that the commands recognize EmailServices.

az extension update --name communication

and, if that fails,

az extension remove --name communication az extension add --name communication

Next, check tht the Communication provider is registered by running

az provider show --namespace Microsoft.Communication --query "registrationState" -o tsv

If it returns anything other than “Registered,” register it wth

az provider register --namespace Microsoft.Communication

and wait until it reports “Registered.” Confirm you’re in the correct subscription by checking

az account show

and, if needed, switch wth

az account set --subscription "<your-subscription-id>"

Then verify the resource group exists:

az group show --name "<YourResourceGroup>"

If that errors out, you are in the wrong resource group or subscription. Once the group check succeeds, verify the top‐level Communication Service by running

az resource show --resource-group "<YourResourceGroup>" --namespace "Microsoft.Communication" --resource-type "CommunicationServices" --name "<YourAcsName>"

If that returns nothing or an error, the ACS wasn’t created, or you have the wrong name. Assuming it shows your ACS, check whether an EmailServices child exists with

az resource list --resource-group "<YourResourceGroup>" --namespace "Microsoft.Communication" --resource-type "EmailServices" --query "[].name" -o tsv

If this returns nothing, you need to create the email subresource. Do that by running

az communication email create --resource-group "<YourResourceGroup>" --name "<DesiredEmailSvcName>" --location "<RegionOfAcs>" --sku-name "Free_Tier"

After it finishes, confirm provisioning by running

az resource show --resource-group "<YourResourceGroup>" --namespace "Microsoft.Communication" --resource-type "EmailServices" --name "<DesiredEmailSvcName>" --query "properties.provisioningState" -o tsv

and wait until it reports “Succeeded.” Once you have an EmailService whose provisioningState is “Succeeded,” list domains with

az communication email domain list --resource-group "<YourResourceGroup>" --email-service-name "<DesiredEmailSvcName>"

If that still errors with “ParentResourceNotFound,” double‐check that the value of <DesiredEmailSvcName> matches exactly (including case) what the earlier az resource list returned, and check that the account has at least the Microsoft.Communication/emailServices/read permission lack of that permission can appear as “not found.” When you run the domain list against the correct, fully provisioned EmailService under the right subscription and resource group, you’ll see the domains (or an empty array) even if the portal still shows an error.
Fabian Fischer 25 Reputation points

2025-06-03T07:46:57.9833333+00:00

Thank you, I am able to list the domains, and the domain I want has provisioning state "succeeded" so that is fine. However, what I'm actually after is I want to list my verified senders and update sender name. According to chatGPT, that's not even possible in azure CLI, is that true? How do I go about it if I cannot see the domain in the portal?
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-06-03T14:41:58.5433333+00:00
Fabian Fischer, you can absolutely manage your verified senders from the CLI, even if the portal isn’t showing your domain. Once you know the domain’s provisioningState is “Succeeded,” just run these commands.

First, to see every sender username tied to a domain (for example, example.com).

az communication email domain sender-username list \ --resource-group MyResourceGroup \ --email-service-name MyEmailService \ --domain-name example.com

You’ll get a JSON list showing each username (the part before “@example.com”) and its current display name.

If you want details on a single sender, say you had a “newsletter@example.com” do:

az communication email domain sender-username show \ --resource-group MyResourceGroup \ --email-service-name MyEmailService \ --domain-name example.com \ --sender-username newsletter

That returns exactly how “newsletter” is configured, including its display name.

To change (or add) a display name for an existing sender.

az communication email domain sender-username update \ --resource-group MyResourceGroup \ --email-service-name MyEmailService \ --domain-name example.com \ --sender-username newsletter \ --display-name "Contoso News Alerts"

If “newsletter” didn’t exist yet, this command actually creates it and sets its display name to “Contoso News Alerts.” It’s the same command whether you’re updating or creating.

If you ever need to delete a sender username, just use:

az communication email domain sender-username delete \ --resource-group MyResourceGroup \ --email-service-name MyEmailService \ --domain-name example.com \ --sender-username newsletter

And finally, if you’d rather explicitly create a brand-new sender (instead of relying on the update command).

az communication email domain sender-username create \ --resource-group MyResourceGroup \ --email-service-name MyEmailService \ --domain-name example.com \ --sender-username billing \ --display-name "Your Company Billing"

That creates “billing@example.com” with the display name “Your Company Billing.”

In every case, just replace MyResourceGroup, MyEmailService, and example.com with whatever matches your setup. Even if the portal still refuses to show your domain, these CLI commands will let you list, add, update, or remove verified senders without any problem.
Fabian Fischer 25 Reputation points

2025-06-04T10:02:34.9266667+00:00
Great, that seems to work. However, I created a new sender and see it when I run the list command like this:
"displayName": "xxx",

"id": "/subscriptions/xxx/resourcegroups/mygroup/providers/microsoft.communication/emailservices/myemailservice/domains/mydomain/senderusernames/info", "name": "info", "resourceGroup": "xxx", "type": "emailservices/domains/senderusernames", "username": "info"

However when I try to send an email using the API from senderaddress info@mydomain, I get the error "Invalid email sender username: 'info'. Please use a username from the list of valid usernames configured by your admin.

Status: 400 (Bad Request)

ErrorCode: InvalidSenderUserName"

Does it need some time for changes to propagate or what could be the problem? It has been a couple of hours since I created it now.

Also , I changed the displayName of my old sender but I still ge the old name when I send emails.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-06-04T15:38:10.4933333+00:00
Hi Fabian Fischer,

Thanks for the update you’ve done everything correctly so far.

Regarding the error with info@yourdomain, this typically happens when the sender username has been created successfully but hasn't fully propagated across the system yet. Even though it shows up in the CLI, it might not be ready for sending immediately. This usually resolves on its own within a couple of hours, but in some cases, it might take a bit longer.

You can double-check the current state of the sender with:

az communication email domain sender-username show \ --resource-group <YourResourceGroup> \ --email-service-name <YourEmailServiceName> \ --domain-name <yourdomain.com> \ --sender-username info

Make sure the provisioning state is Succeeded. If it is, give it a little more time and try sending again.

As for the display name not reflecting the change that’s expected behavior. The email service may cache sender metadata briefly. It usually updates automatically, but there can be a delay before the new display name starts appearing in outbound emails.

If the new display name still doesn’t show after a few more hours, you can try deleting and recreating the sender with the updated display name.

Try to accept the solution if my efforts are helpful.
Fabian Fischer 25 Reputation points

2025-06-05T07:03:43.6566667+00:00

Thank you, it has been very helpful

Answer 2

Dear Fabian Fischer,

Thank you for reaching out about the issue you’re experiencing with retrieving domains in Azure Communication Services. I understand how frustrating it can be when the Azure Portal doesn’t display the information you need, especially when you’re trying to configure domains for your email service.

The error message you’re seeing, "Some domains could not be retrieved," typically occurs when there’s a temporary issue with the Azure Portal or the backend service. Since you mentioned that the service itself is working, this is likely a display or retrieval problem rather than a functional one.

First, refresh the Azure Portal page or log out and log back in. Sometimes, this can resolve temporary glitches in the portal. According to Microsoft’s documentation, refreshing the portal can help clear cached data that might be causing display issues.

Second, check if there are any ongoing service issues in the Azure status page. Occasionally, regional or service-specific outages can affect the portal’s functionality. You can find the latest updates here: Azure Status.

Third, ensure that your account has the necessary permissions to view and manage domains in Azure Communication Services. The error might occur if there’s a permission mismatch.

I hope this helps

Best regards, Alex P.S. If my answer help to you, please Accept my answer PPS That is my Answer and not a Comment https://ctrlaltdel.blog/

Share via

Some domains could not be retrieved in Communication Service

1 additional answer

Your answer