Skip to content

Commit 95e9db9

Browse files
authored
Update tenant-admin-center-capacity.md
1 parent a57a329 commit 95e9db9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

dev-itpro/administration/tenant-admin-center-capacity.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.devlang: na
88
ms.tgt_pltfrm: na
99
ms.workload: na
1010
ms.search.keywords: administration, tenant, admin, environment, sandbox
11-
ms.date: 04/01/2020
11+
ms.date: 09/22/2020
1212
ms.author: jswymer
1313
---
1414

@@ -39,7 +39,7 @@ Customers can also choose to purchase any number of additional production enviro
3939

4040
Production and sandbox environments can be created and used in any country where [!INCLUDE[prodshort](../developer/includes/prodshort.md)] service is available, also in the country where the default [!INCLUDE[prodshort](../developer/includes/prodshort.md)] environments are located. Additional environments can be created by customers, administrators, and partners by using the [!INCLUDE[prodadmincenter](../developer/includes/prodadmincenter.md)].
4141

42-
When customer administrators create users in Microsoft 365 Admin Center and assign them [!INCLUDE[prodshort](../developer/includes/prodshort.md)] licenses, each user, by default, gets access to all [!INCLUDE[prodshort](../developer/includes/prodshort.md)] environments (sandbox and production) under the same single [!INCLUDE[prodshort](../developer/includes/prodshort.md)] license, still acting within the scope of their license within each of these environments. Administrators can limit users' access to any particular environment by [changing their permissions](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-define-granular-permissions), or by [removing users' access](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-how-users-permissions#to-remove-a-users-access-to-the-system) within that environment.
42+
When customer administrators create users in Microsoft 365 Admin Center and assign them [!INCLUDE[prodshort](../developer/includes/prodshort.md)] licenses, each user, by default, gets access to all [!INCLUDE[prodshort](../developer/includes/prodshort.md)] environments (sandbox and production) under the same single [!INCLUDE[prodshort](../developer/includes/prodshort.md)] license, still acting within the scope of their license within each of these environments. Administrators can limit users' access to any particular environment by [changing their permissions](/dynamics365/business-central/ui-define-granular-permissions), or by [removing users' access](/dynamics365/business-central/ui-how-users-permissions#to-remove-a-users-access-to-the-system) within that environment.
4343

4444
## Storage
4545

@@ -53,7 +53,7 @@ Every additional production environment purchased by the customer also increases
5353

5454
#### Storage usage by environment
5555

56-
The **Storage usage by environment** section of the **Capacity** page provides a tenant-level view of where your organization is using storage capacity. Here you can see how much database and file storage is used by each environment. For each of your environments, you can also navigate to the [Table Information page](https://docs.microsoft.com/en-us/dynamics365/business-central/admin-view-table-information) within [!INCLUDE[prodshort](../developer/includes/prodshort.md)], which let's you see the distribution of data size across tables.
56+
The **Storage usage by environment** section of the **Capacity** page provides a tenant-level view of where your organization is using storage capacity. Here you can see how much database and file storage is used by each environment. For each of your environments, you can also navigate to the [Table Information page](/dynamics365/business-central/admin-view-table-information) within [!INCLUDE[prodshort](../developer/includes/prodshort.md)], which let's you see the distribution of data size across tables.
5757

5858
> [!NOTE]
5959
> Only the environments running on version 17 (2020 release wave 2) and later are included in the database capacity calculations.

0 commit comments

Comments
 (0)