Merge pull request #37041 from VanMSFT/vanmsft/uuf-batch-april-2026

Resolve 2 UUF items — CTE execution semantics, Entra user-assigned MI

Author: prmerger-automator[bot]

azure-sql/database/authentication-aad-service-principal-tutorial.md

@@ -4,7 +4,7 @@ description: This tutorial walks you through creating Microsoft Entra users with
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: wiassaf, mathoma
-ms.date: 03/18/2026
+ms.date: 04/10/2026
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: tutorial
@@ -78,6 +78,9 @@ In this tutorial, you learn how to:
 
    :::image type="content" source="media/authentication-aad-service-principals-tutorial/enterprise-applications-object-id.png" alt-text="Screenshot shows where to find the Object ID for an enterprise application.":::
 
+> [!TIP]
+> As an alternative to a system-assigned managed identity, you can use a **user-assigned managed identity**. A user-assigned managed identity can be shared across multiple logical servers, which reduces the number of identities to manage and simplifies role assignments. For more information, see [User-assigned managed identity in Microsoft Entra ID for Azure SQL](authentication-azure-ad-user-assigned-managed-identity.md).
+
 ## Add server identity to Directory Readers role
 
 The server identity requires permissions to query Microsoft Entra ID for administrative functions, which includes creating Microsoft Entra users and logins, and doing group expansion to apply user permissions based on their Microsoft Entra group membership. If server identity permissions to query Microsoft Entra ID are revoked, or the server identity is deleted, Microsoft Entra authentication stops working.

docs/t-sql/queries/with-common-table-expression-transact-sql.md

@@ -4,7 +4,7 @@ description: "Transact-SQL reference for how to use common table expressions (CT
 author: VanMSFT
 ms.author: vanto
 ms.reviewer: randolphwest
-ms.date: 06/25/2025
+ms.date: 04/10/2026
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -127,6 +127,9 @@ The data type of a column in the recursive member must be the same as the data t
 
 The `FROM` clause of a recursive member must refer only one time to the CTE *expression_name*.
 
+> [!NOTE]
+> A recursive CTE executes in the following order: first, the anchor member query runs and produces the initial result set. Then, the recursive member runs repeatedly, with each iteration using the previous iteration's output as its input. Recursion stops when the recursive member returns no rows. Finally, `UNION ALL` combines the results of the anchor member and all recursive iterations into a single result set. This means that `UNION ALL` doesn't deduplicate rows during each recursive step — it concatenates all intermediate results after recursion completes.
+
 The following items aren't allowed in the *CTE_query_definition* of a recursive member:
 
 - `SELECT DISTINCT`