Merge pull request #36745 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-02 23:30 UTC

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

azure-sql/database/database-export.md

@@ -5,7 +5,7 @@ description: Export a database to a BACPAC file using the Azure portal, PowerShe
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, hudequei, randolphwest
-ms.date: 01/26/2026
+ms.date: 03/02/2026
 ms.service: azure-sql
 ms.subservice: data-movement
 ms.topic: how-to
@@ -65,6 +65,22 @@ If the export operation exceeds 20 hours, it might be canceled. To increase perf
 
 1. To monitor the progress of the export operation, open the page for the server containing the database being exported. Under **Data management**, select **Import/Export history**.
 
+## Export with managed identity authentication (preview)
+
+You can export a database in Azure SQL Database to a BACPAC file using [managed identity](/entra/identity/managed-identities-azure-resources/overview) authentication to eliminate the need to provide SQL administrator passwords or storage access keys. 
+
+For a detailed tutorial, see [Use managed identity with import and export (preview)](database-import-export-managed-identity.md).
+
+To export a BACPAC file using managed identity authentication, the following configuration is required:
+
+- A **user-assigned managed identity (UAMI)** assigned to the [logical server](logical-servers.md) for Azure SQL Database.
+- The server has the managed identity configured as the **Microsoft Entra administrator**.
+- A managed identity is assigned to the **Storage Blob Data Contributor** role on the target Azure Storage account. This managed identity can be the same as the one assigned to the server or a different one.
+- The logical server, managed identity, and storage account are in the **same Microsoft Entra tenant**.
+
+> [!NOTE]
+> Export with managed identity authentication is currently in [**preview**](doc-changes-updates-release-notes-whats-new.md#preview) and only available for Azure SQL Database.
+
 ## SQLPackage utility
 
 We recommend the use of the SQLPackage utility for scale and performance in most production environments. You can run multiple SqlPackage commands in parallel for subsets of tables to speed up import/export operations.

azure-sql/database/database-import-export-managed-identity.md

@@ -5,7 +5,7 @@ description: Create a new database in Azure SQL Database or Azure SQL Managed In
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: hudequei, mathoma, drskwier, randolphwest
-ms.date: 01/26/2026
+ms.date: 03/02/2026
 ms.service: azure-sql
 ms.subservice: backup-restore
 ms.topic: quickstart
@@ -59,6 +59,29 @@ Watch this video to see how to import from a BACPAC file in the Azure portal or
 
 1. To verify the database is live on the server, select **SQL databases** and verify the new database is **Online**.
 
+## Import with managed identity authentication (preview)
+
+Azure SQL Database supports importing a BACPAC file using [managed identity](/entra/identity/managed-identities-azure-resources/overview) authentication. This option enables fully credential-free import operations and is recommended for environments that disable SQL authentication or enforce Microsoft Entra-only authentication.
+
+You can import a database to a *new database*, or to an *existing empty database*.
+
+For a detailed tutorial, see [Use managed identity with import and export (preview)](database-import-export-managed-identity.md).
+
+To import a BACPAC file using managed identity authentication, the following configuration is required:
+
+- A **user-assigned managed identity (UAMI)** assigned to the [logical server](logical-servers.md) for Azure SQL Database.
+- The server has the managed identity configured as the **Microsoft Entra administrator**.
+- A managed identity is assigned to the **Storage Blob Data Reader** role on the source Azure Storage account. This managed identity can be the same as the one assigned to the server or a different one.
+- The logical server, managed identity, and storage account are in the **same Microsoft Entra tenant**.
+
+The following scenarios are unsupported: 
+
+- Cross-tenant import operations.
+- Managed identity assigned only at the database level.
+
+> [!NOTE]
+> Import with managed identity authentication is currently in [**preview**](doc-changes-updates-release-notes-whats-new.md#preview) and only available for Azure SQL Database.
+
 ## Use SqlPackage
 
 To import a SQL Server database using the [SqlPackage](/sql/tools/sqlpackage) command-line utility, see [import parameters and properties](/sql/tools/sqlpackage/sqlpackage-import). You can download the latest [SqlPackage](/sql/tools/sqlpackage/sqlpackage-download) for Windows, macOS, or Linux.
@@ -172,7 +195,7 @@ To cancel the import operation, you need to be a member of one of the following
 
 ## Limitations
 
-- Importing to a database in elastic pool isn't supported through the Azure Portal, Azure PowerShell, or Azure CLI. Instead, create a database in the elastic pool and then use [SQLPackage Import](/sql/tools/sqlpackage/sqlpackage-import), or import data using any method into a single database and then move the database to an elastic pool.
+- Importing to a database in elastic pool isn't supported through the Azure portal, Azure PowerShell, or Azure CLI. Instead, create a database in the elastic pool and then use [SQLPackage Import](/sql/tools/sqlpackage/sqlpackage-import), or import data using any method into a single database and then move the database to an elastic pool.
 - Import Export Service doesn't work when Allow access to Azure services is set to OFF. However, you can work around the problem by manually running SqlPackage from an Azure VM, or performing the export directly in your code by using the DacFx API.
 - Import doesn't support specifying a backup storage redundancy while creating a new database and creates with the default geo-redundant backup storage redundancy. To work around, first create an empty database with desired backup storage redundancy using Azure portal or PowerShell and then import the BACPAC into this empty database.
 - Storage behind a firewall is currently not supported.

azure-sql/database/database-import.md

@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, randolphwest
-ms.date: 01/29/2026
+ms.date: 03/02/2026
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: whats-new
@@ -48,6 +48,7 @@ The following table lists the features of Azure SQL Database that are currently
 | **Elastic transactions** | [Elastic transactions](elastic-transactions-overview.md) allow you to execute transactions distributed among cloud databases in Azure SQL Database. |
 | **Fixed server roles** | To simplify permission management, Azure SQL Database provides a set of [fixed server-level roles](security-server-roles.md) to help you manage the permissions on a logical server. | 
 | **Immutable LTR backups** | You can [configure long-term retention backups of Azure SQL Database as immutable](backup-immutability.md) with legal hold immutability (preview feature). Time-based backup immutability is generally available.| 
+| **Import and export using managed identity** | You can [import or export an Azure SQL Database BACPAC file with managed identity authentication](database-import-export-managed-identity.md). Use managed identity authentication for enhanced security when importing or exporting databases. |
 | **Import and export using Private Link** | You can [import or export an Azure SQL Database using private link](database-import-export-private-link.md). Leave *Allow Access to Azure Services* off when you import or export a database using a service-managed endpoint. |
 | **Microsoft Entra server principals** | The ability to [create server principals (logins) for Microsoft Entra identities](authentication-azure-ad-logins.md) in Azure SQL Database is in preview. |
 | **Multiple geo-replicas for Hyperscale** | The ability to create up to four geo-replicas for Azure SQL Hyperscale is in preview.  Learn more about [multiple geo-replicas for Hyperscale](https://aka.ms/sqlhs-multi-geo-announcement). |
@@ -96,6 +97,12 @@ The following table lists features of Azure SQL Database that have been made gen
 
 Learn about significant changes to the Azure SQL Database documentation. For previous years, see the [What's new archive](doc-changes-updates-release-notes-whats-new-archive.md).
 
+### March 2026
+
+| Changes | Details |
+| --- | --- |
+| **Import and export using managed identity preview** | You can [import or export an Azure SQL Database BACPAC file with managed identity authentication](database-import-export-managed-identity.md). Use managed identity authentication for enhanced security when importing or exporting databases. This capability is currently in preview for Azure SQL Database. |
+
 ### January 2026
 
 | Changes | Details |

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -5,7 +5,7 @@ description: Use the update policy setting in Azure SQL Managed Instance to cont
 author: MladjoA
 ms.author: mlandzic
 ms.reviewer: mathoma
-ms.date: 11/18/2025
+ms.date: 2/27/2026
 ms.service: azure-sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: how-to
@@ -32,7 +32,7 @@ Azure SQL Managed Instance offers the following three update policies:
 ## SQL Server 2025 update policy
 
 > [!NOTE]
-> The **SQL Server 2025** update policy is currently in preview. Changing the update policy from **SQL Server 2025** to **Always-up-to-date** is currently and temporarily disabled.
+> Changing the update policy from **SQL Server 2025** to **Always-up-to-date** is currently and temporarily disabled.
 
 The **SQL Server 2025** update policy aligns your database format with [!INCLUDE [sssql25-md](../../docs/includes/sssql25-md.md)].
 

azure-sql/managed-instance/update-policy.md

@@ -353,6 +353,8 @@
       items:
       - name: Migrate using DMS
         href: /azure/dms/tutorial-sql-server-to-azure-sql?toc=/azure/azure-sql/toc.json
+      - name: Import or export database with managed identity authentication
+        href: database/database-import-export-managed-identity.md
     - name: Scale out
       items:
       - name: Configure Hyperscale named replicas

azure-sql/toc.yml

@@ -3,7 +3,7 @@ title: "Import and Export Data from SQL Server and Azure SQL Database"
 description: You can use Transact-SQL, command-line tools, and wizards to import and export data in SQL Server and Azure SQL Database in various data formats.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 07/15/2025
+ms.date: 03/02/2026
 ms.service: sql
 ms.subservice: data-movement
 ms.topic: concept-article
@@ -27,6 +27,36 @@ You can import data with the `BULK INSERT` or the `OPENROWSET(BULK...)` commands
 
 You can import and export data with the BCP command-line utility. For more information, see [Import and export bulk data using bcp (SQL Server)](import-and-export-bulk-data-by-using-the-bcp-utility-sql-server.md).
 
+### Azure portal import and export
+
+The Azure portal provides **Import** and **Export** actions for Azure SQL Database. You can use these actions to import or export a database as a BACPAC file through the **Azure SQL Import/Export service**.
+
+- **Export**: From an Azure SQL Database page, select **Export** to create a BACPAC file in Azure Blob Storage.
+- **Import**: From a [logical server for Azure SQL Database](https://portal.azure.com/#servicemenu/SqlAzureExtension/AzureSqlHub/DatabaseServer) page, select **Import database** to create a new database from a BACPAC file stored in Azure Blob Storage.
+
+Portal-based import and export operations:
+
+- Use the same import or export service and APIs as PowerShell, Azure CLI, and REST.
+- Support BACPAC files stored in Azure Blob Storage.
+- Surface operation status and history through **Import/Export history** on the logical server.
+
+Authentication options available in the Azure portal align with those supported by the import and export service. Support for **Managed Identity authentication** is in **Preview**.
+
+For a detailed tutorial, see [Use managed identity with import and export (preview)](/azure/azure-sql/database/database-import-export-managed-identity).
+
+In this model:
+
+- A **user‑assigned managed identity (UAMI)** is assigned to the logical server for Azure SQL Database.
+- The managed identity is configured as a **Microsoft Entra administrator** on the server.
+- The same or a different managed identity is granted **Azure RBAC data-plane access** to the target Azure Storage account.
+
+> [!NOTE]
+> - Import and export with managed identity authentication is currently in [**preview**](/azure/azure-sql/database/doc-changes-updates-release-notes-whats-new#preview) and only available for Azure SQL Database.
+> - Only **server-level user-assigned managed identities** are supported in the current preview.
+
+For more information, see [Import a BACPAC file to a database in Azure SQL Database](/azure/azure-sql/database/database-import#import-with-managed-identity-authentication-preview) and [Export a database to a BACPAC file](/azure/azure-sql/database/database-export##export-with-managed-identity-authentication-preview).
+
+
 ### Use the Import Flat File Wizard
 
 If you don't need all the configuration options available in the Import and Export Wizard and other tools, you can import a text file into SQL Server by using the **Import Flat File Wizard** in SQL Server Management Studio (SSMS). For more information, see the following articles: