Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into asc-melvyn-containerwork

Author: memildin

.openpublishing.redirection.json

@@ -7556,6 +7556,46 @@
       "redirect_url": "/azure/azure-monitor/app/java-get-started",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-disable-instrumentation-engine.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-disable-monitoring.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-enable-instrumentation-engine.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-enable-monitoring.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-get-config.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-get-status.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-set-config.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-monitor/app/status-monitor-v2-api-start-trace.md",
+      "redirect_url": "/azure/azure-monitor/app/status-monitor-v2-api-reference.md",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/application-insights/app-insights-mobile-hockeyapp.md",
       "redirect_url": "/azure/azure-monitor/app/hockeyapp-bridge-app",

articles/active-directory-b2c/stringcollection-transformations.md

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 02/27/2020
+ms.date: 04/21/2020
 ms.author: mimart
 ms.subservice: B2C
 ---
@@ -155,4 +155,38 @@ Following example checks whether the `roles` stringCollection claim type contain
 - Output claims:
     - **outputClaim**: "true"
 
+## StringCollectionContainsClaim
 
+Checks if a StringCollection claim type contains a claim value.
+
+| Item | TransformationClaimType | Data Type | Notes |
+| ---- | ----------------------- | --------- | ----- |
+| InputClaim | collection | stringCollection | The claim type which is to be searched. |
+| InputClaim | item|string| The claim type that contains the value to search.|
+|InputParameter|ignoreCase|string|Specifies whether this comparison should ignore the case of the strings being compared.|
+| OutputClaim | outputClaim | boolean | The ClaimType that is produced after this ClaimsTransformation has been invoked. A boolean indicator if the collection contains such a string |
+
+Following example checks whether the `roles` stringCollection claim type contains the value of the `role` claim type.
+
+```XML
+<ClaimsTransformation Id="HasRequiredRole" TransformationMethod="StringCollectionContainsClaim">
+  <InputClaims>
+    <InputClaim ClaimTypeReferenceId="roles" TransformationClaimType="collection" />
+    <InputClaim ClaimTypeReferenceId="role" TransformationClaimType="item" />
+  </InputClaims>
+  <InputParameters>
+    <InputParameter Id="ignoreCase" DataType="string" Value="true" />
+  </InputParameters>
+  <OutputClaims>
+    <OutputClaim ClaimTypeReferenceId="hasAccess" TransformationClaimType="outputClaim" />
+  </OutputClaims>
+</ClaimsTransformation> 
+```
+
+- Input claims:
+    - **collection**: ["reader", "author", "admin"]
+    - **item**: "Admin"
+- Input parameters:
+    - **ignoreCase**: "true"
+- Output claims:
+    - **outputClaim**: "true"

articles/app-service/webjobs-sdk-get-started.md

