Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into bv-april2025-sql

Author: markingmyname

azure-sql/managed-instance/winauth-azuread-overview.md

@@ -1,18 +1,19 @@
 ---
-title: What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
+title: What Is Windows Authentication for Microsoft Entra Principals on Azure SQL Managed Instance?
 titleSuffix: Azure SQL Managed Instance
 description: Learn about Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance.
 author: sravanisaluru
 ms.author: srsaluru
-ms.reviewer: mathoma, bonova, urmilano, wiassaf
-ms.date: 09/27/2023
+ms.reviewer: mathoma, bonova, urmilano, wiassaf, randolphwest
+ms.date: 04/17/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: overview
 ---
 
-# What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance? 
-[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
+# What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
+
+[!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
 
 [Azure SQL Managed Instance](sql-managed-instance-paas-overview.md) is the intelligent, scalable cloud database service that combines the broadest SQL Server database engine compatibility with the benefits of a fully managed and evergreen platform as a service. Kerberos authentication for Microsoft Entra ID ([formerly Azure Active Directory](/entra/fundamentals/new-name)) enables Windows Authentication access to Azure SQL Managed Instance. Windows Authentication for managed instances empowers customers to move existing services to the cloud while maintaining a seamless user experience and provides the basis for infrastructure modernization.
 
@@ -24,7 +25,7 @@ As customers modernize their infrastructure, application, and data tiers, they a
 
 [!INCLUDE [entra-authentication-options](../includes/entra-authentication-options.md)]
 
-However, some legacy apps can't change their authentication to Microsoft Entra ID: legacy application code may longer be available, there may be a dependency on legacy drivers, clients may not be able to be changed, and so on. Windows Authentication for Microsoft Entra principals removes this migration blocker and provides support for a broader range of customer applications.
+However, some legacy apps can't change their authentication to Microsoft Entra ID: legacy application code might no longer be available, there could be a dependency on legacy drivers, clients might not be able to be changed, and so on. Windows Authentication for Microsoft Entra principals removes this migration blocker and provides support for a broader range of customer applications.
 
 Windows Authentication for Microsoft Entra principals on managed instances is available for devices or virtual machines (VMs) joined to Active Directory, Microsoft Entra ID, or hybrid Microsoft Entra ID - a hybrid Microsoft Entra user identity exists both in Microsoft Entra ID and Active Directory and can access a managed instance in Azure using Microsoft Entra Kerberos.
 
@@ -38,7 +39,6 @@ By enabling Windows Authentication for Microsoft Entra principals, customers can
 
 Windows Authentication for Microsoft Entra principals also enables the following patterns on managed instances. These patterns are frequently used in traditional on-premises SQL Servers:
 
-
 - **"Double hop" authentication**: Web applications use IIS identity impersonation to run queries against an instance in the security context of the end user.
 - **Traces using extended events and SQL Server Profiler** can be launched using Windows authentication, providing ease of use for database administrators and developers accustomed to this workflow. Learn how to [run a trace against Azure SQL Managed Instance using Windows Authentication for Microsoft Entra principals](winauth-azuread-run-trace-managed-instance.md).
 
@@ -48,9 +48,7 @@ Enabling Windows Authentication for Microsoft Entra principals on Azure SQL Mana
 
 For example, a customer can enable a mobile analyst, using proven tools that rely on Windows Authentication, to authenticate to a managed instance using biometric credentials. This can be accomplished even if the mobile analyst works from a laptop that is joined to Microsoft Entra ID.
 
-## Next steps
-
-Learn more about implementing Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance:
+## Related content
 
 - [How Windows Authentication for Azure SQL Managed Instance is implemented with Microsoft Entra ID and Kerberos](winauth-implementation-aad-kerberos.md)
 - [How to set up Windows Authentication for Azure SQL Managed Instance using Microsoft Entra ID and Kerberos](winauth-azuread-setup.md)

docs/database-engine/configure-windows/enable-or-disable-a-server-network-protocol.md

@@ -62,7 +62,7 @@ All network protocols are installed during installation, by [!INCLUDE[ssNoVersio
    You can run this script from any machine, with or without SQL Server installed. Make sure you have the **SqlServer** module installed.
 
    ```powershell
-   #requires the SqlServer module
+   # This script requires the SqlServer module
    Import-Module SQLServer
 
    $wmi = New-Object Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer <#computer_name#>
@@ -76,7 +76,7 @@ All network protocols are installed during installation, by [!INCLUDE[ssNoVersio
    $Tcp.IsEnabled = $true
    $Tcp.Alter()
    $Tcp
- 
+
    # Enable the named pipes protocol for the default instance.
    $uri = "ManagedComputer[@Name='<#computer_name#>']/ServerInstance[@Name='MSSQLSERVER']/ServerProtocol[@Name='Np']"
    $Np = $wmi.GetSmoObject($uri)
@@ -99,22 +99,31 @@ After you enable or disable protocols, you must stop and restart the [!INCLUDE[s
 
 ```powershell
 # Get a reference to the ManagedComputer class.
-CD SQLSERVER:\SQL\<computer_name>
+Set-Location SQLSERVER:\SQL\<computer_name>
 $Wmi = (get-item .).ManagedComputer
+
 # Get a reference to the default instance of the Database Engine.
 $DfltInstance = $Wmi.Services['MSSQLSERVER']
+
 # Display the state of the service.
 $DfltInstance
+
 # Stop the service.
 $DfltInstance.Stop();
+
 # Wait until the service has time to stop.
+
 # Refresh the cache.
 $DfltInstance.Refresh();
+
 # Display the state of the service.
 $DfltInstance
+
 # Start the service again.
 $DfltInstance.Start();
+
 # Wait until the service has time to start.
+
 # Refresh the cache and display the state of the service.
 $DfltInstance.Refresh();
 $DfltInstance

docs/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup.md

@@ -3,7 +3,7 @@ title: "Upgrade: Installation Wizard (Setup)"
 description: The SQL Server Installation Wizard provides a single feature tree for an in-place upgrade of SQL Server components to the latest version of SQL Server.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/31/2024
+ms.date: 04/17/2025
 ms.service: sql
 ms.subservice: install
 ms.topic: install-set-up-deploy
@@ -21,9 +21,7 @@ monikerRange: ">=sql-server-2016"
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation Wizard provides a single feature tree for an in-place upgrade of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] components to the latest version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
 
 > [!WARNING]  
-> When you upgrade [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], the previous version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is overwritten, and no longer exists on your computer.
->
-> Before upgrading, back up SQL Server databases and other objects associated with the previous SQL Server instance.
+> When you upgrade [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], the previous version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is overwritten, and no longer exists on your computer. Before upgrading, back up SQL Server databases and other objects associated with the previous SQL Server instance.
 
 For many production and some development environments, a new installation upgrade or a rolling upgrade is more appropriate than an in-place upgrade. For more information regarding upgrade methods, see:
 
@@ -40,7 +38,7 @@ For many production and some development environments, a new installation upgrad
 You must run Setup as an administrator. If you install [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] from a remote share, you must use a domain account that has read and execute permissions on the remote share, and is a local administrator.
 
 > [!WARNING]  
-> Be aware that you can't change the features to be upgraded, and you can't add features during the upgrade operation. For more information about how to add features to an upgraded instance of [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] after the upgrade operation is complete, see [Add Features to an Instance of SQL Server (Setup)](add-features-to-an-instance-of-sql-server-setup.md).
+> You can't change the features to be upgraded, and you can't add features during the upgrade operation. For more information about how to add features to an upgraded instance of [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] after the upgrade operation is complete, see [Add Features to an Instance of SQL Server (Setup)](add-features-to-an-instance-of-sql-server-setup.md).
 
 If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Plan and test the Database Engine upgrade plan](plan-and-test-the-database-engine-upgrade-plan.md) and then perform the following tasks, as appropriate for your environment:
 
@@ -52,7 +50,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
 - Ensure that existing SQL Server system databases - master, model, `msdb`, and `tempdb` - are configured to autogrow, and ensure that they have sufficient hard disk space.
 
-- Ensure that all database servers have logon information in the `master` database. This is important for restoring a database, as system logon information resides in master.
+- Ensure that all database servers have logon information in the `master` database. This is important for restoring a database, as system logon information resides in `master`.
 
 - Disable all startup stored procedures, as the upgrade process stops and starts services on the SQL Server instance being upgraded. Stored procedures processed at startup time might block the upgrade process.
 
@@ -67,7 +65,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
 <a id="to-upgrade-include-ssnoversionincludesssnoversion-mdmd"></a>
 
-### Upgrade [!INCLUDE [ssNoversion](../../includes/ssnoversion-md.md)]
+### Upgrade SQL Server
 
 1. Insert the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] installation media, and from the root folder, double-click Setup.exe. To install from a network share, move to the root folder on the share, and then double-click Setup.exe.
 
@@ -94,7 +92,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
    The prerequisites for the selected features are displayed on the right-hand pane. [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Setup installs the prerequisites that aren't already installed during the installation step described later in this procedure.
 
    > [!NOTE]  
-   > If you have opted to upgrade the shared features by selecting **\<Upgrade shared features only>** on the **Select Instance** page, all the shared features are preselected on the Feature Selection page. All the shared components are upgraded at the same time.
+   > If you elect to upgrade the shared features by selecting **\<Upgrade shared features only>** on the **Select Instance** page, all the shared features are preselected on the Feature Selection page. All the shared components are upgraded at the same time.
 
 1. On the Instance Configuration page, specify the Instance ID for the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
 
@@ -112,7 +110,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
    To specify the same login account for all service accounts in this instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], provide credentials in the fields at the bottom of the page.
 
-   > [!CAUTION]
+   > [!CAUTION]  
    > [!INCLUDE [ssNoteStrongPass](../../includes/ssnotestrongpass-md.md)]
 
      When you're finished specifying login information for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] services, select **Next**.
@@ -127,9 +125,10 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
 1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] installation process, select **Close**.
 
-1. If you're instructed to restart the computer, do so now. It's important to read the message from the Installation Wizard when you have finished with Setup. For more information about Setup log files, see [View and Read SQL Server Setup Log Files](view-and-read-sql-server-setup-log-files.md).
+1. If you're instructed to restart the computer, do so now. You must read the message from the Installation Wizard when you finish with Setup. For more information about Setup log files, see [View and Read SQL Server Setup Log Files](view-and-read-sql-server-setup-log-files.md).
 
 ## Related content
 
 - [Upgrade SQL Server](upgrade-sql-server.md)
-- [Backward Compatibility_deleted](/previous-versions/sql/sql-server-2016/cc280407(v=sql.130))
+- [Issues when upgrading to SQL Server 2022](/troubleshoot/sql/database-engine/install/windows/issues-upgrading-sql-server-2022)
+- [Backward Compatibility](/previous-versions/sql/sql-server-2016/cc280407(v=sql.130))