I have a SQL database as an Azure instance that has been working quite well for almost a year. I have created a new flow with a trigger on one table (not used previously but in the database since it was initially created). To my surprise, the flow trigger failed the first time I tested it. I then created a second flow with just the trigger and an Initialize Variable and the same error occurs.
Before I post the error, a few other (what I think are) strange behaviors.
- On the trigger, the server and database show as choices but not the table. The only table that is in the list is one that is a used in several other flows as a trigger or GET ROWS or CREATE ROW, all of which are working fine.
However, if I add the table as a custom value, the fields for that table appear in dynamic content, so it "finds" the table properly. - In the small test with just the trigger and varable, I added a third step of GET ROWS for that table. In the step parameters, the server, database, and a full list of tables appeared as choices, unlike the trigger step which only showed one table.
However, I was unable to save the flow.
The full error on the save is
Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sql' operation 'GetTable_V2' failed with status code 'Forbidden'. This may indicate invalid input parameters. Error response: {"status":403,"source":"https://unitedstates-002.token.azure-apim.net:443/tokens/unitedstates-002/sql/545a5edd99fe4eb19ab9cf735f44c085/exchange","message":"Error from token exchange: Permission denied due to missing connection ACL: Connection https://unitedstates-002.azure-apim.net/@unitedstates-002/logicflows/3a2acfad-c7bb-454c-90d2-427c71a6672a version -9223372036854775808, connection=unitedstates-002/sql/545a5edd99fe4eb19ab9cf735f44c085"}'.
When a new row is added to the table and the original flow is triggered, the trigger fails with just part of this message, starting with Error from token exchange: Permission denied due to missing connection ACL: Connection and continuing with the remainder of that message.
In Azure, I am the owner of the database, global admin on the tenant, have premium license, etc. As I mentioned earlier, I have created several flows (and they run multiple times a day) that havve a trigger of When a New Row is Created for other SQL tables
I next created a duplicate flow (trigger, variable, GET ROWS) for another table which I had to enter as a custom value as well, but I could successfully save it without any error. Did the same for annother 2 tables. It seems that this table is the only one giving me the errors, but with over 50 tables, I haven't checked - and don't need - all of them.
The table contains no protected data (checked on the Azure dashboard). In fact, it is amazingly similar to the table in use that works.
There is only one thing else I can think of to mention.
When I was first setting up this tenant, I had not migrated the domain to Office 365, so the original account I set upi was
<myname>@<tenant>.onmicrosoft.com but now just <myname>.<tenant.>com
In connectors for the SQL database, there are two, one for each email address above (and onmicrosoft.com remains an alias of course). For the no-omicrosoft connector there are no apps or flows but plenty for the original one. I think that might be a red herring because if I use another table, I can create and save flows, just not on the one I am trying to get to work.
Despite rummaging through Azure settings, I could find nothing related to table level access parameters or anything else similar, so i have a) no idea what is causing this error and b) no clue how to get around it. Is it a SQL thing or something else? Lookig forward to some wisdom from you experts.

Report
All responses (
Answers (