You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/configuration-provider-overview.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: zhiyuanliang-ms
7
7
ms.author: zhiyuanliang
8
8
ms.service: azure-app-configuration
9
9
ms.topic: overview
10
-
ms.date: 01/22/2025
10
+
ms.date: 02/04/2026
11
11
#Customer intent: I want to learn about the configuration provider libraries of different languages, specifically to track their feature development status.
JSON Content Type Handling | [GA](./reference-dotnet-provider.md#json-content-type-handling) | [GA](/azure/developer/java/spring-framework/app-configuration-support#json) | GA | [GA](./reference-python-provider.md#json-content-type-handling) | [GA](./reference-javascript-provider.md#json-content-type-handling) | [GA](./reference-go-provider.md#json-content-type-handling)
57
-
JSON with Comments | [GA](./reference-dotnet-provider.md#json-content-type-handling) | GA | GA | GA | [GA](./reference-javascript-provider.md#json-content-type-handling) | [GA](./reference-go-provider.md#json-content-type-handling)
JSON with Comments | [GA](./reference-dotnet-provider.md#json-content-type-handling) | GA | GA | [GA](./reference-python-provider.md#json-content-type-handling) | [GA](./reference-javascript-provider.md#json-content-type-handling) | [GA](./reference-go-provider.md#json-content-type-handling)
Variant Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag) | [GA](./reference-go-provider.md#feature-flags)
65
-
Feature Flag Telemetry | [GA](./reference-dotnet-provider.md#feature-flag-telemetry) | GA | GA | GA | GA | WIP
65
+
Feature Flag Telemetry | [GA](./reference-dotnet-provider.md#feature-flag-telemetry) | GA | GA | [GA](./reference-python-provider.md#feature-flag-telemetry) | GA | WIP
66
66
Key Prefix Trim | [GA](./reference-dotnet-provider.md#trim-prefix-from-keys) | GA | GA | [GA](./reference-python-provider.md#trimming-keys) | [GA](./reference-javascript-provider.md#trim-prefix-from-keys) | [GA](./reference-go-provider.md#trim-prefix-from-keys)
Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | GA | [GA](./reference-javascript-provider.md#geo-replication) | [GA](./reference-go-provider.md#geo-replication)
70
+
Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | [GA](./reference-python-provider.md#geo-replication) | [GA](./reference-javascript-provider.md#geo-replication) | [GA](./reference-go-provider.md#geo-replication)
71
71
Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | [GA](./reference-python-provider.md#load-configuration-from-snapshots) | [GA](./reference-javascript-provider.md#snapshot) | [GA](./reference-go-provider.md#snapshot)
Select by Tag Filters | [GA](./reference-dotnet-provider.md#load-specific-key-values-using-selectors) | WIP | GA | GA | [GA](./reference-javascript-provider.md#tag-filters) | [GA](./reference-go-provider.md#tag-filters)
74
+
Select by Tag Filters | [GA](./reference-dotnet-provider.md#load-specific-key-values-using-selectors) | WIP | GA | [GA](./reference-python-provider.md#tag-filters) | [GA](./reference-javascript-provider.md#tag-filters) | [GA](./reference-go-provider.md#tag-filters)
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/feature-management-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: zhiyuanliang-ms
7
7
ms.author: zhiyuanliang
8
8
ms.service: azure-app-configuration
9
9
ms.topic: overview
10
-
ms.date: 01/22/2025
10
+
ms.date: 02/04/2026
11
11
#Customer intent: I want to learn about the feature management libraries of different languages, specifically to track their feature development status.
> Starting with version *2.2.0* of `azure-appconfiguration-provider`, the configuration provider allows comments, as defined in ([JSONC](https://jsonc.org/)), in key-values with an `application/json` content type.
99
+
97
100
### Load specific key-values using selectors
98
101
99
102
By default, the `load` method loads all configurations with no label from the configuration store. You can configure the behavior of the `load` method through the optional parameter of `selects`, which is a list of `SettingSelector`s.
> Key-values are loaded in the order in which the selectors are listed. If multiple selectors retrieve key-values with the same key, the value from the last one overrides any previously loaded value.
115
118
119
+
#### Tag filters
120
+
121
+
The tag filters parameter selects key-values with specific tags. A key-value is only loaded if it has all of the tags and corresponding values specified in the filters.
122
+
123
+
```python
124
+
from azure.appconfiguration.provider import load, SettingSelector
> The characters asterisk (`*`), comma (`,`), and backslash (`\`) are reserved and must be escaped with a backslash when used in a tag filter.
133
+
116
134
### Load configuration from snapshots
117
135
118
136
You can load configuration settings from [snapshots](./concept-snapshots.md) by using the `snapshot_name` parameter in `SettingSelector`. When you specify a snapshot name, all configuration settings from that snapshot are loaded. The `snapshot_name` parameter can't be used with `key_filter`, `label_filter`, or `tag_filters`.
print(config["message"]) # Access the key "message" instead of "/application/message"
143
161
```
144
162
163
+
### Configuration setting mapping
164
+
165
+
The `configuration_mapper` parameter allows you to transform configuration settings before they're processed and added to the provider. The mapper function receives each `ConfigurationSetting` object and can modify it in-place.
The provider can be configured to pull the latest settings from the App Configuration store without having to restart the application. You can use the `refresh_on` parameter to enable this behavior. The `refresh_on` parameter is a `List[WatchKey]`, which specifies the one or more key/labels to watch for changes. The loaded configuration is updated when any change of selected key-values is detected on the server. By default, a refresh interval of 30 seconds is used, but you can override it with the `refresh_interval` parameter.
@@ -225,6 +280,16 @@ print(f"Beta is: {feature_manager.is_enabled("Beta")}")
225
280
226
281
For more information about how to use the Python feature management library, go to the [feature flag quickstart](./quickstart-feature-flag-python.md).
227
282
283
+
### Feature flag telemetry
284
+
285
+
When feature flag telemetry is enabled, the Azure App Configuration provider injects additional properties to feature flag telemetry data. These properties provide more context about the feature flag and its evaluation:
286
+
287
+
-**AllocationID**: A unique identifier representing the state of the feature flag's allocation.
288
+
-**ETag**: The current ETag for the feature flag.
289
+
-**FeatureFlagReference**: A reference to the feature flag in the format of `<your_store_endpoint>kv/<feature_flag_key>`. When a label is present, the reference includes it as a query parameter: `<your_store_endpoint>kv/<feature_flag_key>?label=<feature_flag_label>`.
290
+
291
+
The full schema can be found in the [App Configuration Feature Evaluation Event schema definition](https://github.com/microsoft/FeatureManagement/blob/main/Schema/FeatureEvaluationEvent/AppConfigurationFeatureEvaluationEvent.v1.0.0.schema.json). For more information about how to use the feature flag telemetry, go to the [enable telemetry for feature flags](./howto-telemetry.md) walkthrough.
292
+
228
293
### Feature flag refresh
229
294
230
295
To enable refresh for feature flags, you need to set `feature_flag_refresh_enabled=True`. This parameter allows the provider to refresh feature flags the same way it refreshes configurations. Unlike configurations, all loaded feature flags are monitored for changes and cause a refresh. Refresh of configuration settings and feature flags are independent of each other. Both configuration settings and feature flags are updated by the `refresh` method, but a feature flag changing doesn't cause a refresh of configurations and vice versa. Also, if refresh for configuration settings isn't enabled, feature flags can still be enabled for refresh.
Azure App Configuration enables you to configure secret refresh intervals independently of your configuration refresh cycle. This is crucial for security because while the Key Vault reference URI in App Configuration remains unchanged, the underlying secret in Key Vault might be rotated as part of your security practices.
365
+
366
+
To ensure your application always uses the most current secret values, configure the `secret_refresh_interval` key word in `load`. This forces the provider to retrieve fresh secret values from Key Vault when:
367
+
368
+
- Your application calls `refresh`
369
+
- The configured refresh interval for the secret has elapsed
370
+
371
+
This mechanism works even when no changes are detected in your App Configuration store, ensuring your application stays in sync with rotated secrets.
372
+
373
+
```python
374
+
from azure.appconfiguration.provider import load
375
+
from azure.identity import DefaultAzureCredential
376
+
377
+
config = load(
378
+
endpoint=endpoint,
379
+
credential=DefaultAzureCredential(),
380
+
keyvault_credential=DefaultAzureCredential(),
381
+
secret_refresh_interval=7200# 2 hours
382
+
)
383
+
```
384
+
296
385
## Geo-replication
297
386
298
387
The Azure App Configuration Provider library automatically discovers the provided configuration store's replicas and uses the replicas if any issue arises. For more information, see [geo-replication](./howto-geo-replication.md).
| Account Kind | Only block blobs in a standard general-purpose v2 HNS-enabled storage account. <br><br>*Accounts using Network File Shares (NFS) 3.0, and Secure File Transfer Protocol (SFTP) protocols for blobs are currently not supported*.|
Copy file name to clipboardExpand all lines: articles/backup/confidential-vm-backup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This article describes how to configure and back up Confidential VM (CVM) with P
25
25
26
26
Before you configure backup for CVM with CMK, ensure that the following prerequisites are met:
27
27
28
-
- Register for the preview feature `RestorePointSupportForConfidentialVMV2`under the `Microsoft.Compute` provider namespace by running the following cmdlet. The registration is autoapproved.
28
+
- Register for the preview feature in your Azure subscription - Name: `RestorePointSupportForConfidentialVMV2`Provider: `Microsoft.Compute`. You can follow the steps [here to do this on the portal.](../azure-resource-manager/management/preview-features.md) You can also run the following PowerShell cmdlet. The registration is autoapproved.
0 commit comments