Skip to content

Commit 9e80f99

Browse files
Merge pull request #231726 from khdownie/kendownie032223
configure coexistence for ADDS and AAD Kerb
2 parents edc5a0d + 979921e commit 9e80f99

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

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

Lines changed: 18 additions & 2 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: 12/05/2022
7+
ms.date: 03/22/2023
88
ms.author: kendownie
99
ms.subservice: files
1010
ms.custom: engagement-fy23
@@ -152,7 +152,7 @@ After enabling Azure AD Kerberos authentication, you'll need to explicitly grant
152152

153153
4. Select the application with the name matching **[Storage Account] `<your-storage-account-name>`.file.core.windows.net**.
154154
5. Select **API permissions** in the left pane.
155-
6. Select **Grant admin consent for "DirectoryName"**.
155+
6. Select **Grant admin consent**.
156156
7. Select **Yes** to confirm.
157157

158158
## Disable multi-factor authentication on the storage account
@@ -202,6 +202,22 @@ Use one of the following three methods:
202202

203203
Changes are not instant, and require a policy refresh or a reboot to take effect.
204204

205+
> [!IMPORTANT]
206+
> Once this change is applied, the client(s) won't be able to connect to storage accounts that are configured for on-premises AD DS integration without configuring Kerberos realm mappings. If you want the client(s) to be able to connect to storage accounts configured for AD DS as well as storage accounts configured for Azure AD Kerberos, follow the steps in [Configure coexistence with storage accounts using on-premises AD DS](#configure-coexistence-with-storage-accounts-using-on-premises-ad-ds).
207+
208+
### Configure coexistence with storage accounts using on-premises AD DS
209+
210+
If you want to enable client machines to connect to storage accounts that are configured for AD DS as well as storage accounts configured for Azure AD Kerberos, follow these steps. If you're only using Azure AD Kerberos, skip this section.
211+
212+
Add an entry for each storage account that uses on-premises AD DS integration. Use one of the following three methods to configure Kerberos realm mappings:
213+
214+
- Configure this Intune [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider) and apply it to the client(s): [Kerberos/HostToRealm](/windows/client-management/mdm/policy-csp-admx-kerberos#hosttorealm)
215+
- Configure this group policy on the client(s): `Administrative Template\System\Kerberos\Define host name-to-Kerberos realm mappings`
216+
- Configure the following registry value on the client(s): `reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\domain_realm /v <DomainName> /d <StorageAccountEndPoint>`
217+
- For example, `reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\domain_realm /v contoso.local /d <your-storage-account-name>.file.core.windows.net`
218+
219+
Changes are not instant, and require a policy refresh or a reboot to take effect.
220+
205221
## Disable Azure AD authentication on your storage account
206222

207223
If you want to use another authentication method, you can disable Azure AD authentication on your storage account by using the Azure portal, Azure PowerShell, or Azure CLI.

0 commit comments

Comments
 (0)