{"id":40561,"date":"2025-03-10T15:56:31","date_gmt":"2025-03-10T10:26:31","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=40561"},"modified":"2025-03-27T12:19:34","modified_gmt":"2025-03-27T06:49:34","slug":"regenerating-a-sas-key-for-an-http-triggered-flow-in-power-automate","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2025\/03\/regenerating-a-sas-key-for-an-http-triggered-flow-in-power-automate\/","title":{"rendered":"Regenerating a SAS Key for an HTTP-Triggered Flow in Power Automate"},"content":{"rendered":"

As mentioned in our previous blog<\/a>, we discussed securing workflows by adding OAuth authentication to ensure that only authorized users within the tenant or specific individuals can execute the flow.<\/p>\n

However, when dealing with HTTP-triggered flows with anonymous access, keeping your Power Automate workflows secure is essential. Secure Access Signature (SAS) keys help protect these flows by controlling access to their HTTP endpoints, ensuring that only authorized requests can execute a flow.<\/p>\n

Whenever a new flow is created with the trigger \u201cWhen an HTTP request is received\u201d, and the \u201cWho can trigger the flow?\u201d option is set to \u201cAnyone\u201d, Power Automate<\/a> automatically generates an HTTP POST URL containing a SAS key. This key is embedded within the URL, as shown below.<\/p>\n

\"HTTP-Triggered<\/p>\n

While this mechanism provides security, SAS keys may need to be regenerated over time due to various reasons, such as key compromise, compliance with security policies, or periodic key rotation to mitigate potential risks.<\/p>\n

In this blog, we will walk through the steps to regenerate a SAS key for an HTTP-triggered flow.<\/p>\n

Steps to Regenerate the SAS Key<\/strong><\/p>\n

1. Sign in toPower Automate Portal<\/a> and navigate to your flows.<\/p>\n

2. Find the flow that contains the HTTP Trigger Flows and click on Edit.<\/p>\n

3. Select the When a HTTP request is received step and note down the existing HTTP POST URL that includes the current SAS key.<\/p>\n

\"HTTP-Triggered<\/p>\n

4. Navigate back to the Details page and open your browser\u2019s developer tools (F12).<\/p>\n

\"HTTP-Triggered<\/p>\n

5. Go to the Network tab and Filter requests by typing “runs?api-version”.If you are unable to find the request refresh the Detail page.<\/p>\n

6. Click on runs?api-version.<\/p>\n

\"HTTP-Triggered<\/p>\n

7. Under the Header section, copy the Request URL and replace “runs” with “regenerateAccessKey” within the URL.<\/p>\n

\"HTTP-Triggered<\/p>\n

8. Scroll down to the Request Header section and note down Authorization Access Token, as shown in the screenshot below.<\/p>\n

\"HTTP-Triggered<\/p>\n

9. Open Postman and create a new POST request using the modified Request URL.<\/p>\n

\"HTTP-Triggered<\/p>\n

10. Under the Authorization tab, select Bearer Token as the authentication type and paste the Access Token into the token field.<\/p>\n

\"HTTP-Triggered<\/p>\n

11. Click Send. If successful, you will receive a 200 OK response, confirming that the SAS key has been regenerated.<\/p>\n

\"HTTP-Triggered<\/p>\n

12. To verify the new SAS key, return to Power Automate and edit the flow. Compare the new HTTP POST URL with the previous one to confirm that the key has changed.<\/p>\n

\"HTTP-Triggered<\/p>\n

Conclusion<\/strong><\/p>\n

Regenerating SAS keys for HTTP-triggered flows is a vital security measure that helps protect your Power Automate workflows from unauthorized access. By following these steps, you can efficiently update the SAS keys in your Power Automate flow while ensuring continued security and functionality.<\/p>\n","protected":false},"excerpt":{"rendered":"

As mentioned in our previous blog, we discussed securing workflows by adding OAuth authentication to ensure that only authorized users within the tenant or specific individuals can execute the flow. However, when dealing with HTTP-triggered flows with anonymous access, keeping your Power Automate workflows secure is essential. Secure Access Signature (SAS) keys help protect these\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1985,2361],"tags":[3126],"class_list":["post-40561","post","type-post","status-publish","format-standard","hentry","category-power-automate","category-technical","tag-http-triggered-flow-in-power-automate"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/40561","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=40561"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/40561\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=40561"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=40561"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=40561"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}