> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/client-portal/systems/setup-guides/business-central.md).

# Business Central

Register a Microsoft Entra application and configure Business Central in Zwapgrid.

Microsoft Dynamics 365 Business Central is a cloud ERP for financial and operational processes. Set up new integrations with an application registered in Microsoft Entra ID and stored in a Zwapgrid System Setting.

| Item                        | Details                                                                                                                         |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Client Portal configuration | Available                                                                                                                       |
| Test option                 | Business Central trial or sandbox environment                                                                                   |
| Vendor documentation        | [Business Central developer documentation](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/) |

## Prepare a test environment

Create a [Business Central trial](https://learn.microsoft.com/en-us/dynamics365/business-central/trial-signup) or use an existing sandbox environment. The sample CRONUS company can provide representative data for initial testing.

## Register the Microsoft Entra application

1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/).
2. Open **Entra ID → App registrations** and create a registration.
3. For an integration offered to organisations in different Microsoft Entra tenants, select the multitenant organisational-directory account type.
4. Record the Application (client) ID.
5. Under **Certificates & secrets**, create a client secret and store its value securely. The value is shown only when it is created.
6. Under **API permissions**, add the required Dynamics 365 Business Central application permissions. The existing Zwapgrid connection requires `API.ReadWrite.All`.
7. Grant administrator consent and confirm that the permission status is granted.

Microsoft documents the general process in [Register an application in Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app).

## Configure Zwapgrid

1. In the Client Portal, open **Systems → Business Central → Configure**.
2. Create a System Setting with a name that identifies its environment and purpose.
3. Enter the Application (client) ID and client secret value.
4. Save, review, and publish the setting.

See [System Settings](/client-portal/systems/system-settings.md) for the shared workflow and lifecycle rules.

## Test and move to production

1. Create a Development Consent using the published setting.
2. Complete the [Onboarding Flow](/onboarding-flow/onboarding-flow.md) with the test tenant.
3. Confirm that tenant consent and Business Central permissions allow every required operation.
4. Test with a representative company and environment.
5. Before production, document who owns Entra application administration and client-secret rotation.

{% hint style="warning" %}
Creating an application registration does not by itself grant access to Business Central data. The required permissions and administrator consent must also be in place.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zwapgrid.com/client-portal/systems/setup-guides/business-central.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.