Skip to content

Commit 5f07580

Browse files
committed
multi-ad ga updates
1 parent 91ef4dc commit 5f07580

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
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
@@ -22,7 +22,7 @@ Several features of Azure NetApp Files require that you have an Active Directory
2222
2323
* An Azure NetApp Files account must be created in the region where the Azure NetApp Files volumes are to be deployed.
2424

25-
* Azure NetApp Files, by default, allows one Active Directory (AD) connection per subscription. You can modify the default to [create one Active Directory connection per NetApp account](#multi-ad).
25+
* Azure NetApp Files, by default, allows one Active Directory (AD) connection per subscription and account. You can modify the default to [create one Active Directory connection per NetApp account](#multi-ad).
2626

2727
* The Azure NetApp Files AD connection admin account must have the following properties:
2828
* It must be an AD DS domain user account in the same domain where the Azure NetApp Files computer accounts are created.
@@ -279,7 +279,7 @@ For more information about the relationship between NetApp accounts and subscrip
279279
280280
## <a name="multi-ad"></a> Create one Active Directory connection per NetApp account
281281
282-
The current default behavior of Azure NetApp Files supports one AD connection per subscription and region. By enabling this feature, you modify behavior so that each NetApp account within an Azure subscription can have its own AD connection.
282+
The current default behavior of Azure NetApp Files supports one AD connection per subscription and region. By enabling this feature, you modify behavior so that each NetApp account within an Azure subscription can have its own AD connection. When this feature is enabled, _newly created_ NetApp accounts maintain their own AD connection.
283283
284284
Once configured, the AD connection of the NetApp account is used when you create an [SMB volume](azure-netapp-files-create-volumes-smb.md), a [NFSv4.1 Kerberos volume](configure-kerberos-encryption.md), or a [dual-protocol volume](create-volumes-dual-protocol.md). That means Azure NetApp Files supports more than one AD connection per Azure subscription when multiple NetApp accounts are used.
285285

articles/azure-netapp-files/whats-new.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,9 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
1616

1717
* [Support for one Active Directory connection per NetApp account](create-active-directory-connections.md#multi-ad) is now generally available (GA)
1818

19-
The Azure NetApp Files support for one Active Directory (AD) connection per NetApp account feature now allows each NetApp account to connect to its own AD Forest and Domain, providing the ability to manage more than one AD connections within a single region under a subscription. This feature is now generally available.
19+
The Azure NetApp Files support for Active Directory connection per NetApp account feature is now generally available. The feature allows each NetApp account to connect to its own Active Directory Forest and Domain, providing the ability to manage more than one Active Directory connections within a single region under a subscription. This enhancement enables distinct Active Directory connections for each NetApp account, facilitating operational isolation and specialized hosting scenarios. Active Directory connections can be configured multiple times for multiple NetApp accounts to make use of it. With the creation of SMB volumes in Azure NetApp Files now tied to these Active Directory connections in the NetApp account, the management of Active Directory environments becomes more scalable, streamlined, and efficient.
20+
21+
You're still required [to register for this feature](create-active-directory-connections.md#register-the-feature).
2022

2123
## April 2025
2224

0 commit comments

Comments
 (0)