Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowFabric Data Days Monthly is back. Join us on March 26th for two expert-led sessions on 1) Getting Started with Fabric IQ and 2) Mapping & Spacial Analytics in Fabric. Register now
After following the Microsoft documentation to synchronize code from a GitHub repository to Airflow in Microsoft Fabric, the DAG files are not appearing in the Airflow UI. Configuration steps were completed according to the official guide 'https://learn.microsoft.com/en-us/fabric/data-factory/apache-airflow-jobs-sync-git-repo#synchronize-...', but DAGs remain invisible in the interface. Seeking clarification on DAG folder structure requirements and assistance in troubleshooting the synchronization process to ensure DAGs are properly detected and displayed.
Im having the exact same problem and couldnt find any solution.
Hi, @uthanuja
Please check to confirm that it is now visible?
Solved: Airflow not recognizing DAGs when File storage cha... - Microsoft Fabric Community
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,
I noticed in the documentation that since I'm using GitHub as my Git service, I should be using Personal Access Token authentication rather than Service Principal. Could you please confirm if this is the correct approach?
Best Regards
Hi, @uthanuja
Yes, you are correct. When using GitHub as your Git service, it is recommended to use Personal Access Token (PAT) authentication rather than Service Principal.
For reference:
Managing your personal access tokens - GitHub Enterprise Server 3.15 Docs
Use service principals & managed identities - Azure DevOps | Microsoft Learn
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Yes, I have been using a PAT for authentication. The issue you linked to mentions that it was resolved using service principal authorization, but that approach doesn’t work in my case. Could you help me understand why Airflow is not recognizing DAGS when using Git sync?
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Fabric update to learn about new features.