Merge pull request #239104 from MicrosoftDocs/main

Publish to live, Wednesday 4 AM PST, 5/24

Author: ttorble

.openpublishing.publish.config.json

@@ -997,7 +997,13 @@
       "url": "https://github.com/MicrosoftGraph/microsoft-graph-docs",
       "branch": "main",
       "branch_mapping": {}
-    }
+    },
+    {
+      "path_to_root": "azure-actions-workflow-samples",
+      "url": "https://github.com/Azure/actions-workflow-samples",
+      "branch": "main",
+      "branch_mapping": {}
+    }  
   ],
   "branch_target_mapping": {
     "live": ["Publish", "PDF"],

articles/active-directory/develop/tutorial-v2-android.md

@@ -35,7 +35,6 @@ In this tutorial:
 
 - [Android Studio](https://developer.android.com/studio)
 - [Android documentation on generating a key](https://developer.android.com/studio/publish/app-signing#generate-key)
-- [Layout resource](https://developer.android.com/guide/topics/resources/layout-resource)
 
 ## How this tutorial works
 

articles/active-directory/external-identities/customers/quickstart-trial-setup.md

@@ -3,7 +3,7 @@ title: Quickstart - Set up a customer tenant free trial
 description: Use our quickstart to set up the customer tenant free trial.
 services: active-directory
 author: csmulligan
-manager: celestedg
+manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.subservice: ciam
@@ -12,7 +12,7 @@ ms.date: 05/10/2023
 ms.author: cmulligan
 ms.custom: it-pro
 
-#Customer intent: As a dev, devops, or it admin, I want to set up the customer tenant free trial.
+#Customer intent: As a dev, devops, or IT admin, I want to set up the customer tenant free trial.
 ---
 # Quickstart: Get started with Azure AD for customers (Preview)
 
@@ -26,7 +26,7 @@ Your free trial of a customer tenant provides you with the opportunity to try ne
 During the free trial period, you'll have access to all product features with few exceptions. See the following table for comparison: 
 
 |  Features | Azure AD for customers Trial (without credit card) | Azure Active Directory account includes Partners (needs credit card)  | 
-|----------|-----------|------------|
+|----------|:-----------:|:------------:|
 | **Self-service account experiences** (Sign-up, sign-in, and password recovery.)   | :heavy_check_mark: |  :heavy_check_mark:  | 
 | **MFA** (With email OTP.)  | :heavy_check_mark: |  :heavy_check_mark:  |  
 | **Custom token augmentation** (From external sources.) |  :heavy_check_mark: |  :heavy_check_mark:  |
@@ -43,7 +43,7 @@ During the free trial period, you'll have access to all product features with fe
 
 ## Sign up to your customer tenant free trial
 
-1. Open your browser and visit [https://aka.ms/ciam-free-trial](https://aka.ms/ciam-free-trial?wt.mc_id=ciamcustomertenantfreetrial_linkclick_content_cnl).
+1. Open your browser and visit <a href="https://aka.ms/ciam-free-trial?wt.mc_id=ciamcustomertenantfreetrial_linkclick_content_cnl" target="_blank">https://aka.ms/ciam-free-trial</a>.
 1. You can sign in to the customer trial tenant using your personal account, and your Microsoft account (MSA) or GitHub account.  
 1. You'll notice that a domain name and location have been set for you. The domain name and the data location can't be changed later in the free trial. Select **Change settings** if you would like to adjust them.
 1. Select **Continue** and hang on while we set up your trial. It will take a few minutes for the trial to become ready for the next step.

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

@@ -15,7 +15,7 @@ ms.custom: template-concept
 # Lifecycle Workflows templates (Preview)
 
 
-Lifecycle Workflows allows you to automate the lifecycle management process for your organization by creating workflows that contain both built-in tasks, and custom task extensions. These workflows, and the tasks within them, all fall into categories based on the Joiner-Mover-Leaver(JML) model of lifecycle management. To make this process even more efficient, Lifecycle Workflows also provide you templates, which you can use to accelerate the set up, creation, and configuration of common lifecycle management processes. You can create workflows based on these templates as is, or you can customize them even further to match the requirements for users within your organization. In this article you'll get the complete list of workflow templates, common template parameters, default template parameters for specific templates, and the list of compatible tasks for each template. For full task definitions, see [Lifecycle Workflow tasks and definitions](lifecycle-workflow-tasks.md).
+Lifecycle Workflows allows you to automate the lifecycle management process for your organization by creating workflows that contain both built-in tasks, and custom task extensions. These workflows, and the tasks within them, all fall into categories based on the Joiner-Mover-Leaver(JML) model of lifecycle management. To make this process even more efficient, Lifecycle Workflows also provide you with templates, which you can use to accelerate the setup, creation, and configuration of common lifecycle management processes. You can create workflows based on these templates as is, or you can customize them even further to match the requirements for users within your organization. In this article you get the complete list of workflow templates, common template parameters, default template parameters for specific templates, and the list of compatible tasks for each template. For full task definitions, see [Lifecycle Workflow tasks and definitions](lifecycle-workflow-tasks.md).
 
 
 ## Lifecycle Workflow Templates
@@ -28,6 +28,7 @@ The list of templates are as follows:
 
 - [Onboard pre-hire employee](lifecycle-workflow-templates.md#onboard-pre-hire-employee)
 - [Onboard new hire employee](lifecycle-workflow-templates.md#onboard-new-hire-employee)
+- [Post-Onboarding of an employee](lifecycle-workflow-templates.md#post-onboarding-of-an-employee)
 - [Real-time employee termination](lifecycle-workflow-templates.md#real-time-employee-termination)  
 - [Pre-Offboarding of an employee](lifecycle-workflow-templates.md#pre-offboarding-of-an-employee)
 - [Offboard an employee](lifecycle-workflow-templates.md#offboard-an-employee)
@@ -59,7 +60,7 @@ The default specific parameters and properties for the **Onboard pre-hire employ
 
 ### Onboard new hire employee
 
-The **Onboard new-hire employee** template is designed to configure tasks that will be completed on an employee's start date.
+The **Onboard new-hire employee** template is designed to configure tasks that are completed on an employee's start date.
 
 :::image type="content" source="media/lifecycle-workflow-templates/onboard-new-hire-template.png" alt-text="Screenshot of a Lifecycle Workflow onboard new hire template.":::
 
@@ -72,16 +73,36 @@ The default specific parameters for the **Onboard new hire employee** template a
 |Trigger Type     | Trigger and Scope Based        |  ❌       |
 |Days from event     | 0        | ❌        |
 |Event timing     | On        |  ❌       |
-|Event User attribute     | EmployeeHireDate        |   ❌      |
+|Event User attribute     | EmployeeHireDate, createdDateTime        |   ✔️      |
 |Scope type     | Rule based        | ❌        |
 |Execution conditions     | (department eq 'Marketing')        |  ✔️       |
 |Tasks     | **Add User To Group**, **Enable User Account**, **Send Welcome Email**      |  ✔️       |
 
 
+### Post-Onboarding of an employee
+
+The **Post-Onboarding of an employee** template is designed to configure tasks that will be completed after an employee's start, or creation, date.
+
+:::image type="content" source="media/lifecycle-workflow-templates/onboard-post-employee-template.png" alt-text="Screenshot of a Lifecycle Workflow post-onboard new hire template.":::
+
+The default specific parameters for the **Post-Onboarding of an employee** template are as follows:
+
+
+|parameter  |description  |Customizable  |
+|---------|---------|---------|
+|Category     |  Joiner       |  ❌       |
+|Trigger Type     | Trigger and Scope Based        |  ❌       |
+|Days from event     | 7       | ✔️        |
+|Event timing     | After        |  ❌       |
+|Event User attribute     | EmployeeHireDate, createdDateTime        |   ✔️      |
+|Scope type     | Rule based        | ❌        |
+|Execution conditions     | (department eq 'Marketing')        |  ✔️       |
+|Tasks     | **Add User To Group**, **Add user to selected teams**    |  ✔️       |
+
 
 ### Real-time employee termination
 
-The **Real-time employee termination** template is designed to configure tasks that will be completed immediately when an employee is terminated.
+The **Real-time employee termination** template is designed to configure tasks that are completed immediately when an employee is terminated.
 
 :::image type="content" source="media/lifecycle-workflow-templates/on-demand-termination-template.png" alt-text="Screenshot of a Lifecycle Workflow real time employee termination template.":::
 
@@ -101,7 +122,7 @@ The default specific parameters for the **Real-time employee termination** templ
 
 ### Pre-Offboarding of an employee
 
-The **Pre-Offboarding of an employee** template is designed to configure tasks that will be completed before an employee's last day of work.
+The **Pre-Offboarding of an employee** template is designed to configure tasks that are completed before an employee's last day of work.
 
 :::image type="content" source="media/lifecycle-workflow-templates/offboard-pre-employee-template.png" alt-text="Screenshot of a pre offboarding employee template.":::
 
@@ -124,7 +145,7 @@ The default specific parameters for the **Pre-Offboarding of an employee** templ
 
 ### Offboard an employee
 
-The **Offboard an employee** template is designed to configure tasks that will be completed on an employee's last day of work.
+The **Offboard an employee** template is designed to configure tasks that are completed on an employee's last day of work.
 
 :::image type="content" source="media/lifecycle-workflow-templates/offboard-employee-template.png" alt-text="Screenshot of an offboard employee template lifecycle workflow.":::
 

articles/active-directory/governance/media/create-lifecycle-workflow/template-list.png

@@ -56,12 +56,12 @@ A workflow can be broken down into the following three main parts:
 |Workflow part|Description|
 |-----|-----|
 |General information|This portion of a workflow covers basic information such as display name, and a description of what the workflow does.|
-|Tasks|Tasks are the actions that will be taken when a workflow is executed.|
-|Execution conditions| Defines when(trigger), and for who(scope), a scheduled workflow will run. For more information on these two parameters, see  [Trigger details](understanding-lifecycle-workflows.md#trigger-details) and [Configure Scope](understanding-lifecycle-workflows.md#configure-scope).|
+|Tasks|Tasks are the actions that are taken when a workflow is executed.|
+|Execution conditions| Defines when(trigger), and for who(scope), a scheduled workflow runs. For more information on these two parameters, see  [Trigger details](understanding-lifecycle-workflows.md#trigger-details) and [Configure Scope](understanding-lifecycle-workflows.md#configure-scope).|
 
 ## Templates
 
-Creating a workflow via the Azure portal requires the use of a template. A Lifecycle Workflow template is a framework that is used for pre-defined tasks, and helps automate the creation of a workflow.  
+Creating a workflow via the Azure portal requires the use of a template. A Lifecycle Workflow template is a framework that is used for predefined tasks, and helps automate the creation of a workflow.  
 
   [![Understanding workflow template diagram.](media/understanding-lifecycle-workflows/workflow-3.png)](media/understanding-lifecycle-workflows/workflow-3.png#lightbox)
 
@@ -80,11 +80,11 @@ Every workflow has its own overview section, where you can either take quick act
 - My Feed
 - Quick Action
 
-In this section you'll learn what each section tells you, and what actions you'll be able to take from this information.
+In this section you learn what each section tells you, and what actions you're able to take from this information.
 
 ### Basic Information
 
-When selecting a workflow, the overview provides you a list of basic details in the **Basic Information** section. These basic details provide you information such as the workflow category, its ID, when it was modified, and when it's scheduled to run again. This information is important in providing quick details surrounding its current usage for administrative purposes. Basic information is also live data, meaning any quick change action that you take place on the overview page, is shown immediately within this section.
+When selecting a workflow, the overview provides you with a list of basic details in the **Basic Information** section. These basic details provide you with information such as the workflow category, its ID, when it was modified, and when it's scheduled to run again. This information is important in providing quick details surrounding its current usage for administrative purposes. Basic information is also live data, meaning any quick change action that you take place on the overview page, is shown immediately within this section.
 
 Within the **Basic Information** you can view the following information:
 
@@ -126,21 +126,22 @@ Actions taken from the overview of a workflow allow you to quickly complete task
 ## Workflow basics
 
 After selecting a template, on the basics screen:
- - Provide the information that will be used in the description portion of the workflow.
+ - Provide the information that is used in the description portion of the workflow.
  - The trigger, defines when of the execution condition.
 
  [![Basics of a workflow.](media/understanding-lifecycle-workflows/workflow-4.png)](media/understanding-lifecycle-workflows/workflow-4.png#lightbox)
 
 ## Trigger details
 
-The trigger of a workflow defines when a scheduled workflow will run for users in scope for the workflow. The trigger is a combination of a time-based attribute, and an offset value.  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. 
+The trigger of a workflow defines when a scheduled workflow runs for users in scope for the workflow. The trigger is a combination of a time-based attribute, and an offset value.  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. 
 
-The time-based attribute can be either one of two values, which are automatically chosen based on the template in which you select during the creation of your workflow. The two values can be:
+The time-based attribute can be either one of two values, which are automatically chosen based on the template in which you select during the creation of your workflow. The three values can be:
 
-- employeeHireDate: If the template is a joiner workflow.
-- employeeLeaveDateTime: If the template is a leaver workflow.
+- employeeHireDate: If the template is a joiner workflow
+- createdDateTime: if the template is a joiner workflow designed to run either on hire or post onboarding
+- employeeLeaveDateTime: If the template is a leaver workflow
 
-These two values must be set within Azure AD for users. For more information on this process, see [How to synchronize attributes for Lifecycle workflows](how-to-lifecycle-workflow-sync-attributes.md)
+The values employeeHireDate and employeeLeaveDateTime must be set within Azure AD for users. For more information on this process, see [How to synchronize attributes for Lifecycle workflows](how-to-lifecycle-workflow-sync-attributes.md)
 
 The offset determines how many days before or after the time-based attribute the workflow should be triggered. For example, if the attribute is employeeHireDate and offsetInDays is 7, then the workflow should trigger one week(7 days) before the employee hire date. The offsetInDays value can be as far ahead, or behind, as 60.
 
@@ -149,12 +150,12 @@ The offset determines how many days before or after the time-based attribute the
 
 [![Screenshot showing the rule section.](media/understanding-lifecycle-workflows/workflow-5.png)](media/understanding-lifecycle-workflows/workflow-5.png#lightbox)
 
-The scope defines for who the scheduled workflow will run. Configuring this parameter allows you to further narrow down the users for whom the workflow is to be executed.
+The scope defines for who the scheduled workflow runs. Configuring this parameter allows you to further narrow down the users for whom the workflow is to be executed.
 
 The scope is made up of the following two parts:
 
 - Scope type: Always preset as Rule based.
-- Rule: Where you can set expressions on user properties that define for whom the scheduled workflow will run. You can add extra expressions using **And, And not, Or, Or not** to create complex conditionals, and apply the workflow more granularly across your organization. Lifecycle Workflows supports a [rich set of user properties](/graph/api/resources/identitygovernance-rulebasedsubjectset#supported-user-properties-and-query-parameters) for configuring the scope.
+- Rule: Where you can set expressions on user properties that define for whom the scheduled workflow runs. You can add extra expressions using **And, And not, Or, Or not** to create complex conditionals, and apply the workflow more granularly across your organization. Lifecycle Workflows supports a [rich set of user properties](/graph/api/resources/identitygovernance-rulebasedsubjectset#supported-user-properties-and-query-parameters) for configuring the scope.
 
 [![Extra expressions.](media/understanding-lifecycle-workflows/workflow-8.png)](media/understanding-lifecycle-workflows/workflow-8.png#lightbox)
 
@@ -164,7 +165,7 @@ For a detailed guide on setting the execution conditions for a workflow, see: [C
 
 While newly created workflows are enabled by default, scheduling is an option that must be enabled manually. To verify whether the workflow is scheduled, you can view the **Scheduled** column. 
 
-Once scheduling is enabled, the workflow will be evaluated every three hours to determine whether or not it should run based on the execution conditions.
+Once scheduling is enabled, the workflow is evaluated every three hours to determine whether or not it should run based on the execution conditions.
 
  [![Workflow template schedule.](media/understanding-lifecycle-workflows/workflow-10.png)](media/understanding-lifecycle-workflows/workflow-10.png#lightbox)