Merge pull request #228496 from OWinfreyATL/owinfreyATL-TaskExtension-Updates

Custom task extension updates

Author: Stacyrch140

articles/active-directory/governance/configure-logic-app-lifecycle-workflows.md

@@ -241,4 +241,4 @@ Now that your Logic app is configured for use with Lifecycle Workflows, you can
 ## Next steps
 
 - [Lifecycle workflow extensibility (Preview)](lifecycle-workflow-extensibility.md)
-- [Manage Workflow Versions](manage-workflow-tasks.md)
+- [Manage Workflow Versions](manage-workflow-tasks.md)

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

@@ -16,7 +16,7 @@ ms.custom: template-concept
 # Lifecycle Workflows Custom Task Extension (Preview)
 
 
-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'll be able to utilize the concept of custom task extensions to call-out to external systems as part of a workflow. By calling out to the external systems, you're able to accomplish things, which can extend the purpose of your workflows. 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).
+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. By calling out to the external systems, you're able to accomplish things, which can extend the purpose of your workflows. 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).
 
 
 ## Prerequisite Logic App roles required for integration with the custom task extension
@@ -34,13 +34,27 @@ The roles on the Azure Logic App, which allows it to be compatible with the cust
 
 ## Custom task extension deployment scenarios
 
-When creating custom task extensions, the scenarios for how it will interact with Lifecycle Workflows can be one of two ways:
+When creating custom task extensions, the scenarios for how it interacts with Lifecycle Workflows can be one of two ways:
 
  :::image type="content" source="media/lifecycle-workflow-extensibility/task-extension-deployment-scenarios.png" alt-text="Screenshot of custom task deployment scenarios.":::
 
 - **Launch and continue** - The Azure Logic App is started, and the following task execution immediately continues with no response expected from the Azure Logic App. This scenario is best suited if the Lifecycle workflow doesn't require any feedback (including status) from the Azure Logic App. With this scenario, as long as the workflow is started successfully, the workflow is viewed as a success.
-- **Launch and wait** - The Azure Logic App is started, and the following task's execution waits on the response from the Logic App. You enter a time duration for how long the custom task extension should wait for a response from the Azure Logic App. If no response is received within a customer defined duration window, the task will be considered failed.
- :::image type="content" source="media/lifecycle-workflow-extensibility/custom-task-launch-wait.png" alt-text="Screenshot of custom task launch and wait task choice.":::
+- **Launch and wait** - The Azure Logic App is started, and the following task's execution waits on the response from the Logic App. You enter a time duration for how long the custom task extension should wait for a response from the Azure Logic App. If no response is received within a customer defined duration window, the task is considered failed.
+ :::image type="content" source="media/lifecycle-workflow-extensibility/custom-task-launch-wait.png" alt-text="Screenshot of custom task launch and wait task choice." lightbox="media/lifecycle-workflow-extensibility/custom-task-launch-wait.png":::
+
+## Response authorization
+
+When creating a custom task extension that waits for a response from the Logic App, you're able to define which applications can send a response
+
+:::image type="content" source="media/lifecycle-workflow-extensibility/launch-wait-options.png" alt-text="Screenshot of custom task extension launch and wait options.":::
+
+Response authorization can be utilized in one of the following ways:
+
+- **System-assigned managed identity (Default)** - Enables and utilizes the Logic Apps system-assigned managed identity. For more information on this, see: [Authenticate access to Azure resources with managed identities in Azure Logic Apps](/azure/logic-apps/create-managed-service-identity)
+- **No authorization** - Grants no authorization to the Logic App. You're responsible for assigning an application permission, or role assignment.
+- **Existing application** - You can choose an existing application to respond.
+
+
 
 ## Custom task extension integration with Azure Logic Apps high-level steps
 

articles/active-directory/governance/media/lifecycle-workflow-extensibility/launch-wait-options.png

@@ -25,51 +25,36 @@ Lifecycle Workflows can be used to trigger custom tasks via an extension to Azur
 For more information about Lifecycle Workflows extensibility, see: [Workflow Extensibility](lifecycle-workflow-extensibility.md).
 
 
-## Create a custom task extension with a new Azure Logic App
+## Create a custom task extension using the Azure portal
 
-To use a custom task extension in your workflow, first a custom task extension must be created to be linked with an Azure Logic App. You're able to create a Logic App at the same time you're creating a custom task extension. To do this, you'll complete these steps:
+To use a custom task extension in your workflow, first a custom task extension must be created to be linked with an Azure Logic App. You're able to create a Logic App at the same time you're creating a custom task extension. To do this, you complete these steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com). 
 
 1. Select **Azure Active Directory** and then select **Identity Governance**. 
 
 1. In the left menu, select **Lifecycle Workflows (Preview)**. 
 
-1. In the left menu, select **Workflows (Preview)**.
+1. On the Lifecycle workflows screen, select **Custom task extension**. 
 
-1. On the workflows screen, select **Custom task extension**. 
-    :::image type="content" source="media/trigger-custom-task/custom-task-extension-select.png" alt-text="Screenshot of selecting a custom task extension from a workflow overview page.":::
 1. On the custom task extensions page, select **Create custom task extension**.
     :::image type="content" source="media/trigger-custom-task/create-custom-task-extension.png" alt-text="Screenshot for creating a custom task extension selection.":::
 1. On the basics page you, enter a unique display name and description for the custom task extension and select **Next**.
     :::image type="content" source="media/trigger-custom-task/custom-task-extension-basics.png" alt-text="Screenshot of the basics section for creating a custom task extension.":::
-1. On the **Task behavior** page, you specify how the custom task extension will behave after executing the Azure Logic App and select **Next**.
+1. On the **Task behavior** page, you specify how the custom task extension will behave after executing the Azure Logic App. If you choose **Launch and continue** you can immediately select **Next: Details**.
     :::image type="content" source="media/trigger-custom-task/custom-task-extension-behavior.png" alt-text="Screenshot for choose task behavior for custom task extension.":::
-    > [!NOTE]
-    > For more information about custom task extension behavior, see: [Lifecycle Workflow extensibility](lifecycle-workflow-extensibility.md)
+
+1. If you select **Launch and wait**, you're given an option of how long to wait for a response from the logic app before the task is considered a failure, and also options to set **Response authorization**. After choosing these options, you would be able to select **Next: Details**. 
+    :::image type="content" source="media/trigger-custom-task/custom-task-extension-launch-wait.png" alt-text="Screenshot of launch and wait option for custom task extension." lightbox="media/trigger-custom-task/custom-task-extension-launch-wait.png"::: 
+     > [!NOTE]
+     > For more information about custom task extension behavior, see: [Lifecycle Workflow extensibility](lifecycle-workflow-extensibility.md)
 1. On the **Logic App details** page, you select **Create new Logic App**, and specify the subscription and resource group where it will be located. You'll also give the new Azure Logic App a name.
     :::image type="content" source="media/trigger-custom-task/custom-task-extension-new-logic-app.png" alt-text="screen showing to create new logic app for custom task extension.":::
-1. If deployed successfully, you'll get confirmation on the **Logic App details** page immediately, and then you can select **Next**. 
-
-1. On the  **Review** page, you can review the details of the custom task extension and the Azure Logic App you've created. Select **Create** if the details match what you desire for the custom task extension.
-    
-
-## Configure a custom task extension with an existing Azure Logic App
-
-You can also link a custom task extension to an existing Azure Logic App. To do this, you'd complete the following steps:
-
-> [!IMPORTANT]
-> A Logic App must be configured to be compatible with the custom task extension. For more information, see [Configure a Logic App for Lifecycle Workflow use](configure-logic-app-lifecycle-workflows.md)
-
-1. In the left menu, select **Lifecycle workflows (Preview)**. 
-
-1. In the left menu, select **Workflows (Preview)**.
-
-1. On the workflows screen, select **custom task extension**. 
+   > [!IMPORTANT]
+   > A Logic App must be configured to be compatible with the custom task extension. For more information, see [Configure a Logic App for Lifecycle Workflow use](configure-logic-app-lifecycle-workflows.md) 
+1. If deployed successfully, you get confirmation on the **Logic App details** page immediately, and then you can select **Next**. 
 
-1. On the **Logic App details** page, you select **Choose an existing Logic App**, and specify the subscription and resource group where the Azure Logic App is located and select **Next**.
-    :::image type="content" source="media/trigger-custom-task/custom-task-extension-existing-logic-app.png" alt-text="Screenshot for selecting an existing logic app with custom task extension.":::
-1. You can Review information about the updated custom task extension and the existing Logic App linked to it. Select **Create** if the details match what you desire for the custom task extension.
+1. On the  **Review** page, you can review the details of the custom task extension and the Azure Logic App you've created. Select **Create** if the details match what you desire for the custom task extension.    
 
 
 ## Add your custom task extension to a workflow
@@ -88,9 +73,9 @@ To Add a custom task extension to a workflow, you'd do the following steps:
 
 1. On the tasks screen, select **Add task**.
 
-1. In the **Select tasks** drop down, select **Run a Custom Task Extension**, and select **Add**.
+1. In the **Select tasks** side menu, select **Run a Custom Task Extension**, and select **Add**.
 
-1. On the custom task extension page, you can give the task a name and description. You can also choose from a list of configured custom task extensions to use.
+1. On the custom task extension page, you can give the task a name and description. You also choose from a list of configured custom task extensions to use.
     :::image type="content" source="media/trigger-custom-task/add-custom-task-extension.png" alt-text="Screenshot showing to add a custom task extension to workflow.":::     
 1. When finished, select **Save**.