Merge pull request #211368 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

.openpublishing.redirection.azure-monitor.json

@@ -69,90 +69,31 @@ To get further information than just the runs summary for a workflow, you're als
 
 To view a status list of users processed by a workflow, which are UserProcessingResults, you'd make the following API call:
 
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/userProcessingResults
-```
-
-By default **userProcessingResults** returns only information from the last 7 days. To get information as far back as 30 days, you would run the following API call:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/userProcessingResults?$filter=<Date range for processing results>
-```
-
-by default **userProcessingResults** returns only information from the last 7 days. To filter information as far back as 30 days, you would run the following API call:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<id>/userProcessingResults?$filter=<Date range for processing results>
-```
-
-An example of a call to get **userProcessingResults** for a month would be as follows:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/userProcessingResults?$filter=< startedDateTime ge 2022-05-23T00:00:00Z and startedDateTime le 2022-06-22T00:00:00Z
-```
+To view a list of user processing results using API via Microsoft Graph, see: [List userProcessingResults](/graph/api/identitygovernance-workflow-list-userprocessingresults)
 
 ### User processing results using Microsoft Graph
 
-When multiple user events are processed by a workflow, running the **userProcessingResults** may give incomprehensible information. To get a summary of information such as total users and tasks, and failed users and tasks, Lifecycle Workflows provides a call to get count totals.
-
-To view a summary in count form, you would run the following API call:
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/userProcessingResults/summary(<Date Range>)
-```
-
-An example to get the summary between May 1, and May 30, you would run the following call:
+To view a summary of user processing results via API using Microsoft Graph, see: [userProcessingResult: summary](/graph/api/identitygovernance-userprocessingresult-summary)
 
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/userProcessingResults/summary(startDateTime=2022-05-01T00:00:00Z,endDateTime=2022-05-30T00:00:00Z)
-```
 
-### List task processing results of a given user processing result
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/userProcessingResults/<userProcessingResultId>/taskProcessingResults/
-```
 
 ## Run workflow history via Microsoft Graph
 
 ### List runs using Microsoft Graph
 
-With Microsoft Graph, you're able to get full details of workflow and user processing run information.
-
-To view a list of runs, you'd make the following API call:
+To view runs of a workflow via API using Microsoft Graph, see: [runs](/graph/api/resources/identitygovernance-run)
 
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/runs
-```
 
 ### Get a summary of runs using Microsoft Graph
 
-To get a summary of runs for a workflow, which includes detailed information for counts of failed runs and tasks, along with successful runs and tasks for a time range, you'd make the following API call:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/runs/summary(startDateTime=<time>,endDateTime=<time>)
-```
-An example to get a summary of runs of a workflow through the time interval of May 2022 would be as follows:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/runs/summary(startDateTime=2022-05-01T00:00:00Z,endDateTime=202205-31T00:00:00Z)
-```
+To view run summary via API using Microsoft Graph, see: [run summary of a lifecycle workflow](/graph/api/identitygovernance-run-summary)
 
 ### List user and task processing results of a given run using Microsoft Graph
 
-With Lifecycle Workflows, you're able to check the status of each user and task who had a workflow processed for them as part of a run.
-
- 
-You're also able to use **userProcessingResults** with the run call to get users processed for a run by making the following API call:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId>/runs/<runId>/userProcessingResults
-```
+To get user processing result for a run of a lifecycle workflow via API using Microsoft Graph, see: [Get userProcessingResult (for a run of a lifecycle workflow)](/graph/api/identitygovernance-userprocessingresult-get)
 
-This API call will also return a **userProcessingResults ID** value, which can be used to retrieve task processing information in the following call:
+To list task processing results for a user processing result via API using Microsoft Graph, see: [List taskProcessingResults (for a userProcessingResult)](/graph/api/identitygovernance-userprocessingresult-list-taskprocessingresults)
 
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<workflowId> /runs/<runId>/userProcessingResults/<userProcessingResultId>/taskProcessingResults
-```
 
 > [!NOTE]
 > A workflow must have activity in the past 7 days to get **userProcessingResults ID**. If there has not been any activity in that time-frame, the **userProcessingResults** call will not return a value.

.openpublishing.redirection.json

@@ -64,234 +64,9 @@ If you are using the Azure portal to create a workflow, you can customize existi
 
 ## Create a workflow using Microsoft Graph
 
