Forum Discussion
403 GraphQL API
Thanks for sharing the error details. This error points to authentication between the GraphQL API and its underlying data source, rather than simply a missing GraphQL Execute permission. The request is reaching the accounts resolver, but the API cannot successfully authenticate to the source.
Please check the connection mode configured for your GraphQL API:
- If using Single sign-on (SSO): The calling service principal needs access to the underlying data source and the tables exposed by the API. For a lakehouse-backed API, verify access to its SQL analytics endpoint and the relevant Account table—not just the GraphQL item. Grant only the read permissions required for your query.
- If using Saved credentials: Check the connection used by the API. Ensure its credentials are valid and that the configured identity can connect to the source and read the Account table. Reauthenticate or update the connection if needed. In this mode, granting the calling service principal direct source access is not the first fix; the saved connection is used to access the data.
Keep Run Queries and Mutations assigned to the calling service principal on the GraphQL API. However, that permission alone does not resolve a data-source authentication failure.
To isolate the issue, test access to the backing table using the same identity used for source access. A successful test in the Fabric editor under your personal account does not prove that the service principal or saved connection has equivalent access.
Please share the backing data-source type (lakehouse SQL analytics endpoint, warehouse, SQL database, etc.) and whether the API uses SSO or Saved credentials. These details will help identify the specific permission or connection setting to check. Please don’t share tokens, passwords, or client secrets.
Reference: Connect to a data source and build your GraphQL schema.
Thank you.