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

Author: gitName

articles/api-management/azure-openai-enable-semantic-caching.md

@@ -61,6 +61,10 @@ Configure a [backend](backends.md) resource for the embeddings API deployment wi
         ```
         https://my-aoai.openai.azure.com/openai/deployments/embeddings-deployment/embeddings
         ```
+* **Authorization credentials** - Go to **Managed Identity** tab.
+  * **Client indentity** - Select *System assigned identity* or type in a User assigned managed identity client ID.
+  * **Resource ID** - Enter `https://cognitiveservices.azure.com/` for Azure OpenAI Service.
+
 ### Test backend 
 
 To test the backend, create an API operation for your Azure OpenAI Service API:
@@ -123,7 +127,6 @@ Configure the following policies to enable semantic caching for Azure OpenAI API
     <azure-openai-semantic-cache-lookup
         score-threshold="0.8"
         embeddings-backend-id="embeddings-deployment"
-        embeddings-backend-auth="system-assigned"
         ignore-system-messages="true"
         max-message-count="10">
         <vary-by>@(context.Subscription.Id)</vary-by>

articles/api-management/azure-openai-semantic-cache-lookup-policy.md

@@ -34,7 +34,6 @@ Use the `azure-openai-semantic-cache-lookup` policy to perform cache lookup of r
 <azure-openai-semantic-cache-lookup
     score-threshold="similarity score threshold"
     embeddings-backend-id ="backend entity ID for embeddings API"
-    embeddings-backend-auth ="system-assigned"             
     ignore-system-messages="true | false"      
     max-message-count="count" >
     <vary-by>"expression to partition caching"</vary-by>
