Skip to content

Commit cd8140b

Browse files
committed
Limits and restrictions update
1 parent ec47d3e commit cd8140b

File tree

1 file changed

+23
-6
lines changed

1 file changed

+23
-6
lines changed

articles/active-directory/governance/understanding-lifecycle-workflows.md

Lines changed: 23 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,31 @@ The following document provides an overview of a workflow created using Lifecycl
2323

2424
[!INCLUDE [Azure AD Premium P2 license](../../../includes/lifecycle-workflows-license.md)]
2525

26-
## Permissions
26+
## Permissions and Roles
2727

28-
The following permissions are required for Lifecycle Workflows:
28+
For a full list of supported delegate and application permissions required to use Lifecycle Workflows, see: [Lifecycle workflows permissions](/graph/permissions-reference#lifecycle-workflows-permissions).
2929

30-
|Parameter |Display String |Description |Admin Consent Required |
31-
|---------|---------|---------|---------|
32-
|LifecycleWorkflows.Read.All | Read all lifecycle workflows and tasks.| Allows the app to list and read all workflows and tasks related to lifecycle workflows on behalf of the signed-in user.| Yes
33-
|LifecycleWorkflows.ReadWrite.All | Read and write all lifecycle workflows and tasks.| Allows the app to create, update, list, read and delete all workflows and tasks related to lifecycle workflows on behalf of the signed-in user.| Yes
30+
For delegated scenarios, the admin needs one of the following [Azure AD roles](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#available-roles):
31+
32+
- Global administrator
33+
- Global reader
34+
- Lifecycle workflows administrator
35+
36+
## Restrictions
37+
38+
39+
|Column1 |Limit |
40+
|---------|---------|
41+
|Number of Workflows | 50 per tenant |
42+
|Number of Tasks | 25 per workflow |
43+
|Number of Custom Task Extensions | 100 per tenant |
44+
|offsetInDays range of triggerAndScopeBasedConditions executionConditions | 60 days |
45+
|Workflow schedule interval in hours | 1-24 hours |
46+
|Number of users per on-demand selection | 10 |
47+
|durationBeforeTimeout range of custom task extensions | 5 minutes-3 hours |
48+
49+
> [!NOTE]
50+
> If creating, or updating, a workflow via API the offsetInDays range will be between -60-60 days. The negative value will signal happening before the timeBasedAttribute, while the positive value will signal happening afterwards.
3451
3552
## Parts of a workflow
3653

0 commit comments

Comments
 (0)