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

Author: halkazwini

articles/azure-maps/media/tutorial-ev-routing/create-project.png

@@ -25,7 +25,7 @@ Users of ExpressRoute rely on the availability and performance of edge sites, WA
 There are three ExpressRoute resiliency architectures that can be utilized to ensure high availability and resiliency in your network connections between on-premises and Azure. These architecture designs include:
 
 * [Maximum resiliency](#maximum-resiliency)
-* [High resiliency](#high-resiliency---in-preview)
+* [High resiliency](#high-resiliency)
 * [Standard resiliency](#standard-resiliency)
 
 ### Maximum resiliency
@@ -34,7 +34,7 @@ The Maximum resiliency architecture in ExpressRoute is structured to eliminate a
 
 :::image type="content" source="./media/design-architecture-for-resiliency/maximum-resiliency.png" alt-text="Diagram illustrating a pair of ExpressRoute circuits, configured at two distinct peering locations, between an on-premises network and Microsoft.":::
 
-### High resiliency - In Preview
+### High resiliency
 
 High resiliency, also referred to as ExpressRoute Metro, enables the use of multiple sites within the same metropolitan (Metro) area to connect your on-premises network through ExpressRoute to Azure. High resiliency offers site diversity by splitting a single circuit across two sites. The first connection is established at one site and the second connection at a different site. The objective of ExpressRoute Metro is to mitigate the effect of edge-sites isolation and failures by introducing capabilities to enable site diversity. Site diversity is achieved by using a single circuit across paired sites within a metropolitan city, which offers resiliency to failures between edge and region. ExpressRoute Metro provides a higher level of site resiliency than Standard resiliency, but not as much as Maximum resiliency. ExpressRoute Metro architecture can be used for business and mission-critical workloads within a region. For more information, see [ExpressRoute Metro](metro.md)
 

articles/azure-maps/media/tutorial-ev-routing/install-packages.png

@@ -36,15 +36,14 @@ Here's a list of the availability zones for Azure Health Data Services.
 - UK South
 - Sweden Central
 - Germany West Central*
-- Qatar Central*
 - East US*
 - East US 2
 - South Central US*
 - West US 2*
 - West US 3*
 - Canada Central
 
-Zones marked with a star ("*") have quota issues due to high demand. Enabling AZ features in these zones may take longer.
+Regions marked with a star ("*") have quota issues due to high demand. Enabling AZ features in these regions may take longer.
 
 ### Limitations
 
@@ -74,4 +73,4 @@ To enable the availability zone on a specific instance, customers need to submit
 
 More information can be found at [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
 
-[!INCLUDE [FHIR trademark statement](includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE [FHIR trademark statement](includes/healthcare-apis-fhir-trademark.md)]

articles/azure-maps/media/tutorial-ev-routing/location-range.png

@@ -30,10 +30,10 @@ To link a BrokerListener to a *BrokerAuthentication* resource, specify the `auth
 
 ## Default BrokerAuthentication resource
 
-Azure IoT Operations Preview deploys a default *BrokerAuthentication* resource named `default` linked with the *default* listener in the `azure-iot-operations` namespace. It's configured to only use Kubernetes Service Account Tokens (SATs) for authentication. To inspect it, run:
+Azure IoT Operations Preview deploys a default *BrokerAuthentication* resource named `authn` linked with the *default* listener named `listener` in the `azure-iot-operations` namespace. It's configured to only use Kubernetes Service Account Tokens (SATs) for authentication. To inspect it, run:
 
 ```bash
-kubectl get brokerauthentication default -n azure-iot-operations -o yaml
+kubectl get brokerauthentication authn -n azure-iot-operations -o yaml
 ```
 
 The output shows the default *BrokerAuthentication* resource, with metadata removed for brevity:
@@ -42,7 +42,7 @@ The output shows the default *BrokerAuthentication* resource, with metadata remo
 apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthentication
 metadata:
-  name: default
+  name: authn
   namespace: azure-iot-operations
 spec:
   authenticationMethods:
@@ -79,7 +79,7 @@ With multiple authentication methods, MQTT broker has a fallback mechanism. For
 apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthentication
 metadata: 
-  name: default
+  name: authn
   namespace: azure-iot-operations
 spec:
   authenticationMethods: