Azure SRE Agent chat section is getting error

Golekha Sahu 5 Reputation points Microsoft Employee
2026-07-23T13:12:33.52+00:00

Hi Team,

Can anyone help me to resolve the below Chat error issue ?

ErrorI am unable to fully address your request due to an internal error. Please retry to continue the conversation!

Azure AI Bot Service
Azure AI Bot Service

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sina Salam 31,296 Reputation points Volunteer Moderator
    2026-07-26T20:00:58.54+00:00

    Hello Golekha Sahu,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that your Azure SRE Agent chat section is getting error.

    The issue is between a failed SRE Agent conversation thread, missing SRE Agent access/managed identity permissions, blocked network access, or a service-side SRE Agent backend execution failure. This should not be treated first as an Azure AI Bot Service channel issue, because Azure SRE Agent chat uses its own thread, role, managed identity, connector, and network-control model. Azure SRE Agent conversations are handled as threads, and each thread has an ID that can be used for debugging and backend trace correlation. - https://learn.microsoft.com/en-us/azure/sre-agent/threads

    What you can do is to:

    • Start a new Azure SRE Agent chat thread and test with a simple prompt.
    • Confirm the signed-in user has SRE Agent Standard User or SRE Agent Administrator access.
    • Confirm the agent’s user-assigned managed identity has the required Azure RBAC permissions.
    • Confirm the target resource groups are added under Managed resources.
    • Check network mode and connectors only if the failing prompt depends on private resources, external systems, repositories, Kusto, Teams, Outlook, MCP, or other connectors.
    • If the same internal error happens in a new clean thread after these validations, open an Azure Support request with the failing thread ID because the remaining root cause requires Microsoft backend trace correlation.

    After validating the user role, managed identity permissions, managed resources, network path, and connector state, the issue can either be resolved directly by correcting the failed configuration, or escalated with the exact SRE Agent thread ID for backend investigation.

    Create an Azure support request via your portal - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request If a new clean thread still returns the same internal error after validating the user role, managed identity/RBAC, managed resources, and network path. At that point, the issue is not reliably fixable from the customer side and requires Microsoft backend trace correlation using the SRE Agent thread ID.

    I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

    Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

    Was this answer helpful?

    0 comments
  2. Karnam Venkata Rajeswari 5,090 Reputation points Microsoft External Staff Moderator
    2026-07-23T14:14:54.6733333+00:00

    Hello @Golekha Sahu ,

    Welcome to Microsoft Q&A .Thank you for reaching out to us.

    The behavior indicates that the Azure SRE Agent was unable to complete a chat request successfully. Since the chat workflow depends on multiple layers such as session state, permissions, resource access, network connectivity, telemetry availability, and backend processing ,the most effective approach is to begin with a few quick isolation checks before proceeding to deeper configuration and access reviews.

    1. Initial Isolation Checks To quickly determine whether the issue is related to the current session, browser, or environment, please perform the following:
      • Create a new Azure SRE Agent chat thread and test with a simple prompt.
      • Retry using:
      • Microsoft Edge InPrivate mode
      • Google Chrome Incognito mode
      • Temporarily disable browser extensions and test again.
      • If permitted, test from an alternative network connection.
      In addition, please confirm:
      • Whether the behavior affects all users or only specific users.
      • Whether all prompts fail or only certain requests.
      • Whether the functionality worked previously or if this is a first-time deployment scenario.
      These checks help determine whether the issue is isolated to the current conversation state, browser session, or environment before moving into deeper troubleshooting.
    2. Validating Access and Permission Configuration The next step is to confirm that both the user account and the SRE Agent have the necessary permissions to perform the requested operations. Please review:
      • Azure role assignments at the:
      • Subscription level
      • Resource Group level
      • Resource level
      • Whether permissions are assigned directly or inherited through group membership.
      • Effective access using Azure Portal > Access Control (IAM) > Check Access.
      Azure SRE Agent functionality relies on appropriate RBAC assignments and SRE Agent role permissions for chat, diagnostics, and resource operations.
    3. Validating Managed Identity Configuration Azure SRE Agent uses a managed identity to authenticate and access Azure resources. If required permissions are missing, requests may fail during resource discovery, telemetry collection, or remediation workflows. Please verify:
      • Managed Identity is enabled.
      • Required RBAC assignments are present.
      • Access exists to monitored resources and workspaces.
      • No Azure Policy, Conditional Access policy, or security controls are blocking access.
    4. Reviewing Network and Connectivity Requirements If access validation is successful, the next area to review is network communication. Please validate:
      • Proxy, firewall, VPN, and secure web gateway policies.
      • Private Endpoint and Virtual Network integration settings.
      • Private DNS configuration and name resolution.
      • WebSocket and real-time communication traffic restrictions.
      • Outbound connectivity to required Azure services and dependencies.
      Azure SRE Agent network functionality depends on correct network routing, DNS resolution, and outbound access to required services.
    5. Confirming Resource and Telemetry Availability Azure SRE Agent investigations rely on resource data and monitoring telemetry. Please review:
      • Resource health and accessibility.
      • Log Analytics workspace availability.
      • Telemetry ingestion and query results.
      • Monitoring permissions and data visibility.
      Missing or delayed telemetry can impact the agent's ability to process requests successfully

    The following references might be helpful , please check them out

    Please let us know if the response was helpful

     

    Thank you

     

    Was this answer helpful?

    0 comments

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.