Merge pull request #34879 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-04 17:30 UTC

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

data-migration/sql-server/database/database-migration-service.md

@@ -74,7 +74,7 @@ To complete this tutorial, you need the following prerequisites:
 To create the login and user on the target Azure SQL Database, run the following script on the `master` database:
 
 ```sql
-CREATE LOGIN testuser with Password = '*********'
+CREATE LOGIN testuser WITH PASSWORD = '<password>';
 
 ALTER SERVER ROLE ##MS_DefinitionReader## ADD MEMBER [testuser];
 GO
@@ -88,9 +88,9 @@ GO
 ALTER SERVER ROLE ##MS_LoginManager## ADD MEMBER [testuser];
 GO
 
-CREATE USER testuser from login testuser;
-EXEC sp_addRoleMember 'dbmanager', 'testuser';
-EXEC sp_addRoleMember 'loginmanager', 'testuser';
+CREATE USER testuser FOR LOGIN testuser;
+EXECUTE sp_addRoleMember 'dbmanager', 'testuser';
+EXECUTE sp_addRoleMember 'loginmanager', 'testuser';
 ```
 
 Now, you can migrate both the database schema and data using Database Migration Service. You can also use other tools such as the [SQL Server dacpac extension](/azure-data-studio/extensions/sql-server-dacpac-extension) or the [SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension) in Azure Data Studio to migrate the schema before selecting the list of tables to migrate.
@@ -207,7 +207,6 @@ To open the Migrate to Azure SQL wizard:
 > [!NOTE]  
 > If no tables are selected or if a username and password aren't entered, the **Next** button isn't available to select.
 
-
 Now, you can migrate database Schema and data both using Database Migration Service. Also, you can use tools like the [SQL Server dacpac extension](/azure-data-studio/extensions/sql-server-dacpac-extension) or the [SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension) in Azure Data Studio to migrate Schema before selecting the list of tables to migrate.
 
 ### Create a Database Migration Service instance
@@ -358,7 +357,7 @@ Before you begin the tutorial:
 To create the login and user on the target Azure SQL Database, run the following script on the `master` database:
 
 ```sql
-CREATE LOGIN testuser with Password = '*********'
+CREATE LOGIN testuser WITH PASSWORD = '<password>';
 
 ALTER SERVER ROLE ##MS_DefinitionReader## ADD MEMBER [testuser];
 GO
@@ -372,9 +371,9 @@ GO
 ALTER SERVER ROLE ##MS_LoginManager## ADD MEMBER [testuser];
 GO
 
-CREATE USER testuser from login testuser;
-EXEC sp_addRoleMember 'dbmanager', 'testuser';
-EXEC sp_addRoleMember 'loginmanager', 'testuser';
+CREATE USER testuser FOR LOGIN testuser;
+EXECUTE sp_addRoleMember 'dbmanager', 'testuser';
+EXECUTE sp_addRoleMember 'loginmanager', 'testuser';
 ```
 
 Now, you can migrate both the database schema and data using Database Migration Service. You can also use other tools such as the [SQL Server dacpac extension](/azure-data-studio/extensions/sql-server-dacpac-extension) or the [SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension) in Azure Data Studio to migrate the schema before selecting the list of tables to migrate.
@@ -396,17 +395,17 @@ Now, you can migrate both the database schema and data using Database Migration
 
    :::image type="content" source="media/database-migration-service/dms-portal-sql-database-scenario-new.png" alt-text="Screenshot of select new migration scenario." lightbox="media/database-migration-service/dms-portal-sql-database-scenario-new.png":::
 
-1. On the **Azure SQL Database Offline Migration Wizard**, follow these steps: 
+1. On the **Azure SQL Database Offline Migration Wizard**, follow these steps:
 
-   1. On the **Source details** tab, enter details for the source SQL Server instance, and then select **Next: Connect to source SQL Server**: 
+   1. On the **Source details** tab, enter details for the source SQL Server instance, and then select **Next: Connect to source SQL Server**:
 
       :::image type="content" source="media/database-migration-service/dms-portal-sql-database-source-1-new.png" alt-text="Screenshot of Source Tracking." lightbox="media/database-migration-service/dms-portal-sql-database-source-1-new.png":::
 
