# Understanding the infrastructure of Business Central online
When someone wants to buy Business Central online, a couple of questions must be answered because Business Central can be configured along several different axes. This section explains the topology of Business Central online so you can decide how to deploy and configure a Business Central tenant.
> TIP
> Business Central is available in a limited number of markets. See Country/regional availability and supported languages<../compliance/apptest-countries-and-translations>.
## Microsoft 365 and Microsoft Entra ID
The first decision to make is related to the Microsoft Entra tenant that is required to use for Business Central online. To sign up for a trial, use a work or school account. See Try or buy a Microsoft 365 for business subscription<https://learn.microsoft.com/microsoft-365/commerce/try-or-buy-microsoft-365?view=o365-worldwide&preserve-view=true>.
This account is an important step because it's tied to a region of the world. Users are defined in the Microsoft Entra account and then assigned the relevant licenses in the Microsoft 365 admin center. It's also important for the reseller's Microsoft Entra ID. Learn more in the Enroll in the Cloud Solution Provider (CSP) program<tenant-administration#enroll-in-the-csp-program> section.
> TIP
> For some customers, the right approach is to have multiple Microsoft Entra tenants due to their own organizational structure. However, in Business Central, all users of an environment must belong to the same Microsoft Entra tenant.
If an organization's structure changes over time, admins can transfer environments from one Microsoft Entra tenant to another. See Move an Environment to another Microsoft Entra organization<tenant-admin-center-environments-move>.
## Environments and companies
Each Microsoft Entra tenant that buys a Business Central online license automatically gets some environments. Each environment is tied to a specific country and localization.
> NOTE
> The Premium and Essential subscription types give each Business Central customer one production environment and three sandbox environments at no extra charge. If the customer needs more production environments, they can buy more through their CSP partner. Each extra production environment includes three extra sandbox environments and 4 GB extra tenant-wide database capacity.
Administrators can create the additional environments in the Business Central administration center. The environments can be created for any country or region where Business Central is available<../compliance/apptest-countries-and-translations>, on any available version. The environments quota is applied when you try to create a new environment, or copy or restore an existing environment.
Each environment can be divided into multiple companies, where each company defines a legal entity or a business unit that has separate accounting requirements. All users who have a Business Central license for a specific Microsoft Entra tenant can access all companies in each Business Central environment that the Microsoft Entra tenant has. You can define different permissions inside Business Central. See Create Users According to Licenses</ui-how-users-permissions> in the business functionality content.
## Example
Let's review a scenario for an organization that is based in Denmark but has a subsidiary in Germany. They have three business units in Denmark and two in Germany. The following diagram illustrates how this fictitious company set up their Business Central:
![Chart that shows one Microsoft Entra tenant using two Business Central production environments and one sandbox with three and two companies, respectively.]
In this example, the production environment that is based on the Danish localization of Business Central is part of the default assignment as described earlier. This production environment has three companies to represent the following business units, all located in central Jutland:
 The administrative headquarters
 The production facilities
 The Danish sales office
Contoso chose to add a sandbox environment with two companies so that their users can train new employees in a safe environment. The sandbox started out as a copy of the Danish production environment. Over time, it becomes a training ground with sample data that Contoso's reselling partner creates for them.
Because Contoso has a German subsidiary that has separate accounting requirements, they decided to buy another production environment. This extra environment has two companies, one for the sales offices in Munich, and one for the warehouse near Stuttgart.
The users in all three environments are defined in the same Microsoft Entra tenant. This way, all licensed users can work in all environments. Individual access to various capabilities is controlled through permissions.
Alternatively, the organization could have chosen to use a separate Microsoft Entra tenant for the German subsidiary so that the German environment could use the Essentials license type rather than the Premium license type.
The following diagram illustrates how things would look for Contoso if they wanted to use two different license types:
![Chart that shows two Microsoft Entra tenants with each one production environment and one sandbox.]
In this type of configuration, users from the Danish Microsoft Entra tenant can't access the German environments. However, Business Central supports consolidation of financial data from different companies</finance-consolidated-company-reporting> so that Contoso's HQ can still get a complete overview of the business.
> IMPORTANT
> As the examples illustrate, the Microsoft Entra tenant plays an important role in how users can access Business Central. Users from one Microsoft Entra tenant can't access environments that belong to another Microsoft Entra tenant.
Contoso is just an example to illustrate how the Microsoft Entra tenant both affects and reflects the organizational structure. In some cases, this example is overly simplistic; in other cases, the example is too complicated. We recommend that customers work closely with their Microsoft reselling partner to understand how to configure their Business Central online.
> TIP
> Learn how to find out which Azure region a Business Central environment is deployed to in Country/regional availability and supported languages<../compliance/apptest-countries-and-translations>.
## Related information
Administration of Business Central online<tenant-administration>
Production and sandbox environments<environment-types>
The Business Central administration center<tenant-admin-center>
The Business Central administration center API<administration-center-api>
Version numbers in Business Central<version-numbers>
Monitoring and analyzing<telemetry-overview>
Get started as a reseller of Business Central online<get-started-online>
Deliver consulting services as a VAR: aka.ms/BusinessCentralConsultingServices<https://aka.ms/BusinessCentralConsultingServices>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-environment-topology, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/administration/tenant-environment-topology/
