Error validating Execution Restrictions - Bad Execution Restrictions

[Jose_Malan]

AzureBlobStorage.CreateFile failed: { "error": { "code": 400, "message": "Error validating Execution Restrictions - Bad Execution Restrictions", "source": "europe-002.azure-apim.net", "path": "choose[3]\\when[1]\\choose\\when[1]", "policyId": "", "clientRequestId": "9227fcd6-8b6b-4117-9957-3e69cdb6c50b" } }

I deleted the data source and reconnected, but it's not working.

Until April 2nd it was running on version 3.24032.26. From version 3.24034.17 the problem started.

[mrscherry2000]

At the very least, they need to allow us to revert back to version 3.24032.26 otherwise we are stuck.  I can't make any updates until this is resolved and I have items to revise.

[VictorOrquisa]

Hello, we are still waiting a fix or at least a feedback from microsoft about this error, the app wasn't modified in the last month but it's giving errors due to Microsoft fault on the update, 

Do we have at least an ETA about this error?

[kenbossy22]

Hey everyone, I checked this morning and was able to publish an update that didn't contain this Azure Storage error message. The authoring version was 3.24042.18 which seems to be a reversion by Microsoft. I'm not sure how this will affect your apps but it may be worth publishing to a test environment to check it out. It would be nice to get some sort of update from Microsoft with whatever they're doing but I guess that's not going to come

[TimErtl]

I was able to submit a ticket to Ms via our internal IT department, the answer is only a workaround but may be helpful to prevent an app from automatically updating the PowerApps version and also to predefine a version.

Attention: I got the same error message, but with BingMaps Connector!
You have to start your app in edit mode and then add the following at the end of the url:
&make.redirectToPreview=false&studio-version=v3.24032.26.291114409

[worklist]

The issue appears to have been resolved in authoring version 3.24044.13.  Haven't checked the prior version.

[MikeyMole]

Just FYI I am also seeing normal Azure Blob Stroage Connector (with secure implicit connection) behaviour in authoring version 3.24044.13.

I might wait a little while before publishing anything in PROD just in case. But looks like progress!

Phew!

[Jenske93]

Version 3.24044.13 works for me as well 😄 (it took them long enough though, but happy to finally get back to work!)

[cmckee]

This is a known issue, while going back in the version may fix it in the short term the correct solution is listed below. Hope this helps everyone.

Error validating Execution Restrictions when using AzureBlobStorage connector

Problem

This issue is a regression for some apps that were previously not using secure implicit connections who had it automatically enabled in an effort to secure SQL apps.

Workaround

Mitigation is to turn the setting on to disable the feature for now (customers were previously not using the feature) then save and re-publish the affected apps.

You can do this by turning on the 'Disable secure implicit connections' app setting in the retired section.

NOTE: In the case of model driven form apps with multiple custom pages, all of the custom pages need to have the setting enabled and the model driven form then needs to be republished.