@@ -131,7 +131,7 @@ In this section, you set up console logging that uses the [ASP.NET Core logging
     * Disables [dashboard logging](https://github.com/Azure/azure-webjobs-sdk/wiki/Queues#logs). The dashboard is a legacy monitoring tool, and dashboard logging is not recommended for high-throughput production scenarios.
     * Adds the console provider with default [filtering](webjobs-sdk-how-to.md#log-filtering).
 
-Now, you can add a function that is triggered by messages arriving in an [Azure Storage queue](../azure-functions/functions-bindings-storage-queue.md).
+Now, you can add a function that is triggered by messages arriving in an Azure Storage queue.
 
 ## Install the Storage binding extension
 
@@ -181,7 +181,7 @@ Starting with version 3.x, you must explicitly install the Storage binding exten
 
    The `QueueTrigger` attribute tells the runtime to call this function when a new message is written on an Azure Storage queue called `queue`. The contents of the queue message are provided to the method code in the `message` parameter. The body of the method is where you process the trigger data. In this example, the code just logs the message.
 
-   The `message` parameter doesn't have to be a string. You can also bind to a JSON object, a byte array, or a [CloudQueueMessage](https://docs.microsoft.com/dotnet/api/microsoft.azure.storage.queue.cloudqueuemessage) object. [See Queue trigger usage](../azure-functions/functions-bindings-storage-queue-trigger.md#usage). Each binding type (such as queues, blobs, or tables) has a different set of parameter types that you can bind to.
+   The `message` parameter doesn't have to be a string. You can also bind to a JSON object, a byte array, or a [CloudQueueMessage](https://docs.microsoft.com/dotnet/api/microsoft.azure.storage.queue.cloudqueuemessage) object. [See Queue trigger usage](/azure/azure-functions/functions-bindings-storage-queue-trigger?tabs=csharp#usage). Each binding type (such as queues, blobs, or tables) has a different set of parameter types that you can bind to.
 
 ## Create a storage account
 
@@ -277,7 +277,7 @@ In this section, you build and run the project locally and trigger the function
 
    Because you used the `QueueTrigger` attribute in the `ProcessQueueMessage` function, the WeJobs SDK runtime listens for queue messages when it starts up. It finds a new queue message in the queue named *queue* and calls the function.
 
-   Due to [queue polling exponential backoff](../azure-functions/functions-bindings-storage-queue-trigger.md#polling-algorithm), it might take as long as 2 minutes for the runtime to find the message and invoke the function. This wait time can be reduced by running in [development mode](webjobs-sdk-how-to.md#host-development-settings).
+   Due to [queue polling exponential backoff](/azure/azure-functions/functions-bindings-storage-queue-trigger?tabs=csharp#polling-algorithm), it might take as long as 2 minutes for the runtime to find the message and invoke the function. This wait time can be reduced by running in [development mode](webjobs-sdk-how-to.md#host-development-settings).
 
    The console output looks like this:
 
@@ -441,7 +441,7 @@ During deployment, you create an app service instance in which to run your funct
 1. Refresh the **Queue** page, and the new message disappears because it has been processed by the function running in Azure.
 
    > [!TIP]
-   > When you're testing in Azure, use [development mode](webjobs-sdk-how-to.md#host-development-settings) to ensure that a queue trigger function is invoked right away and avoid delays due to [queue polling exponential backoff](../azure-functions/functions-bindings-storage-queue-trigger.md#polling-algorithm).
+   > When you're testing in Azure, use [development mode](webjobs-sdk-how-to.md#host-development-settings) to ensure that a queue trigger function is invoked right away and avoid delays due to [queue polling exponential backoff](/azure/azure-functions/functions-bindings-storage-queue-trigger?tabs=csharp#polling-algorithm).
 
 ### View logs in Application Insights
 

articles/automation/TOC.yml

@@ -44,35 +44,35 @@
   items:
     - name: Automation Account
       items:
-        - name: Create using Azure portal
+        - name: Create Automation account using Azure portal
           href: automation-create-standalone-account.md
-        - name: Create with Resource Manager template
+        - name: Create Automation account with Resource Manager template
           href: automation-create-account-template.md
         - name: Manage an Automation Run As account
           href: manage-runas-account.md
-        - name: Role permissions and security
+        - name: Manage role permissions and security
           href: automation-role-based-access-control.md
-        - name: Move Automation Account to another subscription
+        - name: Move Automation account to another subscription
           href: how-to/move-account.md
         - name: Migrate from System Center Orchestrator
           href: automation-orchestrator-migration.md
-    - name: Manage shared resources
+    - name: Shared resources
       items:
-        - name: Certificates
+        - name: Manage certificates
           href: shared-resources/certificates.md
-        - name: Connections
+        - name: Manage connections
           href: automation-connections.md
-        - name: Credentials
+        - name: Manage credentials
           href: shared-resources/credentials.md
-        - name: PowerShell modules
+        - name: Manage PowerShell modules
           items:
             - name: Manage modules in Azure Automation
               href: shared-resources/modules.md
             - name: Update Azure PowerShell modules
               href: automation-update-azure-modules.md
-        - name: Schedules
+        - name: Manage schedules
           href: shared-resources/schedules.md
-        - name: Variables
+        - name: Manage variables
           href: shared-resources/variables.md
         - name: Manage Python 2 packages
           href: python-packages.md
@@ -104,13 +104,13 @@
               href: automation-webhooks.md
             - name: Track updated files with watcher task
               href: automation-watchers-tutorial.md
-            - name: Working with the Graphical runbook SDK
+            - name: Work with the Graphical runbook SDK
               href: graphical-runbook-sdk.md
         - name: Monitor runbooks
           items:
-            - name: Runbook output
+            - name: Monitor runbook output
               href: automation-runbook-output-and-messages.md
-            - name: Handle errors in Graphical runbooks
+            - name: Handle errors in graphical runbooks
               href: automation-runbook-graphical-error-handling.md
             - name: Forward job data to Azure Monitor Logs
               href: automation-manage-send-joblogs-log-analytics.md
@@ -120,7 +120,7 @@
               href: troubleshoot/runbooks.md
             - name: Data to collect before opening support case
               href: troubleshoot/collect-data-microsoft-azure-automation-case.md
-        - name: Hybrid Runbook Worker
+        - name: Work with a Hybrid Runbook Worker
           items: 
             - name: Deploy Windows Hybrid Runbook Worker
               href: automation-windows-hrw-install.md
@@ -130,15 +130,15 @@
               href: automation-hrw-run-runbooks.md
             - name: Troubleshoot Hybrid Runbook Worker
               href: troubleshoot/hybrid-runbook-worker.md
-        - name: Source control integration
+        - name: Use source control integration
           href: source-control-integration.md
     - name: Configuration Management
       items:
-        - name: State Configuration (DSC)
+        - name: Manage State Configuration (DSC)
           items:
             - name: Overview
               href: automation-dsc-overview.md
-            - name: Get started using DSC
+            - name: Get started using State Configuration
               href: automation-dsc-getting-started.md
             - name: Onboard machines for management
               href: automation-dsc-onboarding.md
@@ -156,13 +156,13 @@
               href: automation-dsc-diagnostics.md
             - name: Troubleshoot issues with DSC
               href: troubleshoot/desired-state-configuration.md
-        - name: Change Tracking and Inventory
+        - name: Manage Change Tracking and Inventory
           items:
             - name: Overview
               href: change-tracking.md
             - name: Supported regions for linked Log Analytics workspace
               href: how-to/region-mappings.md
-            - name: Enable
+            - name: Enable Change Tracking and Inventory
               items:
                 - name: Use Azure portal
                   href: automation-onboard-solutions-from-browse.md

articles/automation/automation-connections.md

@@ -1,13 +1,13 @@
 ---
-title: Connection assets in Azure Automation
+title: Manage connections in Azure Automation
 description: Connection assets in Azure Automation contain the information required to connect to an external service or application from a runbook or DSC configuration. This article explains the details of connections and how to work with them in both textual and graphical authoring.
 services: automation
 ms.subservice: shared-capabilities
 ms.date: 01/13/2020
 ms.topic: conceptual
 ---
 
-# Connection assets in Azure Automation
+# Manage connections in Azure Automation
 
 An Automation connection asset contains the information required to connect to an external service or application from a runbook or DSC configuration. This may include information required for authentication such as a username and password in addition to connection information such as a URL or a port. The value of a connection is keeping all of the properties for connecting to a particular application in one asset as opposed to creating multiple variables. The user can edit the values for a connection in one place, and you can pass the name of a connection to a runbook or DSC configuration in a single parameter. The properties for a connection can be accessed in the runbook or DSC configuration with the `Get-AutomationConnection` activity.
 

articles/automation/automation-update-azure-modules.md

@@ -1,13 +1,13 @@
 ---
-title: Update Azure modules in Azure Automation
+title: Update Azure PowerShell modules in Azure Automation
 description: This article describes how you can now update common Azure PowerShell modules provided by default in Azure Automation.
 services: automation
 ms.subservice: process-automation
 ms.date: 06/14/2019
 ms.topic: conceptual
 ---
 
-# How to update Azure PowerShell modules in Azure Automation
+# Update Azure PowerShell modules in Azure Automation
 
 To update the Azure modules in your Automation account you need to use the [Update Azure modules runbook](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update), which is available as open source. To start using the **Update-AutomationAzureModulesForAccount** runbook to update your Azure modules, download it from the [Update Azure modules runbook repository](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) on GitHub. You can then import it into your Automation account or run it as a script. To learn how to import a runbook in your Automation account, see [Import a runbook](manage-runbooks.md#importing-a-runbook).
 

articles/automation/shared-resources/certificates.md

@@ -1,5 +1,5 @@
 ---
-title: Certificate assets in Azure Automation
+title: Manage certificate in Azure Automation
 description: Certificates are securely stored in Azure Automation so that runbooks or DSC configurations can access them to authenticate against Azure and third-party resources. This article explains the details of certificates and how to work with them in both textual and graphical authoring.
 services: automation
 ms.service: automation
@@ -11,7 +11,7 @@ ms.topic: conceptual
 manager: carmonm
 ---
 
-# Certificate assets in Azure Automation
+# Manage certificates in Azure Automation
 
 Certificates are stored securely in Azure Automation so they can be accessed by runbooks or DSC configurations using the [Get-AzAutomationCertificate](https://docs.microsoft.com/powershell/module/Az.Automation/Get-AzAutomationCertificate?view=azps-3.7.0) activity for Azure Resource Manager resources. Secure certificate storage allows you to create runbooks and DSC configurations that use certificates for authentication or add them to Azure or third-party resources.
 

articles/automation/shared-resources/credentials.md

@@ -1,5 +1,5 @@
 ---
-title: Manage credential assets in Azure Automation
+title: Manage credentials in Azure Automation
 description: Credential assets in Azure Automation contain security credentials that can be used to authenticate to resources accessed by the runbook or DSC configuration. This article describes how to create credential assets and use them in a runbook or DSC configuration.
 services: automation
 ms.service: automation
@@ -11,7 +11,7 @@ ms.topic: conceptual
 manager: carmonm
 ---
 
-# Manage credential assets in Azure Automation
+# Manage credentials in Azure Automation
 
 An Automation credential asset holds an object that contains security credentials, such as a user name and a password. Runbooks and DSC configurations use cmdlets that accept a [PSCredential](https://docs.microsoft.com/dotnet/api/system.management.automation.pscredential?view=pscore-6.2.0) object for authentication. Alternatively, they can extract the user name and password of the `PSCredential` object to provide to some application or service requiring authentication. 
 

articles/automation/shared-resources/schedules.md

@@ -1,5 +1,5 @@
 ---
-title: Schedules in Azure Automation
+title: Manage schedules in Azure Automation
 description: Automation schedules are used to schedule runbooks in Azure Automation to start automatically. Describes how to create and manage a schedule in so that you can automatically start a runbook at a particular time or on a recurring schedule.
 services: automation
 ms.service: automation
@@ -10,7 +10,7 @@ ms.date: 04/04/2019
 ms.topic: conceptual
 manager: carmonm
 ---
-# Scheduling a runbook in Azure Automation
+# Manage schedules in Azure Automation
 
 To schedule a runbook in Azure Automation to start at a specified time, you link it to one or more schedules. A schedule can be configured to either run once or on a reoccurring hourly or daily schedule for runbooks in the Azure  portal. You can also schedule them for weekly, monthly, specific days of the week or days of the month, or a particular day of the month. A runbook can be linked to multiple schedules, and a schedule can have multiple runbooks linked to it.
 

articles/automation/shared-resources/variables.md

@@ -1,5 +1,5 @@
 ---
-title: Variable assets in Azure Automation
+title: Manage variables in Azure Automation
 description: Variable assets are values that are available to all runbooks and DSC configurations in Azure Automation.  This article explains the details of variables and how to work with them in both textual and graphical authoring.
 services: automation
 ms.service: automation
@@ -10,7 +10,7 @@ ms.date: 05/14/2019
 ms.topic: conceptual
 manager: carmonm
 ---
-# Variable assets in Azure Automation
+# Manage variables in Azure Automation
 
 Variable assets are values that are available to all runbooks and DSC configurations in your Automation account. You can manage them from the Azure portal, from PowerShell, within a runbook, or in a DSC configuration.