You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: concepts/tutorial-lifecycle-workflows-set-employeeleavedatetime.md
+4-6Lines changed: 4 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.reviewer: Alexander.Filipin
7
7
ms.localizationpriority: medium
8
8
ms.subservice: entra-id-governance
9
9
ms.topic: how-to
10
-
ms.date: 01/03/2024
10
+
ms.date: 01/13/2025
11
11
#Customer intent: As a developer integrating with Microsoft Graph, I want programmatically configure the employeeLeaveDateTime property for a user, so that I can trigger scheduled "leaver" workflows using Lifecycle Workflows.
12
12
---
13
13
@@ -25,16 +25,14 @@ Choose the permission or permissions marked as least privileged for this API. Us
25
25
|Delegated (personal Microsoft account)|Not supported.|Not supported.|
26
26
|Application|User.Read.All and User-LifeCycleInfo.ReadWrite.All|Not available.|
27
27
28
-
For delegated scenarios, the admin must also have the Global Administrator [Microsoft Entra role](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#available-roles).
28
+
For delegated scenarios, the admin must also have the Global Administrator [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json).
29
29
30
30
> [!NOTE]
31
31
> This information is best updated via automation by using either an HR provisioning, Microsoft Entra Connect, or custom sync solution. For more information about this process, see [How to synchronize attributes for lifecycle workflows](/entra/id-governance/how-to-lifecycle-workflow-sync-attributes).
32
32
33
33
## Set the employeeLeaveDateTime property
34
34
35
-
### Request
36
-
37
-
The following example configures September 30, 2022 at 23:59 as the date and time when the user will leave the organization.
35
+
The following example configures September 30, 2022 at 23:59 as the date and time when the user will leave the organization. The request returns `204 No Content` response code.
0 commit comments