Skip to content

Commit bc4bbd1

Browse files
Merge pull request #304989 from netapp-manishc/sep3-jira
Adding note to the topic
2 parents a6ecffd + e2ba4ff commit bc4bbd1

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

articles/azure-netapp-files/kerberos.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: whyistheinternetbroken
66
ms.service: azure-netapp-files
77
ms.topic: concept-article
8-
ms.date: 03/11/2025
8+
ms.date: 09/03/2025
99
ms.author: anfdocs
1010
# Customer intent: As a cloud storage administrator, I want to understand how Kerberos authentication works in Azure NetApp Files, so that I can configure secure access for SMB and NFS protocols and manage authentication processes effectively within my organization.
1111
---
@@ -415,7 +415,12 @@ The NFS Kerberos realm is configured when the Kerberos realm information is fill
415415

416416
:::image type="content" source="media/kerberos/kerberos-realm.png" alt-text="Screenshot of Kerberos realm configuration." lightbox="media/kerberos/multiple-dns-smb.png":::
417417

418-
The AD Server Name and KDC IP are used to connect to the AD KDC services on the initial machine account creation. The Azure NetApp Files service leverages the existing domain information to fill out the rest of the realm configuration. For example:
418+
The AD Server Name and KDC IP are used to connect to the AD KDC services on the initial machine account creation.
419+
420+
>[!NOTE]
421+
>The KDC IP and AD Server Name fields in the Active Directory object cannot be cleared out until the Active Directory object is deleted. It can only be changed to a valid non-empty value.
422+
423+
The Azure NetApp Files service leverages the existing domain information to fill out the rest of the realm configuration. For example:
419424

420425
```
421426
Kerberos Realm: CONTOSO.COM

0 commit comments

Comments
 (0)