Skip to content

Commit d59e58f

Browse files
AnnaMHuffAnnaMHuff
authored
Merge pull request #239053 from OWinfreyATL/owinfreyATL-EntitlementManagement-LCW-Tasks
LCW GA feature PR
2 parents b9d9a74 + b549ff3 commit d59e58f

12 files changed

+226
-22
lines changed

‎articles/active-directory/governance/check-workflow-execution-scope.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,8 @@ ms.reviewer: krbain
1414
ms.collection: M365-identity-device-management
1515
---
1616

17-
# Check execution user scope of a workflow
17+
# Check execution user scope of a workflow
18+
1819

1920
Workflow scheduling will automatically process the workflow for users meeting the workflows execution conditions. This article walks you through the steps to check the users who fall into the execution scope of a workflow. For more information about execution conditions, see: [workflow basics](../governance/understanding-lifecycle-workflows.md#workflow-basics).
2021

‎articles/active-directory/governance/lifecycle-workflow-extensibility.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.custom: template-concept
1313
---
1414

1515

16-
# Lifecycle Workflows Custom Task Extension (Preview)
16+
# Lifecycle Workflows custom task extension
1717

1818

1919
Lifecycle Workflows allow you to create workflows that can be triggered based on joiner, mover, or leaver scenarios. While Lifecycle Workflows provide several built-in tasks to automate common scenarios throughout the lifecycle of users, eventually you may reach the limits of these built-in tasks. With the extensibility feature, you're able to utilize the concept of custom task extensions to call-out to external systems as part of a workflow. For example, when a user joins your organization you can have a workflow with a custom task extension that assigns a Teams number, or have a separate workflow that grants access to an email account for a manager when a user leaves. With the extensibility feature, Lifecycle Workflows currently support creating custom tasks extensions to call-out to [Azure Logic Apps](../../logic-apps/logic-apps-overview.md).
@@ -67,10 +67,10 @@ The response can be authorized in one of the following ways:
6767
The high-level steps for the Azure Logic Apps integration are as follows:
6868

6969
> [!NOTE]
70-
> Creating a custom task extension and logic app through the Azure portal will automate most of these steps. For a guide on creating a custom task extension this way, see: [Trigger Logic Apps based on custom task extensions (Preview)](trigger-custom-task.md).
70+
> Creating a custom task extension and logic app through the Azure portal will automate most of these steps. For a guide on creating a custom task extension this way, see: [Trigger Logic Apps based on custom task extensions](trigger-custom-task.md).
7171
7272
- **Create a consumption-based Azure Logic App**: A consumption-based Azure Logic App that is used to be called to from the custom task extension.
73-
- **Configure the Azure Logic App so its compatible with Lifecycle workflows**: Configuring the consumption-based Azure Logic App so that it can be used with the custom task extension. For more information, see: [Configure a Logic App for Lifecycle Workflow use (Preview)](configure-logic-app-lifecycle-workflows.md)
73+
- **Configure the Azure Logic App so its compatible with Lifecycle workflows**: Configuring the consumption-based Azure Logic App so that it can be used with the custom task extension. For more information, see: [Configure a Logic App for Lifecycle Workflow use](configure-logic-app-lifecycle-workflows.md)
7474
- **Build your custom business logic within your Azure Logic App**: Set up your business logic within the Azure Logic App using Logic App designer.
7575
- **Create a lifecycle workflow customTaskExtension which holds necessary information about the Azure Logic App**: Creating a custom task extension that references the configured Azure Logic App.
7676
- **Update or create a Lifecycle workflow with the “Run a custom task extension” task, referencing your created customTaskExtension**: Adding the newly created custom task extension to a new workflow, or updating the information to an existing workflow.

‎articles/active-directory/governance/lifecycle-workflow-tasks.md‎

Lines changed: 183 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -253,6 +253,96 @@ For Microsoft Graph, the parameters for the **Generate Temporary Access Pass and
253253
254254
```
255255

256+
### Send email to notify manager of user move
257+
258+
When a user moves within your organization Lifecycle Workflows allow you to send an email to the users manager notifying them of the move. You're also able to customize the email that is sent to the user's manager.
259+
260+
:::image type="content" source="media/lifecycle-workflow-task/notify-user-move-task.png" alt-text="Screenshot of the notify manager of user move task.":::
261+
262+
The Azure AD prerequisite to run the **Send email to notify manager of user move** task are:
263+
264+
- A populated manager attribute for the user.
265+
- A populated manager's mail attribute for the user.
266+
267+
For Microsoft Graph the parameters for the **Send email to notify manager of user move** task are as follows:
268+
269+
|Parameter |Definition |
270+
|---------|---------|
271+
|category | Mover |
272+
|displayName | Send email to notify manager of user move (Customizable by user) |
273+
|description | Send email to notify user’s manager of user move (Customizable by user) |
274+
|taskDefinitionId | aab41899-9972-422a-9d97-f626014578b7 |
275+
276+
```Example for usage within the workflow
277+
{
278+
"category": "mover",
279+
"continueOnError": true,
280+
"displayName": "Send email to notify manager of user move",
281+
"description": "Send email to notify user’s manager of user move",
282+
"isEnabled": true,
283+
"taskDefinitionId": "aab41899-9972-422a-9d97-f626014578b7",
284+
"arguments": [
285+
{
286+
"name": "cc",
287+
"value": "b47471b9-af8f-4a5a-bfa2-b78e82398f6e, a7a23ce0-909b-40b9-82cf-95d31f0aaca2"
288+
},
289+
{
290+
"name": "customSubject",
291+
"value": "Reminder that {{userDisplayName}} has moved."
292+
},
293+
{
294+
"name": "customBody",
295+
"value": "Hello {{managerDisplayName}}. \nThis is a reminder that {{userDisplayName}} has moved roles in the organization."
296+
},
297+
{
298+
"name": "locale",
299+
"value": "en-us"
300+
},
301+
]
302+
}
303+
304+
```
305+
306+
### Request user access package assignment
307+
308+
Allows you to request an access package assignment for users. Access packages are bundles of resources, with specific access, that a user would need to accomplish tasks. For more information on access packages, see [What are access packages and what resources can I manage with them?](entitlement-management-overview.md#what-are-access-packages-and-what-resources-can-i-manage-with-them).
309+
310+
You're able to customize the task name and task description for this task. You must also select an access package that is provided to the user, and the access package policy.
311+
:::image type="content" source="media/lifecycle-workflow-task/request-user-access-package-assignment-task.png" alt-text="Screenshot of the request user access package assignment task.":::
312+
313+
For Microsoft Graph, the parameters for the **Request user access package assignment** task are as follows:
314+
315+
|Parameter |Definition |
316+
|---------|---------|
317+
|category | joiner |
318+
|displayName | Request user access package assignment (Customizable by user) |
319+
|description | Request user assignment to selected access package (Customizable by user) |
320+
|taskDefinitionId | c1ec1e76-f374-4375-aaa6-0bb6bd4c60be |
321+
|arguments | Argument contains two name parameter that is the "assignmentPolicyId", and "accessPackageId". |
322+
323+
324+
```Example for usage within the workflow
325+
{
326+
"category": "joiner",
327+
"description": "Request user assignment to selected access package",
328+
"displayName": "Request user access package assignment",
329+
"id": "c1ec1e76-f374-4375-aaa6-0bb6bd4c60be",
330+
"parameters": [
331+
{
332+
"name": "assignmentPolicyId",
333+
"values": [],
334+
"valueType": "string"
335+
},
336+
{
337+
"name": "accessPackageId",
338+
"values": [],
339+
"valueType": "string"
340+
}
341+
]
342+
}
343+
344+
```
345+
256346
### Add user to groups
257347

258348

@@ -571,6 +661,96 @@ For Microsoft Graph, the parameters for the **Remove users from all teams** task
571661
572662
```
573663

664+
### Remove access package assignment for user
665+
666+
Allows you to remove an access package assignment from users. Access packages are bundles of resources, with specific access, that a user would need to accomplish tasks. For more information on access packages, see [What are access packages and what resources can I manage with them?](entitlement-management-overview.md#what-are-access-packages-and-what-resources-can-i-manage-with-them).
667+
668+
You're able to customize the task name and description for this task in the Azure portal. You must also select the access package which you want to unassign from users.
669+
:::image type="content" source="media/lifecycle-workflow-task/remove-access-package-assignment-user-task.png" alt-text="Screenshot of the remove access package assignment for user task.":::
670+
671+
For Microsoft Graph, the parameters for the **Remove access package assignment for user** task are as follows:
672+
673+
|Parameter |Definition |
674+
|---------|---------|
675+
|category | leaver |
676+
|displayName | Remove access package assignment for user (Customizable by user) |
677+
|description | Remove user assignment of selected access package (Customizable by user) |
678+
|taskDefinitionId | 4a0b64f2-c7ec-46ba-b117-18f262946c50 |
679+
|arguments | Argument contains a name parameter that is the "accessPackageId". |
680+
681+
682+
```Example for usage within the workflow
683+
{
684+
"category": "leaver",
685+
"description": "Remove user assignment of selected access package",
686+
"displayName": "Remove access package assignment for user",
687+
"id": "4a0b64f2-c7ec-46ba-b117-18f262946c50",
688+
"parameters": [
689+
{
690+
"name": "accessPackageId",
691+
"values": [],
692+
"valueType": "string"
693+
}
694+
]
695+
}
696+
```
697+
698+
### Remove all access package assignments for user
699+
700+
Allows you to remove all access package assignments from users. Access packages are bundles of resources, with specific access, that a user would need to accomplish tasks. For more information on access packages, see [What are access packages and what resources can I manage with them?](entitlement-management-overview.md#what-are-access-packages-and-what-resources-can-i-manage-with-them).
701+
702+
You're able to customize the task name and description for this task in the Azure portal.
703+
:::image type="content" source="media/lifecycle-workflow-task/remove-all-access-package-assignment-user-task.png" alt-text="Screenshot of the remove all user access package assignment task.":::
704+
705+
For Microsoft Graph, the parameters for the **Remove all access package assignments for user** task are as follows:
706+
707+
|Parameter |Definition |
708+
|---------|---------|
709+
|category | leaver |
710+
|displayName | Remove all access package assignments for user (Customizable by user) |
711+
|description | Remove all access packages assigned to the user (Customizable by user) |
712+
|taskDefinitionId | 42ae2956-193d-4f39-be06-691b8ac4fa1d |
713+
714+
715+
```Example for usage within the workflow
716+
{
717+
"category": "leaver",
718+
"description": "Remove all access packages assigned to the user",
719+
"displayName": "Remove all access package assignments for user",
720+
"id": "42ae2956-193d-4f39-be06-691b8ac4fa1d",
721+
"parameters": []
722+
}
723+
```
724+
725+
726+
### Cancel all pending access package assignment requests for user
727+
728+
Allows you to remove all access package assignments from users. Access packages are bundles of resources, with specific access, that a user would need to accomplish tasks. For more information on access packages, see [What are access packages and what resources can I manage with them?](entitlement-management-overview.md#what-are-access-packages-and-what-resources-can-i-manage-with-them).
729+
730+
You're able to customize the task name and description for this task in the Azure portal.
731+
:::image type="content" source="media/lifecycle-workflow-task/cancel-all-pending-access-package-assignments-task.png" alt-text="Screenshot of the cancel all pending access package assignments requests for a user task.":::
732+
733+
For Microsoft Graph, the parameters for the **Cancel all pending access package assignment requests for user** task are as follows:
734+
735+
|Parameter |Definition |
736+
|---------|---------|
737+
|category | leaver |
738+
|displayName | Cancel pending access package assignment requests for user (Customizable by user) |
739+
|description | Cancel all pending access packages assignment requests for the user (Customizable by user) |
740+
|taskDefinitionId | 498770d9-bab7-4e4c-b73d-5ded82a1d0b3 |
741+
742+
743+
```Example for usage within the workflow
744+
{
745+
"category": "leaver",
746+
"description": "Cancel all pending access packages assignment requests for the user",
747+
"displayName": "Cancel pending access package assignment requests for user",
748+
"id": "498770d9-bab7-4e4c-b73d-5ded82a1d0b3",
749+
"parameters": []
750+
}
751+
```
752+
753+
574754
### Remove all license assignments from User
575755

576756
Allows all direct license assignments to be removed from a user. For group-based license assignments, you would run a task to remove the user from the group the license assignment is part of.
@@ -632,7 +812,7 @@ For Microsoft Graph, the parameters for the **Delete User** task are as follows:
632812
633813
```
634814

635-
## Send email to manager before user's last day
815+
### Send email to manager before user's last day
636816

637817
Allows an email to be sent to a user's manager before their last day. You're able to customize the task name and the description for this task in the Azure portal.
638818
:::image type="content" source="media/lifecycle-workflow-task/send-email-before-last-day.png" alt-text="Screenshot of Workflows task: send email before user last day task.":::
@@ -682,7 +862,7 @@ For Microsoft Graph the parameters for the **Send email before user's last day**
682862
683863
```
684864

685-
## Send email on user's last day
865+
### Send email on user's last day
686866

687867
Allows an email to be sent to a user's manager on their last day. You're able to customize the task name and the description for this task in the Azure portal.
688868
:::image type="content" source="media/lifecycle-workflow-task/send-email-last-day.png" alt-text="Screenshot of Workflows task: task to send email last day.":::
@@ -731,7 +911,7 @@ For Microsoft Graph, the parameters for the **Send email on user last day** task
731911
732912
```
733913

734-
## Send email to user's manager after their last day
914+
### Send email to user's manager after their last day
735915

736916
Allows an email containing off-boarding information to be sent to the user's manager after their last day. You're able to customize the task name and description for this task in the Azure portal.
737917
:::image type="content" source="media/lifecycle-workflow-task/offboard-email-manager.png" alt-text="Screenshot of Workflows task: send off-boarding email to users manager after their last day.":::

0 commit comments

Comments
 (0)