Merge pull request #7355 from MicrosoftDocs/main

Auto Publish – main to live - 2026-05-27 13:00 UTC

Author: learn-build-service-prod[bot]

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

@@ -97,7 +97,8 @@ To export data when moving the customer's [!INCLUDE [prod_short](../developer/in
 Learn more in [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).  
 
 > [!NOTE]
-> If you're getting an error saying your file contains corrupted data when importing the bacpac file, make sure you're using the .NET Core version of [SqlPackage.exe](/sql/tools/sqlpackage/sqlpackage-download).
+> - If you're getting an error saying your file contains corrupted data when importing the bacpac file, make sure you're using the .NET Core version of [SqlPackage.exe](/sql/tools/sqlpackage/sqlpackage-download).
+> - When importing the exported database using SQL Server Management Studio (SSMS), we recommend using latest version. Earlier versions might not support all scenarios. Learn how to update SSMS in [Update SQL Server Management Studio](/ssms/install/update).
 
 ## Restoring the exported data to Business Central online
 

dev-itpro/developer/includes/mcp-server-headers.md

@@ -1,6 +1,12 @@
 | HTTP header | Description | Example |
 |--------|-------------|---------|
 | `TenantId` | Your Microsoft Entra tenant ID (GUID) | `aaaabbbb-0000-cccc-1111-dddd2222eeee` |
-| `EnvironmentName` | The name of the Business Central environment to connect to| `Production` |
-| `Company` | The company name within the environment | `CRONUS USA, Inc.` |
-| `ConfigurationName` | (Optional) The MCP server configuration in the environment to use | `SalesTeamConfig` |
+| `EnvironmentName` | The name of the Business Central environment to connect to | `Production` |
+| `Company` | The company name within the environment |`CRONUS USA, Inc.` (ASCII)<br><br>`=?base64?Q3JvbnVzIMOFcmh1cyBBL1M=?=` (Base64-encoding of `CRONUS Århus A/S`) |
+| `ConfigurationName` | (Optional) The MCP server configuration in the environment to use | `SalesTeamConfig`<br><br>`=?base64?w4VyaHVzU2FsZXNUZWFtQ29uZmln?=` (Base64-encoding of `ÅrhusSalesTeamConfig`)|
+
+> [!NOTE]
+> If the `Company` or `ConfigurationName` values contain non-ASCII characters (for example, `ø`, `æ`, or `å`), you must encode the values using Base64 (UTF-8).  
+> The encoded value must use the format `=?base64?<encodedvalue>?=`. Learn more in [Base64 decoding in the MCP HTTP standard](https://modelcontextprotocol.io/seps/2243-http-standardization#base64-decoding).
+>
+> With Copilot Studio, the platform handles the encoding, so manual encoding isn't required.