web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / Getting an error like ...
Copilot Studio
Suggested Answer

Getting an error like Response is not in JSON format

(0) ShareShare
ReportReport
Posted on by Microsoft Employee
When trying to use Azure queues connection in Agent flows getting an error like below.

Troubleshooting performed:

 

-Validated and confirmed that the access key credentials being used are correct and the storage account is public network access enabled. And there are no firewall restrictions in the Azure storage account side and also have storage contributor role as well. 

-Validated the situation in our internal test instance and can be able to see the same error from our side as well.

-When the end user is trying to create the connection from Power Apps or Power Automate portal, they are getting the same issue.


-When using the Entra id authentication type, we are getting the below error. But I prefers using the access key as it wont require any additional permissions from Azure side of things.

 

Ask:

Why am I unable to establish Azure Queues connector properly in the Agent flows as well as in Power Apps and Power Automate and even though providing the appropriate credentials why the connection is not being established properly.

I have the same question (0)
  • chiaraalina Profile Picture
    1,884 Super User 2026 Season 1 on at
     
    The issue is authorization. Can you add Storage Queue Data Contributor (Storage Contributor is not enough) and try again?
  • Suggested answer
    deepakmehta13a Profile Picture
    322 on at

    Hi,

    From the screenshots and the details, you shared, the error “Response is not in JSON format” can sometimes occur when the connector request is not authorized correctly and the service returns a non-JSON response (for example an authentication or permission error page).

    For Azure Queue Storage, it is important to note that there are two types of permissions:

    Management plane roles (like Storage Contributor)
    Data plane roles (required to read/write queue messages)

    When using Entra ID authentication with Azure Queues, the connector typically requires the Storage Queue Data Contributor role on the storage account or queue resource.

    You may want to check the following:

    1️⃣ In Azure Portal → Storage Account → Access control (IAM)
    Ensure the user or service principal has Storage Queue Data Contributor assigned.

    2️⃣ Confirm the queue endpoint is accessible and not restricted by network rules or firewall settings.

    3️⃣ After updating permissions, try re-creating the connection in Power Automate / Power Apps, as sometimes the connector caches the previous authentication attempt.

    The reason this matter is that connectors in Power Platform expect the service response in JSON format, and if the request is not authorized correctly the service may return a different response format which causes this parsing error.

    If you are able to test again after assigning the Storage Queue Data Contributor role, it would be interesting to see if the connection succeeds.

    Hope this helps.

  • AK-16030901-0 Profile Picture
    Microsoft Employee on at
    Hi  & 

    Grateful for the responses !!

    As I have mentioned above, I have checked the access (Storage Queue Data Contributor) . 

    I have also checked the below information as well. (Mentioned above)

     

    1️⃣ In Azure Portal → Storage Account → Access control (IAM)
    Ensure the user or service principal has Storage Queue Data Contributor assigned.

    2️⃣ Confirm the queue endpoint is accessible and not restricted by network rules or firewall settings.

    3️⃣ After updating permissions, try re-creating the connection in Power Automate / Power Apps, as sometimes the connector caches the previous authentication attempt.

    Is there any other way, I can troubleshoot the issue ?

     

  • Suggested answer
    deepakmehta13a Profile Picture
    322 on at

    Hi,

    Thanks for confirming those checks, that helps narrow it down.

    Since you have already verified:

    • Storage Queue Data Contributor role

    • No firewall / network restrictions

    • Recreated the connection

    there are a couple of additional things you could try, as this error can sometimes be a bit misleading.

    1. Try with Access Key vs Entra ID (both ways)
      Even though access key does not require RBAC, it might be worth testing both authentication types again. If both are failing with the same error, it could indicate a connector-side issue rather than configuration.

    2. Validate the queue name and endpoint
      Double check that the queue name is correct and already exists in the storage account. If the connector is pointing to a non-existing queue, the service can return a non-JSON response which leads to this error.

    3. Check storage account configuration
      Ensure that:

    • The storage account is using standard Azure Queue Storage (not Data Lake / hierarchical namespace scenarios)

    • The queue service endpoint is reachable

    1. Try from a simple Power Automate flow
      Instead of Agent flows, try creating a basic cloud flow with the same Azure Queues connector (for example “Peek messages” or similar action).
      This helps isolate whether the issue is:

    • specific to Copilot / Agent flows, or

    • a general connector issue

    1. Test with a new storage account / queue
      If possible, try creating a new storage account and queue and test the connection there. This can help identify if the issue is related to a specific resource configuration.

    2. Possible connector/platform issue
      Since you mentioned you are able to reproduce this internally as well, and it happens across Power Apps / Power Automate, there is a possibility this could be a temporary connector issue or regression rather than configuration.

    If none of the above works, it might help to capture:

    • exact connector action used

    • authentication type

    • region of the storage account

    so it can be checked further.

    Hope this gives a few more directions to try. If you find the root cause, it would be great to share it here as well for others.

    If this or the earlier response was helpful, you can mark "Was this reply helpful?" as Yes, and if it resolves your issue, please consider marking it as Verified.

    Thanks.

  • Suggested answer
    Sayali Profile Picture
    Microsoft Employee on at
    ,Hello @AK-16030901-0

    First, in your MCP + GitLab scenario, your setup is largely correct—ngrok connectivity, authentication, and SSE handshake all succeed. However, Copilot Studio fails to complete tool discovery and execution, resulting in SystemError. This is due to strict and incomplete MCP-over-SSE support, where Copilot expects precise message formatting, immediate tool discovery, stateless connections, and small/fast responses. Any deviation (e.g., delayed schema, reused sessions, large GitLab payloads, or minor SSE formatting issues) causes silent failures. This is a known limitation of Copilot Studio’s MCP runtime, making it unreliable for production use. The recommended workaround is to avoid MCP and instead use Power Automate or custom connectors.

      Second, the Azure Queues connector failure across Copilot Studio, Power Apps, and Power Automate—despite valid credentials, correct roles, and no network restrictions—indicates a connector-level issue on the platform side. Since the error reproduces even in internal environments and across authentication methods (Access Key and Entra ID).

    Final takeaway: Both issues stem from current platform gaps in Copilot Studio and connector infrastructure, not from your implementation. For now, rely on alternative integration patterns (e.g., Power Automate, custom connectors) until these limitations are resolved.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 837

#2
Vish WR Profile Picture

Vish WR 294

#3
Haque Profile Picture

Haque 249

Last 30 days Overall leaderboard