Merge pull request #302240 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/api-management/azure-openai-api-from-specification.md

@@ -1,6 +1,6 @@
 ---
 title: Import an Azure OpenAI API as REST API - Azure API Management
-description: How to import an Azure OpenAI API as a REST API from the Azure OpenAI in Foundry Models or from an OpenAPI specification.
+description: How to import an Azure OpenAI API as a REST API from Azure OpenAI in Foundry Models or from an OpenAPI specification.
 ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
@@ -20,7 +20,8 @@ You can import AI model endpoints deployed in [Azure OpenAI in Foundry Models](/
 
 This article shows two options to import an Azure OpenAI API into an Azure API Management instance as a REST API:
 
-- [Import an Azure OpenAI API directly from Azure OpenAI in Foundry Models](#option-1-import-api-from-azure-openai) (recommended)
+- [Import an Azure OpenAI API directly from Azure OpenAI](#option-1-import-api-from-azure-openai) (recommended)
+ 
 - [Download and add the OpenAPI specification](#option-2-add-an-openapi-specification-to-api-management) for Azure OpenAI and add it to API Management as an OpenAPI API.
 
 Learn more about managing AI APIs in API Management:
@@ -35,12 +36,12 @@ Learn more about managing AI APIs in API Management:
     Make a note of the ID (name) of the deployment. You'll need it when you test the imported API in API Management.
 
     > [!NOTE]
-    > API Management policies such as [azure-openai-token-limit](azure-openai-token-limit-policy.md) and [azure-openai-emit-token-metric](azure-openai-emit-token-metric-policy.md) are supported for certain API endpoints exposed through specific Azure OpenAI models. For more information, see [Supported Azure OpenAI in Foundry Models](azure-openai-token-limit-policy.md).
+    > API Management policies such as [azure-openai-token-limit](azure-openai-token-limit-policy.md) and [azure-openai-emit-token-metric](azure-openai-emit-token-metric-policy.md) are supported for certain API endpoints exposed through specific Azure OpenAI models. For more information, see [Supported Azure OpenAI models](azure-openai-token-limit-policy.md#supported-azure-openai-in-foundry-models-models).
 
 - Permissions to grant access to the Azure OpenAI resource from the API Management instance.
 
-## Option 1. Import API from Azure OpenAI
-
+## Option 1. Import API from Azure OpenAI 
+ 
 You can import an Azure OpenAI API directly from Azure OpenAI to API Management. 
 
 [!INCLUDE [api-management-workspace-availability](../../includes/api-management-workspace-availability.md)]
@@ -135,8 +136,8 @@ To ensure that your Azure OpenAI API is working as expected, test it in the API
 1. Select an operation that's compatible with the model you deployed in the Azure OpenAI resource. 
     The page displays fields for parameters and headers.
 1. In **Template parameters**, enter the following values:
-    * `deployment-id` - the ID of a deployment in the Azure OpenAI
-    * `api-version` - a valid Azure OpenAI API version, such as the API version you selected when you imported the API.
+     * `deployment-id` - the ID of a deployment in Azure OpenAI   
+     * `api-version` - a valid Azure OpenAI API version, such as the API version you selected when you imported the API.
       :::image type="content" source="media/azure-openai-api-from-specification/test-azure-openai-api.png" alt-text="Screenshot of testing an Azure OpenAI API in the portal." lightbox="media/azure-openai-api-from-specification/test-azure-openai-api.png" :::
 1. Enter other parameters and headers as needed. Depending on the operation, you might need to configure or update a **Request body**.
     > [!NOTE]

articles/azure-app-configuration/enable-dynamic-configuration-java-spring-app.md

@@ -7,7 +7,7 @@ author: mrm9084
 ms.service: azure-app-configuration
 ms.devlang: java
 ms.topic: tutorial
-ms.date: 12/04/2024
+ms.date: 06/18/2025
 ms.custom: devx-track-java, devx-track-extended-java
 ms.author: mametcal
 #Customer intent: As a Java Spring developer, I want to dynamically update my app to use the latest configuration data in App Configuration.
@@ -29,7 +29,7 @@ Refresh allows you to update your configuration values without having to restart
 
 To use manual refresh, start with a Spring Boot app that uses App Configuration, such as the app you create by following the [Spring Boot quickstart for App Configuration](quickstart-java-spring-app.md).
 
-App Configuration exposes `AppConfigurationRefresh`, which can be used to check if the cache is expired. If it's expired, a refresh is triggered.
+App Configuration exposes `AppConfigurationRefresh`, which checks if the refresh interval has passed. If the refresh interval has passed, it triggers a refresh.
 
 1. To use `AppConfigurationRefresh`, update HelloController.
 
@@ -59,6 +59,13 @@ App Configuration exposes `AppConfigurationRefresh`, which can be used to check
 
     `AppConfigurationRefresh`'s `refreshConfigurations()` returns a `Mono` that is true if a refresh is triggered, and false if not. False means either the cache expiration time isn't expired, there was no change, or another thread is currently checking for a refresh.
 
+    > [!NOTE]
+    > For libraries such as Spring WebFlux that require non-blocking calls, `refreshConfigurations()` needs to be wrapped in a thread as loading configurations requires a blocking call. 
+    >
+    >    ```java
+    >    new Thread(() -> refresh.refreshConfigurations()).start();
+    >    ```
+            
 1.  To enable refresh update `bootstrap.properties`:
 
     ```properties
@@ -106,8 +113,8 @@ App Configuration exposes `AppConfigurationRefresh`, which can be used to check
 
 1. Refresh the browser page twice to see the new message displayed. The first time triggers the refresh, the second loads the changes.
 
-> [!NOTE]
-> The library only checks for changes on the after the refresh interval has passed. If the period hasn't passed then no change is displayed. Wait for the period to pass, then trigger the refresh check.
+    > [!NOTE]
+    > The library checks for changes only after the refresh interval passes. If the refresh interval hasn't passed, it doesn't check for changes. Wait for the interval to pass, then trigger the refresh check.
 
 ## Use automated refresh
 
@@ -119,7 +126,7 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `spr
 <dependency>
     <groupId>com.azure.spring</groupId>
     <artifactId>spring-cloud-azure-appconfiguration-config-web</artifactId>
-    <version>5.18.0</version>
+    <version>5.22.0</version>
 </dependency>
 ```
 
@@ -170,8 +177,8 @@ Then, open the *pom.xml* file in a text editor and add a `<dependency>` for `spr
 
 1. Refresh the browser page twice to see the new message displayed. The first time triggers the refresh, the second loads the changes, as the first request returns using the original scope.
 
-> [!NOTE]
-> The library only checks for changes on after the refresh interval has passed. If the refresh interval hasn't passed, then it doesn't check for changes. Wait for the interval to pass, then trigger the refresh check.
+    > [!NOTE]
+    > The library checks for changes only after the refresh interval passes. If the refresh interval hasn't passed, it doesn't check for changes. Wait for the interval to pass, then trigger the refresh check.
 
 ## Next steps
 

articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md

@@ -9,7 +9,7 @@ ms.service: azure-app-configuration
 ms.devlang: java
 ms.custom: devx-track-extended-java
 ms.topic: tutorial
-ms.date: 12/04/2024
+ms.date: 06/18/2025
 ms.author: mametcal
 #Customer intent: I want to use push refresh to dynamically update my app to use the latest configuration data in App Configuration.
 ---
@@ -63,7 +63,7 @@ In this tutorial, you learn how to:
         <dependency>
         <groupId>com.azure.spring</groupId>
         <artifactId>spring-cloud-azure-dependencies</artifactId>
-        <version>5.18.0</version>
+        <version>5.22.0</version>
         <type>pom</type>
         <scope>import</scope>
         </dependency>

articles/azure-app-configuration/feature-flag-telemetry-reference.md

@@ -21,7 +21,7 @@ In this document, you:
 
 ## Feature evaluation
 
-The Feature evaluation event is emitted whenever a feature flag that has telemetry enabled is evaluated in your application. This event, named `EvaluationEvent`, occurs each time your code checks a feature flag's status or gets a variant. The event captures the evaluation result, variant assignment details, and contextual information about why specific decisions were made.
+The Feature evaluation event is emitted whenever a feature flag that has telemetry enabled is evaluated in your application. This event, named `FeatureEvaluation`, occurs each time your code checks a feature flag's status or gets a variant. The event captures the evaluation result, variant assignment details, and contextual information about why specific decisions were made.
 
 This event contains the following fields:
 
@@ -54,4 +54,4 @@ The full schema can be found in the [App Configuration Feature Evaluation Event
 
 ## Next steps
 
-In this document, you learned about the telemetry data available for feature flags. To learn about how to use the telemetry data in your applications, continue to the following document for your language or platform.
+In this document, you learned about the telemetry data available for feature flags. To learn about how to use the telemetry data in your applications, continue to the following document for your language or platform.