Stored Procedure is not allowed (bug?)

[FredericForest]

So I'm having a weird behaviour with the new feature for stored procedure calls directly in PowerApps canvas... This might be a bug since the feature is still in preview, or maybe I'm doing something wrong.

I have this setup : 

- A SQL Login type connexion to a SQL Database in the environnement

- A connexion reference in my solution, pointing to the connexion

- An app in my solution, pointing to the connexion reference

In the app, I create a datasource of type Stored Procedure against the connexion reference. It works well in the authoring client (yay!) and works well in the published app. So far so good.

But then, I change the connexion object to point to a different database... It still works fine in the authoring client (proving the new login works), but when I publish the app I get a 403 "Procedure XXX is not allowed".

I can see with the monitor that the request's server and database have been properly updated. The request from the web authoring client seems a bit different than from the published app, but the published app includes a "x-ms-shared-connection-id" property that points to the right connexion.

Any idea what might be going on?

[kennethplatt]

I'm having the same issue. Workes well in my development environment, but when I push it to test, it fails.

[FredericForest]

Nice to hear that I'm not the only one. ^^
Does anyone know how to report it as a bug? That completly blocks adoption of this (amazing) feature.

[kennethplatt]

I may have an answer soon. It may be as simple as a DLP policy in my target environment that is not allowing this. Apparently, someone else in my company had the same issue and they were able to get it fixed. Does not make sense why it would be a DLP considering I can call stored procedures via flows without issues, but I guess they fixed it. I'll let you know what I learn in the next day or 2.

[FredericForest]

Interesting! I'd love to hear more from what you learn. On my end, I didn't install any DLP yet there.

[Tharen]

@kennethplatt - I'm also kind of struck with this issue. In my case, I am using SQL connector to execute a stored procedure. All stored procedures are working fine, but when I tried to add a new stored procedure, I am getting this error.

"Procedure dbo.blahblahblah is not allowed", "source": "unitedstates-xxx.azure-apim.net", "path": "choose[3]\\when[1]\\choose\\when[2]",

[kennethplatt]

I think I found it with some help from our IT Team. Here is the source article, but I enabled this setting and it worked!

https://powerusers.microsoft.com/t5/Building-Power-Apps/Enabling-SQL-Server-Stored-Procedures-from-t...

By selecting this feature in retired, it seemed to go away. Not sure if this will work long term as they actually retire it, but now it works just fine. I'm going to bring this back up with our MSFT contacts, but in the short term... give it a shot. 

If you have any additional thoughts on it, I'd love to hear it.

[Tharen]

Thanks @kennethplatt , but disabling the "Secure Implicit Connection" can't be a solution for this. Disabling the "Secure Implicit Connection" is a Risk of exposing the connection. This will lead to having other APP Makers to use the connection.

Also, very recently in JAN 2024, Microsoft introduced the "Secure Implicit Connection" concept, so don't think they will encourage go against it.

[kennethplatt]

I agree with you. That's why I'm going to my MSFT contact to ask about it. Feels like this is a bug in the feature that is exposed by secure connections. 

[jcambareri]

Hello, does anyone have any updates on this issue? Thank you.