Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

.github/workflows/stale.yml

@@ -20,7 +20,7 @@ jobs:
         exempt-pr-labels: keep-open
         operations-per-run: 800
         ascending: true
-        start-date: '2021-07-13'
+        start-date: '2018-11-29'
         stale-pr-message: >
           This pull request has been inactive for at least 14 days.
           If you are finished with your changes, don't forget to sign off. See the [contributor guide](https://review.docs.microsoft.com/help/contribute/contribute-how-to-write-pull-request-automation) for instructions.

articles/active-directory/develop/active-directory-claims-mapping.md

@@ -91,7 +91,7 @@ In this example, you create a policy that adds the EmployeeID and TenantCountry
    1. To create the policy, run the following command:
 
       ``` powershell
-      New-AzureADPolicy -Definition @('{"ClaimsMappingPolicy":{"Version":1,"IncludeBasicClaimSet":"true", "ClaimsSchema": [{"Source":"user","ID":"employeeid","SamlClaimType":"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/employeeid","JwtClaimType":"name"},{"Source":"company","ID":"tenantcountry","SamlClaimType":"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/country","JwtClaimType":"country"}]}}') -DisplayName "ExtraClaimsExample" -Type "ClaimsMappingPolicy"
+      New-AzureADPolicy -Definition @('{"ClaimsMappingPolicy":{"Version":1,"IncludeBasicClaimSet":"true", "ClaimsSchema": [{"Source":"user","ID":"employeeid","SamlClaimType":"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/employeeid","JwtClaimType":"employeeid"},{"Source":"company","ID":"tenantcountry","SamlClaimType":"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/country","JwtClaimType":"country"}]}}') -DisplayName "ExtraClaimsExample" -Type "ClaimsMappingPolicy"
       ```
 
       > [!WARNING]

articles/aks/quotas-skus-regions.md

@@ -26,6 +26,10 @@ All other network, compute, and storage limitations apply to the provisioned inf
 >
 > For Windows Server containers, you can perform an upgrade operation to apply the latest node updates. If you don't have the available IP address space or vCPU quota to handle these temporary resources, the cluster upgrade process will fail. For more information on the Windows Server node upgrade process, see [Upgrade a node pool in AKS][nodepool-upgrade].
 
