update doc-1

Author: v-missam

articles/active-directory/saas-apps/atea-provisioning-tutorial.md

@@ -99,17 +99,16 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 11. Review the user attributes that are synchronized from Azure AD to Atea in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Atea for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Atea API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
 
-      |Attribute|Type|Supported for filtering|
-      |---|---|---|
-      |userName|String|✓|
-      |active|Boolean|
-      |emails[type eq "work"].value|String|
-      |name.givenName|String|
-      |name.familyName|String|
-      |name.formatted|String|
-      |phoneNumbers[type eq "mobile"].value|String|
-      |locale|String|
-      |nickName|String|
+      Attribute|Type|Supported for filtering|Required by LawVu|
+      |---|---|---|---|
+      |userName|String|✓|✓|
+      |active|Boolean||✓|
+      |emails[type eq "work"].value|String||✓|
+      |name.givenName|String|||
+      |name.familyName|String|||
+      |name.formatted|String||✓|
+      |phoneNumbers[type eq "mobile"].value|String|||
+      |locale|String|||
 
 12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
 
@@ -134,6 +133,11 @@ Once you've configured provisioning, use the following resources to monitor your
 * Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it's to completion.
 * If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).  
 
+## Change Log
+* 10/25/2022 - Drop core user attribute **nickName**. 
+* 10/25/2022 - Changed the mapping of core user attribute **name.formatted** to **Join(" ", [givenName], [surname]) -> name.formatted**.
+* 10/25/2022 - Domain name of all OAuth config urls of Atea app changed to Atea owned domain.
+
 ## Additional resources
 
 * [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)

articles/active-directory/saas-apps/gong-provisioning-tutorial.md

@@ -109,9 +109,10 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 	![Provisioning tab automatic](common/provisioning-automatic.png)
 
-1. In the **Admin Credentials** section, click on Authorize, make sure that you enter your Taskize Connect account's Admin credentials. Click **Test Connection** to ensure Azure AD can connect to Taskize Connect. If the connection fails, ensure your Taskize Connect account has Admin permissions and try again.
+1. In the **Admin Credentials** section, click on Authorize, make sure that you enter your Gong account's Admin credentials. Click **Test Connection** to ensure Azure AD can connect to Gong. If the connection fails, ensure your Gong account has Admin permissions and try again.
 
    ![Token](media/gong-provisioning-tutorial/gong-authorize.png)
+   
 1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
 
 	![Notification Email](common/provisioning-notification-email.png)