Orchestrating the Orchestrator
Talking to Airflow through Copilot Studio Agent using Microsoft Teams
A DAG fails. Time to play detective!
Open Airflow. Hunt down the run. Click the red task. Dig through the logs.
Ten clicks, three screens, and one coffee later… “Aha! So that’s what broke!”
What if you could do it all directly from Microsoft Teams, without logging into the Airflow UI?
By connecting a Copilot Studio Agent to Airflow through a custom connector, we can bring everyday Airflow operations into Teams. Simply ask a question, investigate a failure, retrieve logs, or initiate an action—all through a familiar conversational interface.
Monitor: Retrieve DAG runs, identify failed tasks, and find long-running jobs.
Investigate: Fetch task details, execution history, and logs.
Perform RCA: Identify likely causes and recommend corrective actions.
Take action: Clear tasks, rerun DAGs, pause or unpause DAGs, and perform other supported operations.
Copilot Studio is the conversational brain. Teams is where you chat. The custom connector is the bridge. And Airflow’s REST APIs? They’re the ones doing the actual legwork.
Together, they turn Teams into your Airflow control room—check runs, investigate failures, dig into logs, and take action without playing hide-and-seek with the Airflow UI.
Airflow orchestrates the workflows. Copilot Studio brings the drama, the detective work, and the action right into Teams.
Fewer clicks. Less detective work. More getting things done.
CONNECT WITH ME