refresh updates

Author: suzuber

articles/azure-vmware/configure-external-identity-source-nsx-t.md

@@ -3,7 +3,7 @@ title: Set an external identity source for VMware NSX
 description: Learn how to use Azure VMware Solution to set an external identity source for VMware NSX.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/29/2024
+ms.date: 3/26/2026
 ms.custom:
   - engagement-fy23
   - sfi-image-nochange
@@ -14,20 +14,20 @@ ms.custom:
 
 In this article, learn how to set up an external identity source for VMware NSX in an instance of Azure VMware Solution.
 
-You can set up NSX to use an external Lightweight Directory Access Protocol (LDAP) directory service to authenticate users. A user can sign in by using their Windows Server Active Directory account credentials or credentials from a third-party LDAP server. Then, the account can be assigned an NSX role, like in an on-premises environment, to provide role-based access for NSX users.
+You can set up NSX to use an external Lightweight Directory Access Protocol (LDAP) directory service to authenticate users. A user can sign in by using their Windows Server Active Directory account credentials or credentials from a non-Microsoft LDAP server. Then, the account can be assigned an NSX role, like in an on-premises environment, to provide role-based access for NSX users.
 
 :::image type="content" source="media/nsxt/azure-vmware-solution-to-ldap-server.png" alt-text="Screenshot that shows NSX connectivity to the LDAP Windows Server Active Directory server." lightbox="media/nsxt/azure-vmware-solution-to-ldap-server.png":::
 
 ## Prerequisites
 
 - A working connection from your Windows Server Active Directory network to your Azure VMware Solution private cloud.
 - A network path from your Windows Server Active Directory server to the management network of the instance of Azure VMware Solution in which NSX is deployed.
-- A Windows Server Active Directory domain controller that has a valid certificate. The certificate can be issued by a [Windows Server Active Directory Certificate Services Certificate Authority (CA)](https://social.technet.microsoft.com/wiki/contents/articles/2980.ldap-over-ssl-ldaps-certificate.aspx) or by a [third-party CA](/troubleshoot/windows-server/identity/enable-ldap-over-ssl-3rd-certification-authority).
+- A Windows Server Active Directory domain controller that has a valid certificate. The certificate is issued by a [Windows Server Active Directory Certificate Services Certificate Authority (CA)](https://social.technet.microsoft.com/wiki/contents/articles/2980.ldap-over-ssl-ldaps-certificate.aspx) or by a [third-party CA](/troubleshoot/windows-server/identity/enable-ldap-over-ssl-3rd-certification-authority).
 
    We recommend that you use two domain controllers that are located in the same Azure region as the Azure VMware Solution software-defined datacenter.
 
    > [!NOTE]
-   > Self-signed certificates are not recommended for production environments.
+   > Self-signed certificates aren't recommended for production environments.
 
 - An account that has Administrator permissions.
 - Azure VMware Solution DNS zones and DNS servers that are correctly configured. For more information, see [Configure NSX DNS for resolution to your Windows Server Active Directory domain and set up DNS forwarder](configure-dns-azure-vmware-solution.md).
@@ -41,7 +41,7 @@ You can set up NSX to use an external Lightweight Directory Access Protocol (LDA
 
    :::image type="content" source="media/nsxt/configure-nsx-t-pic-1.png" alt-text="Screenshot that shows NSX Manager with the options highlighted.":::
 
-1. Enter values for **Name**, **Domain Name (FQDN)**, **Type**, and **Base DN**.  You can add a description (optional).
+1. Enter values for **Name**, **Domain Name (FQDN)**, **Type**, and **Base DN**. You can add a description (optional).
 
    The base DN is the container where your user accounts are kept. The base DN is the starting point that an LDAP server uses when it searches for users in an authentication request. For example, **CN=users,dc=azfta,dc=com**.
 
@@ -61,7 +61,7 @@ You can set up NSX to use an external Lightweight Directory Access Protocol (LDA
     | **Port**     | Leave the default secure LDAP port. |
     | **Enabled**              | Leave as **Yes**. |
     | **Use Start TLS**        | Required only if you use standard (unsecured) LDAP. |
-    | **Bind Identity**        | Use your account that has read permissions to directory. For example, `<[email protected]>`. |
+    | **Bind Identity**        | Use your account that read permissions to directory. For example, `<[email protected]>`. |
     | **Password**            | Enter the password for the LDAP server. This password is the one that you use with the example `<[email protected]>` account. |
     | **Certificate**          | Leave empty (see step 6). |