Skip to content

Commit 7f0d965

Browse files
authored
Apply pencil edits for blocking issues from PR review
1 parent 22582f0 commit 7f0d965

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

azure-sql/virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Starting with SQL Server 2022, you can connect to SQL Server on Azure VM using o
2727
- Azure Active Directory access token
2828

2929

30-
When enabling a [managed identity](/azure/active-directory/managed-identities-azure-resources/overview#managed-identity-types) for SQL Server on Azure Virtual Machines, the security boundary of the identity is the resource to which it's attached. For example, the security boundary for a virtual machine with managed identities for Azure resources enabled, is the virtual machine. Any code running on that VM, is able to call the managed identities endpoint and request tokens. The experience is similar experience when working with other resources that support managed identities. For more information, read the [Managed Identities faq](/azure/active-directory/managed-identities-azure-resources/managed-identities-faq).
30+
When enabling a [managed identity](/azure/active-directory/managed-identities-azure-resources/overview#managed-identity-types) for SQL Server on Azure Virtual Machines, the security boundary of the identity is the resource to which it's attached. For example, the security boundary for a virtual machine with managed identities for Azure resources enabled is the virtual machine. Any code running on that VM is able to call the managed identities endpoint and request tokens. The experience is similar experience when working with other resources that support managed identities. For more information, read the [Managed Identities FAQ](/azure/active-directory/managed-identities-azure-resources/managed-identities-faq).
3131

3232
## Prerequisites
3333

@@ -75,7 +75,7 @@ To grant your managed identity the **Azure AD Directory** role permission, follo
7575

7676
:::image type="content" source="media/configure-azure-ad-authentication-for-sql-vm/azure-ad-verify-assignment-settings.png" alt-text="Screenshot of settings on the Add assignment in the Azure portal.":::
7777

78-
1. On the **Directory Readers | Assignments** page, confirm you see your newly-added identity under **Directory Readers**.
78+
1. On the **Directory Readers | Assignments** page, confirm you see your newly added identity under **Directory Readers**.
7979

8080
:::image type="content" source="media/configure-azure-ad-authentication-for-sql-vm/azure-ad-verify-directory-reader.png" alt-text="Screenshot of the Directory Readers page of the Azure portal showing your VM assignment added to the role.":::
8181

@@ -101,7 +101,7 @@ Consider the following limitations:
101101
- Currently, enabling Azure AD authentication is only possible through the Azure portal.
102102
- Currently, Azure AD authentication is only available to SQL Server VMs deployed to the public cloud.
103103
- Azure AD authentication is only supported for Azure Windows VMs.
104-
- Currently, authenticating to SQL VM through AAD authentication using [FIDO2 method](/azure/active-directory/authentication/howto-authentication-passwordless-faqs) is not supported.
104+
- Currently, authenticating to SQL VM through Azure AD authentication using [FIDO2 method](/azure/active-directory/authentication/howto-authentication-passwordless-faqs) is not supported.
105105

106106
## Next steps
107107

0 commit comments

Comments
 (0)