Merge pull request #289401 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: Taojunshen

articles/container-apps/TOC.yml

@@ -227,7 +227,7 @@
           href: managed-identity.md
         - name: Azure Container Registry image pull with managed identity
           href: managed-identity-image-pull.md
-- name: Resiliency (preview)
+- name: Resiliency
   items:
     - name: Service discovery resiliency
       href: service-discovery-resiliency.md
@@ -264,7 +264,7 @@
         items:
         - name: Dapr components
           href: dapr-components.md
-        - name: Dapr component resiliency (preview)
+        - name: Dapr component resiliency
           href: dapr-component-resiliency.md
         - name: Scale Dapr apps with KEDA using Bicep
           href: dapr-keda-scaling.md

articles/container-apps/dapr-component-resiliency.md

@@ -1,5 +1,5 @@
 ---
-title: Dapr component resiliency (preview)
+title: Dapr component resiliency
 titleSuffix: Azure Container Apps
 description: Learn how to make your Dapr components resilient in Azure Container Apps.
 services: container-apps
@@ -12,7 +12,7 @@ ms.custom: ignite-fall-2023, ignite-2023, devx-track-azurecli
 # Customer Intent: As a developer, I'd like to learn how to make my container apps resilient using Azure Container Apps.
 ---
 
-# Dapr component resiliency (preview)
+# Dapr component resiliency
 
 Resiliency policies proactively prevent, detect, and recover from your container app failures. In this article, you learn how to apply resiliency policies for applications that use Dapr to integrate with different cloud services, like state stores, pub/sub message brokers, secret stores, and more. 
 

articles/container-apps/service-discovery-resiliency.md

@@ -1,5 +1,5 @@
 ---
-title: Service discovery resiliency (preview)
+title: Service discovery resiliency
 titleSuffix: Azure Container Apps
 description: Learn how to apply container app to container app resiliency when using the application's service name in Azure Container Apps.
 services: container-apps
@@ -12,7 +12,7 @@ ms.custom: ignite-fall-2023, ignite-2023, devx-track-azurecli
 # Customer Intent: As a developer, I'd like to learn how to make my container apps resilient using Azure Container Apps.
 ---
 
-# Service discovery resiliency (preview)
+# Service discovery resiliency
 
 With Azure Container Apps resiliency, you can proactively prevent, detect, and recover from service request failures using simple resiliency policies. In this article, you learn how to configure Azure Container Apps resiliency policies when initiating requests using Azure Container Apps service discovery.
 
@@ -238,7 +238,7 @@ az containerapp resiliency delete --group MyResourceGroup --name MyResiliency --
 
 # [Azure portal](#tab/portal)
 
-Navigate into your container app in the Azure portal. In the left side menu under **Settings**, select **Resiliency (preview)** to open the resiliency pane.
+Navigate into your container app in the Azure portal. In the left side menu under **Settings**, select **Resiliency** to open the resiliency pane.
 
 :::image type="content" source="media/service-discovery-resiliency/resiliency-pane.png" alt-text="Screenshot demonstrating how to access the service discovery resiliency pane.":::
 

articles/dev-box/concept-dev-box-network-requirements.md

@@ -144,7 +144,7 @@ The following table is the list of FQDNs and endpoints your dev boxes need to ac
 
 |Address    |Protocol    |Outbound port    |Purpose    |Service tag|
 |---|---|---|---|---|
-|login.microsoftonline.com    |TCP    |443    |Authentication to Microsoft Online Services |    
+|login.microsoftonline.com    |TCP    |443    |Authentication to Microsoft Online Services | AzureActiveDirectory |    
 |*.wvd.microsoft.com    |TCP    |443    |Service traffic    |WindowsVirtualDesktop |
 |*.prod.warm.ingest.monitor.core.windows.net    |TCP    |443    |Agent traffic [Diagnostic output](/azure/virtual-desktop/diagnostics-log-analytics) |AzureMonitor |
 |catalogartifact.azureedge.net    |TCP    |443    |Azure Marketplace    |AzureFrontDoor.Frontend|

articles/event-grid/handler-event-grid-namespace-topic.md

@@ -102,7 +102,7 @@ Now, you're ready to create an event subscription to the system topic for the so
 1. On the **Create Event Subscription** page, follow these steps:
     1. For **Name**, enter the name for an event subscription.
     1. For **Event Schema**, select the event schema as **Cloud Events Schema v1.0**. It's the only schema type that the Event Grid Namespace Topic destination supports.
-    1. For **Filter to Event Types**, select types of events you want to subscribe too. 
+    1. For **Filter to Event Types**, select types of events you want to subscribe to. 
     1. For **Endpoint type**, select **Event Grid Namespace Topic**.
     1. Select **Configure an endpoint**.
 

articles/event-hubs/schema-registry-concepts.md

@@ -34,7 +34,7 @@ To learn more about using Avro schema format with Event Hubs Schema Registry, se
 - [How to use schema registry with Kafka and Avro](schema-registry-kafka-java-send-receive-quickstart.md)
 - [How to use Schema registry with Event Hubs .NET SDK (AMQP) and Avro.](schema-registry-dotnet-send-receive-quickstart.md)
 
-#### JSON Schema (Preview)
+#### JSON Schema
 [JSON Schema](https://json-schema.org/) is a standardized way of defining the structure and data types of the events. JSON Schema enables the confident and reliable use of the JSON data format in event streaming. 
 
 To learn more about using JSON schema format with Event Hubs Schema Registry, see:  

articles/iot-edge/tutorial-monitor-with-workbooks.md

@@ -50,9 +50,9 @@ A Log Analytics workspace is necessary to collect the metrics data and provides
 
 1. Once your workspace is created, select **Go to resource**.
 
-1. From the main menu under **Settings**, select **Agents management**.
+1. From the main menu under **Settings**, select **Agents**.
 
-1. Copy the values of **Workspace ID** and **Primary key**. You'll use these two values later in the tutorial to configure the metrics collector module to send the metrics to this workspace.
+1. Copy the values of **Workspace ID** and **Primary key**, available under 'Log Analytics agent instructions'. You'll use these two values later in the tutorial to configure the metrics collector module to send the metrics to this workspace.
 
 ## Retrieve your IoT hub resource ID
 

articles/oracle/oracle-db/oracle-database-regions.md

@@ -22,7 +22,7 @@ The following table lists Azure regions and corresponding OCI regions that suppo
 |----------------|--------------------------|-------------------|-------------------|
 | Australia East | Australia East (Sydney)  | ✓  |          ✓                      |
 | Southeast Asia | Singapore (Singapore)  | ✓  |          ✓                      |
-| Japan East     | Japan East(Tokyo)  | ✓  |          ✓                      |
+| Japan East     | Japan East(Tokyo)  | ✓  |                                 |
 
 ## Europe, Middle East, Africa (EMEA)