-   1. On the **Connect to source SQL Server** tab, provide connection details and then select **Next: Select databases for migration**: 
-    
+   1. On the **Connect to source SQL Server** tab, provide connection details and then select **Next: Select databases for migration**:
+
       :::image type="content" source="media/database-migration-service/dms-portal-sql-database-source-2-new.png" alt-text="Screenshot of Connect to source." lightbox="media/database-migration-service/dms-portal-sql-database-source-2-new.png":::
 
-   1. On the **Select databases for migration** tab, check the box next to the databases you want to migrate. Populating the list of databases can take some time. Select **Next: Connect to target Azure SQL Database**. 
+   1. On the **Select databases for migration** tab, check the box next to the databases you want to migrate. Populating the list of databases can take some time. Select **Next: Connect to target Azure SQL Database**.
 
       :::image type="content" source="media/database-migration-service/dms-portal-sql-database-select-db-1-new.png" alt-text="Screenshot of select db." lightbox="media/database-migration-service/dms-portal-sql-database-select-db-1-new.png":::
 
@@ -418,7 +417,7 @@ Now, you can migrate both the database schema and data using Database Migration
 
       :::image type="content" source="media/database-migration-service/dms-portal-sql-database-map-db-1-new.png" alt-text="Screenshot of Map databases." lightbox="media/database-migration-service/dms-portal-sql-database-map-db-1-new.png":::
 
-   1. (Optional) Check the box next to **Migrate Missing schema** to deploy missing schema objects from the source to the Azure SQL Database target to migrate the following schema objects with a *single checkbox*: 
+   1. (Optional) Check the box next to **Migrate Missing schema** to deploy missing schema objects from the source to the Azure SQL Database target to migrate the following schema objects with a *single checkbox*:
 
       - Schemas
       - Tables (selected)
@@ -442,8 +441,8 @@ Now, you can migrate both the database schema and data using Database Migration
       - XmlSchemaCollections
 
       > [!NOTE]  
-      > - If you select **Migrate Missing Schema**, the Database Migration service performs the schema migration before data is migrated. 
-      > - DMS proceeds with the data migration phase even if schema migration encounters errors, unless there are issues with table objects. 
+      > - If you select **Migrate Missing Schema**, the Database Migration service performs the schema migration before data is migrated.
+      > - DMS proceeds with the data migration phase even if schema migration encounters errors, unless there are issues with table objects.
 
       Next, either use **Select all tables** to migrate all tables, or use the text entry box to filter the list of tables and select individual tables to migrate. Then select **Next: Database migration summary**.
 
@@ -477,7 +476,7 @@ Now, you can migrate both the database schema and data using Database Migration
    | **Rebuilding indexes** | The service is rebuilding indexes on target tables. |
    | **Succeeded** | All data is copied and the indexes are rebuilt. |
 
-1. Under **Source name**, select a database name to open the table view.. In this detailed view, you see the current status of the migration, the number of tables that currently are in that status, and a detailed status of each table: 
+1. Under **Source name**, select a database name to open the table view.. In this detailed view, you see the current status of the migration, the number of tables that currently are in that status, and a detailed status of each table:
 
    :::image type="content" source="media/database-migration-service/dms-portal-sql-database-monitoring-1-new.png" alt-text="Screenshot of Detailed migration monitoring." lightbox="media/database-migration-service/dms-portal-sql-database-monitoring-1-new.png":::
 

docs/includes/entra-id-tutorial.md

@@ -2,7 +2,7 @@
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 07/11/2025
+ms.date: 07/31/2025
 ms.service: sql
 ms.topic: include
 ---
@@ -179,6 +179,10 @@ Or,
 
 ## Configure Microsoft Entra authentication for SQL Server through Azure portal
 
+The steps in Azure portal apply to [!INCLUDE [sssql22-md](sssql22-md.md)].
+
+The steps in Azure portal do not apply to [!INCLUDE [sssql25-md](sssql25-md.md)].
+
 > [!NOTE]  
 > You can configure Microsoft Entra authentication with any of the following experiences:
 >
@@ -238,7 +242,7 @@ After the Azure Arc agent on the SQL Server host has completed its operation, th
 The same syntax for creating Microsoft Entra logins and users on Azure SQL Database and Azure SQL Managed Instance can now be used on SQL Server.
 
 > [!NOTE]  
-> On SQL Server, any account that has the `ALTER ANY LOGIN` or `ALTER ANY USER` permission can create Microsoft Entra logins or users, respectively. The account doesn't need to be a Microsoft Entra login.
+> On SQL Server, any Microsoft Entra account that has the `ALTER ANY LOGIN` or `ALTER ANY USER` permission can create Microsoft Entra logins or users, respectively. Otherwise, only accounts with `sysadmin` permissions can create Microsoft Entra logins or users.
 
 To create a login for a Microsoft Entra account, execute the following T-SQL command in the `master` database:
 

docs/relational-databases/security/authentication-access/azure-ad-authentication-sql-server-setup-tutorial.md

@@ -4,7 +4,7 @@ description: Tutorial on how to set up Microsoft Entra authentication for SQL Se
 author: PratimDasgupta
 ms.author: prdasgu
 ms.reviewer: vanto, randolphwest
-ms.date: 04/04/2025
+ms.date: 07/31/2025
 ms.service: sql
 ms.subservice: security
 ms.topic: tutorial
@@ -13,6 +13,6 @@ monikerRange: ">=sql-server-ver16||>= sql-server-linux-ver16"
 
 # Tutorial: Set up Microsoft Entra authentication for SQL Server
 
-[!INCLUDE [SQL Server 2022](../../../includes/applies-to-version/sqlserver2022.md)]
+[!INCLUDE [SQL Server 2022](../../../includes/applies-to-version/sqlserver2022.md)] only.
 
 [!INCLUDE [entra-id-tutorial](../../../includes/entra-id-tutorial.md)]

docs/relational-databases/security/authentication-access/microsoft-entra-authentication-sql-server-enable-without-arc.md

@@ -4,7 +4,7 @@ description: Tutorial on how to set up Microsoft Entra authentication for SQL Se
 author: PratimDasgupta
 ms.author: prdasgu
 ms.reviewer: vanto
-ms.date: 05/09/2025
+ms.date: 07/31/2025
 ms.service: sql
 ms.subservice: security
 ms.topic: tutorial
@@ -13,7 +13,7 @@ monikerRange: ">=sql-server-ver16 || >=sql-server-linux-ver16"
 
 # Tutorial: Enable Microsoft Entra authentication for SQL Server on Windows without Azure Arc
 
-[!INCLUDE [SQL Server 2022](../../../includes/applies-to-version/sqlserver2022.md)]
+[!INCLUDE [SQL Server 2022](../../../includes/applies-to-version/sqlserver2022.md)] and later.
 
 This article describes how to authenticate with Microsoft Entra ID without setting up Azure Arc for your on-premises SQL Server 2022 and later versions. Microsoft Entra authentication is a cloud-based identity management service that provides secure access to SQL Server databases. This tutorial guides you through the process of setting up Microsoft Entra authentication for SQL Server on Windows without Azure Arc.
 

docs/sql-server/azure-arc/managed-identity.md

@@ -4,7 +4,7 @@ description: Learn how to use a managed identity with SQL Server 2025.
 author: PratimDasgupta
 ms.author: prdasgu
 ms.reviewer: mikeray, randolphwest, mathoma, vanto
-ms.date: 07/06/2025
+ms.date: 07/28/2025
 ms.service: sql
 ms.topic: how-to
 ms.custom:
@@ -38,6 +38,7 @@ When using managed identity with SQL Server enabled by Azure Arc, consider the f
   - `Inbound connections` are logins and users connecting to SQL Server. Inbound connections can also be achieved by using [App registration](entra-authentication-setup-tutorial.md), starting in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)].
   - `Outbound connections` are SQL Server connections to Azure resources, like backup to URL, or connecting to Azure Key Vault.
 - App Registration **can't** enable a SQL Server to make outbound connections. Outbound connections need a primary managed identity assigned to the SQL Server.
+- For SQL Server 2025 and later, we recommend that you use managed identity based Microsoft Entra setup, as detailed in this article. Alternatively, you can configure an [app registration for SQL Server 2025.](/sql/relational-databases/security/authentication-access/microsoft-entra-authentication-sql-server-enable-without-arc)
 
 ## Prerequisites
 

docs/tools/sql-database-projects/concepts/package-references.md

@@ -90,6 +90,7 @@ The available system database packages are:
 - [SQL Server `master` system database](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs.Master)
 - [SQL Server `msdb` system database](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs.Msdb)
 - [Azure SQL Database `master` system database](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs.Azure.Master)
+- [SQL database in Fabric system objects](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs.DbFabric)
 - [Azure Synapse Analytics `master` system database](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs.Synapse.Master)
 - [Azure Synapse Analytics serverless pools `master` system database](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs.SynapseServerless.Master)