Merge pull request #213334 from MicrosoftDocs/main

merge main to Live, Sunday 4 PM

Author: jborsecnik

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

@@ -20,27 +20,7 @@ Lifecycle Workflows come with many pre-configured tasks that are designed to aut
 Lifecycle Workflow's built-in tasks each include an identifier, known as **taskDefinitionID**, and can be used to create either new workflows from scratch, or inserted into workflow templates so that they fit the needs of your organization. For more information on templates available for use with Lifecycle Workflows, see: [Lifecycle Workflow Templates](lifecycle-workflow-templates.md).
 
 
-
-Lifecycle Workflows currently support the following tasks:
-
-|Task  |taskdefinitionID  |Category  |
-|---------|---------|---------|
-|[Send welcome email to new hire](lifecycle-workflow-tasks.md#send-welcome-email-to-new-hire)     |   70b29d51-b59a-4773-9280-8841dfd3f2ea      | Joiner         |
-|[Generate Temporary Access Pass and send via email to user's manager](lifecycle-workflow-tasks.md#generate-temporary-access-pass-and-send-via-email-to-users-manager)     |  1b555e50-7f65-41d5-b514-5894a026d10d       | Joiner         |
-|[Add user to groups](lifecycle-workflow-tasks.md#add-user-to-groups)     |    22085229-5809-45e8-97fd-270d28d66910     | Joiner, Leaver
-|[Add user to teams](lifecycle-workflow-tasks.md#add-user-to-teams)      |  e440ed8d-25a1-4618-84ce-091ed5be5594       | Joiner, Leaver
-|[Enable user account](lifecycle-workflow-tasks.md#enable-user-account)     |    6fc52c9d-398b-4305-9763-15f42c1676fc     | Joiner, Leaver
-|[Run a custom task extension](lifecycle-workflow-tasks.md#run-a-custom-task-extension)    |    4262b724-8dba-4fad-afc3-43fcbb497a0e    | Joiner, Leaver
-|[Disable user account](lifecycle-workflow-tasks.md#disable-user-account)     |   1dfdfcc7-52fa-4c2e-bf3a-e3919cc12950      | Leaver
-|[Remove user from selected group](lifecycle-workflow-tasks.md#remove-user-from-selected-groups)     |   1953a66c-751c-45e5-8bfe-01462c70da3c      | Leaver
-|[Remove users from all groups](lifecycle-workflow-tasks.md#remove-users-from-all-groups)     |    b3a31406-2a15-4c9a-b25b-a658fa5f07fc     | Leaver
-|[Remove user from teams](lifecycle-workflow-tasks.md#remove-user-from-teams)    |    06aa7acb-01af-4824-8899-b14e5ed788d6     | Leaver        |
-|[Remove user from all teams](lifecycle-workflow-tasks.md#remove-users-from-all-teams)     |    81f7b200-2816-4b3b-8c5d-dc556f07b024     | Leaver        |
-|[Remove all license assignments from user](lifecycle-workflow-tasks.md#remove-all-license-assignments-from-user)     | 8fa97d28-3e52-4985-b3a9-a1126f9b8b4e         | Leaver
-|[Delete user](lifecycle-workflow-tasks.md#delete-user)    |    8d18588d-9ad3-4c0f-99d0-ec215f0e3dff     | Leaver         |
-|[Send email to manager before user last day](lifecycle-workflow-tasks.md#send-email-to-manager-before-user-last-day)    |    52853a3e-f4e5-4eb8-bb24-1ac09a1da935     | Leaver         |
-|[Send email on users last day](lifecycle-workflow-tasks.md#send-email-on-users-last-day)    |    9c0a1eaf-5bda-4392-9d9e-6e155bb57411     | Leaver         |
-|[Send offboarding email to users manager after their last day](lifecycle-workflow-tasks.md#send-offboarding-email-to-users-manager-after-their-last-day)    |    6f22ddd4-b3a5-47a4-a846-0d7c201a49ce     | Leaver         |
+[!INCLUDE [Lifecylce Workflows tasks table](../../../includes/lifecycle-workflows-tasks-table.md)]
 
 ## Common task parameters (preview)
 

articles/azure-monitor/agents/azure-monitor-agent-windows-client.md

@@ -259,6 +259,8 @@ Invoke-RestMethod -Uri $request -Headers $AuthenticationHeader -Method PUT -Body
 
 #2. Create Monitored Object
 
+# "location" property value under the "body" section should be the Azure region where the MO object would be stored. It should be the "same region" where you created the Data Collection Rule. This is the location of the region from where agent communications would happen.
+
 $request = "https://management.azure.com/providers/Microsoft.Insights/monitoredObjects/$TenantID`?api-version=2021-09-01-preview"
 $body = @'
 {
@@ -271,7 +273,7 @@ $body = @'
 $Respond = Invoke-RestMethod -Uri $request -Headers $AuthenticationHeader -Method PUT -Body $body -Verbose
 $RespondID = $Respond.id
 
-#########
+##########################
 
 #3. Associate DCR to Monitored Object
 

articles/azure-resource-manager/bicep/scenarios-rbac.md

@@ -29,7 +29,7 @@ If you don't explicitly specify the scope, Bicep uses the file's `targetScope`.
 ::: code language="bicep" source="~/azure-docs-bicep-samples/samples/scenarios-rbac/scope-default.bicep" highlight="4" :::
 
 > [!TIP]
-> Ensure you use the smallest scope required for your requirements.
+> Use the smallest scope that you need to meet your requirements.
 >
 > For example, if you need to grant a managed identity access to a single storage account, it's good security practice to create the role assignment at the scope of the storage account, not at the resource group or subscription scope.
 

articles/cognitive-services/Speech-Service/includes/quickstarts/call-center/azure-prerequisites.md

@@ -15,4 +15,4 @@ ms.author: eur
 > [!IMPORTANT]
 > This quickstart requires access to [conversation summarization](/azure/cognitive-services/language-service/summarization/how-to/conversation-summarization). To get access, you must submit an [online request](https://aka.ms/applyforconversationsummarization/) and have it approved. 
 > 
-> The `--languageKey` and `--languageEndpoint` values in this quickstart must correspond to a resource that's in one of the regions supported by the [conversation summarization API](https://aka.ms/convsumregions). 
+> The `--languageKey` and `--languageEndpoint` values in this quickstart must correspond to a resource that's in one of the regions supported by the [conversation summarization API](https://aka.ms/convsumregions): `eastus`, `northeurope`, and `uksouth`. 

articles/cognitive-services/Speech-Service/includes/quickstarts/call-center/example-output.md

@@ -40,7 +40,7 @@ The `transcription` property contains a JSON object with the results of sentimen
 }   
 ```
 
-The `conversationAnalyticsResults` property contains a JSON object with the results of the conversation summarization analysis. Here's an example, with redactions for brevity:
+The `conversationAnalyticsResults` property contains a JSON object with the results of the conversation PII and conversation summarization analysis. Here's an example, with redactions for brevity:
 ```json
 {
   "conversationAnalyticsResults": {

articles/cognitive-services/Speech-Service/includes/quickstarts/call-center/usage-arguments.md

@@ -7,7 +7,7 @@ ms.author: eur
 ---
 
 > [!IMPORTANT]
-> You can use a <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne" title="Create a Cognitive Services resource"  target="_blank">Cognitive Services multi-service</a> resource or separate <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics"  title="Create a Language resource"  target="_blank">Language</a> and <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices"  title="Create a Speech resource"  target="_blank">Speech</a> resources. In either case, the `--languageKey` and `--languageEndpoint` values must correspond to a resource that's in one of the regions supported by the [conversation summarization API](https://aka.ms/convsumregions). 
+> You can use a <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne" title="Create a Cognitive Services resource"  target="_blank">Cognitive Services multi-service</a> resource or separate <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics"  title="Create a Language resource"  target="_blank">Language</a> and <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesSpeechServices"  title="Create a Speech resource"  target="_blank">Speech</a> resources. In either case, the `--languageKey` and `--languageEndpoint` values must correspond to a resource that's in one of the regions supported by the [conversation summarization API](https://aka.ms/convsumregions): `eastus`, `northeurope`, and `uksouth`.  
 
 Connection options include:
 
@@ -21,7 +21,7 @@ Input options include:
 
 - `--input URL`: Input audio from URL. You must set either the `--input` or `--jsonInput` option. 
 - `--jsonInput FILE`: Input an existing batch transcription JSON result from FILE. With this option, you only need a Language resource to process a transcription that you already have. With this option, you don't need an audio file or a Speech resource. Overrides `--input`. You must set either the `--input` or `--jsonInput` option.
-- `--stereo`: Use stereo audio format. If stereo isn't specified, then mono 16khz 16 bit PCM wav files are assumed. Diarization of mono files is used to separate multiple speakers. Diarization of stereo files isn't supported, since 2-channel stereo files should already have one speaker per channel.
+- `--stereo`: Indicates that the audio via ```input URL` should be in stereo format. If stereo isn't specified, then mono 16khz 16 bit PCM wav files are assumed. Diarization of mono files is used to separate multiple speakers. Diarization of stereo files isn't supported, since 2-channel stereo files should already have one speaker per channel.
 - `--certificate`: The PEM certificate file. Required for C++. 
 
 Language options include:
@@ -32,4 +32,4 @@ Language options include:
 Output options include:
 
 - `--help`: Show the usage help and stop
-- `--output FILE`: Output the transcription, sentiment, and conversation summaries in JSON format to a text file. For more information, see [output examples](/azure/cognitive-services/speech-service/call-center-quickstart#check-results).
+- `--output FILE`: Output the transcription, sentiment, conversation PII, and conversation summaries in JSON format to a text file. For more information, see [output examples](/azure/cognitive-services/speech-service/call-center-quickstart#check-results).

articles/load-testing/how-to-create-and-run-load-test-with-jmeter-script.md

@@ -7,7 +7,7 @@ ms.service: load-testing
 ms.topic: how-to
 author: ntrogh
 ms.author: nicktrog
-ms.date: 06/10/2022
+ms.date: 10/02/2022
 adobe-target: true
 ---
 
@@ -34,9 +34,11 @@ Use cases for creating a load test with an existing JMeter script include:
 
 ## Create an Apache JMeter script
 
-If you don't have an existing Apache JMeter script, you'll create a sample script to load test a single web application endpoint. For more information about creating an Apache JMeter script, see [Getting started with Apache JMeter](https://jmeter.apache.org/usermanual/get-started.html).
+If you already have a script, you can skip to [Create a load test](#create-a-load-test). In this section, you'll create a sample JMeter test script to load test a single web endpoint.
 
-If you already have a script, you can skip to [Create a load test](#create-a-load-test).
+You can also use the [Apache JMeter test script recorder](https://jmeter.apache.org/usermanual/jmeter_proxy_step_by_step.html) to record the requests while navigating the application in a browser. Alternatively, [import cURL commands](https://jmeter.apache.org/usermanual/curl.html) to generate the requests in the JMeter test script.
+
+To create a sample JMeter test script: 
 
 1. Create a *SampleTest.jmx* file on your local machine:
 
@@ -78,7 +80,7 @@ If you already have a script, you can skip to [Create a load test](#create-a-loa
           </ThreadGroup>
           <hashTree>
             <HTTPSamplerProxy guiclass="HttpTestSampleGui" testclass="HTTPSamplerProxy" testname="HTTP request" enabled="true">
-              <elementProp name="HTTPsampler.Arguments" elementType="Arguments" guiclass="HTTPArgumentsPanel" testclass="Arguments" testname="User Defined Variables" enabled="true">
+              <elementProp name="HTTPsampler.Arguments" elementType="Arguments" guiclass="HTTPArgumentsPanel" testclass="Arguments" testname="Sample web test" enabled="true">
                 <collectionProp name="Arguments.arguments"/>
               </elementProp>
               <stringProp name="HTTPSampler.domain"></stringProp>
@@ -113,10 +115,9 @@ If you already have a script, you can skip to [Create a load test](#create-a-loa
 
 ## Create a load test
 
-To create a load test in Azure Load Testing, you have to specify a JMeter script. This script defines the [test plan](./how-to-create-manage-test.md#test-plan) for the load test. You can create multiple load tests in an Azure Load Testing resource.
+When you create a load test in Azure Load Testing, you specify a JMeter script to define the [load test plan](./how-to-create-manage-test.md#test-plan). An Azure Load Testing resource can contain multiple load tests.
 
-> [!NOTE]
-> When you [create a quick test by using a URL](./quickstart-create-and-run-load-test.md), Azure Load Testing automatically generates the JMeter script.
+When you [create a quick test by using a URL](./quickstart-create-and-run-load-test.md), Azure Load Testing automatically generates the corresponding JMeter script.
 
 To create a load test using an existing JMeter script in the Azure portal:
 
@@ -139,14 +140,11 @@ To create a load test using an existing JMeter script in the Azure portal:
 
 1. Select **Review + create**. Review all settings, and then select **Create** to create the load test.
 
-    :::image type="content" source="./media/how-to-create-and-run-load-test-with-jmeter-script/create-new-test-review.png" alt-text="Screenshot that shows the tab for reviewing and creating a test." :::
-
-> [!NOTE]
-> You can update the test configuration at any time, for example to upload a different JMX file. Choose your test in the list of tests, and then select **Edit**.
+You can update the test configuration at any time, for example to upload a different JMX file. Choose your test in the list of tests, and then select **Edit**.
 
 ## Run the load test
 
-When Azure Load Testing starts your load test, it will first deploy the JMeter script and any other files onto test engine instances and run the test.
+When Azure Load Testing starts your load test, it will first deploy the JMeter script, and any other files onto test engine instances, and then start the load test.
 
 If you selected **Run test after creation**, your load test will start automatically. To manually start the load test you created earlier, perform the following steps:
 
@@ -161,14 +159,16 @@ If you selected **Run test after creation**, your load test will start automatic
     > [!TIP]
     > You can stop a load test at any time from the Azure portal.
 
-While the test runs and after it finishes, you can view the test run details, statistics, and metrics in the test run dashboard.
+1. Notice the test run details, statistics, and client metrics in the Azure portal.
 
-:::image type="content" source="./media/how-to-create-and-run-load-test-with-jmeter-script/test-run-aggregated-by-percentile.png" alt-text="Screenshot that shows the test run dashboard." :::
+    :::image type="content" source="./media/how-to-create-and-run-load-test-with-jmeter-script/test-run-aggregated-by-percentile.png" alt-text="Screenshot that shows the test run dashboard." :::
 
-## Next steps
+    Use the run statistics and error information to identify performance and stability issues for your application under load.
 
-- To learn more about [creating and managing tests](./how-to-create-manage-test.md).
+## Next steps
 
-- To learn how to export test results, see [Export test results](./how-to-export-test-results.md).
+You've created a cloud-based load test based on an existing JMeter test script. For Azure-hosted applications, you can also [monitor server-side metrics](./how-to-monitor-server-side-metrics.md) for further application insights.
 
-- To learn how to monitor server side metrics, see [Monitor server side metrics](./how-to-monitor-server-side-metrics.md).
+- Learn how to [export test results](./how-to-export-test-results.md).
+- Learn how to [parameterize a load test with environment variables](./how-to-parameterize-load-tests.md).
+- Learn how to [configure your test for high-scale load](./how-to-high-scale-load.md).

articles/load-testing/media/how-to-create-and-run-load-test-with-jmeter-script/create-new-test-review.png

@@ -35,6 +35,8 @@
   items:
   - name: Role definitions
     href: role-definitions.md
+  - name: Role assignments
+    href: role-assignments.md
   - name: Scope
     href: scope-overview.md
   - name: Best practices