LifecycleWorkflows.ReadBasic.Workflows

Merill's Note

For an app to access data in Microsoft Graph, the user or administrator must grant it the permissions it needs. This article lists all the Microsoft Graph APIs and your tenant data that can be accessed by the application (vendor/developer) if you consent to the LifecycleWorkflows.ReadBasic.Workflows permission.

If you need to create an audit report of the permissions granted to all the apps in your tenant, you can run the Export-MsIdAppConsentGrantReport command. See How To: Run a quick OAuth app audit of your tenant

Category	Application	Delegated
Identifier	-	-
DisplayText	-	-
Description	-	-
AdminConsentRequired	Yes	No

Graph Methods

• API [v1.0]
• API [beta]
• PowerShell [v1.0]
• PowerShell [beta]

→ API supports delegated access (access on behalf of a user)
→ API supports app-only access (access without a user)

	Methods
	GET /identityGovernance/lifecycleWorkflows/workflows

Resources

Granting this permission allows the calling application to access (and/or update) the following information in your tenant.

• workflow

Graph reference: workflow

Property	Type	Description
category	microsoft.graph.identityGovernance.lifecycleWorkflowCategory	The category of the HR function supported by the workflows created using this template. A workflow can only belong to one category. The possible values are: joiner, leaver, mover, unknownFutureValue. Inherited from workflowBase. Required. Supports $filter(eq,ne) and $orderby
createdDateTime	DateTimeOffset	When the workflow was created. Inherited from workflowBase. Supports $filter(lt, le, gt, ge, eq, ne) and $orderby.
deletedDateTime	DateTimeOffset	When the workflow was deleted. Supports $filter(lt, le, gt, ge, eq, ne) and $orderby.
description	String	The description of the workflow. Inherited from workflowBase. Optional.
displayName	String	The display name of the workflow. Inherited from workflowBase. Required. Supports $filter(eq, ne) and orderby.
executionConditions	microsoft.graph.identityGovernance.workflowExecutionConditions	Conditions describing when to execute the workflow and the criteria to identify in-scope subject set. Inherited from workflowBase. Required.
id	String	Identifier used for individually addressing a specific workflow. Supports $filter(eq, ne) and $orderby.
isEnabled	Boolean	Whether the workflow is enabled or disabled. If this setting is true, the workflow can be run on demand or on schedule when isSchedulingEnabled is true. Inherited from workflowBase. Optional. Defaults to true. Supports $filter(eq, ne) and orderBy.
isSchedulingEnabled	Boolean	If true, the Lifecycle Workflow engine executes the workflow based on the schedule defined by tenant settings. Cannot be true for a disabled workflow (where isEnabled is false). Inherited from workflowBase. Optional. Defaults to false. Supports $filter(eq, ne) and orderBy.
lastModifiedDateTime	DateTimeOffset	The date time when the workflow was last modified. Inherited from workflowBase. Supports $filter(lt, le, gt, ge, eq, ne) and $orderby.
nextScheduleRunDateTime	DateTimeOffset	The date time when the workflow is expected to run next based on the schedule interval, if there are any users matching the execution conditions. Supports $filter(lt,gt) and $orderby.
version	Int32	The current version number of the workflow. Value is 1 when the workflow is first created. Supports $filter(lt, le, gt, ge, eq, ne) and $orderby.