Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nat-posh-diagram

Author: asudbring

.openpublishing.publish.config.json

@@ -413,7 +413,7 @@
     {
       "path_to_root": "azureml-examples-vj",
       "url": "https://github.com/azure/azureml-examples",
-      "branch": "vijetajo-patch-2",
+      "branch": "main",
       "branch_mapping": {}
     },
     {

articles/active-directory/authentication/media/how-to-mfa-server-migration-utility/settings.png

@@ -13,7 +13,7 @@
     href: what-is-identity-lifecycle-management.md
   - name: What is provisioning?
     href: what-is-provisioning.md
-  - name: What are Lifecycle Workflows? (Preview)
+  - name: What are Lifecycle Workflows? 
     href: what-are-lifecycle-workflows.md  
 - name: Tutorials
   expanded: true
@@ -54,7 +54,7 @@
         href: /graph/tutorial-accessreviews-securitygroup?toc=/azure/active-directory/governance/toc.json&bc=/azure/active-directory/governance/breadcrumb/toc.json
       - name: Review access to privileged roles - Microsoft Graph
         href: /graph/tutorial-accessreviews-roleassignments?toc=/azure/active-directory/governance/toc.json&bc=/azure/active-directory/governance/breadcrumb/toc.json
-    - name: Lifecycle Workflows (Preview)
+    - name: Lifecycle Workflows
       items:
       - name: Automate employee onboarding tasks - Azure portal
         href: tutorial-onboard-custom-workflow-portal.md 
@@ -89,7 +89,7 @@
       href: review-recommendations-access-reviews.md
     - name:  Review and remove users from external organizations
       href: access-reviews-external-users.md
-  - name: Lifecycle Workflows (Preview) 
+  - name: Lifecycle Workflows
     items:
     - name: Understanding Lifecycle Workflows
       href: understanding-lifecycle-workflows.md
@@ -156,7 +156,7 @@
         href: entitlement-management-access-package-resources.md
       - name: Change request settings
         href: entitlement-management-access-package-request-policy.md
-      - name: Configure verified ID settings (Preview)
+      - name: Configure verified ID settings
         href: entitlement-management-verified-id-settings.md  
       - name: Change approval settings
         href: entitlement-management-access-package-approval-policy.md
@@ -218,11 +218,11 @@
         href: ../privileged-identity-management/pim-perform-azure-ad-roles-and-resource-roles-review.md?toc=%2fazure%2factive-directory%2fgovernance%2ftoc.json
       - name: Complete an access review
         href: ../privileged-identity-management/pim-complete-azure-ad-roles-and-resource-roles-review.md?toc=%2fazure%2factive-directory%2fgovernance%2ftoc.json
-    - name: Azure AD PIM for Groups (Preview)
+    - name: Azure AD PIM for Groups
       items:
       - name: Create an access review
         href: create-access-review-pim-for-groups.md
-  - name: Lifecycle Workflows (Preview)
+  - name: Lifecycle Workflows
     items:
       - name: Deployment
         href: lifecycle-workflows-deployment.md   
@@ -263,7 +263,7 @@
     href: /graph/api/resources/accessreviewsv2-overview
   - name: Entitlement management - Microsoft Graph API
     href: /graph/api/resources/entitlementmanagement-overview
-  - name: Lifecycle Workflows (Preview)
+  - name: Lifecycle Workflows
     items:
     - name: Lifecycle Workflows - Microsoft Graph API
       href: /graph/api/resources/identitygovernance-lifecycleworkflows-overview

articles/active-directory/governance/TOC.yml

@@ -13,7 +13,7 @@ ms.custom: template-how-to
 ---
 
 
-# Check the status of a workflow (Preview)
+# Check the status of a workflow
 
 When a workflow is created, it's important to check its status, and run history to make sure it ran properly for the users it processed both by schedule and by on-demand. To get information about the status of workflows, Lifecycle Workflows allows you to check run and user processing history. This history also gives you summaries to see how often a workflow has run, and who it ran successfully for. You're also able to check the status of both the workflow, and its tasks. Checking the status of workflows and their tasks allows you to troubleshoot potential problems that could come up during their execution.
 
@@ -26,9 +26,9 @@ You're able to retrieve run information of a workflow using Lifecycle Workflows.
 
 1. Select **Azure Active Directory** and then select **Identity Governance**.
 
-1. On the left menu, select **Lifecycle Workflows (Preview)**.
+1. On the left menu, select **Lifecycle Workflows**.
 
-1. On the Lifecycle Workflows overview page, select **Workflows (Preview)**.
+1. On the Lifecycle Workflows overview page, select **Workflows**.
 
 1. Select the workflow you want to run history of. 
 
@@ -45,13 +45,13 @@ You're able to retrieve run information of a workflow using Lifecycle Workflows.
 To get further information than just the runs summary for a workflow, you're also able to get information about users processed by a workflow. To check the status of users a workflow has processed using the Azure portal, you would do the following steps:
 
 
-1. In the left menu, select **Lifecycle Workflows (Preview)**.
+1. In the left menu, select **Lifecycle Workflows**.
 
-1. select **Workflows (Preview)**.
+1. select **Workflows**.
 
 1. select the workflow you want to see user processing information for. 
 
-1. On the workflow overview screen, select **Workflow history (Preview)**.
+1. On the workflow overview screen, select **Workflow history**.
     :::image type="content" source="media/check-status-workflow/workflow-history.png" alt-text="Screenshot of a workflow overview history.":::
 1. On the workflow history page, you're presented with a summary of every user processed by the workflow along with counts of successful and failed users and tasks.
     :::image type="content" source="media/check-status-workflow/workflow-history-list.png" alt-text="Screenshot of a list of workflow summaries.":::

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

@@ -14,7 +14,7 @@ ms.reviewer: krbain
 ms.collection: M365-identity-device-management
 ---
 
-# Check execution user scope of a workflow (Preview)
+# Check execution user scope of a workflow
 
 Workflow scheduling will automatically process the workflow for users meeting the workflows execution conditions. This article walks you through the steps to check the users who fall into the execution scope of a workflow. For more information about execution conditions, see: [workflow basics](../governance/understanding-lifecycle-workflows.md#workflow-basics).
 
@@ -26,11 +26,11 @@ To check the users who fall under the execution scope of a workflow, you'd follo
 
 1. Type in **Identity Governance** on the search bar near the top of the page and select it.
 
-1. In the left menu, select **Lifecycle workflows (Preview)**.
+1. In the left menu, select **Lifecycle workflows**.
 
 1. From the list of workflows, select the workflow you want to check the execution scope of.
 
-1. On the workflow overview page, select **Execution conditions (Preview)**.
+1. On the workflow overview page, select **Execution conditions**.
 
 1. On the Execution conditions page, select the **Execution User Scope** tab.
 

articles/active-directory/governance/check-workflow-execution-scope.md

@@ -11,9 +11,9 @@ ms.custom: template-how-to
 
 
 
-# Configure a Logic App for Lifecycle Workflow use (Preview)
+# Configure a Logic App for Lifecycle Workflow use
 
-Before you can use an existing Azure Logic App with the custom task extension feature of Lifecycle Workflows, it must first be made compatible. This reference guide provides a list of steps that must be taken to make the Azure Logic App compatible. For a guide on creating a new compatible Logic App via the Lifecycle Workflows portal, see [Trigger Logic Apps based on custom task extensions (preview)](trigger-custom-task.md).
+Before you can use an existing Azure Logic App with the custom task extension feature of Lifecycle Workflows, it must first be made compatible. This reference guide provides a list of steps that must be taken to make the Azure Logic App compatible. For a guide on creating a new compatible Logic App via the Lifecycle Workflows portal, see [Trigger Logic Apps based on custom task extensions](trigger-custom-task.md).
 
 ## Determine type of token security of your custom task extension
 
@@ -23,7 +23,7 @@ Before configuring your Azure Logic App custom extension for use with Lifecycle
 - Proof of Possession(POP)
 
 
-To determine the security token type of your custom task extension, you'd check the **Custom extensions (Preview)** page:
+To determine the security token type of your custom task extension, you'd check the **Custom extensions** page:
 
 :::image type="content" source="media/configure-logic-app-lifecycle-workflows/custom-task-extension-token-type.png" alt-text="Screenshot of custom task extension and token type.":::
 
@@ -229,7 +229,7 @@ If the security token type is **Proof of Possession (POP)** for your custom task
 
     Policy name: POP-Policy
     
-    Policy type: (Preview) AADPOP   
+    Policy type: AADPOP   
     
     |Claim  |Value  |
     |---------|---------|
@@ -292,5 +292,5 @@ Now that your Logic app is configured for use with Lifecycle Workflows, you can
 
 ## Next steps
 
-- [Lifecycle workflow extensibility (Preview)](lifecycle-workflow-extensibility.md)
+- [Lifecycle workflow extensibility](lifecycle-workflow-extensibility.md)
 - [Manage Workflow Versions](manage-workflow-tasks.md)

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

@@ -1,5 +1,5 @@
 ---
-title: Create a lifecycle workflow (preview) - Azure AD
+title: Create a lifecycle workflow - Azure AD
 description: This article guides you in creating a lifecycle workflow. 
 author: OWinfreyATL
 ms.author: owinfrey
@@ -12,9 +12,9 @@ ms.subservice: compliance
 ms.custom: template-how-to 
 ---
 
-# Create a lifecycle workflow (preview)
+# Create a lifecycle workflow
 
-Lifecycle workflows (preview) allow for tasks associated with the lifecycle process to be run automatically for users as they move through their lifecycle in your organization. Workflows consist of:
+Lifecycle workflows allow for tasks associated with the lifecycle process to be run automatically for users as they move through their lifecycle in your organization. Workflows consist of:
 
 - **Tasks**: Actions taken when a workflow is triggered.
 - **Execution conditions**: The who and when of a workflow. These conditions define which users (scope) this workflow should run against, and when (trigger) the workflow should run.
@@ -35,9 +35,9 @@ To create a workflow based on a template:
 
 1. Select **Azure Active Directory** > **Identity Governance**.
 
-1. On the left menu, select **Lifecycle Workflows (Preview)**.
+1. On the left menu, select **Lifecycle Workflows**.
 
-1. Select **Workflows (Preview)**.
+1. Select **Workflows**.
 
 1. On the **Choose a workflow** page, select the workflow template that you want to use.
 

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

@@ -11,9 +11,9 @@ ms.date: 05/31/2023
 ms.custom: template-how-to
 ---
 
-# Customize emails sent from workflow tasks (preview)
+# Customize emails sent from workflow tasks
 
-Lifecycle workflows provide several tasks that send email notifications. You can customize email notifications to suit the needs of a specific workflow. For a list of these tasks, see [Lifecycle workflow built-in tasks (preview)](lifecycle-workflow-tasks.md).
+Lifecycle workflows provide several tasks that send email notifications. You can customize email notifications to suit the needs of a specific workflow. For a list of these tasks, see [Lifecycle workflow built-in tasks](lifecycle-workflow-tasks.md).
 
 Email tasks allow for the customization of:
 
@@ -40,11 +40,11 @@ When you're customizing an email sent via lifecycle workflows, you can choose to
 
 1. On the search bar near the top of the page, enter **Identity Governance** and select the result.
 
-1. On the left menu, select **Lifecycle workflows (Preview)**.
+1. On the left menu, select **Lifecycle workflows**.
 
-1. On the left menu, select **Workflows (Preview)**.
+1. On the left menu, select **Workflows**.
 
-1. Select **Tasks (Preview)**.
+1. Select **Tasks**.
 
 1. On the pane that lists tasks, select the task for which you want to customize the email.
 
@@ -94,16 +94,16 @@ You can customize emails that you send via lifecycle workflows to have your own
 To enable these features, you need the following prerequisites:
 
 - A verified domain. To add a custom domain, see [Managing custom domain names in Azure Active Directory](../enterprise-users/domains-manage.md).
-- Custom branding set within Azure AD if you want to use your custom branding in emails. To set organizational branding within your Azure tenant, see [Configure your company branding (preview)](../fundamentals/how-to-customize-branding.md).
+- Custom branding set within Azure AD if you want to use your custom branding in emails. To set organizational branding within your Azure tenant, see [Configure your company branding](../fundamentals/how-to-customize-branding.md).
 
 > [!NOTE]
 > For compliance with the [RFC for sending and receiving email](https://www.ietf.org/rfc/rfc2142.txt), we recommend using a domain that has the appropriate DNS records to facilitate email validation, like SPF, DKIM, DMARC, and MX. [Learn more about Exchange Online email routing](/exchange/mail-flow-best-practices/mail-flow-best-practices).
 
 After you meet the prerequisites, follow these steps:
 
-1. On the page for lifecycle workflows, select **Workflow settings (Preview)**.
+1. On the page for lifecycle workflows, select **Workflow settings**.
 
-1. On the **Workflow settings (Preview)** pane, for **Email domain**, select your domain from the drop-down list of verified domains.
+1. On the **Workflow settings** pane, for **Email domain**, select your domain from the drop-down list of verified domains.
 
    :::image type="content" source="media/customize-workflow-email/workflow-email-settings.png" alt-text="Screenshot of workflow domain settings.":::
 1. Turn on the **Use company branding banner logo** toggle if you want to use company branding in emails.

articles/active-directory/governance/customize-workflow-email.md

@@ -14,23 +14,23 @@ ms.reviewer: krbain
 ms.collection: M365-identity-device-management
 ---
 
-# Customize the schedule of workflows (preview)
+# Customize the schedule of workflows
 
 When you create workflows by using lifecycle workflows, you can fully customize them to match the schedule that fits your organization's needs. By default, workflows are scheduled to run every 3 hours. But you can set the interval to be as frequent as 1 hour or as infrequent as 24 hours.
 
 ## Customize the schedule of workflows by using the Azure portal
 
-Workflows that you create within lifecycle workflows follow the same schedule that you define on the **Workflow settings (Preview)** pane. To adjust the schedule, follow these steps:
+Workflows that you create within lifecycle workflows follow the same schedule that you define on the **Workflow settings** pane. To adjust the schedule, follow these steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
 1. On the search bar near the top of the page, enter **Identity Governance** and select the result.
 
-1. On the left menu, select **Lifecycle workflows (Preview)**.
+1. On the left menu, select **Lifecycle workflows**.
 
-1. On the **Lifecycle workflows** overview page, select **Workflow settings (Preview)**.
+1. On the **Lifecycle workflows** overview page, select **Workflow settings**.
 
-1. On the **Workflow settings (Preview)** pane, set the schedule of workflows as an interval of 1 to 24.
+1. On the **Workflow settings** pane, set the schedule of workflows as an interval of 1 to 24.
 
    :::image type="content" source="media/customize-workflow-schedule/workflow-schedule-settings.png" alt-text="Screenshot of the settings for a workflow schedule.":::
 1. Select **Save**.

articles/active-directory/governance/customize-workflow-schedule.md

@@ -14,7 +14,7 @@ ms.reviewer: krbain
 ms.collection: M365-identity-device-management
 ---
 
-# Delete a lifecycle workflow (preview)
+# Delete a lifecycle workflow
 
 You can remove workflows that you no longer need. Deleting these workflows helps keep your lifecycle strategy up to date.
 
@@ -30,9 +30,9 @@ The preview of lifecycle workflows requires Azure Active Directory (Azure AD) Pr
 
 1. On the search bar near the top of the page, enter **Identity Governance**. Then select **Identity Governance** in the results.
 
-1. On the left menu, select **Lifecycle Workflows (Preview)**.
+1. On the left menu, select **Lifecycle Workflows**.
 
-1. Select **Workflows (Preview)**.
+1. Select **Workflows**.
 
 1. On the **Workflows** page, select the workflow that you want to delete. Then select **Delete**.
 
@@ -46,7 +46,7 @@ The preview of lifecycle workflows requires Azure Active Directory (Azure AD) Pr
 
 After you delete workflows, you can view them on the **Deleted workflows** page.
 
-1. On the left pane, select **Deleted workflows (Preview)**.
+1. On the left pane, select **Deleted workflows**.
 
 1. On the **Deleted workflows** page, check the list of deleted workflows. Each workflow has a description, the date of deletion, and a permanent delete date. By default, the permanent delete date for a workflow is 30 days after it was originally deleted.