Merge pull request #210788 from MicrosoftDocs/main

Publish Live, Sunday 4 PM PT, 9/11

Author: LJSpiller

articles/active-directory/governance/TOC.yml

@@ -89,6 +89,8 @@
       href: lifecycle-workflow-extensibility.md
     - name: Versioning (Preview)
       href: lifecycle-workflow-versioning.md 
+    - name: Workflow Audit logs
+      href: lifecycle-workflow-audits.md
     - name: Workflow History (Preview)
       href: lifecycle-workflow-history.md     
 - name: How-to guides

articles/active-directory/governance/how-to-lifecycle-workflow-sync-attributes.md

@@ -25,8 +25,6 @@ The following table shows the scheduling (trigger) relevant attributes and the m
 |employeeHireDate|DateTimeOffset|Yes|Yes|Yes|
 |employeeLeaveDateTime|DateTimeOffset|Not currently(manually setting supported)|Not currently(manually setting supported)|Not currently(manually setting supported)|
 
-These attributes **are not** automatically populated using such synchronization methods such as Azure AD Connect or Azure AD Connect cloud sync.
-
 > [!NOTE]
 > Currently, automatic synchronization of the employeeLeaveDateTime attribute for HR Inbound scenarios is not available. To take advantaged of leaver scenarios, you can set the employeeLeaveDateTime manually. Manually setting the attribute can be done in the portal or with Graph. For more information see [User profile in Azure](../fundamentals/active-directory-users-profile-azure-portal.md) and [Update user](/graph/api/user-update?view=graph-rest-beta&tabs=http).
 

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

@@ -0,0 +1,48 @@
+---
+title: Auditing Lifecycle Workflows
+description: Information about audit logs with Lifecycle Workflows
+author: owinfreyATL
+ms.author: owinfrey
+manager: amycolannino
+ms.service: active-directory
+ms.workload: identity
+ms.topic: conceptual 
+ms.date: 08/01/2022
+ms.custom: template-concept 
+---
+
+# Auditing Lifecycle Workflows
+
+Workflows created using Lifecycle Workflows allow for the automation of lifecycle task for users no matter where they fall in the Joiner-Mover-Leaver (JML) model of their identity lifecycle in your organization. Making sure workflows are processed correctly is an important part of an organization's lifecycle management process. Workflows that aren't processed correctly can lead to many issues in terms of security and compliance. With audit logs, every action that Lifecycle Workflows complete over a time-frame up to 30 days are recorded.
+
+## Audit Logs
+
+Every time a workflow is processed, an event is logged. These events are stored in the **Audit Logs** section, and can be used to gain information about workflows for historical, and auditing, purposes. 
+
+:::image type="content" source="media/lifecycle-workflow-audits/audit-logs-concept.png" alt-text="Screenshot of a workflow audit log.":::
+
+On the **Audit Log** page you're presented a sequential list, by date, of every action Lifecycle Workflows has taken. From this information you're able to filter based on the following parameters:
+
+|Filter  |Description  |
+|---------|---------|
+|Date     | You can filter a specific range for the audit logs from as short as 24 hours up to 30 days.        |
+|Date option     | You can filter by your tenant's local time, or by UTC.        |
+|Service     | The Lifecycle Workflow service.        |
+|Category     | Categories of the event being logged. Separated into <br><br>  **All**- All events logged by Lifecycle Workflows.<br><br>  **TaskManagement**- Task specific related events logged by Lifecycle Workflows. <br><br> **WorkflowManagement**- Events dealing with the workflow itself.       |
+|Activity     |  You can filter based on specific activities, which are based on categories.       |
+
+After filtering this information, you're also able to see other information in the log such as:
+
+- **Status**: Whether or not the logged event was successful or not.
+- **Status Reason**: If the event failed, a reason is given why.
+- **Target(s)**: Who the logged event ran for. Information given as their Azure Active Directory object ID.
+- **Initiated by (actor)**: Who did the event being logged. Information given by the user name. 
+
+
+
+## Next steps
+
+- [Lifecycle Workflow History](lifecycle-workflow-history.md)
+- [Check the status of a workflow (Preview)](check-status-workflow.md)
+
+

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

@@ -16,37 +16,11 @@ ms.custom: template-concept
 
 
 
