Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
gwayne
Frequent Visitor

Calling the Fabric API via Data Pipeline to load workspace data into lakehouse

Not sure if this is the right forum or not..,. 

 

I'm attempting to use the Fabric API to pull data into a Fabric Lakehouse. I'm currently utizling a data pipeline with a copy activity, where the source is of type REST, and  the destination is a lakehouse table within the same workspace.

 

I've set up a security group that includes my account as well as a service principal. This group has been granted the Admin role within the workspace, and I've also enabled the following permissions within the Fabric Tenant: 

 

  • Service principals can use Fabric APIs
  • Service principals can access read-only admin APIs
  • Enhance admin APIs responses with detailed metadata
  • Enhance admin APIs responses with DAX and mashup expressions

Note that my account is also a Fabric Administrator. 

 

I'm using the following API: https://api.fabric.microsoft.com/v1/workspaces

 

This API works seamlessly when I test it via the "Try It" feature on Microsoft Learn using my credentials. However, when I attempt to connect via the pipeline, the connection tests successful, however, I encounter a 403 error whenever I try to preview data or import a schema.

When I attempt to connect with the Service Principal the connection does not test successful. I am assuming this is API permissions not configured correctly on the applicaiton/sp.

I'm hoping this is just a matter of user error or a gap in my understanding. Looking for any insights or guidance on what migh be going wrong. I feel like I should be able to use my credentials to connect and successfully call the Fabric API.

1 REPLY 1
Anonymous
Not applicable

Hi @gwayne 

 

A 403 error usually indicates that the application does not have the appropriate permissions. Ensure that the service principal has the necessary API permissions configured correctly on the application.

 

HTTP status code in Fabric Public APIs surface follows the standard HTTP code semantics:

  • 2XX - represents a successful operation
  • 4XX - represents client originated failures
  • 5XX - represents server originated failures

 

Error handling in Fabric Public APIs | Power BI Documentation (eng.ms)

 

How to fix "403 - You cannot consume this service" error? | FabriXAPI User Guide

 

Regards,

Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

Check out the July 2025 Fabric update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.