Skip to content

Commit 59b3e95

Browse files
Merge pull request #309127 from MicrosoftDocs/main
Auto Publish – main to live - 2025-12-07 12:00 UTC
2 parents fb4865e + 89e9290 commit 59b3e95

File tree

3 files changed

+8
-5
lines changed

3 files changed

+8
-5
lines changed

articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.custom:
88
- linux-related-content
99
- build-2025
1010
ms.topic: concept-article
11-
ms.date: 10/15/2025
11+
ms.date: 12/07/2025
1212
ms.author: anfdocs
1313
# Customer intent: As a cloud architect, I want to implement Azure NetApp Files to migrate and run mission-critical applications, so that I can ensure high performance, scalability, and security for diverse workloads in the cloud.
1414
---
@@ -148,6 +148,7 @@ This section provides references to SAP on Azure solutions.
148148
* [Manual Recovery Guide for SAP DB2 on Azure VMs from Azure NetApp Files snapshot with AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-db2-on-azure-vms-from-azure-netapp/ba-p/3865379)
149149
* [SAP ASE 16.0 on Azure NetApp Files for SAP Workloads on SLES15](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-ase-16-0-on-azure-netapp-files-for-sap-workloads-on-sles15/ba-p/3729496)
150150
* [SAP Netweaver 7.5 with MaxDB 7.9 on Azure using Azure NetApp Files](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-netweaver-7-5-with-maxdb-7-9-on-azure-using-azure-netapp/ba-p/3905041)
151+
* [Running SAP Applications on the Microsoft Platform](https://techcommunity.microsoft.com/blog/sapapplications/designing-migrating-and-managing-a-151-node-sap-bw-scale-out-landscape-on-micros/3715003)
151152

152153
### SAP IQ-NLS
153154

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 10/01/2025
8+
ms.date: 12/07/2025
99
ms.author: anfdocs
1010
ms.custom:
1111
- devx-track-azurepowershell
@@ -64,6 +64,8 @@ Several features of Azure NetApp Files require that you have an Active Directory
6464
6565
If you set both AES-128 and AES-256 Kerberos encryption on the admin account of the AD connection, the Windows client negotiates the highest level of encryption supported by your AD DS. For example, if both AES-128 and AES-256 are supported, and the client supports AES-256, then AES-256 will be used.
6666
67+
* If you change the Kerberos Distribution Center (KDC) IP address or AD Server Name, you must wait for the Kerberos ticket lifetime to mount the volume on the same NFS Linux client. The Kerberos ticket lifetime can be configured on both the client and the KDC. By default, Microsoft Active Directory sets the Kerberos ticket lifetime to 600 minutes (10 hours).
For more information, see [Maximum lifetime for service ticket](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/maximum-lifetime-for-service-ticket).
68+
6769
* If you have a requirement to enable and disable certain Kerberos encryption types for Active Directory computer accounts for domain-joined Windows hosts used with Azure NetApp Files, you must use the Group Policy `Network Security: Configure Encryption types allowed for Kerberos`.
6870
6971
Do not set the registry key `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\SupportedEncryptionTypes`. Doing this will break Kerberos authentication with Azure NetApp Files for the Windows host where this registry key was manually set.

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article shows you how to modify Active Directory connections f
44
author: b-hchen
55
ms.service: azure-netapp-files
66
ms.topic: how-to
7-
ms.date: 05/06/2025
7+
ms.date: 12/03/2025
88
ms.author: anfdocs
99
# Customer intent: As an IT administrator managing Active Directory connections, I want to modify existing Active Directory configurations in Azure NetApp Files, so that I can ensure secure and efficient integration between Active Directory and my file storage environment.
1010
---
@@ -43,8 +43,8 @@ For more information, see [Understand guidelines for Active Directory Domain Ser
4343
| Administrators | Specify users or groups to grant administrator privileges on the volume to | Yes | None | User account receives administrator privileges |
4444
| Username | Username of the Active Directory domain administrator | Yes | None* | Credential change to contact DC |
4545
| Password | Password of the Active Directory domain administrator | Yes | None* <br></br> Password can't exceed 64 characters. | Credential change to contact DC |
46-
| Kerberos Realm: AD Server Name | The name of the Active Directory machine. This option is only used when creating a Kerberos volume. | Yes | None* | |
47-
| 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. You can only modify a KDC IP by editing the AD setting. | Yes | None | A new KDC IP address will be used |
46+
| Kerberos Realm: AD Server Name | The name of the Active Directory machine. This option is only used when creating a Kerberos volume. | Yes | None* | |
47+
| 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. You can only modify a KDC IP by editing the AD setting. | Yes | None | A new KDC IP address will be used |
4848
| Region | The region where the Active Directory credentials are associated | No | None | N/A |
4949
| 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. |
5050
| 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. |

0 commit comments

Comments
 (0)