Forum Discussion
Pipeline trigger via API stopped working
I had a working POST call to trigger a pipeline via power automate with Invoke HTTP request using address:
It has stopped working in the past few weeks. Is this still correct? The error just says "Forbidden"
It looks like Microsoft has recently updated security or permissions policies for triggering Fabric pipelines via the API, which may be causing the "Forbidden" error you're now seeing. This issue can often occur due to:
Permission changes: The service principal or user account previously used for the API call may no longer have the necessary permissions or roles.
Authentication issues: Token expiration or updated scope requirements can result in access being blocked.
Changes to API requirements: Microsoft sometimes updates REST API endpoints or the way authentication works, which may require modifications to Power Automate or any custom logic.
Recommended steps:
Double-check the permissions for the service principal or user in the Azure portal and ensure the correct roles are assigned for both the workspace and pipeline execution.
Review any recent Microsoft Fabric documentation or announcements for changes related to API authentication or permissions.
Try manually triggering the pipeline API call using Postman or a similar tool to isolate whether the issue is with Power Automate or the API itself.
Confirm that your authentication tokens include the required scopes for the Fabric API.
Hi jbaz ,
The Forbidden error typically results from recent updates to Fabric API security or permissions. While the API endpoint is still active, you now need
- Appropriate roles and permissions for your service principal or user in both the workspace and pipeline
- Access tokens updated with the necessary API scopes
- Compliance with any new authentication requirements for the API
Make sure the calling identity (user or service principal) has at least the Contributor role for both the workspace and pipeline. Even setups that worked before may require checking.
Try making the same API call with Postman or curl. If it fails there, the issue is likely with authentication or permissions, not Power Automate.
Review the latest Fabric REST API documentation for updates on endpoints or required headers.
REST API capabilities for Fabric Data Factory - Microsoft Fabric | Microsoft LearnRegards,
Yugandhar.
2 Replies
- V-yubandi-msftCommunity Support
Hi jbaz ,
The Forbidden error typically results from recent updates to Fabric API security or permissions. While the API endpoint is still active, you now need
- Appropriate roles and permissions for your service principal or user in both the workspace and pipeline
- Access tokens updated with the necessary API scopes
- Compliance with any new authentication requirements for the API
Make sure the calling identity (user or service principal) has at least the Contributor role for both the workspace and pipeline. Even setups that worked before may require checking.
Try making the same API call with Postman or curl. If it fails there, the issue is likely with authentication or permissions, not Power Automate.
Review the latest Fabric REST API documentation for updates on endpoints or required headers.
REST API capabilities for Fabric Data Factory - Microsoft Fabric | Microsoft LearnRegards,
Yugandhar. - MJParikhSuper User
It looks like Microsoft has recently updated security or permissions policies for triggering Fabric pipelines via the API, which may be causing the "Forbidden" error you're now seeing. This issue can often occur due to:
Permission changes: The service principal or user account previously used for the API call may no longer have the necessary permissions or roles.
Authentication issues: Token expiration or updated scope requirements can result in access being blocked.
Changes to API requirements: Microsoft sometimes updates REST API endpoints or the way authentication works, which may require modifications to Power Automate or any custom logic.
Recommended steps:
Double-check the permissions for the service principal or user in the Azure portal and ensure the correct roles are assigned for both the workspace and pipeline execution.
Review any recent Microsoft Fabric documentation or announcements for changes related to API authentication or permissions.
Try manually triggering the pipeline API call using Postman or a similar tool to isolate whether the issue is with Power Automate or the API itself.
Confirm that your authentication tokens include the required scopes for the Fabric API.