Skip to content

Commit 6976785

Browse files
Merge pull request #33845 from rwestMSFT/rw-0417-fix-420837
Fix typo, related links, in winauth-azyuread article (UUF 420837)
2 parents 6ae49a8 + 1e4c3ef commit 6976785

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

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

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,19 @@
11
---
2-
title: What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
2+
title: What Is Windows Authentication for Microsoft Entra Principals on Azure SQL Managed Instance?
33
titleSuffix: Azure SQL Managed Instance
44
description: Learn about Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance.
55
author: sravanisaluru
66
ms.author: srsaluru
7-
ms.reviewer: mathoma, bonova, urmilano, wiassaf
8-
ms.date: 09/27/2023
7+
ms.reviewer: mathoma, bonova, urmilano, wiassaf, randolphwest
8+
ms.date: 04/17/2025
99
ms.service: azure-sql-managed-instance
1010
ms.subservice: deployment-configuration
1111
ms.topic: overview
1212
---
1313

14-
# What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
15-
[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
14+
# What is Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance?
15+
16+
[!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
1617

1718
[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.
1819

@@ -24,7 +25,7 @@ As customers modernize their infrastructure, application, and data tiers, they a
2425

2526
[!INCLUDE [entra-authentication-options](../includes/entra-authentication-options.md)]
2627

27-
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.
28+
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.
2829

2930
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.
3031

@@ -38,7 +39,6 @@ By enabling Windows Authentication for Microsoft Entra principals, customers can
3839

3940
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:
4041

41-
4242
- **"Double hop" authentication**: Web applications use IIS identity impersonation to run queries against an instance in the security context of the end user.
4343
- **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).
4444

@@ -48,9 +48,7 @@ Enabling Windows Authentication for Microsoft Entra principals on Azure SQL Mana
4848

4949
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.
5050

51-
## Next steps
52-
53-
Learn more about implementing Windows Authentication for Microsoft Entra principals on Azure SQL Managed Instance:
51+
## Related content
5452

5553
- [How Windows Authentication for Azure SQL Managed Instance is implemented with Microsoft Entra ID and Kerberos](winauth-implementation-aad-kerberos.md)
5654
- [How to set up Windows Authentication for Azure SQL Managed Instance using Microsoft Entra ID and Kerberos](winauth-azuread-setup.md)

0 commit comments

Comments
 (0)