Merge pull request #310470 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-14 12:00 UTC

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

articles/azure-app-configuration/configuration-provider-overview.md

@@ -72,7 +72,7 @@ Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | [GA]
 Distributed Tracing | [GA](./reference-dotnet-provider.md#distributed-tracing) | WIP | WIP | WIP | WIP | N/A
 Health Check | [GA](./reference-dotnet-provider.md#health-check) | GA | WIP | WIP | WIP | N/A 
 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)
-Snapshot Reference | [GA](./reference-dotnet-provider.md#snapshot-reference) | WIP | WIP | WIP | WIP | WIP
+Snapshot Reference | [GA](./reference-dotnet-provider.md#snapshot-reference) | WIP | WIP | WIP | [GA](./reference-javascript-provider.md#snapshot-reference) | WIP
 Load from Azure Front Door | [Preview](./reference-dotnet-provider.md#connect-to-azure-front-door) | WIP | WIP | WIP | [Preview](./reference-javascript-provider.md#connect-to-azure-front-door)  | WIP
 
 

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

@@ -651,6 +651,8 @@ For information about using snapshots, go to [Create and use snapshots](./howto-
 
 A snapshot reference is a configuration setting that references a snapshot in the same App Configuration store. When loaded, the provider resolves it and adds all key-values from that snapshot. Using snapshot references enables switching between snapshots at runtime, unlike `SelectSnapshot("...")`, which requires code changes and/or restarts to switch to a new snapshot.
 
+For more information about creating a snapshot reference, go to [snapshot reference concept](./concept-snapshot-references.md).
+
 > [!NOTE] 
 > To use snapshot references, use the version *8.4.0* or later of `Microsoft.Extensions.Configuration.AzureAppConfiguration`.
 

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

@@ -461,6 +461,15 @@ const appConfig = await load(endpoint, credential, {
 });
 ```
 
+### Snapshot reference
+
+A snapshot reference is a configuration setting that references a snapshot in the same App Configuration store. When loaded, the provider resolves it and adds all key-values from that snapshot. Using snapshot references enables switching between snapshots at runtime, unlike adding a snapshot selector, which requires code changes and/or restarts to switch to a new snapshot.
+
+For more information about creating a snapshot reference, go to [snapshot reference concept](./concept-snapshot-references.md).
+
+> [!NOTE] 
+> To use snapshot references, use the version *2.3.0* or later of `@azure/app-configuration-provider`.
+
 ## Startup retry
 
 Configuration loading is a critical path operation during application startup. To ensure reliability, the Azure App Configuration provider implements a robust retry mechanism during the initial configuration load. This helps protect your application from transient network issues that might otherwise prevent successful startup.

articles/connectors/connectors-create-api-cosmos-db.md

@@ -43,7 +43,7 @@ You can connect to Azure Cosmos DB from both Consumption and Standard logic app
 
 In Azure Logic Apps, every workflow must start with a [trigger](../logic-apps/logic-apps-overview.md#logic-app-concepts), which fires when a specific event happens or when a specific condition is met.
 
-If you're working with a Standard workflow, the built-in trigger named **When an item is created or modified** is available and is based on the [Azure Cosmos DB change feed design pattern](/azure/cosmos-db/sql/change-feed-design-patterns). This trigger is unavailable for Consumption workflows.
+If you're working with a Standard workflow, the built-in trigger named **When an item is created or modified** is available and is based on the [Azure Cosmos DB change feed design pattern](/azure/cosmos-db/change-feed-design-patterns). This trigger is unavailable for Consumption workflows.
 
 ### [Consumption](#tab/consumption)
 

articles/reliability/reliability-cosmos-db-nosql.md

@@ -93,7 +93,7 @@ To enable availability zone support you can use:
 
 * [Azure portal](/azure/cosmos-db/how-to-manage-database-account#add-remove-regions-from-your-database-account)
 
-* [Azure CLI](/azure/cosmos-db/sql/manage-with-cli#add-or-remove-regions)
+* [Azure CLI](/azure/cosmos-db/manage-with-cli#add-or-remove-regions)
 
 * [Azure Resource Manager templates](/azure/cosmos-db/manage-with-templates)
 

articles/sentinel/geographical-availability-data-residency.md

@@ -65,8 +65,6 @@ The following table shows the supported regions supporting Microsoft Sentinel SI
 |**Australia** | **Australia**| • Australia Central<br>Australia Central 2<br>• Australia East<br>• Australia Southeast	|  • Australia East |
 |**Africa** | **South Africa**| • South Africa North |
 
-> [!NOTE]
-> In the light of strong customer demand in public preview, at GA we are expanding Microsoft Sentinel data lake availability to additional regions. These new regions will roll out progressively over the coming weeks.
 
 > [!IMPORTANT]
 > Microsoft Sentinel data lake must be deployed in the same Azure region as the associated primary Sentinel workspace.

includes/functions-cosmosdb-attributes-v4.md

@@ -13,7 +13,7 @@ ms.author: glenga
 |**LeaseConnection** | (Optional) The name of an app setting or setting collection that specifies how to connect to the Azure Cosmos DB account that holds the lease container. <br><br> When not set, the `Connection` value is used. This parameter is automatically set when the binding is created in the portal. The connection string for the leases container must have write permissions.|
 |**LeaseDatabaseName** | (Optional) The name of the database that holds the container used to store leases. When not set, the value of the `databaseName` setting is used. |
 |**LeaseContainerName** | (Optional) The name of the container used to store leases. When not set, the value `leases` is used. |
-|**CreateLeaseContainerIfNotExists** | (Optional) When set to `true`, the leases container is automatically created when it doesn't already exist. The default value is `false`. When using Microsoft Entra identities if you set the value to `true`, creating containers is not [an allowed operation](/azure/cosmos-db/sql/troubleshoot-forbidden#non-data-operations-are-not-allowed) and your Function won't be able to start.|
+|**CreateLeaseContainerIfNotExists** | (Optional) When set to `true`, the leases container is automatically created when it doesn't already exist. The default value is `false`. When using Microsoft Entra identities if you set the value to `true`, creating containers is not [an allowed operation](/azure/cosmos-db/troubleshoot-forbidden#non-data-operations-are-not-allowed) and your Function won't be able to start.|
 |**LeasesContainerThroughput** | (Optional) Defines the number of Request Units to assign when the leases container is created. This setting is only used when `CreateLeaseContainerIfNotExists` is set to `true`. This parameter is automatically set when the binding is created using the portal. |
 |**LeaseContainerPrefix** | (Optional) When set, the value is added as a prefix to the leases created in the Lease container for this function. Using a prefix allows two separate Azure Functions to share the same Lease container by using different prefixes. |
 |**FeedPollDelay**| (Optional) The time (in milliseconds) for the delay between polling a partition for new changes on the feed, after all current changes are drained. Default is 5,000 milliseconds, or 5 seconds.|

includes/functions-cosmosdb-settings-v4.md

@@ -16,7 +16,7 @@ ms.author: glenga
 |**leaseConnection** | (Optional) The name of an app setting or setting container that specifies how to connect to the Azure Cosmos DB account that holds the lease container. <br><br> When not set, the `connection` value is used. This parameter is automatically set when the binding is created in the portal. The connection string for the leases container must have write permissions.|
 |**leaseDatabaseName** | (Optional) The name of the database that holds the container used to store leases. When not set, the value of the `databaseName` setting is used. |
 |**leaseContainerName** | (Optional) The name of the container used to store leases. When not set, the value `leases` is used. |
-|**createLeaseContainerIfNotExists** | (Optional) When set to `true`, the leases container is automatically created when it doesn't already exist. The default value is `false`. When using Microsoft Entra identities if you set the value to `true`, creating containers is not [an allowed operation](/azure/cosmos-db/sql/troubleshoot-forbidden#non-data-operations-are-not-allowed) and your Function won't be able to start. |
+|**createLeaseContainerIfNotExists** | (Optional) When set to `true`, the leases container is automatically created when it doesn't already exist. The default value is `false`. When using Microsoft Entra identities if you set the value to `true`, creating containers is not [an allowed operation](/azure/cosmos-db/troubleshoot-forbidden#non-data-operations-are-not-allowed) and your Function won't be able to start. |
 |**leasesContainerThroughput** | (Optional) Defines the number of Request Units to assign when the leases container is created. This setting is only used when `createLeaseContainerIfNotExists` is set to `true`. This parameter is automatically set when the binding is created using the portal. |
 |**leaseContainerPrefix** | (Optional) When set, the value is added as a prefix to the leases created in the Lease container for this function. Using a prefix allows two separate Azure Functions to share the same Lease container by using different prefixes. |
 |**feedPollDelay**| (Optional) The time (in milliseconds) for the delay between polling a partition for new changes on the feed, after all current changes are drained. Default is 5,000 milliseconds, or 5 seconds.|