LifecycleWorkflows.ReadWrite.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.ReadWrite.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 supports delegated access (access on behalf of a user)
→ API supports app-only access (access without a user)
Methods | |
---|---|
Resources
Granting this permission allows the calling application to access (and/or update) the following information in your tenant.
- timeBasedAttributeTrigger
- triggerAndScopeBasedConditions
- userProcessingResult
- workflow
- workflowExecutionConditions
Graph reference: timeBasedAttributeTrigger
Property | Type | Description |
---|---|---|
offsetInDays | Int32 | How many days before or after the time-based attribute specified the workflow should trigger. For example, if the attribute is employeeHireDate and offsetInDays is -1, then the workflow should trigger one day before the employee hire date. The value can range between -180 and 180 days. |
timeBasedAttribute | microsoft.graph.identityGovernance.workflowTriggerTimeBasedAttribute | Determines which time-based identity property to reference. The possible values are: employeeHireDate , employeeLeaveDateTime , createdDateTime , unknownFutureValue . |