-Workflows created using Lifecycle Workflows allow for the automation of lifecycle task for users no matter where they fall in the Joiner-Mover-Leaver (JML) model of their identity lifecycle in your organization. Making sure workflows are processed correctly is an important part of an organization's lifecycle management process. Workflows that aren't processed correctly can lead to many issues in terms of security and compliance. With Audit logs every action that Lifecycle Workflows complete are recorded. With history features, Lifecycle Workflows allow you to specify workflow events based on user, runs, or task summaries. This reporting feature allows you to quickly see what ran for who, and rather or not it was successful. In this article you'll learn the difference between auditing logs and 3 different type of history summaries you can query with Lifecycle Workflows. You'll also learn when you would use each when getting more information about how your workflows were utilized for users in your organization.
-
-
-
-## Audit Logs
-
-Every time a workflow is processed, an event is logged. These events are stored in the **Audit Logs** section, and can be used to gain information about workflows for historical, and auditing, purposes. 
-
-:::image type="content" source="media/lifecycle-workflow-history/audit-logs-concept.png" alt-text="Screenshot of a workflow audit log.":::
-
-On the **Audit Log** page you're presented a sequential list, by date, of every action Lifecycle Workflows has taken. From this information you're able to filter based on the following parameters:
-
-
-|Filter  |Description  |
-|---------|---------|
-|Date     | You can filter a specific range for the audit logs from as short as 24 hours up to 30 days.        |
-|Date option     | You can filter by your tenant's local time, or by UTC.        |
-|Service     | The Lifecycle Workflow service.        |
-|Category     | Categories of the event being logged. Separated into <br><br>  **All**- All events logged by Lifecycle Workflows.<br><br>  **TaskManagement**- Task specific related events logged by Lifecycle Workflows. <br><br> **WorkflowManagement**- Events dealing with the workflow itself.       |
-|Activity     |  You can filter based on specific activities, which are based on categories.       |
-
-After filtering this information, you're also able to see other information in the log such as:
-
-- **Status**: Whether or not the logged event was successful or not.
-- **Status Reason**: If the event failed, a reason is given why.
-- **Target(s)**: Who the logged event ran for. Information given as their Azure Active Directory object ID.
-- **Initiated by (actor)**: Who did the event being logged. Information given by the user name. 
+Workflows created using Lifecycle Workflows allow for the automation of lifecycle task for users no matter where they fall in the Joiner-Mover-Leaver (JML) model of their identity lifecycle in your organization. Making sure workflows are processed correctly is an important part of an organization's lifecycle management process. Workflows that aren't processed correctly can lead to many issues in terms of security and compliance. With Lifecycle Workflow's history features, you can specify which workflow events you want to view a history of based on user, runs, or task summaries. This reporting feature allows you to quickly see what ran for who, and rather or not it was successful. Along with the summaries in these specific areas, you're also able to view detailed information about each specific event recorded in their respective summary section. In this article you'll learn the difference between the three different type of history summaries, and details, you can query with Lifecycle Workflows. You'll also learn when you would use each when getting more information about how your workflows were utilized for users in your organization. For detailed information about every action Lifecycle Workflows take, see: [Auditing Lifecycle Workflows](lifecycle-workflow-audits.md).
 
 ## Lifecycle Workflow History Summaries
 
-While the large set of information contained in audit logs can be useful for compliance reasons, for regular administration use it might be too much information. To make this large set of information processed easier to read, Lifecycle Workflows provide summaries for quick use. You can view these history summaries in three ways:
+Lifecycle Workflows introduce a history feature based on summaries and details. These history summaries allow you to quickly get information about for who a workflow ran, and whether or not this run was successful or not. This is valuable because the large set of information given by audit logs might become too numerous to be efficiently used. To make a large set of information processed easier to read, Lifecycle Workflows provide summaries for quick use. You can view these history summaries in three ways:
 
 - **Users summary**: Shows a summary of users processed by a workflow, and which tasks failed, successfully, and totally ran for each specific user. 
 - **Runs summary**: Shows a summary of workflow runs in terms of the workflow. Successful, failed, and total task information when workflow runs are noted.
@@ -61,7 +35,7 @@ User summaries allow you to view workflow information through the lens of users
 :::image type="content" source="media/lifecycle-workflow-history/users-summary-concept.png" alt-text="Screenshot of a workflow user summary.":::
 
 
-Within the user summary you're able to find the following information:
+Within the user summary, you're able to find the following information:
 
 
 |Parameter  |Description  |
@@ -72,8 +46,9 @@ Within the user summary you're able to find the following information:
 |Total tasks     | The total number of tasks processed for users in a workflow during the selected time frame.        |
 |Failed tasks     |  The total number of failed tasks processed for users in a workflow during the selected time frame.       |
 
+### User history details
 
-User summaries allow you to filter based on:
+User detailed history information allows you to filter for specific information based on:
 
 - **Date**: You can filter a specific range from as short as 24 hours up to 30 days of when workflow ran.
 - **Status**: You can filter a specific status of the user processed. The supported statuses are: **Completed**, **In Progress**, **Queued**, **Canceled**, **Completed with errors**, and **Failed**. 
@@ -89,7 +64,7 @@ Runs summaries allow you to view workflow information through the lens of its ru
 
 :::image type="content" source="media/lifecycle-workflow-history/runs-status-concept.png" alt-text="Screenshot of a workflow runs summary.":::
 
-Within the runs summary you're able to find the following information:
+Within the runs summary, you're able to find the following information:
 
 
 |Parameter  |Description  |
@@ -99,7 +74,9 @@ Within the runs summary you're able to find the following information:
 |Failed     | Workflows that failed to run.        |
 |Failed tasks     | Workflows that ran with failed tasks.        |
 
-Runs summaries allow you to filter based on:
+### Runs history details
+
+Runs detailed history information allows you to filter for specific information based on:
 
 - **Date**: You can filter a specific range from as short as 24 hours up to 30 days of when workflow ran.
 - **Status**: You can filter a specific status of the workflow run. The supported statuses are: **Completed**, **In Progress**, **Queued**, **Canceled**, **Completed with errors**, and **Failed**. 
@@ -115,7 +92,7 @@ Task summaries allow you to view workflow information through the lens of its ta
 
 :::image type="content" source="media/lifecycle-workflow-history/task-summary-concept.png" alt-text="Screenshot of a workflow task summary.":::
 
-Within the tasks summary you're able to find the following information:
+Within the tasks summary, you're able to find the following information:
 
 
 |Parameter  |Description  |
@@ -125,7 +102,10 @@ Within the tasks summary you're able to find the following information:
 |Failed     | The number of failed processed tasks by a workflow.         |
 |Unprocessed     | The number of unprocessed tasks by a workflow.        |
 
-Task summaries allow you to filter based on:
+
+### Task history details
+
+Task detailed history information allows you to filter for specific information based on:
 
 - **Date**: You can filter a specific range from as short as 24 hours up to 30 days of when workflow ran.
 - **Status**: You can filter a specific status of the workflow run. The supported statuses are: **Completed**, **In Progress**, **Queued**, **Canceled**, **Completed with errors**, and **Failed**. 

articles/active-directory/governance/media/lifecycle-workflow-history/audit-logs-concept.png renamed to articles/active-directory/governance/media/lifecycle-workflow-audits/audit-logs-concept.png

@@ -22,8 +22,6 @@
       href: advisor-alerts-arm.md
 - name: Concepts
   items:
-  - name: Security baseline
-    href: /security/benchmark/azure/baselines/advisor-security-baseline?toc=/azure/advisor/toc.json
   - name: Recommendations
     items:
     - name: Cost
@@ -34,6 +32,8 @@
       href: advisor-reference-performance-recommendations.md
     - name: Reliability
       href: advisor-reference-reliability-recommendations.md    
+    - name: Security
+      href: /azure/defender-for-cloud/recommendations-reference
 - name: Samples 
   items:
   - name: Azure Resource Graph queries
@@ -62,6 +62,8 @@
     href: azure-advisor-score.md
 - name: Reference
   items:
+  - name: Security baseline
+    href: /security/benchmark/azure/baselines/advisor-security-baseline?toc=/azure/advisor/toc.json
   - name: Defender for Cloud
     href: https://azure.microsoft.com/services/security-center/
   - name: SQL Database Advisor
@@ -91,4 +93,4 @@
   - name: Stack Overflow
     href: https://stackoverflow.com/search?q=azure+advisor
   - name: Code samples
-    href: /samples/browse/?products=azure
+    href: /samples/browse/?products=azure   

articles/advisor/toc.yml

@@ -5,7 +5,7 @@ ms.topic: conceptual
 author: EdB-MSFT
 ms.author: edbaynash
 ms.subservice: autoscale
-ms.date: 07/18/2022
+ms.date: 09/11/2022
 ms.custom: references_regions
 ms.reviewer: riroloff
 ---
@@ -26,12 +26,12 @@ Predictive autoscale adheres to the scaling boundaries you've set for your virtu
 
 The following limitations apply during public preview. Predictive autoscale:
 
-- Only works for workloads exhibiting cyclical CPU usage patterns.
-- Only can be enabled for virtual machine scale sets.
-- Only supports using the metric *Percentage CPU* with the aggregation type *Average*.
-- Only supports scale-out. You can't use predictive autoscale to scale in.
+- Predictive autoscale is for workloads exhibiting cyclical CPU usage patterns.
+- Support is only available for virtual machine scale sets.
+- The *Percentage CPU* metric with the aggregation type *Average* is the only metric currently supported.
+- Predictive autoscale supports scale-out only. Configure standard autoscale to manage scaling in.
+- Predictive autoscale is only available for the Azure Commercial cloud. Azure Government clouds are not currently supported.
 
-You must enable standard (or reactive) autoscale to manage scale-in.
 
 ## Enable predictive autoscale or forecast only with the Azure portal
 

articles/azure-monitor/autoscale/autoscale-predictive.md

@@ -27,7 +27,7 @@ The trial account option is not available on the Azure Government cloud. For oth
 
 You can later create a paid account where you're not limited by the quota. Two types of paid accounts are available to you: Azure Resource Manager (recommended) and classic. The main difference between the two is account management platform. 
 
-* ARM-based accounts management is built on Azure, which enables using [Azure RBAC](../role-based-access-control/overview.md).
+* ARM-based accounts management is built on Azure, which enables using [Azure RBAC](../role-based-access-control/overview.md) (recommended).
 * Classic accounts are built on the API Management.
 
 With the paid option, you pay for indexed minutes, for more information, see [Azure Video Indexer pricing](https://azure.microsoft.com/pricing/details/video-indexer/).

articles/azure-video-indexer/accounts-overview.md

@@ -8,14 +8,9 @@ ms.author: juliako
 
 # People's featured clothing (preview)
 
-When indexing a video using Azure Video Indexer advanced video settings, you can view the featured clothing of an observed person. The featured clothing insight provides the following information: key items worn by individuals within a video and the specific time in which the clothing appears. 
+When indexing a video using Azure Video Indexer advanced video settings, you can view the featured clothing of an observed person. The insight provides information of key items worn by individuals within a video and the timestamp in which the clothing appears. This allows high-quality in-video contextual advertising, where relevant clothing ads are matched with the specific time within the video in which they are viewed.
 
-This insight enables scenarios like 
-
-* Placing more targeted ads
-* Creating a summary of the most interesting outfits appearing in the video
-
-The article discusses how to view the featured clothing insight and how the featured clothing images are ranked.
+This article discusses how to view the featured clothing insight and how the featured clothing images are ranked.
 
 ## Viewing featured clothing
 
@@ -26,7 +21,7 @@ The featured clothing insight is available when indexing your file by choosing t
 The featured clothing images are ranked based on some of the following factors: key moments of the video, general emotions from text or audio. The `id` property indicates the ranking index. For example, `"id": 1` signifies the most important featured clothing.
 
 > [!NOTE]
-> The featured clothing currently can be viewed only from the artifact file.  
+> The featured clothing currently can only be viewed from the artifact file.  
 
 1. In the right-upper corner, select to download the artifact zip file: **Download** -> **Artifact (ZIP)**
 1. Open `featuredclothing.zip`. 

articles/azure-video-indexer/observed-people-featured-clothing.md

@@ -58,11 +58,13 @@ The [Azure Video Indexer website](https://vi.microsoft.com) session length was e
 
 ## July 2022
 
-### Featured clothing insight (preview)
+### The featured clothing insight (preview)
 
-When indexing a video using Azure Video Indexer advanced video settings, you can view the featured clothing of an observed person. The featured clothing insight provides information of key items worn by individuals within a video and the specific time in which the clothing appears. Based on this insight, you can enable more targeted ads placement.
+The featured clothing insight enables more targeted ads placement. 
 
-For details on how featured clothing images are ranked and how to view this insight, see [observed people featured clothing](observed-people-featured-clothing.md).
+The insight provides information of key items worn by individuals within a video and the timestamp in which the clothing appears. This allows high-quality in-video contextual advertising, where relevant clothing ads are matched with the specific time within the video in which they are viewed.
+
+To view the featured clothing of an observed person, you have to index the video using Azure Video Indexer advanced video settings. For details on how featured clothing images are ranked and how to view this insight, see [featured clothing](observed-people-featured-clothing.md).
 
 ## June 2022
 
@@ -302,7 +304,7 @@ Azure Video Indexer has a new [Developer Portal](https://api-portal.videoindexer
 
 SDK is now available to embed Azure Video Indexer's insights widget in your own service and customize its style and data. The SDK supports the standard Azure Video Indexer insights widget and a fully customizable insights widget. Code sample is available in [Azure Video Indexer GitHub repository](https://github.com/Azure-Samples/media-services-video-indexer/tree/master/Embedding%20widgets/widget-customization). With this advanced customization capabilities, solution developer can apply custom styling and bring customer’s own AI data and present that in the insight widget (with or without Azure Video Indexer insights).
 
-### Azure Video Indexer deployed in the US North Central , US West and Canada Central
+### Azure Video Indexer deployed in the US North Central, US West and Canada Central
 
 You can now create an Azure Video Indexer paid account in the US North Central, US West and Canada Central regions