Load Dynamics 365 Business Central data to Microsoft Fabric

Dynamics 365 Business Central is an ERP platform that provides a REST API for connecting third-party solutions to manage financial and business data. Everything needed to build a working Dynamics 365 Business Central → Microsoft Fabric pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Dynamics 365 Business Central to Microsoft Fabric pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Dynamics 365 Business Central API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Dynamics 365 Business Central API at a glance

These values come from the Dynamics 365 Business Central API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Dynamics 365 Business Central API?

Authentication is performed using the OAuth 2.0 protocol via Microsoft Entra ID. Requests must include an Authorization header with a Bearer token: 'Authorization: Bearer <access_token>'.

1. Get your credentials

Dynamics 365 Business Central utilizes Microsoft Entra ID (formerly Azure AD) OAuth 2.0 for authentication. To obtain credentials: 1. Sign in to the Azure portal and navigate to App registrations. 2. Register a new application to represent your integration. 3. On the 'API permissions' page, select 'Add a permission', choose 'Dynamics 365 Business Central', and grant 'Delegated permissions' (e.g., Financials.ReadWrite.All). 4. Navigate to 'Certificates & secrets', select 'New client secret', and save the generated secret value immediately as it cannot be retrieved later. 5. Record the Application (client) ID and Directory (tenant) ID from the app's 'Overview' page for use in your authentication flow.

2. Add them to .dlt/secrets.toml

Copy
[sources.dynamics_365_business_central_source]
access_token = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Dynamics 365 Business Central data can I load into Microsoft Fabric?

These are the Dynamics 365 Business Central endpoints dlt can load into Microsoft Fabric:

---

How do I load only new Dynamics 365 Business Central records?

Dynamics 365 Business Central exposes lastModifiedDateTime on api/v2.0/companies({id})/items, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "items", "endpoint": {
    "path": "api/v2.0/companies({id})/items",
    "data_selector": "value",
    "incremental": {"cursor_path": "lastModifiedDateTime", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Dynamics 365 Business Central pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading companies and items (or customers as standard v2.0 API entities) from the Dynamics 365 Business Central API into Microsoft Fabric:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def dynamics_365_business_central_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.businesscentral.dynamics.com/v2.0",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "items", "endpoint": {"path": "api/v2.0/companies({id})/items", "data_selector": "value"}},
            {"name": "customers", "endpoint": {"path": "api/v2.0/companies({id})/customers", "data_selector": "value"}}
        ],
    }
    yield from rest_api_resources(config)


def load_dynamics_365_business_central_to_fabric() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="dynamics_365_business_central_pipeline",
        destination="fabric",
        dataset_name="dynamics_365_business_central_data",
    )
    load_info = pipeline.run(dynamics_365_business_central_source())
    print(load_info)


if __name__ == "__main__":
    load_dynamics_365_business_central_to_fabric()

Run it with python dynamics_365_business_central_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Dynamics 365 Business Central data in Microsoft Fabric?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("dynamics_365_business_central_pipeline").dataset()
df = data.items.df()
print(df.head())

SQL:

Copy
SELECT * FROM dynamics_365_business_central_data.items LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Dynamics 365 Business Central to Microsoft Fabric pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Dynamics 365 Business Central loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Dynamics 365 Business Central data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack