Merge pull request #2060 from MicrosoftDocs/master

Updates to Admin Center for capacities, renaming, and operations log

Author: jswymer

dev-itpro/TOC.md

@@ -104,6 +104,7 @@
 ### [Managing Environments](administration/tenant-admin-center-environments.md)
 ### [Managing Apps](administration/tenant-admin-center-manage-apps.md)
 ### [Exporting Databases](administration/tenant-admin-center-database-export.md)
+### [Capacity](administration/tenant-admin-center-capacity.md)
 ### [Tenant Notifications](administration/tenant-admin-center-notifications.md)
 ### [Managing Updates](administration/tenant-admin-center-update-management.md)
 ### [Environment Telemetry](administration/tenant-admin-center-telemetry.md)

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

@@ -0,0 +1,87 @@
+---
+title: Managing Capacity | Microsoft Docs
+description: Use the Business Central administration center to manage your tenant capacity 
+author: jswymer
+ms.service: dynamics365-business-central
+ms.topic: article
+ms.devlang: na
+ms.tgt_pltfrm: na
+ms.workload: na
+ms.search.keywords: administration, tenant, admin, environment, sandbox
+ms.date: 09/22/2020
+ms.author: jswymer
+---
+
+#  Managing Capacity
+
+To help customers manage and plan their storage costs on an ongoing basis, the [!INCLUDE[prodadmincenter](../developer/includes/prodadmincenter.md)] includes the **Capacity** page. The **Capacity** page provides an overview of the total database and file storage usage, with details about the storage used by every environment. The page also displays the currently used and the maximum allowed number of production and sandbox environments available for the customer.  
+
+Customers can purchase additional database capacity and environments via their reselling partner by using the following add-ons:  
+- Dynamics 365 Business Central Database Capacity 
+- Dynamics 365 Business Central Additional Environment Add-on
+
+## Number of environments
+
+[!INCLUDE[prodshort](../developer/includes/prodshort.md)] administrators can create multiple sandbox and production type environments for various purposes, like:
+- Creating more business branches
+- Moving into more countries
+- Expanding within their current country
+- Development
+- Testing changes
+- Learning new product capabilities
+
+Every [!INCLUDE[prodshort](../developer/includes/prodshort.md)] customer with [!INCLUDE[prodshort](../developer/includes/prodshort.md)] Premium or Essential subscriptions can use one production environment and three sandbox environments, at no extra charge.  
+
+> [!NOTE]
+> Existing customers with [!INCLUDE[prodshort](../developer/includes/prodshort.md)] Premium or Essentials subscriptions purchased before October 1st 2020 will keep their existing environment entitlements for a period of 1 year until October 1st 2021 or until their subscription is renewed or ended, whichever occurs last. This won't increase their overall database storage capacity and won't enable extra sandbox environments. These benefits are only activated with the production environments purchased by the customers separately.
+
+Customers can also choose to purchase any number of additional production environments via their CSP partner. Each production environment comes with three additional sandbox environments.  
+
+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)]. 
+
+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. 
+
+## Storage
+
+Storage capacity usage of [!INCLUDE[prodshort](../developer/includes/prodshort.md)] is represented by **Database** and **File** on the **Capacity** page.  
+
+[!INCLUDE[prodshort](../developer/includes/prodshort.md)] customers can use up to 80 GB of database storage capacity across all of their environments (production and sandbox), meaning that the sum of database capacity usage of all of their environments must not exceed 80 GB.  
+
+Some businesses have unique scenarios that may require additional storage. For those organizations that need more space, there is an option to purchase extra database capacity as an add-on to their existing [!INCLUDE[prodshort](../developer/includes/prodshort.md)] subscriptions through their reselling CSP partner. Every add-on increases overall database capacity quota by 1 GB.  
+
+Every additional production environment purchased by the customer also increases tenant-wide database capacity quota by 4 GB.  
+
+#### Storage usage by environment
+
+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.
+
+> [!NOTE]
+> Only the environments running on version 17 (2020 release wave 2) and later are included in the database capacity calculations.  
+
+The **File usage** storage is calculated based on the size of the content of the following tables: 
+
+- Tenant Media 
+- Tenant Media Thumbnails 
+
+The content of the other tables is counted towards the **Database usage** storage.  
+
+> [!IMPORTANT]
+> When you uninstall extensions, you have a choice of deleting or leaving the extension data in the database. If you decide not to delete the data when uninstalling extensions, this data will be counted in the overall database storage you use.  
+
+## Exceeding capacity quotas 
+
+Exceeding the paid database storage limit won't interrupt transaction processing within the existing environments. The existing environments that organically grow and eventually exceed the quota will still be accessible and available for the customers to continue their business operations.
+
+However, once the capacity limits are exceeded, the customers won't be able to create new environments or copy their existing environments until the storage used by the existing environments is decreased to fit the quota or additional capacity is purchased.  
+
+Administrative actions are currently not limited by the File storage, however similar restrictions will be applied to the File storage with one of the next releases of [!INCLUDE[prodshort](../developer/includes/prodshort.md)].
+
+## See also
+
+[Working with Administration Tools](administration.md)  
+[The Business Central Administration Center](tenant-admin-center.md)  
+[Managing Environments](tenant-admin-center-environments.md)  
+[Managing Apps](tenant-admin-center-manage-apps.md)  
+[Updating Environments](tenant-admin-center-update-management.md)  
+[Managing Tenant Notifications](tenant-admin-center-notifications.md)  
+[Introduction to automation APIs](itpro-introduction-to-automation-apis.md)  

dev-itpro/administration/tenant-admin-center-database-export.md

@@ -97,12 +97,11 @@ The .bacpac file contains data that is customer-specific business data. Technica
 
 This means that if you want to export the data in order to change the customer's [!INCLUDE [prodshort](../developer/includes/prodshort.md)] from an online deployment to an on-premises deployment, you must also get the application data from the installation media from the same version of [!INCLUDE [prodshort](../developer/includes/prodshort.md)] that the online tenant is using. You can see the version number in the [!INCLUDE [prodadmincenter](../developer/includes/prodadmincenter.md)] or the **Help and Support** page in the customer's [!INCLUDE [prodshort](../developer/includes/prodshort.md)].  
 
-[!IMPORTANT] While you can import the downloaded .bacpac file into your own SQL Server instance, Microsoft does not provide support for creating a working on-premises environment from the .bacpac that you download from [!INCLUDE [prodshort](../developer/includes/prodshort.md)] online.  
+> [!IMPORTANT]
+> While you can import the downloaded .bacpac file into your own SQL Server instance, Microsoft does not provide support for creating a working on-premises environment from the .bacpac that you download from [!INCLUDE [prodshort](../developer/includes/prodshort.md)] online.  
 
 For more information, see [Quickstart: Import a BACPAC file to a database in Azure SQL Database](/azure/sql-database/sql-database-import), [Migrating to Single-Tenancy From Multitenancy](../deployment/Merging-an-Application-Database-with-a-Tenant-Database.md), and [When to choose on-premises deployment](../deployment/Deployment.md#when-to-choose-on-premises-deployment).  
 
-
-
 ## See also
 
 [SQL Server technical documentation](/sql/sql-server/)  

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

@@ -102,6 +102,63 @@ Canceling a session is sometimes the only way to unblock a customer. For example
 
 To cancel a session, select it from the list and then select **Cancel selected sessions**.
 
+## <a name="rename"></a>Renaming an environment
+
+> [!NOTE]
+> This feature is in preview. It might change or be removed in the future updates.
+
+You can change the name of any environment. The name uniquely identifies the environment from your other environments. Before you change a name, you must consider that the name also is part of the environment's URL. The URL is used in links to the environment in various ways. So changing the name can have significant impact.
+
+### Before you rename an environment
+
+- Read the [Environment rename considerations](#consider) section to understand the consequences of renaming an environment.
+- Make sure you notify all your users, including any external service integrations you may have, about the upcoming URL change. It will let them prepare to update their references. 
+- Determine the best time to do the renaming. Renaming an environment requires a restart to the environment. We recommend doing this operation when no users are active in Business Central.  
+
+### Rename an environment
+
+1. Select **Environments**, then select the environment you want to rename.
+2. On the **Environment Details** page, select **Rename**.
+3. On **Rename environment** page, read the information.
+4. Enter the new name, and then select **Rename**.
+5. Confirm your intent to rename the environment.
+
+At this point, the environment state will first change to **Preparing | Rename Scheduled**, then to **Active** again when the rename has been completed. The new name will be available immediately. The environment will no longer be accessible using the old environment name.  
+
+You can also review the log for the Rename operation on the **Operations** page afterwards.
+
+### <a name="consider"></a>Environment rename considerations
+
+Changing the environment name can affect many scenarios and integrations. In the early stages of a customer implementation, it may be a low risk operation. But renaming an environment that's been used by customers for a while or integrated with many external services and components is risky. So carefully plan for it.
+
+Here are some areas where the environment name is used, which will be affected when you change the environment name. You need to consider these areas and plan your communication before attempting to rename an environment:  
+
+- Web client URL, including links to web client bookmarked by users
+- Deep links to specific pages within [!INCLUDE[prodshort](../developer/includes/prodshort.md)] created by users or shared by them via e-mails, internal documentation or training  portals, Teams channels, Word, and Excel documents. They're often exchanged among users in the same company, across companies, across environments, across tenants. Links created by users as desktop shortcuts. Links sent or created before the name change will no longer work after the name change.
+- Integrations that embed the web client, for example, SharePoint apps composed of Business Central pages
+- Integrations that launch the web client  
+- Partner-developed mobile apps, web applications, and so on. These apps likely originate from partners outside the customer's organization where the admin can't update URLS. 
+- Mobile apps, including Windows 10 store app for desktop/tablet. Affects only users who have modified the protocol handler to force the app to connect to environment with name other than "production". If the user keeps working with "production" on the mobile app (which is default now), and the admin renames the environment from "prod2" to "myprod", the mobile user isn't affected. Otherwise, the app would throw an error, and the user would have to exit using a newly created protocol handler link.
+- Browser cache. [!INCLUDE[prodshort](../developer/includes/prodshort.md)] stores the URL, including environment name, in some of its cached data. This data is cached browser-side, that is, in the user's browser and across devices. Admins typically don't have access or control this data cache. When users lose their cache, they lose the link modifications to all their pages and preferences. 
+- Web services URL, potentially affecting external integrations that use OData or SOAP
+
+- [!INCLUDE[prodshort](../developer/includes/prodshort.md)] add-ins and integrations with other Microsoft services
+  - Outlook Add-in. The Add-In manifest that is saved to Exchange Server, either per-organization or per-user, includes the environment name.
+  - Excel Add-in. Each user's Excel worksheet stores the environment name. 
+  - Power BI. All reports, including the default reports deployed from the Role Center, built before the rename will be affected. Also, Power BI apps installed before the rename would be affected. There's no automatic way to repair these items. The partner or user would have to manually update the connections.
+  - Power Apps/Automate. All apps and flows built before rename would be affected with no automatic way to repair. The partner or user would have to manually update the connections. 
+  - CDS. CDS Virtual Entity setup stores environment name.
+- Development scenarios  
+  - Publish to sandbox environment from Visual Studio Code. The launch.json file of extensions might contain the sandbox name, if different from "default". The files require source code updates.
+  - CI/CD pipelines for test and deployment could be impacted by environment renames.
+- Azure Application Insights logs and metrics
+
+## <a name="opslog"></a>Log of administrative operations
+
+The **Operations** section of [!INCLUDE [prodadmincenter](../developer/includes/prodadmincenter.md)] provides a log of operations that internal administrators and delegated administrators from the partner have made in the [!INCLUDE [prodadmincenter](../developer/includes/prodadmincenter.md)] or through the admin center API. Currently, the log includes the following operations: Renaming environments.
+
+Use this log to see which operations were created and when. You can also access detailed error messages in this log, should any operation fail.  
+
 ## See also
 
 [Working with Administration Tools](administration.md)