Microsoft Graph connection

Call the Microsoft Graph API from a task via a managed Leoflow Connection and the Azure provider’s KiotaRequestAdapterHook. The conn_type is msgraph. A connection carries the client id (login), the client secret (password), and the tenant id / api_version in Extra.

Declare the provider

# leoflow.yaml
dag_id: msgraph_users
connectors:
  - msgraph

Fields the UI asks for

The client secret (reserved characters) + tenant/api_version Extra round-trip is pinned by TestMSGraphConnectionURIShapeIntegration.

Example DAG (copy-paste)

Docs-only recipe (needs a real Azure AD app). The hook is imported inside the task — a top-level provider import fails the compile (see Installing a connector’s provider).

# dag.py
from __future__ import annotations

from airflow.sdk import DAG, task


@task
def list_users() -> None:
    from airflow.providers.microsoft.azure.hooks.msgraph import KiotaRequestAdapterHook

    hook = KiotaRequestAdapterHook(conn_id="msgraph_default")
    print("list_users: building Graph adapter via KiotaRequestAdapterHook(msgraph_default)")
    adapter = hook.get_conn()
    print(f"list_users: adapter ready ({adapter})")


with DAG("msgraph_users", schedule=None, catchup=False, tags=["example"]):
    list_users()

# leoflow.yaml
schema_version: "1.0"
dag_id: msgraph_users
description: Call Microsoft Graph via KiotaRequestAdapterHook.
owner: examples
tags:
  - example
python_version: "3.11"
connectors:
  - msgraph

Run it

1. Admin → Connections → +, type msgraph. Set the client id in Login, the client secret in Password, and the tenant id / api_version in Extra.
2. leoflow lite path/to/this/dag → trigger msgraph_users.

Security notes

• Scope the app registration to the minimum Graph permissions and rotate the client secret regularly; it is encrypted at rest and never echoed back.
• Never print() the URI — it carries the client secret.

Related

• docs/connections/index.md — Installing a connector’s provider.
• ADR 0019 / 0021 — secret encryption + agent delivery.