@@ -47,7 +46,6 @@ Use the `azure-openai-semantic-cache-lookup` policy to perform cache lookup of r
 | ----------------- | ------------------------------------------------------ | -------- | ------- |
 | score-threshold	| Similarity score threshold used to determine whether to return a cached response to a prompt. Value is a decimal between 0.0 and 1.0. [Learn more](../azure-cache-for-redis/cache-tutorial-semantic-cache.md#change-the-similarity-threshold). | Yes |	N/A |
 | embeddings-backend-id | [Backend](backends.md) ID for OpenAI embeddings API call. |	Yes |	N/A |
-| embeddings-backend-auth | Authentication used for Azure OpenAI embeddings API backend. | Yes. Must be set to `system-assigned`. | N/A |
 | ignore-system-messages | Boolean. If set to `true`, removes system messages from a GPT chat completion prompt before assessing cache similarity. | No | false |
 | max-message-count | If specified, number of remaining dialog messages after which caching is skipped. | No | N/A |
                                              

articles/api-management/llm-semantic-cache-lookup-policy.md

@@ -34,7 +34,6 @@ Use the `llm-semantic-cache-lookup` policy to perform cache lookup of responses
 <llm-semantic-cache-lookup
     score-threshold="similarity score threshold"
     embeddings-backend-id ="backend entity ID for embeddings API"
-    embeddings-backend-auth ="system-assigned"             
     ignore-system-messages="true | false"      
     max-message-count="count" >
     <vary-by>"expression to partition caching"</vary-by>
@@ -47,7 +46,6 @@ Use the `llm-semantic-cache-lookup` policy to perform cache lookup of responses
 | ----------------- | ------------------------------------------------------ | -------- | ------- |
 | score-threshold	| Similarity score threshold used to determine whether to return a cached response to a prompt. Value is a decimal between 0.0 and 1.0. [Learn more](../azure-cache-for-redis/cache-tutorial-semantic-cache.md#change-the-similarity-threshold). | Yes |	N/A |
 | embeddings-backend-id | [Backend](backends.md) ID for OpenAI embeddings API call. |	Yes |	N/A |
-| embeddings-backend-auth | Authentication used for Azure OpenAI embeddings API backend. | Yes. Must be set to `system-assigned`. | N/A |
 | ignore-system-messages | Boolean. If set to `true`, removes system messages from a GPT chat completion prompt before assessing cache similarity. | No | false |
 | max-message-count | If specified, number of remaining dialog messages after which caching is skipped. | No | N/A |
                                              

articles/container-apps/java-overview.md

@@ -122,14 +122,16 @@ Cores are available in 0.25 core increments, with memory available at a 2:1 rati
 > [!NOTE]
 > For apps using JDK versions 9 and lower, make sure to define custom JVM memory settings to match the memory allocation in Azure Container Apps.
 
-## Spring components support
+## Java components support
 
-Azure Container Apps offers support for the following Spring Components as managed services:
+Azure Container Apps offers support for the following Java components as managed services:
 
 - **Eureka Server for Spring**: Service registration and discovery are key requirements for maintaining a list of live application instances. Your application uses this list to for routing and load balancing inbound requests. Configuring each client manually takes time and introduces the possibility of human error. Eureka Server simplifies the management of service discovery by functioning as a [service registry](java-eureka-server.md) where microservices can register themselves and discover other services within the system.
 
 - **Config Server for Spring**: Config Server provides centralized external configuration management for distributed systems. This component designed to address the challenges of [managing configuration settings across multiple microservices](java-config-server.md) in a cloud-native environment.
 
+- **Gateway for Spring**: Gateway for Spring offers an efficient and powerful way to route, manage and handle API requests as part of a microservices architecture. It serves as an [API Gateway](java-gateway-for-spring.md) that routes external requests to different services, adding various capabilities such as filtering, load balancing, and more. 
+
 - **Admin for Spring**： The Admin for Spring managed component provides an administrative interface is designed for Spring Boot web applications that have actuator endpoints. A managed component provides integration and management to your container app by allowing you to bind your container app to the [Admin for Spring component](java-admin.md).
 
 ## Next steps

articles/load-balancer/load-balancer-manage-health-status.md

@@ -79,9 +79,6 @@ Health status can be retrieved on a per load balancing rule basis. This is suppo
 3. On the **Load Balancers** page, select your load balancer from the list.
 4. In your load balancer's **Settings** section, select **Load balancing rules**.
 5. In the **Load balancing rules** page, select **View details** under the **Health status** column for the rule you want to view.
-   
-   :::image type="content" source="media/load-balancer-manage-health-status/load-balancing-rules-list-small.png" alt-text="Screenshot of list of load balancing rules with health status link." lightbox="media/load-balancer-manage-health-status/load-balancing-rules-list.png":::
-
 6. Review the health status of your backend instances in the **Load balancing rule health status** window.
 7. To retrieve the latest health status, select **Refresh**.
 

articles/load-balancer/load-balancer-monitor-alert-health-event-logs.md

@@ -32,9 +32,6 @@ In this section, you learn configure diagnostic settings to collect LoadBalancer
 
 1. In the Azure portal, navigate to your load balancer resource.
 1. From your load balancer resource's **Overview** page, choose  **Monitoring** > **Diagnostic settings**.
-   
-   :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/add-diagnostic-settings.png" alt-text="Screenshot of diagnostic settings window in Azure portal.":::
-
 1. Select **+ Add diagnostic setting**.
 1. In the **Diagnostic setting** window, select or enter the following settings:
 
@@ -62,12 +59,12 @@ In this section, you learn how to query LoadBalancerHealthEvent logs in a Log An
 
 1. In the Azure portal, navigate to your load balancer resource.
 1. From your load balancer resource’s **Overview** page, choose  **Monitoring** > **Logs**.
-3. In the **Queries** window, enter **Latest SNAT Port** in the search bar.
-4. From the results, select **Load to editor** under **Latest SNAT Port Exhaustion per LB Frontend**.
+1. In the **Queries** window, enter **Latest SNAT Port** in the search bar.
+1. From the results, select **Load to editor** under **Latest SNAT Port Exhaustion per LB Frontend**.
 
    :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/search-queries.png" alt-text="Screenshot of Queries window performing search for built-in query.":::
 
-5. The following code is displayed in the query editor:
+1. The following code is displayed in the query editor:
 
     ```kusto
         // Latest Snat Port Exhaustion Per LB Frontend 
@@ -79,11 +76,10 @@ In this section, you learn how to query LoadBalancerHealthEvent logs in a Log An
     ```
     :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/view-snat-query.png" alt-text="Screenshot of query editor with SNAT port exhaustion kusto query.":::
 
-6. Select **Run** to execute the query.
+1. Select **Run** to execute the query.
 1. If you want to modify and save the query, make your query changes and select **Save**>**Save as query**.
 1. In the **Save a query** window, enter a name for the query, other optional information, and select **Save**.
 
-    :::image type="content" source="media/monitor-alert-load-balancer-health-event-logs/save-snat-query.png" alt-text="Screenshot of Save a query window.":::
 
 ## Create alerts based on LoadBalancerHealthEvent logs
 

articles/load-balancer/load-balancer-test-frontend-reachability.md

@@ -104,9 +104,6 @@ This section describes how to test reachability of a standard public load balanc
 1. In the Search bar at the top of the portal, enter **Virtual machines** and select Virtual machines.
 1. In **Virtual machines**, select your virtual machine from the list.
 1. In the virtual machine’s menu, select **Networking** and then select **Add inbound port rule**.
-
-    :::image type="content" source="media/load-balancer-front-end-reachability-testing/virtual-machine-port-rules-thumb.png" alt-text="Screenshot of Virtual network page listing port rules and selection of add outbound port rule button." lightbox="media/load-balancer-front-end-reachability-testing/virtual-machine-port-rules.png":::
-
 1. In **Add inbound security rule**, enter or select the following information:
 
     | **Setting** | **Value** |
@@ -121,9 +118,6 @@ This section describes how to test reachability of a standard public load balanc
     | **Priority** | Enter **100** or a priority of your choosing. |
     | **Name** | Enter **AllowICMP** or a name of your choosing |
     | **Description** | Leave as Blank or enter a description |
-
-    :::image type="content" source="media/load-balancer-front-end-reachability-testing/add-Inbound-port-rule-thumb.png" alt-text="Screenshot of Add inbound port rule windows with settings allowing ICMP echo messages."lightbox="media/load-balancer-front-end-reachability-testing/add-Inbound-port-rule.png":::
-
 1. Select **Add**.
 
 ### Connect to the virtual machine

articles/load-balancer/manage-admin-state-how-to.md

@@ -71,13 +71,7 @@ In this section, you learn how to set an admin state to **Up** or **Down** as pa
 
 7. Select **Save**.
 8. In your **Backend pools** page, select the corresponding **Admin State** value of your recently added backend pool instance.
-   
-   :::image type="content" source="media/manage-admin-state-how-to/select-admin-state-backend-pools-window.png" alt-text="Screenshot of backend pools window with admin state link highlighted.":::
-
 9.  In your **Admin state details** window, select **Down** from the dropdown menu.
-
-    :::image type="content" source="media/manage-admin-state-how-to/set-admin-state-backend-pool-down.png" alt-text="Screenshot of admin state details windows with down selected for admin state.":::
-    
 10. Select **Save**.
 
 # [Azure PowerShell](#tab/azurepowershell)
@@ -170,9 +164,6 @@ In this section, you learn how to set an admin state to **Up** or **Down** as pa
 8. Select **Add** and **Save**.
 9. In your **Backend pools** page, select the corresponding **Admin State** value of your recently added backend pool instance.
 10. In your **Admin state details** window, select **Up** from the dropdown menu.
-    
-    :::image type="content" source="media/manage-admin-state-how-to/set-admin-state-backend-pool-up.png" alt-text="Screenshot of admin state details window with up selected for admin state.":::
-
 11.	Select **Save**.
 
 # [Azure PowerShell](#tab/azurepowershell)
@@ -264,15 +255,12 @@ In this section, you learn how to update an existing admin state from existing b
 4. In your load balancer's page, select **Backend pools** under **Settings**.
 9. In your **Backend pools** page, select the corresponding **Admin State** value of your recently added backend pool instance.
 10. In your **Admin state details** window, select **Up** from the dropdown menu.
-
-    :::image type="content" source="media/manage-admin-state-how-to/set-admin-state-backend-pool-up.png" alt-text="Screenshot of admin state details window with up selected for admin state value.":::
-
 11. Select **Save**.
 
 # [Azure PowerShell](#tab/azurepowershell)
 
 1. Connect to your Azure subscription with Azure PowerShell.
-2. Update an existing backend pool instance with the admin state value configured to UP or DOWN with [New-AzLoadBalancerBackendAddressConfig](/powershell/module/az.network/new-azloadbalancerbackendaddressconfig).. Replace the values in brackets with the names of the resources in your configuration.
+2. Update an existing backend pool instance with the admin state value configured to UP or DOWN with [New-AzLoadBalancerBackendAddressConfig](/powershell/module/az.network/new-azloadbalancerbackendaddressconfig). Replace the values in brackets with the names of the resources in your configuration.
 
     ```azurepowershell
     
@@ -359,10 +347,7 @@ In this section, you learn how to remove an existing admin state from an existin
 4. In your load balancer's page, select **Backend pools** under **Settings**.
 5. Select the corresponding **Admin State** value of your backend pool instance that you would like to remove.
 6. In your admin state’s window, select **None** from the dropdown menu.
-
-    :::image type="content" source="media/manage-admin-state-how-to/set-admin-state-backend-pool-none.png" alt-text="Screenshot of admin state details windows with none selected for admin state.":::
-
-1. Select **Save**.
+7. Select **Save**.
 
 # [Azure PowerShell](#tab/azurepowershell)