Merge branch 'main' into combinetemps

Author: JasonWHowell

.openpublishing.redirection.azure-monitor.json

@@ -6893,6 +6893,11 @@
           "source_path_from_root": "/articles/azure-monitor/essentials/private-link-data-ingestion.md",
           "redirect_url": "/azure/azure-monitor/containers/kubernetes-monitoring-private-link",
           "redirect_document_id": false
+        },
+        {
+          "source_path_from_root": "/articles/azure-monitor/containers/container-insights-custom-metrics.md",
+          "redirect_url": "/previous-versions/azure/azure-monitor/containers/container-insights-custom-metrics",
+          "redirect_document_id": false
         }
     ]
 }

articles/api-center/enable-managed-api-analysis-linting.md

@@ -14,8 +14,9 @@ ms.custom:
 
 This article explains how to enable API analysis in [Azure API Center](overview.md) without having to manage it yourself (preview). API analysis offers linting capabilities to analyze API definitions in your organization's API center. Linting ensures your API definitions adhere to organizational style rules, generating both individual and summary reports. Use API analysis to identify and correct common errors and inconsistencies in your API definitions.
 
-> [!NOTE]
-> With managed linting and analysis, API Center sets up a linting engine and any required dependencies and triggers. You can also enable linting and analysis [manually](enable-api-analysis-linting.md). 
+> [!IMPORTANT]
+> Managed API analysis in API Center sets up a linting engine and necessary dependencies automatically. You can also enable linting and analysis [manually](enable-api-analysis-linting.md) using a custom Azure function. **Disable any function used for manual linting before enabling managed API analysis.**
+
 
 In this scenario:
 
