These two processes are managed by different teams. How would you create a dependency between them?

When two processes are owned by separate teams, the key is to establish clear interfaces and automated triggers. In Airflow, you can use an ExternalTaskSensor in the downstream DAG to wait for the upstream DAG to finish. The sensor checks the state of the upstream DAG run and only allows the downstream tasks to start once it succeeds. If the teams use different environments, you can expose a REST endpoint or a message queue; the downstream DAG can poll the endpoint or consume a message that signals completion. Another approach is to use XComs or a shared database table where the upstream DAG writes a completion flag. The downstream DAG reads this flag before proceeding. Documenting the dependency contract, setting up CI/CD pipelines that trigger the downstream DAG, and using versioned DAG files help keep the teams in sync and reduce manual coordination.