Microsoft API Pagination Python API Docs | dltHub

Build a Microsoft API Pagination-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Microsoft Graph API provides a unified REST endpoint for accessing data and insights from across the Microsoft 365 cloud platform. The REST API base URL is https://graph.microsoft.com and all requests require a Bearer token in the Authorization header.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Microsoft API Pagination data in under 10 minutes.


What data can I load from Microsoft API Pagination?

Here are some of the endpoints you can load from Microsoft API Pagination:

ResourceEndpointMethodData selectorDescription
users/usersGETvalueRetrieve a list of user objects.
messages/me/messagesGETvalueRetrieve the messages in the signed-in user's mailbox.
events/me/eventsGETvalueRetrieve a list of events in the user's calendar.
drives/me/drivesGETvalueRetrieve a list of drive objects for the user.
groups/groupsGETvalueRetrieve a list of Microsoft 365 group objects.

How do I authenticate with the Microsoft API Pagination API?

Requests to the Microsoft Graph API must include an Authorization header with a Bearer token. The token is obtained from the Microsoft identity platform using OAuth 2.0 flows.

1. Get your credentials

  1. Sign in to the Microsoft Entra admin center (or Azure portal). 2. Navigate to App registrations and click New registration to create an application. 3. Under the Overview section, copy the Application (client) ID and Directory (tenant) ID. 4. Go to API permissions, add Microsoft Graph, and select the required Application permissions (e.g., User.Read.All). 5. Click Grant admin consent for your directory. 6. Navigate to Certificates & secrets, click New client secret, add a description, and generate the secret. Copy the secret value immediately, as it will not be displayed again.

2. Add them to .dlt/secrets.toml

[sources.microsoft_api_pagination_source] client_id = "your_application_client_id_here" client_secret = "your_client_secret_value_here" tenant_id = "your_directory_tenant_id_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Microsoft API Pagination API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python microsoft_api_pagination_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline microsoft_api_pagination_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset microsoft_api_pagination_data The duckdb destination used duckdb:/microsoft_api_pagination.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads v1.0/users and v1.0/me/messages from the Microsoft API Pagination API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def microsoft_api_pagination_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://graph.microsoft.com", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "users", "endpoint": {"path": "users", "data_selector": "value"}}, {"name": "messages", "endpoint": {"path": "me/messages", "data_selector": "value"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="microsoft_api_pagination_pipeline", destination="duckdb", dataset_name="microsoft_api_pagination_data", ) load_info = pipeline.run(microsoft_api_pagination_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("microsoft_api_pagination_pipeline").dataset() sessions_df = data.users.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM microsoft_api_pagination_data.users LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("microsoft_api_pagination_pipeline").dataset() data.users.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Microsoft API Pagination data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Microsoft API Pagination?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines