Microsoft Dynamics 365 | Integration, Dataverse...

Authentication error with HTTP request trigger

(6) Share

Report

Posted on by nelsms

We have a sandbox environment that we recently created by copying our production enviornment.

In the new sandbox, we have several cloud flows are triggered by the step: What a HTTP Request is Received. This trigger generates a url that we are using to call the flowl.

We are using this url in the Ribbon Workbench solution from the XRM Toolkit.

When we click the ribbon button to call the flow, we are getting the following message:

The authentication credentials are not valid.

The trigger option for 'Who can trigger the flow?' is set to Anyone.

We have googled the issue, and out research seems to indicate that our SAS token is invalid or expired. We do not know how to verify this, or how to make the trigger work.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Adis 6,597 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hey,

I am not 100% sure, but could be relevant:

Post | Feed | LinkedIn - please also read the comments for further information.

Troubleshoot common issues with triggers - Power Automate | Microsoft Learn

Basically, you need to deploy the flow again to PROD and the new urls should be triggered.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
Suggested answer

Inogic 748 on at

Like (3)

Report
Copy link

Link copied!
Hi,

The error occurs because the HTTP trigger URL contains a SAS token that's environment-specific. When copying the flow to Sandbox, a new URL is generated.
To fix:

Open the flow in Power Automate (Sandbox).

Copy the new trigger URL after saving the flow.

Update the Ribbon Workbench button with this new URL.

Publish and test.

Hope this Helps!

Thanks!

Inogic

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Nimsara Jayathilaka. 4,950 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

The error "authentication credentials are not valid" when calling a Power Automate flow via HTTP request usually indicates the SAS token included in your flow URL is invalid or may have expired. To correct this you need to re-generate the SAS key used by the HTTP trigger in your flow. To re-generate the SAS key: you need to edit the flow in Power Automate and copy the existing HTTP POST URL (with the SAS token), then generate the new SAS token either via API, or via the Power Automate portal. Finally, you must update the URL including the new SAS token used in the Ribbon Workbench. For more specific steps and validation, Microsoft documentation and blog posts provide a clear overview of how to regenerate and validate SAS keys for HTTP based flows to regain secure access.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Sahan Hasitha 2,683 on at

Like (3)

Report
Copy link

Link copied!

hi

from one environment (such as Production) into another (such as Sandbox), the system automatically generates a new HTTP trigger URL. Since the SAS token is environment-specific, the original Production URL will not work correctly in Sandbox, resulting in errors.
To resolve this, you need to update the Sandbox flow with the newly generated URL:
01. Open the flow in Power Automate within the Sandbox environment.
02. Make sure to save the flow. Once saved, a new HTTP trigger URL will be generated automatically by the system.
03. Copy this new trigger URL.
04. Navigate to the Ribbon Workbench (or wherever you have referenced the flow’s URL). Replace the old Production URL with the new Sandbox URL.
05. Publish your changes and perform a test to confirm the flow works as expected.

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Nimsara Jayathilaka. 4,950 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
The "authentication credentials are not valid" error occurs because the SAS token embedded in the HTTP trigger URL might be expired or invalid. To fix this:

Regenerate the SAS key by editing the flow in Power Automate and saving the trigger URL again (a new SAS token is generated).

Replace the old URL with the updated one in the Ribbon Workbench solution.

Verify the "Who can trigger the flow?" option is set to "Anyone."

Test the URL again with the new SAS token to confirm it works.

If issues persist, check for any OAuth or authentication overlay blocking anonymous requests.

This ensures the flow URL with a valid SAS token is used for triggering the flow successfully.

Thanks

Nimsara

Was this reply helpful? Yes No
nelsms 16 on at

Like (0)

Report
Copy link

Link copied!

It looks like there is just 1 request when I filter for api.flow.

The request url for this request is:

https://api.flow.microsoft.com/providers/microsoft.processsimple/environments/979cd549-ec74-e668-a3f0-c0b178e85904?api-version=2016-11-01

The request does not start with runs?api-version=, and I don’t know how to select or copy the request url, or the authorization header

I don’t know how to find the correct request url or the authorization header to copy into the fetch command, and I’m not sure how to run the command.

Was this reply helpful? Yes No
nelsms 16 on at

Like (0)

Report
Copy link

Link copied!

See attachment

Was this reply helpful? Yes No
Suggested answer

Sahan Hasitha 2,683 on at

Like (2)

Report
Copy link

Link copied!
hi

Step 1 – Check the flow is enabled

In Power Automate → My Flows → Sandbox environment → make sure the HTTP-triggered flows are turned on.

Step 2 – Get the new URL

Open the flow in the sandbox.

Select the “When an HTTP request is received” trigger step.

Copy the new HTTP POST URL (contains the SAS token).

Step 3 – Update the Ribbon Workbench button

Replace the old flow URL in your Ribbon Workbench command with the new sandbox flow URL.

Step 4 – Test authentication

If the trigger is set to Anyone, no authentication is required.

If it’s set to Specific users, you’ll need to pass valid OAuth tokens (but from your description, you’re using Anyone, so this is not the case).

Step 5 – Future-proof

If you promote flows often between environments, consider:

Storing flow URLs in Dataverse configuration table or environment variable.

Updating ribbon commands to pull from that variable, so you only need to update in one place per environment.

1 people found this reply helpful.

Was this reply helpful? Yes No