updates

Author: OWinfreyATL

articles/active-directory/governance/how-to-lifecycle-workflow-sync-attributes.md

@@ -23,10 +23,10 @@ The following table shows the scheduling (trigger) relevant attributes and the m
 |Attribute|Type|Supported in HR Inbound Provisioning|Support in Azure AD Connect Cloud Sync|Support in Azure AD Connect Sync| 
 |-----|-----|-----|-----|-----|
 |employeeHireDate|DateTimeOffset|Yes|Yes|Yes|
-|employeeLeaveDateTime|DateTimeOffset|Not currently(manually setting supported)|Not currently(manually setting supported)|Not currently(manually setting supported)|
+|employeeLeaveDateTime|DateTimeOffset|Yes|Not currently(manually setting supported)|Not currently(manually setting supported)|
 
 > [!NOTE]
-> Currently, automatic synchronization of the employeeLeaveDateTime attribute for HR Inbound scenarios is not available. To take advantaged of leaver scenarios, you can set the employeeLeaveDateTime manually. Manually setting the attribute can be done in the portal or with Graph. For more information see [User profile in Azure](../fundamentals/active-directory-users-profile-azure-portal.md) and [Update user](/graph/api/user-update?view=graph-rest-beta&tabs=http).
+> To take advantaged of leaver scenarios, you can set the employeeLeaveDateTime manually. For more information see [Set employeeLeaveDateTime](set-employee-leave-date-time.md)
 
 This document explains how to set up synchronization from on-premises Azure AD Connect cloud sync and Azure AD Connect for the required attributes.
 

articles/active-directory/governance/set-employee-leave-date-time.md

@@ -10,19 +10,27 @@ ms.custom: template-how-to
 ---
 
 # Set employeeLeaveDateTime
+
+This article describes how to manually set the employeeLeaveDateTime attribute for a user. This attribute can be used to be set as a trigger for leaver workflows created using Lifecycle Workflows.
+
 ## Required permission and roles
+
+To set the employeeLeaveDateTime attribute, you must make sure the correct delegated roles and application permissions are set. These are as following:
+
 ### Delegated
-In delegated scenarios the signed-in user needs the Global Administrator role to update the employeeLeaveDateTime attribute. In addition one of the following delegated permissions is required:
+
+In delegated scenarios, the signed-in user needs the Global Administrator role to update the employeeLeaveDateTime attribute. One of the following delegated permissions are also required:
 - User-LifeCycleInfo.ReadWrite.All
 - Directory.AccessAsUser.All
 
 ### Application
+
 Updating the employeeLeaveDateTime requires the User-LifeCycleInfo.ReadWrite.All application permission.
 
 >[!NOTE]
-> The User-LifeCycleInfo.ReadWrite.All permissions is currently hidden and cannot be configured in Graph Explorer or the API permssion blade of app registrations.
+> The User-LifeCycleInfo.ReadWrite.All permissions is currently hidden and cannot be configured in Graph Explorer or the API permission blade of app registrations.
 
-# Set employeeLeaveDateTime via PowerShell
+## Set employeeLeaveDateTime via PowerShell
 To set the employeeLeaveDateTime for a user using PowerShell enter the following information:
 
  ```powershell