Answered

403 Forbidden Error on newly added Azure SQL table to Canvas App

(0) Share

Report

Posted on by BrianHFASPS

728

I added a link to a new Azure SQL table in one of my apps. I am getting a 403 Forbidden error on the published app when attempting to access that new table. I found Getting 403 forbidden error on canvas app and Solved: 403 Forbidden Error When Saving Data to SQL DB from PCF in Play Mode (Power Apps) but the then retired setting is now gone totally. How do I fix this problem?

{
  "duration": 0,
  "size": 0,
  "status": 403,
  "headers": {
    "Content-Length": 326,
    "Content-Type": "application/json",
    "x-ms-dlp-ef": "-|-/-|-|-",
    "x-ms-dlp-gu": "-|-",
    "x-ms-dlp-re": "-|-",
    "x-ms-environment-id": "default-X",
    "x-ms-mip-sl": "-|-|-|-",
    "x-ms-tenant-id": "X",
    "x-ms-client-request-id": "02a24553-ae12-4e9d-a70d-58b3f6715dd7"
  },
  "body": {
    "error": {
      "code": 403,
      "message": "Method GET is not allowed for table [dbo].[StuListSmallOld]",
      "source": "msmanaged-na.azure-apim.net",
      "path": "choose[2]\\when[1]\\choose\\when[2]",
      "policyId": "",
      "clientRequestId": "a6c8d52e-4622-48ea-9fbc-dd0457dd2beb",
      "dreeSet": true
    }
  },
  "responseType": "text"
}

I blanked my tenant ID above.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

developerAJ 4,763 on at

Like (0)

Report
Copy link

Link copied!

I recommend first ensuring that the account used by your app has proper permissions on the new table. You can grant the necessary access in SQL using the following command:

GRANT SELECT, INSERT, UPDATE, DELETE ON dbo.StuListSmallOld TO [YourUser];

If the account already has the correct permissions but the app is still showing a 403 Forbidden error, it is likely related to a DLP (Data Loss Prevention) policy issue.

If the error occurs across all tables: Check your environment’s DLP policies, as they may be restricting access.

If it occurs only for this table: This may be an isolated issue. In that case, try removing and re-adding the connection, or test using a different account to see if the issue persists. check the access using same account directly in sql server

As a best practice, I recommend using stored procedures rather than direct tables or views in your app. This approach can improve security, reduce direct data access, and simplify your app by minimizing the number of data sources.

Was this reply helpful? Yes No
Suggested answer

developerAJ 4,763 on at

Like (0)

Report
Copy link

Link copied!

Please let us know if the issue still exists. If it has been resolved, kindly close the thread by accepting the solution

If this solution helped you resolve your issue, kindly mark it as accepted — it makes it easier for others to find and also closes the discussion. If you found it useful, a Like ❤️ would be greatly appreciated!

🤝 Let’s connect on LinkedIn || 📘 Explore more on my articles

Was this reply helpful? Yes No
Suggested answer

BrianHFASPS 728 on at

Like (1)

Report
Copy link

Link copied!

The answer for me is going and disabling the enhanced security option in regard to implicit permissions. Granting permission to tables and views via SQL on a per-user basis is much too cumbersome and unnecessary in my environment. Allowing the app to use the connector account for all transactions works for our environment. I only hit this issue now as I hadn't added any new tables / views and it seems the old permissions worked for existing links.

Was this reply helpful? Yes No
Verified answer

developerAJ 4,763 on at

Like (1)

Report
Copy link

Link copied!

That’s great—you were able to resolve the issue.

The statement:

GRANT SELECT, INSERT, UPDATE, DELETE ON dbo.StuListSmallOld TO [YourUser];

is specific to a table, but you can also apply permissions at the schema or database level. The ideal approach is to create a custom security role and use Azure security groups to assign permissions—this is compliant.

If no user-level restriction is required, you can directly assign system roles like db_datawriter to the user.

Using a SQL account is also good, but it is not compliant.

If this solution helped you resolve your issue, kindly mark it as accepted — it makes it easier for others to find and also closes the discussion. If you found it useful, a Like ❤️ would be greatly appreciated!

🤝 Let’s connect on LinkedIn || 📘 Explore more on my articles

2 people found this reply helpful.

Was this reply helpful? Yes No