Skip to content

Commit 038d7c8

Browse files
Merge pull request #219453 from b-ahibbard/anf-ad-23nov
clarify ad admin account
2 parents b04634c + e39a451 commit 038d7c8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-netapp-files/create-active-directory-connections.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 11/22/2022
15+
ms.date: 11/23/2022
1616
ms.author: anfdocs
1717
---
1818
# Create and manage Active Directory connections for Azure NetApp Files
@@ -50,7 +50,7 @@ Several features of Azure NetApp Files require that you have an Active Directory
5050
* Alternatively, an AD domain user account with `msDS-SupportedEncryptionTypes` write permission on the AD connection admin account can also be used to set the Kerberos encryption type property on the AD connection admin account.
5151

5252
>[!NOTE]
53-
>It's _not_ recommended nor required to add the Azure NetApp Files AD admin account to the AD domain groups listed above. Nor is it recommended or required to grant `msDS-SupportedEncryptionTypes` write permission to the AD admin account.
53+
>It's _not_ recommended or required to add the Azure NetApp Files AD admin account to the AD domain groups listed above. Nor is it recommended or required to grant `msDS-SupportedEncryptionTypes` write permission to the Azure NetApp Files AD admin account.
5454
5555
If you set both AES-128 and AES-256 Kerberos encryption on the admin account of the AD connection, the highest level of encryption supported by your AD DS will be used.
5656

0 commit comments

Comments
 (0)