Forum Discussion
DAGRun via API
Hi User,
The behavior you're seeing is expected. The Swagger UI is already authenticated through your Microsoft Fabric session, whereas requests from Postman or a shell script don't have that authentication context, so they're redirected to the Microsoft Entra ID (Azure AD) sign-in page.
A few things to check:
Verify whether the Airflow REST API in Fabric supports Microsoft Entra ID (OAuth 2.0) authentication for external clients. If so, you'll need to acquire an access token and include it in the Authorization: Bearer <token> header.
Basic Authentication is generally not supported for Microsoft Fabric services, so enabling it may not be possible.
If you're calling the API from automation (Postman, curl, or a script), consider using a service principal or another supported Microsoft Entra authentication flow, if the API supports it.
If the API documentation doesn't describe external authentication, it may currently be limited to authenticated Fabric sessions or have preview limitations.
For more information:
Apache Airflow in Microsoft Fabric: https://learn.microsoft.com/fabric/data-factory/apache-airflow-jobs-hello-world
Microsoft Fabric REST API: https://learn.microsoft.com/rest/api/fabric/
Microsoft identity platform (OAuth 2.0): https://learn.microsoft.com/entra/identity-platform/
Could you also clarify:
Which Airflow REST endpoint are you trying to call (for example, POST /dags/{dag_id}/dagRuns)?
Are you using Microsoft Entra user authentication or a service principal?
Is your goal to trigger DAGs from an external application or from another Fabric pipeline?
This will help determine the most appropriate authentication approach for your scenario.
💡 Helpful? Give a Kudos 👍 — keep the community growing.✅ Solved your issue? Mark this as the Accepted Solution ✔️Best regards, |