Merge pull request #205063 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/aks/learn/quick-windows-container-deploy-cli.md

@@ -162,6 +162,8 @@ When ready, refresh the registration of the *Microsoft.ContainerService* resourc
 ```azurecli-interactive
 az provider register --namespace Microsoft.ContainerService
 ```
+> [!NOTE]
+> Windows Server 2022 requires Kubernetes version "1.23.0" or higher.
 
 Use `az aks nodepool add` command to add a Windows Server 2022 node pool:
 

articles/azure-monitor/app/sdk-connection-string.md

@@ -90,7 +90,12 @@ See also: [Regions that require endpoint modification](./custom-endpoints.md#reg
 - [Profiler](./profiler-overview.md): `profiler`
 - [Snapshot](./snapshot-debugger.md): `snapshot`
 
+#### Is Connection string a secret?
 
+Connection string contains iKey which is a unique identifier used by the ingestion service to associate telemetry to a specific Application Insights resource.  It is not to be considered a security token or key. The ingestion endpoint provides Azure AD-based authenticated telemetry ingestion options if you want to protect your AI resource from misuse.
+
+> [!NOTE]
+> Application Insights JavaScript SDK requires the connection string to be passed in during initialization/configuration.  This is viewable in plain text in client browsers. There is no easy way to use the Azure AD-based authentication for browser telemetry.  It is recommended that customers consider creating a separate Application Insights resource for browser telemetry if they need to secure the service telemetry.
 
 ## Connection string examples
 
@@ -297,4 +302,4 @@ Get started at development time with:
 * [ASP.NET Core](./asp-net-core.md)
 * [Java](./java-in-process-agent.md)
 * [Node.js](./nodejs.md)
-* [Python](./opencensus-python.md)
+* [Python](./opencensus-python.md)

articles/azure-vmware/includes/azure-vmware-solutions-limits.md

@@ -3,7 +3,7 @@ title: Azure VMware Solution limits
 description: Azure VMware Solution limitations.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 09/02/2021
+ms.date: 07/18/2022
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -24,5 +24,13 @@ The following table describes the maximum limits for Azure VMware Solution.
 | Azure VMware Solution ExpressRoute port speed | 10 Gbps<br />The virtual network gateway used determines the actual bandwidth. For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
 | Public IPs exposed via vWAN | 100 |
 | vSAN capacity limits | 75% of total usable (keep 25% available for SLA)  |
+| VMware Site Recovery Manager - Number of protected Virtual Machines  | 1,000  |
+| VMware Site Recovery Manager - Number of Virtual Machines per recovery plan  | 1,000  |
+| VMware Site Recovery Manager - Number of protection groups per recovery plan  | 250  |
+| VMware Site Recovery Manager - RPO Values  | 5 min or higher *  |
+| VMware Site Recovery Manager - Total number of virtual machines per protection group  | 500  |
+| VMware Site Recovery Manager - Total number of recovery plans  | 250  |
 
-For other VMware-specific limits, use the [VMware configuration maximum tool!](https://configmax.vmware.com/).
+\* For information about Recovery Point Objective (RPO) lower than 15 minutes, see [How the 5 Minute Recovery Point Objective Works](https://docs.vmware.com/en/vSphere-Replication/8.3/com.vmware.vsphere.replication-admin.doc/GUID-9E17D567-A947-49CD-8A84-8EA2D676B55A.html) in the _vSphere Replication Administration guide_.
+
+For other VMware-specific limits, use the [VMware configuration maximum tool](https://configmax.vmware.com/).

articles/container-instances/container-instances-managed-identity.md

@@ -102,7 +102,7 @@ spID=$(az identity show \
 resourceID=$(az identity show \
   --resource-group myResourceGroup \
   --name myACIId \
-  --query id --output tsv)
+  --query id --output none)
 ```
 
 ### Grant user-assigned identity access to the key vault

articles/virtual-machines/workloads/sap/hana-onboarding-requirements.md

@@ -32,13 +32,14 @@ This article lists the requirements for running SAP HANA on Azure Large Instance
 
 ## Operating system
 
-- Licenses for SUSE Linux Enterprise Server 12 for SAP Applications.
+- Licenses for SUSE Linux Enterprise Server 12 and SUSE Linux Enterprise Server 15 for SAP Applications.
 
    > [!NOTE] 
    > The operating system delivered by Microsoft isn't registered with SUSE. It isn't connected to a Subscription Management Tool instance.
 
 - SUSE Linux Subscription Management Tool deployed in Azure on a VM. This tool provides the capability for SAP HANA on Azure (Large Instances) to be registered and respectively updated by SUSE. (There's no internet access within the HANA Large Instance data center.) 
-- Licenses for Red Hat Enterprise Linux 6.7 or 7.x for SAP HANA.
+
+- Licenses for Red Hat Enterprise Linux 7.9 and 8.2 for SAP HANA.
 
    > [!NOTE]
    > The operating system delivered by Microsoft isn't registered with Red Hat. It isn't connected to a Red Hat Subscription Manager instance.
@@ -54,7 +55,7 @@ For the compatibility matrix of the operating system and HLI firmware/driver ver
 
 
 > [!IMPORTANT] 
-> For Type II units only the SLES 12 SP2 OS version is supported at this point. 
+> For Type II units SLES 12 SP5, SLES 15 SP2 and SLES 15 SP3 OS versions are supported at this point. 
 
 
 ## Database

articles/virtual-machines/workloads/sap/os-upgrade-hana-large-instance.md

@@ -45,23 +45,25 @@ There are a couple of known issues with the upgrade:
 The OS configuration can drift from the recommended settings over time. This drift can occur because of patching, system upgrades, and other changes you may make. Microsoft identifies updates needed to ensure HANA Large Instances are optimally configured for the best performance and resiliency. The following instructions outline recommendations that address network performance, system stability, and optimal HANA performance.
 
 ### Compatible eNIC/fNIC driver versions
-  To have proper network performance and system stability, ensure the appropriate OS-specific version of eNIC and fNIC drivers are installed per the following compatibility table. Servers are delivered to customers with compatible versions. However, drivers can get rolled back to default versions during OS/kernel patching. Ensure the appropriate driver version is running post OS/kernel patching operations.
+  To have proper network performance and system stability, ensure the appropriate OS-specific version of eNIC and fNIC drivers are installed per the following compatibility table (This table has the latest compatible driver version). Servers are delivered to customers with compatible versions. However, drivers can get rolled back to default versions during OS/kernel patching. Ensure the appropriate driver version is running post OS/kernel patching operations.
 
 
   |  OS Vendor    |  OS Package Version     |  Firmware Version  |  eNIC Driver	|  fNIC Driver | 
   |---------------|-------------------------|--------------------|--------------|--------------|
-  |   SuSE        |  SLES 12 SP2            |   3.1.3h           |  2.3.0.40    |   1.6.0.34   |
-  |   SuSE        |  SLES 12 SP3            |   3.1.3h           |  2.3.0.44    |   1.6.0.36   |
   |   SuSE        |  SLES 12 SP2            |   3.2.3i           |  2.3.0.45    |   1.6.0.37   |
   |   SuSE        |  SLES 12 SP3            |   3.2.3i           |  2.3.0.43    |   1.6.0.36   |
-  |   SuSE        |  SLES 12 SP4            |   3.2.3i           |  4.0.0.6     |   2.0.0.60   |  
+  |   SuSE        |  SLES 12 SP4            |   3.2.3i           |  4.0.0.14    |   2.0.0.63   | 
+  |   SuSE        |  SLES 12 SP5            |   3.2.3i           |  4.0.0.14    |   2.0.0.63   |
+  |   Red Hat     |  RHEL 7.6               |   3.2.3i           |  3.1.137.5   |   2.0.0.50   |
   |   SuSE        |  SLES 12 SP4            |   4.1.1b           |  4.0.0.6     |   2.0.0.60   |  
-  |   SuSE        |  SLES 12 SP5            |   3.2.3i           |  4.0.0.8     |   2.0.0.60   |
   |   SuSE        |  SLES 12 SP5            |   4.1.1b           |  4.0.0.6     |   2.0.0.59   |
   |   SuSE        |  SLES 15 SP1            |   4.1.1b           |  4.0.0.8     |   2.0.0.60   |
-  |   Red Hat     |  RHEL 7.2               |   3.1.3h           |  2.3.0.39    |   1.6.0.34   |
-  |   Red Hat     |  RHEL 7.6               |   3.2.3i           |  3.1.137.5   |   2.0.0.50   |
+  |   SuSE        |  SLES 15 SP2            |   4.1.1b           |  4.0.0.8     |   2.0.0.60   |
   |   Red Hat     |  RHEL 7.6               |   4.1.1b           |  4.0.0.8     |   2.0.0.60   |
+  |   SuSE        |  SLES 12 SP4	          |   4.1.3d           |  4.0.0.13    |   2.0.0.69   |
+  |   SuSE        |  SLES 12 SP5	          |   4.1.3d           |  4.0.0.13    |   2.0.0.69   |
+  |   SuSE        |  SLES 15 SP1	          |   4.1.3d           |  4.0.0.13    |   2.0.0.69   |
+  
 
 
 ### Commands for driver upgrade and to clean old rpm packages
@@ -151,4 +153,4 @@ grub2-mkconfig -o /boot/grub2/grub.cfg
 Learn to set up an SMT server for SUSE Linux.
 
 > [!div class="nextstepaction"]
-> [Set up SMT server for SUSE Linux](hana-setup-smt.md)
+> [Set up SMT server for SUSE Linux](hana-setup-smt.md)