Bot Service Channels: Data showing 'Error retrieving bot data' — Portal-side retrieval issue

Pete-8982 0 Reputation points
2026-11-10T19:07:24.8+00:00

Problem description

I am experiencing an issue where the Azure Portal's Bot Service 'Channels' blade displays 'Error retrieving bot data' for multiple bots. The bots continue to operate normally, but I cannot view or configure their channel settings, and this problem blocks setting up new channels. The error started today, and previous access was functioning correctly.

Environment

Multiple Azure Bot resources in the same region, with the issue affecting the Channels blade in the Azure Portal.

What I've already tried

I checked multiple existing bots and observed the same 'Error retrieving bot data' message. I verified that existing bots are operational outside the portal. I attempted a hard refresh and cache clearing, but the problem persists. I also confirmed that the bots' Overview pages show they are functioning normally, and the issue only affects the Channels blade.

Current status

Currently, the Channels blade continues to show 'Error retrieving bot data,' and I am seeking assistance to diagnose whether this is a portal retrieval failure, a permissions issue, or a backend service problem, and to find a resolution.

Azure AI Bot Service
Azure AI Bot Service

An Azure service that provides an integrated environment for bot development.


Answer recommended by moderator
SAI JAGADEESH KUDIPUDI 3,650 Reputation points Microsoft External Staff Moderator
2026-11-10T20:49:30.2533333+00:00

Hi @Pete-8982 ,

Since the bots are operating normally and the issue is limited to the Channels blade showing“Error retrieving bot data” across multiple bots, this appears to be a configuration retrieval issue rather than a bot runtime issue.

Please try the following:

  1. Validate through Azure CLI
       az bot show -g <resource-group> -n <bot-name>
       az bot directline show -g <resource-group> -n <bot-name>
    
  2. Capture a HAR trace while reproducing the issue and collect the HTTP status, x-ms-request-id, correlation ID, and UTC timestamp.
  3. Verify RBAC permissions by testing with an account that has sufficient permissions on the affected bot.
  4. Confirm whether all bots/subscriptions are affected and whether there were any recent RBAC or networking changes.

Result interpretation:

  • CLI works but portal fails → likely portal-side issue.
  • 403 → investigate RBAC/permissions.
  • 5xx from the API → requires further Bot Service backend investigation.

Reference

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Was this answer helpful?

0 comments No comments

0 additional answers

Sort by: Newest

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.