@@ -29,6 +30,9 @@ In this scenario:
 * Currently, only OpenAPI specification documents in JSON or YAML format are analyzed.
 * By default, you enable analysis with the [`spectral:oas` ruleset](https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules). To learn more about the built-in rules, see the [Spectral GitHub repo](https://github.com/stoplightio/spectral/blob/develop/docs/reference/openapi-rules.md). 
 * Currently, you configure a single ruleset, and it's applied to all OpenAPI definitions in your API center.
+* The following are limits for maximum number of API definitions linted per 4 hours:
+    * Free tier: 10
+    * Standard tier: 100
 
 ## Prerequisites
 

articles/api-center/includes/api-center-service-limits.md

@@ -23,6 +23,7 @@ ms.custom: Include file
 | Maximum number of custom metadata properties per entity<sup>3</sup> | 10 | 20 |
 | Maximum number of child properties in custom metadata property of type "object" | 10 |10 | 
 | Maximum requests per minute (data plane) | 3,000 | 6,000  |
+| Maximum number of API definitions [linted](../enable-managed-api-analysis-linting.md) per 4 hours | 10 | 100  |
 
 <sup>1</sup> To increase a limit in the Standard plan, contact [support](https://azure.microsoft.com/support/options/).<br/>
 <sup>2</sup> In the Free plan, use of full service features including API analysis and access through the data plane API is limited to 5 APIs.<br/>

articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md

@@ -2,7 +2,7 @@
 title: Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation 
 description: This article tells how to troubleshoot and resolve issues that arise with Azure Automation extension-based Hybrid Runbook Workers.
 services: automation
-ms.date: 01/03/2024
+ms.date: 08/26/2024
 ms.topic: troubleshooting 
 ms.custom:
 ---
@@ -73,34 +73,6 @@ To help troubleshoot issues with extension-based Hybrid Runbook Workers:
     /home/hweautomation
     ```
 
-
-### Unable to update Az modules while using the Hybrid Worker
-
-#### Issue
-
-The Hybrid Runbook Worker jobs failed as it was unable to import Az modules.
-
-#### Resolution
-
-As a workaround, you can follow these steps:
-
-1. Navigate to the folder:
-   > [!TIP] 
-   > Replace `*` in the below path with the specific version that is installed if you know it.
-   ```
-   C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\*\HybridAgent
-   ```
-
-1. Edit the file with the name `Orchestrator.Sandbox.exe.config`
-
-1. Add the following lines inside the `<assemblyBinding>` tag:
-```xml
-<dependentAssembly>
-  <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
-  <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
-</dependentAssembly>
-```
-
 ### Scenario: Runbooks go into a suspended state on a Hybrid Runbook Worker when using a custom account on a server with User Account Control (UAC) enabled
 
 #### Issue
@@ -411,38 +383,6 @@ This error occurs when you attempt to use a Run As account in a runbook that run
 If your Hybrid Runbook Worker is an Azure VM, you can use [runbook authentication with managed identities](../automation-hrw-run-runbooks.md#runbook-auth-managed-identities) instead. This scenario simplifies authentication by allowing you to authenticate to Azure resources using the managed identity of the Azure VM instead of the Run As account. When the Hybrid Runbook Worker is an on-premises machine, you need to install the Run As account certificate on the machine. To learn how to install the certificate, see the steps to run the PowerShell runbook **Export-RunAsCertificateToHybridWorker** in [Run runbooks on a Hybrid Runbook Worker](../automation-hrw-run-runbooks.md).
 
 
-### Scenario: Set-AzStorageBlobContent fails on a Hybrid Runbook Worker 
-
-#### Issue
-
-Runbook fails when it tries to execute `Set-AzStorageBlobContent`, and you receive the following error message:
-
-`Set-AzStorageBlobContent : Failed to open file xxxxxxxxxxxxxxxx: Illegal characters in path`
-
-#### Cause
-
- This error is caused by the long file name behavior of calls to `[System.IO.Path]::GetFullPath()`, which adds UNC paths.
-
-#### Resolution
-
-As a workaround, you can create a configuration file named `OrchestratorSandbox.exe.config` with the following content:
-
-```azurecli
-<configuration>
-  <runtime>
-    <AppContextSwitchOverrides value="Switch.System.IO.UseLegacyPathHandling=false" />
-  </runtime>
-</configuration>
-```
-
-Place this file in the same folder as the executable file `OrchestratorSandbox.exe`. For example:
-> [!TIP] 
-> Replace `*` in the below path with the specific version that is installed if you know it.
-```
-%ProgramFiles%\Microsoft Monitoring Agent\Agent\AzureAutomation\*\HybridAgent
-```
-
-
 ### Scenario: Microsoft Azure VMs automatically dropped from a hybrid worker group
 
 #### Issue

articles/azure-app-configuration/concept-feature-management.md

@@ -13,7 +13,7 @@ ms.date: 02/20/2024
 
 Traditionally, shipping a new application feature requires a complete redeployment of the application itself. Testing a feature often requires multiple deployments of the application. Each deployment might change the feature or expose the feature to different customers for testing.  
 
-Feature management is a modern software-development practice that decouples feature release from code deployment and enables quick changes to feature availability on demand. It uses a technique called *feature flags* (also known as *feature toggles* and *feature switches*) to dynamically administer a feature's lifecycle.
+Feature management is a software-development practice that decouples feature release from code deployment and enables quick changes to feature availability on demand. It uses a technique called *feature flags* (also known as *feature toggles* and *feature switches*) to dynamically administer a feature's lifecycle.
 
 Feature management helps developers address the following problems:
 

articles/azure-arc/kubernetes/tutorial-use-gitops-flux2.md

@@ -420,11 +420,7 @@ The Azure portal is useful for managing GitOps configurations and the Flux exten
 Follow these steps to apply a sample Flux configuration to a cluster. As part of this process, Azure installs the `microsoft.flux` extension on the cluster, if it wasn't already installed in a previous deployment.
 
 1. Navigate to your cluster in the Azure portal.
-1. In the left pane, under **Settings**, select **GitOps**.
-1. Select **Create**.
-
-   :::image type="content" source="media/tutorial-use-gitops-flux2/portal-gitops-start.png" alt-text="Screenshot showing the GitOps Create option for a cluster in the Azure portal." lightbox="media/tutorial-use-gitops-flux2/portal-gitops-start.png":::
-
+1. From the service menu, under **Settings**, select **GitOps** > **Create**.
 1. In the **Basics** section:
 
    1. Enter a name for the configuration.
@@ -473,15 +469,13 @@ Follow these steps to apply a sample Flux configuration to a cluster. As part of
 
 #### View configurations and objects
 
-To view all of the configurations for a cluster, navigate to the cluster and select **GitOps** in the left pane.
-
-:::image type="content" source="media/tutorial-use-gitops-flux2/portal-view-configurations.png" alt-text="Screenshot showing all configurations for a cluster in the Azure portal." lightbox="media/tutorial-use-gitops-flux2/portal-view-configurations.png":::
+To view all of the configurations for a cluster, navigate to the cluster and select **GitOps** from the service menu.
 
 Select the name of a configuration to view more details such as the configuration's status, properties, and source. You can then select **Configuration objects** to view all of the objects that were created to enable the GitOps configuration. This lets you quickly see the compliance state and other details about each object.
 
 :::image type="content" source="media/tutorial-use-gitops-flux2/portal-configuration-objects.png" alt-text="Screenshots showing configuration objects and their state in the Azure portal." lightbox="media/tutorial-use-gitops-flux2/portal-configuration-objects.png":::
 
-To see other Kubernetes resources deployed on the cluster, return to the cluster overview page and select **Kubernetes resources** in the left pane.
+To see other Kubernetes resources deployed on the cluster, return to the cluster overview page and select **Kubernetes resources** from the service menu.
 
 To view detailed conditions for a configuration object, select its name.
 
@@ -707,7 +701,7 @@ az k8s-extension delete -g flux-demo-rg -c flux-demo-arc -n flux -t connectedClu
 
 #### Delete the Flux configuration
 
-To delete a Flux configuration, navigate to the cluster where the configuration was created and select **GitOps** in the left pane. Select the configuration you want to delete. From the top of the page, select **Delete**, then select **Delete** again when prompted to confirm.
+To delete a Flux configuration, navigate to the cluster where the configuration was created and select **GitOps** from the service menu. Select the configuration you want to delete. From the top of the page, select **Delete**, then select **Delete** again when prompted to confirm.
 
 When you delete a Flux configuration, all of the Flux configuration objects in the cluster are deleted. However, this action doesn't delete the `microsoft.flux` extension itself.
 

articles/azure-arc/resource-bridge/overview.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Arc resource bridge overview
 description: Learn how to use Azure Arc resource bridge to support VM self-servicing on Azure Stack HCI, VMware, and System Center Virtual Machine Manager.
-ms.date: 02/09/2024
+ms.date: 08/26/2024
 ms.topic: overview
 ms.custom: references_regions
 ---
@@ -46,7 +46,7 @@ To summarize, the Azure resources are projections of the resources running in yo
 
 ## Benefits of Azure Arc resource bridge
 
-Through Azure Arc resource bridge, you can accomplish the following for each private cloud infrastructure from Azure:
+Through Azure Arc resource bridge, you can accomplish the following tasks for each private cloud infrastructure from Azure:
 
 ### Azure Stack HCI
 
@@ -121,7 +121,7 @@ Arc resource bridge supports the following Azure regions:
 
 ### Regional resiliency
 
-While Azure has a number of redundancy features at every level of failure, if a service impacting event occurs, Azure Arc resource bridge currently does not support cross-region failover or other resiliency capabilities. In the event of the service becoming unavailable, the on-premises VMs continue to operate unaffected. Management from Azure is unavailable during that service outage.
+While Azure has redundancy features at every level of failure, if a service impacting event occurs, Azure Arc resource bridge currently does not support cross-region failover or other resiliency capabilities. In the event of the service becoming unavailable, the on-premises VMs continue to operate unaffected. Management from Azure is unavailable during that service outage.
 
 ### Private cloud environments
 
@@ -142,12 +142,11 @@ Generally, the latest released version and the previous three versions (n-3) of
 
 There could be instances where supported versions are not sequential. For example, version 1.0.18 is released and later found to contain a bug; a hot fix is released in version 1.0.19 and version 1.0.18 is removed. In this scenario, n-3 supported versions become 1.0.19, 1.0.17, 1.0.16, 1.0.15.
 
-Arc resource bridge typically releases a new version on a monthly cadence, at the end of the month. Delays might occur that could push the release date further out. Regardless of when a new release comes out, if you are within n-3 supported versions (starting with 1.0.15), then your Arc resource bridge version is supported. To stay updated on releases, visit the [Arc resource bridge release notes](https://github.com/Azure/ArcResourceBridge/releases) on GitHub. To learn more about upgrade options, visit [Upgrade Arc resource bridge](upgrade.md).
+Arc resource bridge typically releases a new version on a monthly cadence, at the end of the month. Delays might occur that could push the release date further out. Regardless of when a new release comes out, if you are within n-3 supported versions, then your Arc resource bridge version is supported. To stay updated on releases, visit the [Arc resource bridge release notes](release-notes.md). To learn more about upgrade options, visit [Upgrade Arc resource bridge](upgrade.md).
 
 ### Private Link Support
 
-Arc resource bridge does not currently support private link. 
-
+Arc resource bridge does not currently support private link.
 
 ## Next steps