Merge branch 'main' of https://github.com/seesharprun/azure-docs-pr into cosmos-rename-how-to-model-partition-example

Author: seesharprun

articles/aks/command-invoke.md

@@ -7,7 +7,7 @@ ms.date: 1/14/2022
 
 # Use `command invoke` to access a private Azure Kubernetes Service (AKS) cluster
 
-Accessing a private AKS cluster requires that you connect to that cluster either from the cluster virtual network, from a peered network, or via a configured private endpoint. These approaches require configuring a VPN, Express Route, deploying a *jumpbox* within the cluster virtual network, or creating a private endpoint inside of another virtual network. Alternatively, you can use `command invoke` to access private clusters without having to configure a VPN or Express Route. Using `command invoke` allows you to remotely invoke commands like `kubectl` and `helm` on your private cluster through the Azure API without directly connecting to the cluster. Permissions for using `command invoke` are controlled through the `Microsoft.ContainerService/managedClusters/runcommand/action` and `Microsoft.ContainerService/managedclusters/commandResults/read` roles.
+Accessing a private AKS cluster requires that you connect to that cluster either from the cluster virtual network, from a peered network, or via a configured private endpoint. These approaches require configuring a VPN, Express Route, deploying a *jumpbox* within the cluster virtual network, or creating a private endpoint inside of another virtual network. Alternatively, you can use `command invoke` to access private clusters without having to configure a VPN or Express Route. Using `command invoke` allows you to remotely invoke commands like `kubectl` and `helm` on your private cluster through the Azure API without directly connecting to the cluster. Permissions for using `command invoke` are controlled through the `Microsoft.ContainerService/managedClusters/runcommand/action` and `Microsoft.ContainerService/managedclusters/commandResults/read` actions.
 
 ## Prerequisites
 

articles/aks/workload-identity-migrate-from-pod-identity.md

@@ -120,7 +120,7 @@ If your application is using managed identity and still relies on IMDS to get an
 To update or deploy the workload, add these pod annotations only if you want to use the migration sidecar. You inject the following [annotation][pod-annotations] values to use the sidecar in your pod specification:
 
 * `azure.workload.identity/inject-proxy-sidecar` - value is `true` or `false`
-* `azure.workload.identity/proxy-sidecar-port` - value is the desired port for the proxy sidecar. The default value is `8080`.
+* `azure.workload.identity/proxy-sidecar-port` - value is the desired port for the proxy sidecar. The default value is `8000`.
 
 When a pod with the above annotations is created, the Azure Workload Identity mutating webhook automatically injects the init-container and proxy sidecar to the pod spec.
 
@@ -148,7 +148,7 @@ spec:
       runAsUser: 0
     env:
     - name: PROXY_PORT
-      value: "8080"
+      value: "8000"
   containers:
   - name: nginx
     image: nginx:alpine
@@ -157,7 +157,7 @@ spec:
   - name: proxy
     image: mcr.microsoft.com/oss/azure/workload-identity/proxy:v0.13.0
     ports:
-    - containerPort: 8080
+    - containerPort: 8000
 ```
 
 This configuration applies to any configuration where a pod is being created. After updating or deploying your application, you can verify the pod is in a running state using the [kubectl describe pod][kubectl-describe] command. Replace the value `podName` with the image name of your deployed pod.
@@ -210,4 +210,4 @@ This article showed you how to set up your pod to authenticate using a workload
 
 <!-- EXTERNAL LINKS -->
 [kubectl-describe]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe
-[kubelet-logs]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs
+[kubelet-logs]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs

articles/azure-monitor/app/statsbeat.md

@@ -46,7 +46,8 @@ Statsbeat supports EU Data Boundary for Application Insights resources in the fo
 | Sweden                    | Sweden Central         | 
 | Switzerland               | Switzerland North      |
 | Switzerland               | Switzerland West       | 
-
+| United Kingdom            | United Kingdom South   |
+| United Kingdom            | United Kingdom West    |
 
 #### [Node](#tab/eu-node)
 
@@ -63,7 +64,9 @@ Statsbeat supports EU Data Boundary for Application Insights resources in the fo
 | Norway                    | Norway West            | 
 | Sweden                    | Sweden Central         | 
 | Switzerland               | Switzerland North      |
-| Switzerland               | Switzerland West       | 
+| Switzerland               | Switzerland West       |
+| United Kingdom            | United Kingdom South   |
+| United Kingdom            | United Kingdom West    |
 
 #### [Python](#tab/eu-python)
 
@@ -80,7 +83,9 @@ Statsbeat supports EU Data Boundary for Application Insights resources in the fo
 | Norway                    | Norway West            | 
 | Sweden                    | Sweden Central         | 
 | Switzerland               | Switzerland North      |
-| Switzerland               | Switzerland West       | 
+| Switzerland               | Switzerland West       |
+| United Kingdom            | United Kingdom South   |
+| United Kingdom            | United Kingdom West    |
 
 
 ---