Logic app workflow no longer working

Question

Logic app workflow no longer working

Katherine He 20 Microsoft Employee

Hi, our logic app workflow has suddenly stopped working. We did not make any changes on our end recently and from the logs it seems that the logic app is failing to connect to our storage account. We have validated our private endpoints and vnets and everything seems to be setup correctly. We have also checked rbac permissions but nothing has changed there either.

We are seeing this error message: Workflow Error: operationName='WorkflowRuntimeTriggerListener.StartAsync', message='Workflow runtime could not connect to the configured storage account. Please ensure the connection string to storage account is valid and reachable.', exception='Microsoft.WindowsAzure.ResourceStack.Common.Legacy.StorageException: Unexpected HTTP status code 'Forbidden'. ---> System.Net.WebException: The remote server returned an error: (403) This request is not authorized to perform this operation..

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-29T20:33:58.25+00:00

@Katherine He , following up to see if you have checked the above response and if it was helpful. Please let me know if you have any questions.
Katherine He 20 Reputation points Microsoft Employee

2026-07-14T17:58:02.3133333+00:00

Hi @Pravallika KV the logic app has suddenly stopped working again. I did the checks you suggested and there's nothing wrong from our end.
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-07-15T00:47:45.04+00:00

Hi @Katherine He , Could you please share error details?
Katherine He 20 Reputation points Microsoft Employee

2026-07-15T16:28:12.8266667+00:00

Hi @Pravallika KV I'm not seeing any errors. The app is just not working
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-07-17T04:44:43.3066667+00:00

Hi @Katherine He , I'll check and update you.

Answer accepted by question author

Pravallika KV 18,850 Microsoft External Staff Moderator

Hi @Katherine He ,

Thanks for the confirmation, glad you were able to resolve the issue.

Based on our investigation, the 403 Forbidden error during WorkflowRuntimeTriggerListener.StartAsync is typically caused when Shared Key access is disabled (AllowSharedKeyAccess = false) on the storage account associated with the Logic App. This prevents the Logic App runtime from accessing the required storage resources.

As the error message suggests it's the 403 forbidden error when connecting to storage account, which means the runtime is not able to access the storage account.

https://learn.microsoft.com/en-us/troubleshoot/azure/logic-apps/common-error-deploy-logic-apps-private-storage-account

https://learn.microsoft.com/en-us/troubleshoot/azure/logic-apps/troubleshoot-logic-apps-setup-connectivity

Try connecting to storage account with access keys using storage explorer or tools and check if at all customer has any azure policy that is disabling the access key, that will help us to isolate that access key-based authentication is not working.

Hope this helps!

If the resolution was helpful, kindly take a moment to click on User's image and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Katherine He 20 Reputation points Microsoft Employee

2026-07-30T16:20:07.1066667+00:00

Found solution on my own and resolved the issue. This is not the solution used but accepting answer just so the ticket can be closed.
Sina Salam 31,456 Reputation points Volunteer Moderator

2026-07-30T16:32:12.2066667+00:00
Hello Katherine He,

Thank you for letting us know that you found solution by yourself and the @Pravallika KV response is not the solution, but you only accepted the answer to close the thread.

Please, this is not polite! For the benefit of the community and to avoid false positive and misleading information. Would you please:

Unvote it.

and remove the thumb up.

Then, post your solution as a comment.

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", anyone here among the responders will repost your solution so that you can "Accept " the answer.

NB: All accepted answers show up at the top, resulting in improved discoverability for others.

Please.

2 additional answers

Your answer

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-06-29T20:33:58.25+00:00

@Katherine He , following up to see if you have checked the above response and if it was helpful. Please let me know if you have any questions.
Katherine He 20 Reputation points Microsoft Employee

2026-07-14T17:58:02.3133333+00:00

Hi @Pravallika KV the logic app has suddenly stopped working again. I did the checks you suggested and there's nothing wrong from our end.
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-07-15T00:47:45.04+00:00

Hi @Katherine He , Could you please share error details?
Katherine He 20 Reputation points Microsoft Employee

2026-07-15T16:28:12.8266667+00:00

Hi @Pravallika KV I'm not seeing any errors. The app is just not working
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-07-17T04:44:43.3066667+00:00

Hi @Katherine He , I'll check and update you.
Katherine He 20 Reputation points Microsoft Employee

2026-07-30T16:20:07.1066667+00:00

Found solution on my own and resolved the issue. This is not the solution used but accepting answer just so the ticket can be closed.
Sina Salam 31,456 Reputation points Volunteer Moderator

2026-07-30T16:32:12.2066667+00:00

Hello Katherine He,

Thank you for letting us know that you found solution by yourself and the @Pravallika KV response is not the solution, but you only accepted the answer to close the thread.

Please, this is not polite! For the benefit of the community and to avoid false positive and misleading information. Would you please:

Unvote it.

and remove the thumb up.

Then, post your solution as a comment.

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", anyone here among the responders will repost your solution so that you can "Accept " the answer.

NB: All accepted answers show up at the top, resulting in improved discoverability for others.

Please.

Answer 1

Hi Katherine He

Thanks for reaching out on Microsoft Q&A!

This appears to be a runtime issue with your Logic App Standard. What we need to do is test the configuration one-by-one to find the culprit. Could you execute these steps please?

Quick isolation test: on the Storage Account, go to Networking and allow 'All networks'. Check if it works, and if it does it's 100% network related;
Just to be sure: check your connection string used for the Storage Account
Validate your VNet routing and ensure 'Route All' is enabled in your App Settings (WEBSITE_VNET_ROUTE_ALL = 1) and that the DNS is correctly set (WEBSITE_DNS_SERVER = XXX.XXX.XXX.XXX)
If you have a VM in the same VNet, validate that the DNS resolution shows the private IP for the following command: slookup <storageaccount>.blob.core.windows.net
Verify that private endpoints exist for all services related to the Storage Account, meaning: Queue, Blob, Table & File (very important)
Check your firewall rules whether some traffic might be blocked, for example due to scaling of your Logic Apps Standard workers, allowing not all to have access

Please click ‘Accept answer’ if you think my answer is helpful. Feel free to drop additional queries in the comments below!

Kind regards,

Sonny

Answer 2

Katherine He 20 Microsoft Employee

Found solution on my own and resolved the issue.

0 comments