revised alert 120

Author: Justinha

articles/active-directory-domain-services/troubleshoot-alerts.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: domain-services
 ms.workload: identity
 ms.topic: troubleshooting
-ms.date: 01/29/2023
+ms.date: 02/28/2023
 ms.author: justinha
 
 ---
@@ -245,14 +245,14 @@ To check for applied policies on the Azure AD DS components and update them, com
 
 ### Resolution
 
-If a custom attribute's LDAPName conflicts with an existing AD built-in attribute schema attribute, it cannot be onboarded and will result in an error. Please reach out to Contact Microsoft Support if your scenario is blocked. For more information, see Onboarding Custom Attributes.
-Review the Azure AD DS Health alert to check which indicates the Azure AD extension properties that have failed to onboard successfully. Navigate to the Custom Attributes page to find the expected Azure AD DS LDAPName of the extension. Ensure that the LDAPName does not conflict with another AD attribute schema attribute or is one of the whitelisted allowed built-in AD attributes. Then retry onboarding the custom attribute by completing the following steps in the Custom Attributes page:
+If a custom attribute's LDAPName conflicts with an existing AD built-in schema attribute, it can't be onboarded and results in an error. Contact Microsoft Support if your scenario is blocked. For more information, see [Onboarding Custom Attributes](https://aka.ms/aadds-customattr).
+Review the [Azure AD DS Health](check-health.md) alert to check which Azure AD extension properties failed to onboard successfully. Navigate to the Custom Attributes page to find the expected Azure AD DS LDAPName of the extension. Ensure that the LDAPName does not conflict with another AD schema attribute or is one of the allowed built-in AD attributes. Then retry onboarding the custom attribute by completing the following steps in the Custom Attributes page:
 
-1. Select the attributes that were unsuccessful, then click Remove and Save.
+1. Select the attributes that were unsuccessful, then click **Remove** and **Save**.
 1. Wait for the health alert to be removed, or verify that the corresponding attributes have been removed from the "AADDSCustomAttributes" OU from a domain-joined VM.
 1. Select **Add** and choose the desired attributes again, then click **Save**.
 
-Upon successful onboarding, Azure AD DS will backfill all existing synced users and groups with the onboarded custom attribute values. You should gradually see the custom attribute values being populated in these objects, depending on the size of the tenant. To determine if the backfilling process has completed, go to Azure AD DS Health and verify the Synchronization with Azure AD monitor indicates an updated timestamp in the last hour since onboarding.
+Upon successful onboarding, Azure AD DS will backfill all existing synced users and groups with the onboarded custom attribute values. You should gradually see the custom attribute values being populated in these objects, depending on the size of the tenant. To determine if the backfilling process has completed, go to Azure AD DS Health and verify the **Synchronization with Azure AD** monitor indicates an updated timestamp in the last hour since onboarding.
 
 ## AADDS500: Synchronization has not completed in a while