Merge branch 'master' of https://github.com/mathapli/azure-docs-pr-1

Author: mathapli

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/devtest-labs/devtest-lab-integrate-ci-cd.md",
+      "redirect_url": "/previous-versions/azure/devtest-labs/devtest-lab-integrate-ci-cd",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/devtest-labs/integrate-environments-devops-pipeline.md",
+      "redirect_url": "/previous-versions/azure/devtest-labs/integrate-environments-devops-pipeline",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/confidential-computing/virtual-machine-solutions.md",
       "redirect_url": "/azure/virtual-machines/",
@@ -2010,21 +2020,6 @@
       "redirect_url": "/azure/migrate/migrate-services-overview",
       "redirect_document_id": false
     },
-    {
-      "source_path_from_root": "/articles/monitoring/management-overview-monitoring.md",
-      "redirect_url": "/azure/monitoring/",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/monitoring/monitoring-container-health.md",
-      "redirect_url": "/azure/monitoring/monitoring-container-insights-overview",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/monitoring/monitoring-walkthrough-servicemap.md",
-      "redirect_url": "/azure/monitoring/monitoring-service-map",
-      "redirect_document_id": false
-    },
     {
       "source_path_from_root": "/articles/multi-factor-authentication/end-user/index.md",
       "redirect_url": "/azure/multi-factor-authentication/end-user/multi-factor-authentication-end-user",
@@ -2210,101 +2205,6 @@
       "redirect_url": "/azure/openshift/delete-cluster",
       "redirect_document_id": false
     },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/index.md",
-      "redirect_url": "/azure/monitoring",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/oms-solution-agenthealth.md",
-      "redirect_url": "/azure/monitoring/monitoring-solution-agenthealth",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/oms-solution-office-365.md",
-      "redirect_url": "/azure/monitoring/monitoring-solution-office-365",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-architecture.md",
-      "redirect_url": "/azure/monitoring",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-integration.md",
-      "redirect_url": "/azure/monitoring",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-overview.md",
-      "redirect_url": "/azure/monitoring",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-runbook-datacollect.md",
-      "redirect_url": "/azure/monitoring/monitoring-runbook-datacollect",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-sdk.md",
-      "redirect_url": "/azure/monitoring",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-service-map-scom.md",
-      "redirect_url": "/azure/monitoring/monitoring-service-map-scom",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-service-map.md",
-      "redirect_url": "/azure/monitoring/monitoring-service-map",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solution-targeting.md",
-      "redirect_url": "/azure/monitoring/monitoring-solution-targeting",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions-best-practices.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions-best-practices",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions-creating.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions-creating",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions-resources-automation.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions-resources-automation",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions-resources-searches-alerts.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions-resources-searches-alerts",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions-resources-views.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions-resources-views",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions-solution-file.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions-solution-file",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-solutions.md",
-      "redirect_url": "/azure/monitoring/monitoring-solutions",
-      "redirect_document_id": false
-    },
-    {
-      "source_path_from_root": "/articles/operations-management-suite/operations-management-suite-walkthrough-servicemap.md",
-      "redirect_url": "/azure/monitoring/monitoring-service-map",
-      "redirect_document_id": false
-    },
     {
       "source_path_from_root": "/articles/operator-service-manager/overview.md",
       "redirect_url": "azure/operator-service-manager/azure-operator-service-manager-overview",
@@ -3701,4 +3601,4 @@
       "redirect_document_id": false
     }
   ]
-}
+}

articles/active-directory-b2c/identity-provider-ping-one.md

@@ -25,7 +25,7 @@ zone_pivot_groups: b2c-policy-type
 
 ## Create a PingOne application
 
