Answered

Cloud Flow - Invoke http Request

(1) Share

Report

Posted on by knparksnyc

Hi, I have a cloud flow that I'm invoking a http request. In dev environment it works. But when I moved it to a new environment, I get an error on the Http request. The new environment is enhanced could that cause a problem?

Thanks for your help.

Body :

   "code": 401,
    "source": "power-apis-usgov001-public.azure-apihub.us",
    "clientRequestId": "c68bbcd8-ab0b-4353-b691-c69e4564c0b8",
    "message": "The response is not in a JSON format.",
    "innerError": "Cannot read server response."
  }
Headers
{
  "Set-Cookie": "ARRAffinity=1dbc07afbe1810f640a88f0d21d286576292d85fe1ae53ae16038d5318a6b760dc748ed02332839cb0efbb9e2898da096c2226348c1e154ec1706e5f470d25ad08DEC580C41FF0160000000713933852; path=/; secure; HttpOnly,ReqClientId=135b1c08-cb01-413a-a303-1eacebc3d4d4; expires=Mon, 08-Jun-2076 16:39:57 GMT; path=/; secure; HttpOnly,ARRAffinity=1dbc07afbe1810f640a88f0d21d286576292d85fe1ae53ae16038d5318a6b760dc748ed02332839cb0efbb9e2898da096c2226348c1e154ec1706e5f470d25ad08DEC580C41FF0160000000713933852; path=/; secure; HttpOnly",
  "x-ms-service-request-id": "70cec60f-405e-4c90-93ab-ef5b3e8f1fce",
  "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
  "REQ_ID": "70cec60f-405e-4c90-93ab-ef5b3e8f1fce",
  "AuthActivityId": "b32448b6-411e-4bc6-99b8-7121c3e89b53",
  "401_Error_Reason": "Authorization header is missing.",
  "NativeWebSession-Version": "2",
  "X-Source": "1772214433145203441751212249621711522091611173714223615762371836381871054920446152,2265442414025223323094121167123959821494416512063163662012240378412895254144109",
  "Public": "OPTIONS,GET,HEAD,POST",
  "x-ms-client-region": "gcc",
  "x-ms-flavor": "Gcc",
  "X-Ms-Workflow-Resourcegroup-Name": "32F56FC75F814E22A95B15DA66513BEF-FC69F5958FEFE0E8960E513742129B07-ENV",
  "x-ms-workflow-subscription-id": "c8d4c842-0c0a-4dba-b614-780fcd765007",
  "x-ms-environment-id": "fc69f595-8fef-e0e8-960e-513742129b07",
  "x-ms-tenant-id": "32f56fc7-5f81-4e22-a95b-15da66513bef",
  "x-ms-subscription-id": "c8d4c842-0c0a-4dba-b614-780fcd765007",
  "x-ms-dlp-re": "-|-",
  "x-ms-dlp-gu": "-|-",
  "x-ms-dlp-ef": "-|-/-|-|-|-",
  "x-ms-mip-sl": "-|-|-|-",
  "x-ms-au-creator-id": "26716eb0-9fac-484f-8afb-c59f494b55f7",
  "Timing-Allow-Origin": "*",
  "x-ms-apihub-cached-response": "true",
  "x-ms-apihub-obo": "false",
  "WWW-Authenticate": "Bearer authorization_uri=https://login.microsoftonline.com/32f56fc7-5f81-4e22-a95b-15da66513bef/oauth2/authorize, resource_id=https://dprgreenthumbdev.crm9.dynamics.com/",
  "Date": "Mon, 08 Jun 2026 16:39:56 GMT",
  "Allow": "OPTIONS,GET,HEAD,POST",
  "Content-Length": "273",
  "Content-Type": "application/json"
}

Categories:

Building Power Apps

Connector development

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

SpongYe 5,909 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @knparksnyc

I do not think the environment itself is the direct cause. The error points to an authentication issue.

401_Error_Reason: Authorization header is missing

This means the request is reaching Dataverse, but no bearer token is being sent with the request. The “response is not in a JSON format” message is likely just a secondary error from Power Automate trying to process the unauthorized response.

Microsoft Dataverse Web API documentation shows the common request headers for Web API calls, including:

If you have any questions or feedback, please let me know. Have a great day! 😊

-----------------------
SpongYe Power Platform Enthusiast [LinkedIn] | [Youtube| [My blog]

I love to share my knowledge and learn from others. If you find my posts helpful, please give them a thumbs up 👍 or mark them as a solution ✔️. You can also check out my blog [@S pongYe] for some cool solutions and insights. Feel free to connect with me on any of the platforms above. Cheers! 🍻

Was this reply helpful? Yes No
Suggested answer

Kalathiya 2,456 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello @knparksnyc,

Error looks like an authentication issue rather than something caused by the new environment itself.

I guess you may have forgotten to pass the authentication token or Authorization header. I'd check the HTTP action's authentication settings, connection references, and any environment variables that may have changed when the flow was moved to the new environment.

---------------------------------------------------------------------------

Glad it helped 🙂
If this fixed your issue, please click “Does this answer your question?” to mark it as verified so others can find the solution easily.
A Like 👍 is always appreciated, and I’m around if you need more help @Kalathiya

Was this reply helpful? Yes No