-Workflows can be created using Microsoft Graph API. Creating a workflow using the Graph API allows you to automatically set it to enabled. Setting it to enabled is done using the `isEnabled` parameter.
-
-The table below shows the parameters that must be defined during workflow creation:
-
-|Parameter  |Description  |
-|---------|---------|
-|category     |  A string that identifies the category of the workflow. String is "joiner", "mover", or "leaver. Category of tasks within a workflow must also contain the category of the workflow to run. For full task definitions, see: [Lifecycle workflow tasks and definitions](lifecycle-workflow-tasks.md)    |
-|displayName     |  A unique string that identifies the workflow.       |
-|description     |  A string that describes the purpose of the workflow for administrative use. (Optional)       |
-|isEnabled     |   A boolean value that denotes whether the workflow is set to run or not.  If set to “true" then the workflow will run.      |
-|IsSchedulingEnabled     |   A Boolean value that denotes whether scheduling is enabled or not. Unlike isEnbaled, a workflow can still be run on demand if this value is set to false.     |
-|executionConditions     |  An argument that contains: A time-based attribute and an integer parameter defining when a workflow will run between -60 and a scope attribute defining who the workflow runs for.   |
-|tasks     |  An argument in a workflow that has a unique displayName and a description. It defines the specific tasks to be executed in the workflow. The specified task is outlined by the taskDefinitionID and its parameters. For a list of supported tasks, and their corresponding IDs, see  [Lifecycle Workflow tasks and definitions](lifecycle-workflow-tasks.md).      |
-
-
-
-
-To create a joiner workflow, in Microsoft Graph, use the following request and body:
-```http
-POST https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows 
-Content-type: application/json
-```
-
-```Request body
-{ 
-    "category": "joiner",   
-    "displayName": "<Unique workflow name string>",
-   "description": "<Unique workflow description>", 
-   "isEnabled":true, 
-   "tasks":[ 
-      { 
-         "category": "joiner",
-         "isEnabled": true, 
-         "taskTemplateId": "<Unique Task template>", 
-         "displayName": "<Unique task name>", 
-         "description": "<Task template description>", 
-         "arguments": "<task arguments>"
-      } 
-   ], 
-   "executionConditions": { 
-         "@odata.type" : "microsoft.graph.identityGovernance.scopeAndTriggerBasedCondition",
-         "trigger": {
-            "@odata.type" : "microsoft.graph.identityGovernance.timeBasedAttributeTrigger",
-            "timeBasedAttribute":"<time-based trigger argument>",
-            "arguments": -7
-       },
-        "scope": {
-            "@odata.type" : "microsoft.graph.identityGovernance.ruleBasedScope",
-            "rule": "employeeType eq '<Employee type attribute>' AND department -eq '<department attribute>'"
-        }
-   } 
-} 
-
-> [!NOTE]
-> time based trigger arguments can be from -60 to 60. The negative value denotes **Before** a time based argument, while a positive value denotes **After**. For example the -7 in the workflow example above denotes the workflow will run 1 week before the time-based argument happens.
-
-```
-
-To change this workflow from joiner to leaver, replace the category parameters to "leaver". To get a list of the task definitions that can be added to your workflow run the following call:
-
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/taskDefinitions
-```
-
-The response to the code will look like:
-
-```Response body
-{
-    "@odata.context": "https://graph.microsoft-ppe.com/testppebetalcwpp4/$metadata#identityGovernance/lifecycleWorkflows/taskDefinitions",
-    "@odata.count": 13,
-    "value": [
-        {
-            "category": "joiner,leaver",
-            "description": "Add user to a group",
-            "displayName": "Add User To Group",
-            "id": "22085229-5809-45e8-97fd-270d28d66910",
-            "version": 1,
-            "parameters": [
-                {
-                    "name": "groupID",
-                    "values": [],
-                    "valueType": "string"
-                }
-            ]
-        },
-        {
-            "category": "joiner,leaver",
-            "description": "Disable user account in the directory",
-            "displayName": "Disable User Account",
-            "id": "1dfdfcc7-52fa-4c2e-bf3a-e3919cc12950",
-            "version": 1,
-            "parameters": []
-        },
-        {
-            "category": "joiner,leaver",
-            "description": "Enable user account in the directory",
-            "displayName": "Enable User Account",
-            "id": "6fc52c9d-398b-4305-9763-15f42c1676fc",
-            "version": 1,
-            "parameters": []
-        },
-        {
-            "category": "joiner,leaver",
-            "description": "Run a custom task extension",
-            "displayName": "run a Custom Task Extension",
-            "id": "4262b724-8dba-4fad-afc3-43fcbb497a0e",
-            "version": 1,
-            "parameters":
-                {
-                    "name": "customtaskextensionID",
-                    "values": [],
-                    "valueType": "string"
-                }
-            ]
-        },
-        {
-            "category": "joiner,leaver",
-            "description": "Remove user from membership of selected Azure AD groups",
-            "displayName": "Remove user from selected groups",
-            "id": "1953a66c-751c-45e5-8bfe-01462c70da3c",
-            "version": 1,
-            "parameters": [
-                {
-                    "name": "groupID",
-                    "values": [],
-                    "valueType": "string"
-                }
-            ]
-        },
-        {
-            "category": "joiner",
-            "description": "Generate Temporary Access Password and send via email to user's manager",
-            "displayName": "Generate TAP And Send Email",
-            "id": "1b555e50-7f65-41d5-b514-5894a026d10d",
-            "version": 1,
-            "parameters": [
-                {
-                    "name": "tapLifetimeMinutes",
-                    "values": [],
-                    "valueType": "string"
-                },
-                {
-                    "name": "tapIsUsableOnce",
-                    "values": [
-                        "true",
-                        "false"
-                    ],
-                    "valueType": "enum"
-                }
-            ]
-        },
-        {
-            "category": "joiner",
-            "description": "Send welcome email to new hire",
-            "displayName": "Send Welcome Email",
-            "id": "70b29d51-b59a-4773-9280-8841dfd3f2ea",
-            "version": 1,
-            "parameters": []
-        },
-        {
-            "category": "joiner,leaver",
-            "description": "Add user to a team",
-            "displayName": "Add User To Team",
-            "id": "e440ed8d-25a1-4618-84ce-091ed5be5594",
-            "version": 1,
-            "parameters": [
-                {
-                    "name": "teamID",
-                    "values": [],
-                    "valueType": "string"
-                }
-            ]
-        },
-        {
-            "category": "leaver",
-            "description": "Delete user account in Azure AD",
-            "displayName": "Delete User Account",
-            "id": "8d18588d-9ad3-4c0f-99d0-ec215f0e3dff",
-            "version": 1,
-            "parameters": []
-        },
-        {
-            "category": "joiner,leaver",
-            "description": "Remove user from membership of selected Teams",
-            "displayName": "Remove user from selected Teams",
-            "id": "06aa7acb-01af-4824-8899-b14e5ed788d6",
-            "version": 1,
-            "parameters": [
-                {
-                    "name": "teamID",
-                    "values": [],
-                    "valueType": "string"
-                }
-            ]
-        },
-        {
-            "category": "leaver",
-            "description": "Remove user from all Azure AD groups memberships",
-            "displayName": "Remove user from all groups",
-            "id": "b3a31406-2a15-4c9a-b25b-a658fa5f07fc",
-            "version": 1,
-            "parameters": []
-        },
-        {
-            "category": "leaver",
-            "description": "Remove user from all Teams memberships",
-            "displayName": "Remove user from all Teams",
-            "id": "81f7b200-2816-4b3b-8c5d-dc556f07b024",
-            "version": 1,
-            "parameters": []
-        },
-        {
-            "category": "leaver",
-            "description": "Remove all licenses assigned to the user",
-            "displayName": "Remove all licenses for user",
-            "id": "8fa97d28-3e52-4985-b3a9-a1126f9b8b4e",
-            "version": 1,
-            "parameters": []
-        }
-    ]
-}
-
-```
-For further details on task definitions and their parameters, see [Lifecycle Workflow Tasks](lifecycle-workflow-tasks.md).
-
+To create a workflow using Microsoft Graph API, see [Create workflow (lifecycle workflow)](/graph/api/identitygovernance-lifecycleworkflowscontainer-post-workflows)
 
 ## Next steps
 
-- [Create workflow (lifecycle workflow)](/graph/api/identitygovernance-lifecycleworkflowscontainer-post-workflows?view=graph-rest-beta)
 - [Manage a workflow's properties](manage-workflow-properties.md)
 - [Manage Workflow Versions](manage-workflow-tasks.md)

articles/active-directory/governance/check-status-workflow.md

@@ -58,35 +58,32 @@ After deleting workflows, you can view them on the **Deleted Workflows (Preview)
 
 
 ## Delete a workflow using Microsoft Graph
- You're also able to delete, view deleted, and restore deleted Lifecycle workflows using Microsoft Graph.
+
+To delete a workflow using API via Microsoft Graph, see: [Delete workflow (lifecycle workflow)](/graph/api/identitygovernance-workflow-delete?view=graph-rest-beta).
+
+
+To view
 
 Workflows can be deleted by running the following call:
 ```http
 DELETE https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/workflows/<id> 
 ```
 ## View deleted workflows using Microsoft Graph
-You can view a list of deleted workflows by running the following call:
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/deletedItems/workflows 
-```
+
+To View a list of deleted workflows using API via Microsoft Graph, see: [List deleted workflows](/graph/api/identitygovernance-lifecycleworkflowscontainer-list-deleteditems).
+
 
 ## Permanently delete a workflow using Microsoft Graph
-Deleted workflows can be permanently deleted by running the following call:
-```http
-DELETE https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/deletedItems/workflows/<id>
-```
+
+To permanently delete a workflow using API via Microsoft Graph, see: [Permanently delete a deleted workflow](/graph/api/identitygovernance-deleteditemcontainer-delete)
 
 ## Restore deleted workflows using Microsoft Graph
 
-Deleted workflows are available to be restored for 30 days before they're permanently deleted. To restore a deleted workflow, run the following API call:
-```http
-GET https://graph.microsoft.com/beta/identityGovernance/lifecycleWorkflows/deletedItems/workflows/<id>/restore
-```
+To restore a deleted workflow using API via Microsoft Graph, see: [Restore a deleted workflow](/graph/api/identitygovernance-workflow-restore)
 > [!NOTE]
 > Permanently deleted workflows are not able to be restored.
 
 ## Next steps
 
-- [Delete workflow (lifecycle workflow)](/graph/api/identitygovernance-workflow-delete?view=graph-rest-beta)
 - [What are Lifecycle Workflows?](what-are-lifecycle-workflows.md)
 - [Manage Lifecycle Workflow Versions](manage-workflow-tasks.md)