-To enable sign-in for users with a PingOne (Ping Identity) account in Azure Active Directory B2C (Azure AD B2C), you need to create an application in the Ping Identity Administrator Console. For more information, see [Adding or updating an OIDC application](https://docs.pingidentity.com/access/sources/dita/topic?resourceid=p14e_add_update_oidc_application) in the Ping Identity documentation. If you don't already have a PingOne account, you can sign up at [`https://admin.pingone.com/web-portal/register`](https://admin.pingone.com/web-portal/register).
+To enable sign-in for users with a PingOne (Ping Identity) account in Azure Active Directory B2C (Azure AD B2C), you need to create an application in the Ping Identity Administrator Console. If you don't already have a PingOne account, you can sign up at [`https://admin.pingone.com/web-portal/register`](https://admin.pingone.com/web-portal/register).
 
 1. Sign in to the Ping Identity Administrator Console with your PingOne account credentials.
 1. In the left menu of the page, select **Connections**, then next to **Applications**, select **+**.

articles/active-directory-b2c/partner-grit-authentication.md

@@ -32,7 +32,7 @@ Biometric authentication has the following benefits:
 
 To get started, you'll need:
 
-- License to [Grit's Visual IEF builder](https://www.gritiefedit.com/). Contact [Grit support](mailto:[email protected]) for licensing details. For this tutorial you don't need a license.
+- License to [Grit's Visual IEF builder](/azure/active-directory-b2c/partner-grit-editor). Contact [Grit support](mailto:[email protected]) for licensing details. For this tutorial you don't need a license.
 
 - An Azure subscription. If you don't have one, get a [free account](https://azure.microsoft.com/free/).
 
@@ -62,7 +62,7 @@ Contact [Grit support](mailto:[email protected]) for details to get o
 
 ### Configure Grit's biometric authentication with Azure AD B2C
 
-1. Navigate to <https://www.gritiefedit.com> and enter your email if you're asked for it.
+1. Navigate to </azure/active-directory-b2c/partner-grit-editor> and enter your email if you're asked for it.
 
 1. Press cancel in the quick start wizard.
 

articles/active-directory-b2c/partner-grit-editor.md

@@ -31,7 +31,7 @@ To get started with the IEF Editor, ensure the following prerequisites are met:
 
 - A Microsoft Entra subscription. If you don't have one, you can get an [Azure free account](https://azure.microsoft.com/free/).
 - An Azure AD B2C tenant linked to the Azure subscription. Learn more at [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md).
-- [Visual IEF Editor](https://www.gritiefedit.com) is free and works only with Google Chrome browser.
+- [Visual IEF Editor](/azure/active-directory-b2c/partner-grit-editor) is free and works only with Google Chrome browser.
 - Review and download policies from [Azure AD B2C customer policies starter pack](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack)
 - Install Google Chrome browser
 
@@ -43,7 +43,7 @@ The following illustration shows a sample code-development workflow from XML fil
 
 | Step | Description |
 |:-----|:------|
-| 1. | Go to https://www.gritiefedit.com and upload the policies from [Azure AD B2C customer policies starter pack](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack) using the upload policy button in the user interface.|
+| 1. | Go to /azure/active-directory-b2c/partner-grit-editor and upload the policies from [Azure AD B2C customer policies starter pack](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack) using the upload policy button in the user interface.|
 | 2. | Using the Visual IEF editor tool, select and edit any user journey and self asserted profile that needs update/modification.|
 |3. | Once the files are updated, select the download button. All the policies will be downloaded to the local machine.|
 |4. | Check in the files in GitHub or CI/CD pipeline. |

articles/active-directory-b2c/partner-ping-identity.md

@@ -107,16 +107,14 @@ Use the instructions in the following sections to configure PingAccess and PingF
 
 To configure PingFederate as the token provider for PingAccess, ensure connectivity from PingFederate to PingAccess. Confirm connectivity from PingAccess to PingFederate.  
 
-For more information, see [Configure PingFederate as the token provider for PingAccess](https://docs.pingidentity.com/access/sources/dita/topic?category=pingaccess&Releasestatus_ce=Current&resourceid=pa_configure_pf_as_the_token_provider_for_pa) in the Ping Identity documentation.
-
 ### Configure a PingAccess application for header-based authentication
 
 Use the following instructions to create a PingAccess application for the target web application, for header-based authentication. 
 
 #### Create a virtual host
 
 >[!IMPORTANT]
->Create a virtual host for every application. For more information, see [What can I configure with PingAccess?](https://docs.pingidentity.com/access/sources/dita/topic?category=pingaccess&Releasestatus_ce=Current&resourceid=pa_what_can_I_configure_with_pa) in the Ping Identity documentation.
+>Create a virtual host for every application.
 
 To create a virtual host:
 

articles/automation/disable-local-authentication.md

@@ -3,8 +3,8 @@ title: Disable local authentication in Azure Automation
 description: This article describes disabling local authentication in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 11/20/2023
-ms.custom: engagement-fy23
+ms.date: 06/06/2024
+ms.custom: engagement-fy24
 ms.topic: how-to
 #Customer intent: As an administrator, I want disable local authentication so that I can enhance security.
 ms.service: azure-automation
@@ -40,7 +40,7 @@ The following table describes the behaviors or features that are prevented from
 |Starting a runbook using a webhook. | Start a runbook job using Azure Resource Manager template, which uses Microsoft Entra authentication. |
 |Using Automation Desired State Configuration.| Use [Azure Policy Guest configuration](../governance/machine-configuration/overview.md).  |
 |Using agent-based Hybrid Runbook Workers.| Use [extension-based Hybrid Runbook Workers](./extension-based-hybrid-runbook-worker-install.md).|
-|Using Azure Update Manager |Use [Azure Update Manager](../update-manager/overview.md)|
+|Using Automation Update Management |Use [Azure Update Manager](../update-manager/overview.md)|
 
 
 ## Next steps

articles/azure-app-configuration/enable-dynamic-configuration-aspnet-core.md

@@ -81,7 +81,7 @@ A *sentinel key* is a key that you update after you complete the change of all o
 
 1. Call the `UseAzureAppConfiguration` method. It enables your app to use the App Configuration middleware to update the configuration for you automatically.
 
-    Update *Program.cs* withe the following code. 
+    Update *Program.cs* with the following code. 
 
     ```csharp
     // Existing code in Program.cs

articles/azure-app-configuration/feature-management-dotnet-reference.md

@@ -165,7 +165,7 @@ In the above example, `FeatureW` specifies a `RequirementType` of `All`, meaning
 
 #### Microsoft Feature Management Schema
 
-The feature management library also supports the usage of the [`Microsoft Feature Management schema`](https://github.com/Azure/AppConfiguration/blob/main/docs/FeatureManagement/FeatureManagement.v1.0.0.schema.json) to declare feature flags. This schema is language agnostic in origin and is supported by all Microsoft feature management libraries.
+The feature management library also supports the usage of the [`Microsoft Feature Management schema`](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureManagement.v1.0.0.schema.json) to declare feature flags. This schema is language agnostic in origin and is supported by all Microsoft feature management libraries.
 
 ``` JavaScript
 {
@@ -198,7 +198,7 @@ The feature management library also supports the usage of the [`Microsoft Featur
 
 :::zone target="docs" pivot="preview-version"
 
-The feature management library supports appsettings.json as a feature flag source since it's a provider for .NET Core's `IConfiguration` system. Feature flags are declared using the [`Microsoft Feature Management schema`](https://github.com/Azure/AppConfiguration/blob/main/docs/FeatureManagement/FeatureManagement.v2.0.0.schema.json). This schema is language agnostic in origin and is supported by all Microsoft feature management libraries.
+The feature management library supports appsettings.json as a feature flag source since it's a provider for .NET Core's `IConfiguration` system. Feature flags are declared using the [`Microsoft Feature Management schema`](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureManagement.v2.0.0.schema.json). This schema is language agnostic in origin and is supported by all Microsoft feature management libraries.
 
 Below we have an example of declaring feature flags in a json file.
 
@@ -1407,11 +1407,13 @@ To enable persistance of targeting context in the current activity, you can use
 app.UseMiddleware<TargetingHttpContextMiddleware>();
 ```
 
-An example of its usage can be found in the [EvaluationDataToApplicationInsights](https://github.com/microsoft/FeatureManagement-Dotnet/tree/preview/examples/EvaluationDataToApplicationInsights) example.
+An example of its usage can be found in the [VariantAndTelemetryDemo](https://github.com/microsoft/FeatureManagement-Dotnet/tree/preview/examples/VariantAndTelemetryDemo) example.
 
 #### Prerequisite
 
-This telemetry publisher depends on Application Insights already being [setup](/azure/azure-monitor/app/asp-net-core#enable-application-insights-server-side-telemetry-no-visual-studio) and registered as an application service. For example, that is done [here](https://github.com/microsoft/FeatureManagement-Dotnet/blob/preview/examples/EvaluationDataToApplicationInsights/Program.cs#L20C1-L20C54) in the example application.
+This telemetry publisher depends on Application Insights already being setup registered as an application service. For example, that is done [here](https://github.com/microsoft/FeatureManagement-Dotnet/blob/preview/examples/VariantAndTelemetryDemo/Program.cs#L22-L32) in the example application.
+
+This telemetry publisher depends on Application Insights already being [setup](/azure/azure-monitor/app/asp-net-core#enable-application-insights-server-side-telemetry-no-visual-studio) and registered as an application service.
 
 :::zone-end
 

articles/azure-government/documentation-government-csp-list.md

@@ -151,7 +151,7 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[Diffeo, Inc.](https://diffeo.com)|
 |[DirectApps, Inc. D.B.A. Direct Technology](https://directtechnology.com)|
 |[DominionTech Inc.](https://www.dominiontech.com)|
-|[DOT Personable Inc](http://solutions.personable.com/)|
+|[DOT Personable Inc](https://cloud.personable.com/1/login.htm)|
 |Doublehorn, LLC|
 |[DXC Technology Services LLC](https://www.dxc.technology/services)|
 |[DXL Enterprises, Inc.](https://mahwahnjcoc.wliinc31.com/Supply-Chain-Management/DXL-Enterprises,-Inc-1349)|
@@ -188,7 +188,6 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[General Dynamics Information Technology](https://gdit.com/)|
 |[Giga-Green Technologies](https://giga-green.com)|
 |[Gimmal](https://www.gimmal.com/)|
-|[Global Justice Solutions, LLC](https://www.globaljusticesolutions.us/)|
 |[Global Tech Inc.](https://www.eglobaltech.com)|
 |[Globalscape, Inc.](https://www.globalscape.com)|
 |[Go Full Cloud](https://www.gofullcloud.com/)|
@@ -215,7 +214,7 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |I10 Inc|
 |[I2, Inc. (IBM)](https://www.ibm.com/security/intelligence-analysis/i2)|
 |[i3 Business Solutions, LLC](https://www.i3businesssolutions.com/)|
-|[i3 LLC](http://i3llc.net/)|
+|[i3 LLC](https://i3llc.us/)|
 |[IBM Corporation](https://www.ibm.com/industries/federal)|
 |[Illuminative Strategies Inc](https://illum-strat.com)|
 |[ImageSource](https://imagesourceinc.com/)|
@@ -256,7 +255,6 @@ The following tables contain lists of all the authorized Cloud Solution Provider
 |[Kosh Solutions, LLC](https://www.koshsolutions.com)|
 |[KTL Solutions, Inc.](https://www.ktlsolutions.com)|
 |[Ladlas Prince LLC](https://www.ladlasprince.com)|
-|[Lear360.com](https://www.lear360.com)|
 |[Leidos](https://www.leidos.com)|
 |[Leslie Digital Imaging LLC.](https://www.myldi.com)|
 |[LiftOff, LLC](https://www.liftoffonline.com)|

articles/azure-maps/rest-sdk-developer-guide.md

@@ -117,7 +117,7 @@ For more information, see the [Java SDK Developers Guide].
 
 [js render readme]: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/maps/maps-render-rest/README.md
 [js render package]: https://www.npmjs.com/package/@azure-rest/maps-render
-[js render sample]: https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/maps/maps-render-rest/samples/v1-beta
+[js render sample]: https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/maps/maps-render-rest/samples/v2-beta
 
 [js Geolocation readme]: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/maps/maps-geolocation-rest/README.md
 [js Geolocation package]: https://www.npmjs.com/package/@azure-rest/maps-geolocation