[Launched] Generally Available: Azure NetApp Files support for Active Directory connection per NetApp account
Summary of Azure NetApp Files Support for Active Directory Connection
Azure NetApp Files now supports creating one Active Directory (AD) connection per NetApp account. This feature allows for more flexibility in managing AD connections, which are crucial for various Azure NetApp Files functionalities, such as creating SMB, NFSv4.1 Kerberos, or dual-protocol volumes.
Key Points
- Default Configuration: Previously, Azure NetApp Files supported only one AD connection per subscription and account within the same region. This limitation has been adjusted to allow one AD connection per NetApp account[1].
- AD Integration Requirements: For effective deployment of Azure NetApp Files volumes, it is essential to integrate with Active Directory Domain Services (AD DS) or Microsoft Entra Domain Services. Incorrect integration can lead to client access issues for SMB, dual-protocol, or Kerberos NFSv4.1 volumes[2].
- Supported Authentication Scenarios: Azure NetApp Files supports AD DS authentication for Windows machines and Microsoft Entra Domain Services authentication for cloud-based Windows VMs. Additionally, AD Kerberos authentication is supported for Linux clients over SMB[2].
- LDAP Support: Azure NetApp Files uses Active Directory as the LDAP server, supporting both AD DS and Microsoft Entra Domain Services. This support includes LDAP client configurations for connecting to AD DS or Microsoft Entra Domain Services LDAP servers[3][5].
Implications
This enhanced support allows organizations to manage multiple AD connections more effectively, improving the flexibility and scalability of Azure NetApp Files within their infrastructure. It also aligns with Azure's broader strategy to provide robust and integrated identity services for cloud-based applications and services.
อ้างอิงค์ : https://azure.microsoft.com/updates?id=492144
ความคิดเห็น
แสดงความคิดเห็น