wip

Author: zhiyuanliang-ms

articles/azure-app-configuration/reference-javascript-provider.md

@@ -68,7 +68,7 @@ type AzureAppConfiguration = {
 } & IGettable & ReadonlyMap<string, any> & IConfigurationObject;
 ```
 
-For more information about `refresh` and `onRefresh` methods, see the [Dynamic refresh](#dynamic-refresh) section.
+For more information about `refresh` and `onRefresh` methods, see the [Configuration refresh](#configuration-refresh) section.
 
 ### Consume configuration
 
@@ -196,9 +196,42 @@ const settings = await load(endpoint, credential, {
 });
 ```
 
-## Dynamic refresh
+## Configuration refresh
 
-### Watch sentinel key for refresh (Deprecated)
+You can enable the dynamic refresh for the configuration through the `AzureAppConfigurationOptions.refreshOptions` property. Dynamic refresh for the configurations lets you pull their latest values from the App Configuration store without having to restart the application.
+
+```typescript
+const settings = await load(endpoint, credential, {
+    refreshOptions: {
+        enabled: true
+    }
+});
+// this call s not blocking, the configuration will be updated asynchronously
+settings.refresh();
+```
+
+Setting up `refreshOptions` alone won't automatically refresh the configuration. You need to call the `refresh` method on `AzureAppConfiguration` instance returned by the `load` method to trigger a refresh. This design prevents unnecessary requests to App Configuration when your application is idle. You should include the `refresh` call where your application activity occurs. This is known as **activity-driven configuration refresh**. For example, you can call `refresh` when processing an incoming request or inside an iteration where you perform a complex task. Calling `refresh` is a no-op before the configured refresh interval elapses, so its performance impact is minimal even if it's called frequently.
+
+```typescript
+const settings = await load(endpoint, credential, {
+    refreshOptions: {
+        enabled: true
+    }
+});
+
+const server = express();
+// Use an express middleware to achieve request-driven configuration refresh
+server.use((req, res, next) => {
+    settings.refresh();
+    next();
+})
+```
+
+By default, a refresh interval of 30 seconds is used, but you can override it with the `refreshIntervalInMs` property.
+
+This is done by providing a refresh_on to the provider, which is a list of key(s) that will be watched for changes, and when they do change a refresh can happen. refresh_interval is the period of time in seconds between refreshes. on_refresh_success is a callback that will be called only if a change is detected and no error happens. on_refresh_error is a callback that will be called when a refresh fails.
+
+For information about refresh configuration, please go to [Use dynamic configuration in JavaScript](./enable-dynamic-configuration-javascript.md).
 
 ## Feature flag
 
@@ -235,4 +268,4 @@ For information about use geo-replication, please go to [Enable geo-replication]
 To learn how to use JavaScript configuration provider, continue to the following tutorials.
 
 > [!div class="nextstepaction"]
-> [Use dynamic configuration in JavaScript](./enable-dynamic-configuration-javascript.md)
+> [Use dynamic configuration in JavaScript](./enable-dynamic-configuration-javascript.md)