Modify Active Directory connections for Azure NetApp Files
Once you've created an Active Directory connection in Azure NetApp Files, you can modify it. When you're modifying an Active Directory connection, not all configurations are modifiable.
For more information, see Understand guidelines for Active Directory Domain Services site design and planning for Azure NetApp Files.
Modify Active Directory connections
Select Active Directory connections. Then, select Edit to edit an existing AD connection.
In the Edit Active Directory window that appears, modify Active Directory connection configurations as needed. For an explanation of what fields you can modify, see Options for Active Directory connections.
Options for Active Directory connections
| Field Name | What it is | Is it modifiable? | Considerations & Impacts | Effect |
|---|---|---|---|---|
| Primary DNS | Primary DNS server IP addresses for the Active Directory domain. | Yes | None* | New DNS IP is used for DNS resolution. |
| Secondary DNS | Secondary DNS server IP addresses for the Active Directory domain. | Yes | None* | New DNS IP will be used for DNS resolution in case primary DNS fails. |
| AD DNS Domain Name | The domain name of your Active Directory Domain Services that you want to join. | No | None | N/A |
| AD Site Name | The site to which the domain controller discovery is limited. | Yes | This should match the site name in Active Directory Sites and Services. See footnote.* | Domain discovery is limited to the new site name. If not specified, "Default-First-Site-Name" is used. |
| SMB Server (Computer Account) Prefix | Naming prefix for the computer account in Active Directory that Azure NetApp Files will use for the creation of new accounts. See footnote.* | Yes | Existing volumes need to be mounted again as the mount is changed for SMB shares and NFS Kerberos volumes.* | Renaming the SMB server prefix after you create the Active Directory connection is disruptive. You'll need to remount existing SMB shares and NFS Kerberos volumes after renaming the SMB server prefix as the mount path will change. |
| Organizational Unit Path | The LDAP path for the organizational unit (OU) where SMB server computer accounts will be created. OU=second level, OU=first level |
No | If you're using Azure NetApp Files with Microsoft Entra Domain Services, the organizational path is OU=AADDC Computers when you configure Active Directory for your NetApp Account. |
Computer accounts will be placed under the OU specified. If not specified, the default of OU=Computers is used by default. |
| AES Encryption | To take advantage of the strongest security with Kerberos-based communication, you can enable AES-256 and AES-128 encryption on the SMB server. | Yes | If you enable AES encryption, the user credentials used to join Active Directory must have the highest corresponding account option enabled, matching the capabilities enabled for your Active Directory. For example, if your Active Directory has only AES-128 enabled, you must enable the AES-128 account option for the user credentials. If your Active Directory has the AES-256 capability, you must enable the AES-256 account option (which also supports AES-128). If your Active Directory doesn't have any Kerberos encryption capability, Azure NetApp Files uses DES by default.* | Enable AES encryption for Active Directory Authentication |
| LDAP Signing | This functionality enables secure LDAP lookups between the Azure NetApp Files service and the user-specified Active Directory Domain Services domain controller. | Yes | LDAP signing to Require Signing in group policy* | This option provides ways to increase the security for communication between LDAP clients and Active Directory domain controllers. |
| Allow local NFS users with LDAP | If enabled, this option manages access for local users and LDAP users. | Yes | This option allows access to local users. It's not recommended and, if enabled, should only be used for a limited time and later disabled. | If enabled, this option allows access to local users and LDAP users. If your configuration requires access for only LDAP users, you must disable this option. |
| LDAP over TLS | If enabled, LDAP over TLS is configured to support secure LDAP communication to active directory. | Yes | None | If you've enabled LDAP over TLS and if the server root CA certificate is already present in the database, then the CA certificate secures LDAP traffic. If a new certificate is passed in, that certificate will be installed. |
| Server root CA Certificate | When LDAP over SSL/TLS is enabled, the LDAP client is required to have base64-encoded Active Directory Certificate Service's self-signed root CA certificate. | Yes | None* | LDAP traffic secured with new certificate only if LDAP over TLS is enabled |
| LDAP search scope | See Create and manage Active Directory connections | Yes | - | - |
| Preferred server for LDAP client | You can designate up to two AD servers for the LDAP to attempt connection with first. See Understand guidelines for Active Directory Domain Services site design and planning | Yes | None* | Potentially impede a timeout when the LDAP client seeks to connect to the AD server. |
| Encrypted SMB connections to Domain Controller | This option specifies whether encryption should be used for communication between SMB server and domain controller. See Create Active Directory connections for more details on using this feature. | Yes | SMB, Kerberos, and LDAP enabled volume creation can't be used if the domain controller doesn't support SMB3 | Only use SMB3 for encrypted domain controller connections. |
| Backup policy users | You can include more accounts that require elevated privileges to the computer account created for use with Azure NetApp Files. For more information, see Create and manage Active Directory connections.F | Yes | None* | The specified accounts will be allowed to change the NTFS permissions at the file or folder level. |
| Administrators | Specify users or groups to grant administrator privileges on the volume to | Yes | None | User account receives administrator privileges |
| Username | Username of the Active Directory domain administrator | Yes | None* | Credential change to contact DC |
| Password | Password of the Active Directory domain administrator | Yes | None* Password can't exceed 64 characters. |
Credential change to contact DC |
| Kerberos Realm: AD Server Name | The name of the Active Directory machine. This option is only used when creating a Kerberos volume. | Yes | None* | |
| Kerberos Realm: KDC IP | Specifies the IP address of the Kerberos Distribution Center (KDC) server. KDC in Azure NetApp Files is an Active Directory server | Yes | None | A new KDC IP address will be used |
| Region | The region where the Active Directory credentials are associated | No | None | N/A |
| User DN | User domain name, which overrides the base DN for user lookups Nested userDN can be specified in OU=subdirectory, OU=directory, DC=domain, DC=com format. |
Yes | None* | User search scope gets limited to User DN instead of base DN. |
| Group DN | Group domain name. groupDN overrides the base DN for group lookups. Nested groupDN can be specified in OU=subdirectory, OU=directory, DC=domain, DC=com format. |
Yes | None* | Group search scope gets limited to Group DN instead of base DN. |
| Group Membership Filter | The custom LDAP search filter to be used when looking up group membership from LDAP server. groupMembershipFilter can be specified with the (gidNumber=*) format. |
Yes | None* | Group membership filter will be used while querying group membership of a user from LDAP server. |
| Security Privilege Users | You can grant security privilege (SeSecurityPrivilege) to users that require elevated privilege to access the Azure NetApp Files volumes. The specified user accounts will be allowed to perform certain actions on Azure NetApp Files SMB shares that require security privilege not assigned by default to domain users. See Create and manage Active Directory connections for more information. |
Yes | Using this feature is optional and supported only for SQL Server. The domain account used for installing SQL Server must already exist before you add it to the Security privilege users field. When you add the SQL Server installer's account to Security privilege users, the Azure NetApp Files service might validate the account by contacting the domain controller. The command might fail if it can't contact the domain controller. See SQL Server installation fails if the Setup account doesn't have certain user rights for more information about SeSecurityPrivilege and SQL Server.* |
Allows non-administrator accounts to use SQL severs on top of ANF volumes. |
*There is no impact on a modified entry only if the modifications are entered correctly. If you enter data incorrectly, users and applications will lose access.