+## Supported VM sizes
+
+The list of supported VM sizes in AKS is evolving with the release of new VM SKUs in Azure. Please follow the [AKS release notes](https://github.com/Azure/AKS/releases) to stay informed of new supported SKUs.
+
 ## Restricted VM sizes
 
 Each node in an AKS cluster contains a fixed amount of compute resources such as vCPU and memory. If an AKS node contains insufficient compute resources, pods might fail to run correctly. To ensure the required *kube-system* pods and your applications can  be reliably scheduled, **don't use the following VM SKUs in AKS**:

articles/aks/use-azure-policy.md

@@ -3,7 +3,7 @@ title: Use Azure Policy to secure your cluster
 description: Use Azure Policy to secure an Azure Kubernetes Service (AKS) cluster.
 ms.service: container-service
 ms.topic: how-to 
-ms.date: 02/17/2021
+ms.date: 09/01/2021
 ms.custom: template-how-to
 ---
 
@@ -169,6 +169,6 @@ For more information about how Azure Policy works:
 [azure-policy]: ../governance/policy/overview.md
 [azure-policy-addon]: ../governance/policy/concepts/policy-for-kubernetes.md#install-azure-policy-add-on-for-aks
 [azure-policy-addon-remove]: ../governance/policy/concepts/policy-for-kubernetes.md#remove-the-add-on-from-aks
-[azure-policy-assign-policy]: ../governance/policy/concepts/policy-for-kubernetes.md#assign-a-built-in-policy-definition
+[azure-policy-assign-policy]: ../governance/policy/concepts/policy-for-kubernetes.md#assign-a-policy-definition
 [az-aks-get-credentials]: /cli/azure/aks#az_aks_get_credentials
 [kubernetes-policy-reference]: ../governance/policy/concepts/policy-for-kubernetes.md

articles/azure-arc/servers/agent-overview.md

@@ -1,7 +1,7 @@
 ---
 title:  Overview of the Connected Machine agent
 description: This article provides a detailed overview of the Azure Arc-enabled servers agent available, which supports monitoring virtual machines hosted in hybrid environments.
-ms.date: 08/18/2021
+ms.date: 09/01/2021
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell
 ---
@@ -73,13 +73,13 @@ The Azure Connected Machine agent for Windows and Linux can be upgraded to the l
 
 ### Supported environments
 
-Arc-enabled servers support the installation of the Connected Machine agent on any physical server and virtual machine hosted *outside* of Azure. This includes virtual machines running on platforms like VMware, Azure Stack HCI, and other cloud environments. Arc-enabled servers do not support installing the agent on virtual machines running in Azure, or virtual machines running on Azure Stack Hub or Azure Stack Edge as they are already modeled as Azure VMs.
+Arc-enabled servers support the installation of the Connected Machine agent on any physical server and virtual machine hosted *outside* of Azure. Including virtual machines running on platforms like VMware, Azure Stack HCI, and other cloud environments. Arc-enabled servers do not support installing the agent on virtual machines running in Azure, or virtual machines running on Azure Stack Hub or Azure Stack Edge as they are already modeled as Azure VMs.
 
 ### Supported operating systems
 
 The following versions of the Windows and Linux operating system are officially supported for the Azure Connected Machine agent:
 
-- Windows Server 2008 R2 SP1, Windows Server 2012 R2 and higher (including Server Core)
+- Windows Server 2008 R2 SP1, Windows Server 2012 R2, 2016, 2019, and 2022 (including Server Core)
 - Ubuntu 16.04, 18.04, and 20.04 LTS (x64)
 - CentOS Linux 7 and 8  (x64)
 - SUSE Linux Enterprise Server (SLES) 12 and 15 (x64)
@@ -167,7 +167,7 @@ For more information, review [Service tags overview](../../virtual-network/servi
 
 ### Register Azure resource providers
 
-Azure Arc-enabled servers depends on the following Azure resource providers in your subscription in order to use this service:
+Azure Arc-enabled servers depend on the following Azure resource providers in your subscription in order to use this service:
 
 * **Microsoft.HybridCompute**
 * **Microsoft.GuestConfiguration**

articles/azure-arc/servers/agent-release-notes-archive.md

@@ -0,0 +1,109 @@
+---
+title: Archive for What's new with Azure Arc-enabled servers agent
+description: The What's new release notes in the Overview section for Azure Arc-enabled servers agent contains six months of activity. Thereafter, the items are removed from the main article and put into this article.
+ms.topic: overview
+ms.date: 08/27/2021
+ms.custom: references_regions
+---
+
+# Archive for What's new with Azure Arc-enabled servers agent
+
+The primary [What's new in Azure Arc-enabled servers agent?](agent-release-notes.md) article contains updates for the last six months, while this article contains all the older information.
+
+The Azure Arc-enabled servers Connected Machine agent receives improvements on an ongoing basis. This article provides you with information about:
+
+- Previous releases
+- Known issues
+- Bug fixes
+
+## March 2021
+
+Version 1.4
+
+### New features
+
+- Added support for private endpoints, which is currently in limited preview.
+- Expanded list of exit codes for azcmagent.
+- Agent configuration parameters can now be read from a file with the `--config` parameter.
+- Collect new instance metadata to determine if Microsoft SQL Server is installed on the server
+
+### Fixed
+
+Network endpoint checks are now faster.
+
+## December 2020
+
+Version: 1.3
+
+### New features
+
+Added support for Windows Server 2008 R2 SP1.
+
+### Fixed
+
+Resolved issue preventing the Custom Script Extension on Linux from installing successfully.
+
+## November 2020
+
+Version: 1.2
+
+### Fixed
+
+Resolved issue where proxy configuration could be lost after upgrade on RPM-based distributions.
+
+## October 2020
+
+Version: 1.1
+
+### Fixed
+
+- Fixed proxy script to handle alternate GC daemon unit file location.
+- GuestConfig agent reliability changes.
+- GuestConfig agent support for US Gov Virginia region.
+- GuestConfig agent extension report messages to be more verbose if there is a failure.
+
+## September 2020
+
+Version: 1.0 (General Availability)
+
+### Plan for change
+
+- Support for preview agents (all versions older than 1.0) will be removed in a future service update.
+- Removed support for fallback endpoint `.azure-automation.net`. If you have a proxy, you need to allow the endpoint `*.his.arc.azure.com`.
+- If the Connected Machine agent is installed on a virtual machine hosted in Azure, VM extensions can't be installed or modified from the Arc-enabled servers resource. This is to avoid conflicting extension operations being performed from the virtual machine's **Microsoft.Compute** and **Microsoft.HybridCompute** resource. Use the **Microsoft.Compute** resource for the machine for all extension operations.
+- Name of guest configuration process has changed, from *gcd* to *gcad* on Linux, and *gcservice* to *gcarcservice* on Windows.
+
+### New features
+
+- Added `azcmagent logs` option to collect information for support.
+- Added `azcmagent license` option to display EULA.
+- Added `azcmagent show --json` option to output agent state in easily parseable format.
+- Added flag in `azcmagent show` output to indicate if server is on a virtual machine hosted in Azure.
+- Added `azcmagent disconnect --force-local-only` option to allow reset of local agent state when Azure service cannot be reached.
+- Added `azcmagent connect --cloud` option to support other clouds. In this release, only Azure is supported by service at time of agent release.
+- Agent has been localized into Azure-supported languages.
+
+### Fixed
+
+- Improvements to connectivity check.
+- Corrected issue with proxy server settings being lost when upgrading agent on Linux.
+- Resolved issues when attempting to install agent on server running Windows Server 2012 R2.
+- Improvements to extension installation reliability
+
+## August 2020
+
+Version: 0.11
+
+- This release previously announced support for Ubuntu 20.04. Because some Azure VM extensions don't support Ubuntu 20.04, support for this version of Ubuntu is being removed.
+
+- Reliability improvements for extension deployments.
+
+### Known issues
+
+If you are using an older version of the Linux agent and it's configured to use a proxy server, you need to reconfigure the proxy server setting after the upgrade. To do this, run `sudo azcmagent_proxy add http://proxyserver.local:83`.
+
+## Next steps
+
+- Before evaluating or enabling Arc-enabled servers across multiple hybrid machines, review [Connected Machine agent overview](agent-overview.md) to understand requirements, technical details about the agent, and deployment methods.
+
+- Review the [Planning and deployment guide](plan-at-scale-deployment.md) to plan for deploying Azure Arc-enabled servers at any scale and implement centralized management and monitoring.

articles/azure-arc/servers/agent-release-notes.md

@@ -1,8 +1,9 @@
 ---
 title: What's new with Azure Arc-enabled servers agent
 description: This article has release notes for Azure Arc-enabled servers agent. For many of the summarized issues, there are links to more details.
-ms.topic: conceptual
-ms.date: 07/16/2021
+ms.topic: overview
+ms.date: 09/01/2021
+ms.custom: references_regions
 ---
 
 # What's new with Azure Arc-enabled servers agent
@@ -13,8 +14,29 @@ The Azure Arc-enabled servers Connected Machine agent receives improvements on a
 - Known issues
 - Bug fixes
 
+This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [archive for What's new with Azure Arc-enabled servers agent](agent-release-notes-archive.md).
+
+## August 2021
+
+Version 1.10
+
+### Fixed
+
+- The guest configuration policy agent can now configure and remediate system settings. Existing policy assignments continue to be audit-only. Learn more about the Azure Policy [guest configuration remediation options](../../governance/policy/concepts/guest-configuration-policy-effects.md).
+- The guest configuration policy agent now restarts every 48 hours instead of every 6 hours.
+
 ## July 2021
 
+Version 1.9
+
+## New features
+
+Added support for the Indonesian language
+
+### Fixed
+
+Fixed a bug that prevented extension management in the West US 3 region
+
 Version 1.8
 
 ### New features
@@ -65,92 +87,6 @@ Version 1.5
 - New `-json` parameter to direct output results in JSON format (when used with -useStderr).
 - Collect other instance metadata - Manufacturer, model, and cluster resource ID (for Azure Stack HCI nodes).
 
-## March 2021
-
-Version 1.4
-
-### New features
-
-- Added support for private endpoints, which is currently in limited preview.
-- Expanded list of exit codes for azcmagent.
-- Agent configuration parameters can now be read from a file with the `--config` parameter.
-- Collect new instance metadata to determine if Microsoft SQL Server is installed on the server
-
-### Fixed
-
-Network endpoint checks are now faster.
-
-## December 2020
-
-Version: 1.3
-
-### New features
-
-Added support for Windows Server 2008 R2 SP1.
-
-### Fixed
-
-Resolved issue preventing the Custom Script Extension on Linux from installing successfully.
-
-## November 2020
-
-Version: 1.2
-
-### Fixed
-
-Resolved issue where proxy configuration could be lost after upgrade on RPM-based distributions.
-
-## October 2020
-
-Version: 1.1
-
-### Fixed
-
-- Fixed proxy script to handle alternate GC daemon unit file location.
-- GuestConfig agent reliability changes.
-- GuestConfig agent support for US Gov Virginia region.
-- GuestConfig agent extension report messages to be more verbose if there is a failure.
-
-## September 2020
-
-Version: 1.0 (General Availability)
-
-### Plan for change
-
-- Support for preview agents (all versions older than 1.0) will be removed in a future service update.
-- Removed support for fallback endpoint `.azure-automation.net`. If you have a proxy, you need to allow the endpoint `*.his.arc.azure.com`.
-- If the Connected Machine agent is installed on a virtual machine hosted in Azure, VM extensions can't be installed or modified from the Arc-enabled servers resource. This is to avoid conflicting extension operations being performed from the virtual machine's **Microsoft.Compute** and **Microsoft.HybridCompute** resource. Use the **Microsoft.Compute** resource for the machine for all extension operations.
-- Name of guest configuration process has changed, from *gcd* to *gcad* on Linux, and *gcservice* to *gcarcservice* on Windows.
-
-### New features
-
-- Added `azcmagent logs` option to collect information for support.
-- Added `azcmagent license` option to display EULA.
-- Added `azcmagent show --json` option to output agent state in easily parseable format.
-- Added flag in `azcmagent show` output to indicate if server is on a virtual machine hosted in Azure.
-- Added `azcmagent disconnect --force-local-only` option to allow reset of local agent state when Azure service cannot be reached.
-- Added `azcmagent connect --cloud` option to support other clouds. In this release, only Azure is supported by service at time of agent release.
-- Agent has been localized into Azure-supported languages.
-
-### Fixed
-
-- Improvements to connectivity check.
-- Corrected issue with proxy server settings being lost when upgrading agent on Linux.
-- Resolved issues when attempting to install agent on server running Windows Server 2012 R2.
-- Improvements to extension installation reliability
-
-## August 2020
-
-Version: 0.11
-
-- This release previously announced support for Ubuntu 20.04. Because some Azure VM extensions don't support Ubuntu 20.04, support for this version of Ubuntu is being removed.
-
-- Reliability improvements for extension deployments.
-
-### Known issues
-
-If you are using an older version of the Linux agent and it's configured to use a proxy server, you need to reconfigure the proxy server setting after the upgrade. To do this, run `sudo azcmagent_proxy add http://proxyserver.local:83`.
-
 ## Next steps
 
 - Before evaluating or enabling Arc-enabled servers across multiple hybrid machines, review [Connected Machine agent overview](agent-overview.md) to understand requirements, technical details about the agent, and deployment methods.

articles/azure-arc/servers/toc.yml

@@ -4,8 +4,10 @@
   items:
   - name: About Azure Arc-enabled servers
     href: overview.md
-  - name: What's new with Connected Machine agent
+  - name: What's new with Connected Machine agent?
     href: agent-release-notes.md
+  - name: Archive for Connected Machine agent release notes
+    href: agent-release-notes-archive.md
 - name: Quickstarts
   items:
   - name: Enable Arc-enabled servers agent

articles/azure-cache-for-redis/index.yml

@@ -22,8 +22,8 @@ landingContent:
             url: cache-overview.md
       - linkListType: video
         links:
-          - text: Best practices
-            url: https://azure.microsoft.com/resources/videos/azure-redis-cache-best-practices/
+         # - text: Best practices
+         #   url: https://azure.microsoft.com/resources/videos/azure-redis-cache-best-practices/
           - text: Improve performance
             url: https://azure.microsoft.com/resources/videos/increase-performance-through-redis-cluster-in-azure-redis-cache/
           - text: Security caching

articles/azure-percept/toc.yml

@@ -95,7 +95,7 @@
           href: how-to-update-over-the-air.md
         - name: Update Azure Percept DK over a USB-C connection
           href: how-to-update-via-usb.md
-    - name: Connect to your Azure Percept DK
+    - name: Connect to/from your Azure Percept DK
       items:
         - name: Connect to Azure Percept DK over Ethernet
           href: how-to-connect-over-ethernet.md