Skip to content

Commit a669205

Browse files
authored
Merge pull request #26080 from microsoftgraph/freshness-employeeLeaveDateTime
[Content freshness] Configure the employeeLeaveDateTime property for a user
2 parents 9256bfd + b95f282 commit a669205

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

concepts/tutorial-lifecycle-workflows-set-employeeleavedatetime.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: Alexander.Filipin
77
ms.localizationpriority: medium
88
ms.subservice: entra-id-governance
99
ms.topic: how-to
10-
ms.date: 01/03/2024
10+
ms.date: 01/13/2025
1111
#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.
1212
---
1313

@@ -25,16 +25,14 @@ Choose the permission or permissions marked as least privileged for this API. Us
2525
|Delegated (personal Microsoft account)|Not supported.|Not supported.|
2626
|Application|User.Read.All and User-LifeCycleInfo.ReadWrite.All|Not available.|
2727

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).
2929

3030
> [!NOTE]
3131
> 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).
3232
3333
## Set the employeeLeaveDateTime property
3434

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.
3836

3937
# [HTTP](#tab/http)
4038

@@ -78,4 +76,4 @@ PATCH https://graph.microsoft.com/v1.0/users/aaaaaaaa-bbbb-cccc-1111-22222222222
7876
## Related content
7977

8078
- [Lifecycle Workflows API overview](/graph/api/resources/identitygovernance-lifecycleworkflows-overview)
81-
- [How to synchronize attributes for Lifecycle workflows](/azure/active-directory/governance/how-to-lifecycle-workflow-sync-attributes)
79+
- [Tutorial: How to synchronize attributes for Lifecycle workflows](/entra/id-governance/how-to-lifecycle-workflow-sync-attributes)

0 commit comments

Comments
 (0)