Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tsts

Author: Ankita Dutta

.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/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
 

articles/azure-arc/resource-bridge/release-notes.md

@@ -0,0 +1,227 @@
+---
+title: "What's new with Azure Arc resource bridge"
+ms.date: 08/26/2024
+ms.topic: conceptual
+description: "Learn about the latest releases of Azure Arc resource bridge."
+---
+
+# What's new with Azure Arc resource bridge
+
+Azure Arc resource bridge is updated on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about recent releases.
+
+We generally recommend using the most recent versions of the agents. The [version support policy](overview.md#supported-versions) generally covers the most recent version and the three previous versions (n-3).
+
+## Version 1.2.0 (July 2024)
+
+- Appliance: 1.2.0
+- CLI extension: 1.2.0
+- SFS release: 0.1.32.10710
+- Kubernetes: 1.28.5
+- Mariner: 2.0.20240609
+
+### Arc-enabled SCVMM
+
+- `CreateConfig`: Improve prompt messages and reorder networking prompts for the custom IP range scenario
+- `CreateConfig`: Validate Gateway IP input against specified IP range for the custom IP range scenario
+- `CreateConfig`: Add validation to check infra configuration capability for HA VM deployment. If HA isn't supported, reprompt users to proceed with standalone VM deployment
+
+### Arc-enabled VMware vSphere
+
+- Improve prompt messages in createconfig for VMware
+- Validate proxy scheme and check for required `no_proxy` entries
+
+### Features
+
+- Reject double commas (`,,`) in `no_proxy` string
+- Add default folder to createconfig list
+- Add conditional Fairfax URLs for US Gov Virginia support
+- Add new error codes
+
+### Bug fixes
+
+- Fix for openSSH [CVE-2024-63870](https://github.com/advisories/GHSA-2x8c-95vh-gfv4)
+
+## Version 1.1.1 (April 2024)
+
+- Appliance: 1.1.1
+- CLI extension: 1.1.1
+- SFS release: 0.1.26.10327
+- Kubernetes: 1.27.3
+- Mariner: 2.0.20240301
+
+### Arc-enabled SCVMM
+
+- Add quotes for resource names
+
+### Azure Stack HCI
+
+- HCI auto rotation logic on upgrade
+
+### Features
+
+- Updated log collection with describe nodes
+- Error message enhancement for failure to reach Arc resource bridge VM
+- Improve troubleshoot command error handling with scoped access key
+- Longer timeout for individual pod pulls
+- Updated `execute` command to allow passing in a kubeconfig
+- Catch `<>` in no_proxy string
+- Add validation to see if connections from the client machine are proxied
+- Diagnostic checker enhancement - Add default gateway and dns servers check to telemetry mode
+- Log collection enhancement
+
+### Bug fixes
+
+- HCI MOC image client fix to set storage container on catalog
+
+## Version 1.1.0 (April 2024)
+
+- Appliance: 1.1.0
+- CLI extension: 1.1.0
+- SFS release: 0.1.25.10229
+- Kubernetes: 1.27.3
+- Mariner: 2.0.20240223
+
+### Arc-enabled SCVMM
+
+- Use same `vmnetwork` key for HG and Cloud (`vmnetworkid`)
+- SCVMM - Add fallback for VMM IP pool with support for IP range in appliance network, add `--vlanid` parameter to accept `vlanid`
+- Non-interactive mode for SCVMM `troubleshoot` and `logs` commands
+- `Createconfig` command uses styled text to warn about saving config files instead of standard logger
+- Improved handling and error reporting for timeouts while provisioning/deprovisioning images from the cloud fabric
+- Verify template and snapshot health after provisioning an image, and clean up files associated to the template on image deprovision failures
+- Missing VHD state handing in SCVMM
+- SCVMM `validate` and `createconfig` fixes
+
+### Arc-enabled VMware vSphere
+
+- SSD storage validations added to VMware vSphere in telemetry mode to check if the ESXi host backing the resource pool has any SSD-backed storage
+- Improve missing privilege error message, show some privileges in error message
+- Validate host ESXi version and provide a concrete error message for placement profile
+- Improve message for no datacenters found, display default folder
+- Surface VMware error when finder fails during validate
+- Verify template health and fix it during image provision
+
+### Features
+
+- `deploy` command - diagnostic checker enhancements that add retries with exponential backoff to proxy client calls
+- `deploy` command - diagnostic checker enhancement: adds storage performance checker in telemetry mode to evaluate the storage performance of the VM used to deploy the appliance
+- `deploy` command - Add Timeout for SSH connection: New error message: "Error: Timeout occurred due to management machine being unable to reach the appliance VM IP, 192.168.0.11. Ensure that the requirements are met: `https://aka.ms/arb-machine-reqs: dial tcp 192.168.0.11:22: connect: connection timed out`
+- `validate` command - The appliance deployment now fails if Proxy Connectivity and No Proxy checks report any errors
+
+### Bug fixes
+
+- SCVMM ValueError fix - fallback option for VMM IP Pools with support for Custom IP Range based Appliance Network
+
+## Version 1.0.18 (February 2024)
+
+- Appliance: 1.0.18
+- CLI extension: 1.0.3
+- SFS release: 0.1.24.10201
+- Kubernetes: 1.26.6
+- Mariner: 2.0.20240123
+
+### Fabric/Private cloud provider
+
+- SCVMM `createconfig` command improvements - retry until valid Port and FQDN provided
+- SCVMM and VMware - Validate control plane IP address; add reprompts
+- SCVMM and VMware - extend `deploy` command timeout from 30 to 120 minutes
+
+### Features
+
+- `deploy` command - diagnostic checker enhancement: proxy checks in telemetry mode
+
+### Product
+
+- Reduction in CPU requests
+- ETCD preflight check enhancements for upgrade
+
+### Bug fixes
+
+- Fix for clusters impacted by the `node-ip` being set as `kube-vip` IP issue
+- Fix for SCVMM cred rotation with the same credentials
+
+## Version 1.0.17 (December 2023)
+
+- Appliance: 1.0.17
+- CLI extension: 1.0.2
+- SFS release: 0.1.22.11107
+- Kubernetes: 1.26.6
+- Mariner: 2.0.20231106
+
+### Fabric/Private cloud provider
+
+- SCVMM `createconfig` command improvements
+- Azure Stack HCI - extend `deploy` command timeout from 30 to 120 minutes
+- All private clouds - enable provider credential parameters to be passed in each command
+- All private clouds - basic validations for select `createconfig` command inputs
+- VMware - basic reprompts for select `createconfig` command inputs
+
+### Features
+
+- `deploy` command - diagnostic checker enhancement - improve `context` error messages
+
+### Bug fixes
+
+- Fix for `context` error always being returned as `Deploying`
+
+### Known bugs
+
+- Arc resource bridge upgrade shows appliance version as upgraded, but status shows upgrade failed
+
+## Version 1.0.16 (November 2023)
+
+- Appliance: 1.0.16
+- CLI extension: 1.0.1
+- SFS release: 0.1.21.11013
+- Kubernetes: 1.25.7
+- Mariner: 2.0.20231004
+
+### Fabric/Private cloud provider
+
+- SCVMM image provisioning and upgrade fixes
+- VMware vSphere - use full inventory path for networks
+- VMware vSphere error improvement for denied permission
+- Azure Stack HCI - enable default storage container
+
+### Features
+
+- `deploy` command - diagnostic checker enhancement - add `azurearcfork8s.azurecr.io` URL
+
+### Bug fixes
+
+- vSphere credential issue
+- Don't set storage container for non-`arc-appliance` catalog image provision requests
+- Monitoring agent not installed issue
+
+## Version 1.0.15 (September 2023)
+
+- Appliance: 1.0.15
+- CLI extension: 1.0.0
+- SFS release: 0.1.20.10830
+- Kubernetes: 1.25.7
+- Mariner: 2.0.20230823
+
+### Fabric/Infrastructure
+
+- `az arcappliance` CLI commands now only support static IP deployments for VMware and SCVMM
+- For test purposes only, Arc resource bridge on Azure Stack HCI may be deployed with DHCP configuration
+- Support for using canonical region names
+- Removal of VMware vSphere 6.7 fabric support (vSphere 7 and 8 are both supported)
+
+### Features
+
+- (new) `get-upgrades` command- fetches the new upgrade edge available for a current appliance cluster
+- (new) `upgrade` command - upgrades the appliance to the next available version (not available for SCVMM)
+- (update) `deploy` command - In addition to `deploy`, this command now also calls `create` command. `Create` command is now optional.
+- (new) `get-credentials` command - now allows fetching of SSH keys and kubeconfig, which are needed to run the `logs` command from a different machine than the one used to deploy Arc resource bridge
+- Allowing usage of `config-file` parameter for `get-credentials` command
+(new) Troubleshoot command - help debug live-site issues by running allowed actions directly on the appliance using a JIT access key
+
+### Bug fix
+
+- IPClaim premature deletion issue vSphere static IP
+
+## Next steps
+
+- Learn more about [Arc resource bridge](overview.md).
+- Learn how to [upgrade Arc resource bridge](upgrade.md).