Skip to content

Commit 393a992

Browse files
committed
updating AAD Kerb page
1 parent 5b5fc61 commit 393a992

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

articles/storage/files/storage-files-identity-auth-azure-active-directory-enable.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to enable identity-based Kerberos authentication for hybr
44
author: khdownie
55
ms.service: storage
66
ms.topic: how-to
7-
ms.date: 03/22/2023
7+
ms.date: 03/28/2023
88
ms.author: kendownie
99
ms.subservice: files
1010
ms.custom: engagement-fy23
@@ -75,15 +75,7 @@ To enable Azure AD Kerberos authentication using the [Azure portal](https://port
7575

7676
:::image type="content" source="media/storage-files-identity-auth-azure-active-directory-enable/enable-azure-ad-kerberos.png" alt-text="Screenshot of the Azure portal showing Active Directory configuration settings for a storage account. Azure AD Kerberos is selected." lightbox="media/storage-files-identity-auth-azure-active-directory-enable/enable-azure-ad-kerberos.png" border="true":::
7777

78-
1. **Optional:** If you want to configure directory and file-level permissions through Windows File Explorer, then you also need to specify the domain name and domain GUID for your on-premises AD. You can get this information from your domain admin or by running the following Active Directory PowerShell cmdlets from an on-premises AD-joined client:
79-
80-
```PowerShell
81-
$domainInformation = Get-ADDomain
82-
$domainGuid = $domainInformation.ObjectGUID.ToString()
83-
$domainName = $domainInformation.DnsRoot
84-
```
85-
86-
If you'd prefer to configure directory and file-level permissions using icacls, you can skip this step. However, if you want to use icacls, the client will need line-of-sight to the on-premises AD.
78+
1. **Optional:** If you want to configure directory and file-level permissions through Windows File Explorer, then you need to specify the domain name and domain GUID for your on-premises AD. You can get this information from your domain admin or by running the following Active Directory PowerShell cmdlet from an on-premises AD-joined client: `Get-ADDomain`. Your domain name should be listed in the output under `DNSRoot` and your domain GUID should be listed under `ObjectGUID`. If you'd prefer to configure directory and file-level permissions using icacls, you can skip this step. However, if you want to use icacls, the client will need line-of-sight to the on-premises AD.
8779

8880
1. Select **Save**.
8981

@@ -155,6 +147,9 @@ After enabling Azure AD Kerberos authentication, you'll need to explicitly grant
155147
6. Select **Grant admin consent**.
156148
7. Select **Yes** to confirm.
157149

150+
> [!IMPORTANT]
151+
> If you're connecting to a storage account via a private endpoint/private link using Azure AD Kerberos authentication, you'll also need to add the private link FQDN to the storage account's Azure AD application. For instructions, see the entry in our [troubleshooting guide](files-troubleshoot-smb-authentication.md#error-1326---the-username-or-password-is-incorrect-when-using-private-link).
152+
158153
## Disable multi-factor authentication on the storage account
159154

160155
Azure AD Kerberos doesn't support using MFA to access Azure file shares configured with Azure AD Kerberos. You must exclude the Azure AD app representing your storage account from your MFA conditional access policies if they apply to all apps.

0 commit comments

Comments
 (0)