Merge pull request #300290 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

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

@@ -55,15 +55,16 @@ Configuration Setting Mapping | [GA](./reference-dotnet-provider.md#configuratio
 Key Vault References | [GA](./reference-dotnet-provider.md#key-vault-reference) | GA | GA | GA | [GA](./reference-javascript-provider.md#key-vault-reference)
 Key Vault Secret Refresh | [GA](./reference-dotnet-provider.md#key-vault-secret-refresh) | WIP | GA | WIP | WIP
 Custom Key Vault Secret Resolution | [GA](./reference-dotnet-provider.md#key-vault-reference) | GA | GA | GA | [GA](./reference-javascript-provider.md#key-vault-reference)
+Parallel Secret Resolution | WIP | WIP | WIP | WIP | [GA](./reference-javascript-provider.md#parallel-secret-resolution)
 Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag)
 Variant Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag)
 Feature Flag Telemetry | GA | GA | WIP | GA | GA
 Key Prefix Trim | [GA](./reference-dotnet-provider.md#trim-prefix-from-keys) | GA | GA | GA | [GA](./reference-javascript-provider.md#trim-prefix-from-keys)
-Configurable Startup Time-out | [GA](./reference-dotnet-provider.md#startup-retry) | WIP | N/A | WIP | WIP
+Configurable Startup Time-out | [GA](./reference-dotnet-provider.md#startup-retry) | WIP | N/A | WIP | [GA](./reference-javascript-provider.md#startup-retry)
 Replica Auto Discovery | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | WIP | [GA](./reference-javascript-provider.md#geo-replication)
 Replica Failover | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | WIP | [GA](./reference-javascript-provider.md#geo-replication)
 Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | WIP | GA | WIP | [GA](./reference-javascript-provider.md#geo-replication)
-Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | WIP
+Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | [GA](./reference-javascript-provider.md#snapshot)
 Distributed tracing | [GA](./reference-dotnet-provider.md#distributed-tracing) | WIP | WIP | WIP | WIP
 Health Check | WIP | WIP | WIP | WIP | WIP
 

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

@@ -9,7 +9,7 @@ ms.service: azure-app-configuration
 ms.devlang: javascript
 ms.custom: devx-track-javascript
 ms.topic: tutorial
-ms.date: 02/02/2025
+ms.date: 05/22/2025
 #Customer intent: I want to learn how to use Azure App Configuration JavaScript client library.
 ---
 
@@ -355,6 +355,79 @@ const appConfig = await load(endpoint, credential, {
 });
 ```
 
+You can also set `clientOptions` property to configure `SecretClientOptions` used to connect to Azure Key Vault that has no registered `SecretClient`.
+
+```typescript
+const credential = new DefaultAzureCredential();
+const appConfig = await load(endpoint, credential, {
+    keyVaultOptions: {
+        credential: credential,
+        clientOptions: { // configure a custom SecretClientOptions
+            retryOptions: { 
+                maxRetries: 3, 
+                maxRetryDelayInMs: 1000 
+            }
+        }
+    }
+});
+```
+
+### Parallel secret resolution
+
+Azure Key Vault doesn't provide a batch API for retrieving multiple secrets in a single request. When your application needs to load numerous Key Vault references, you can improve performance by enabling parallel secret resolution using the `parallelSecretResolutionEnabled` property in `KeyVaultOptions`. This allows the provider to fetch multiple secrets in parallel rather than sequentially:
+
+
+```typescript
+const credential = new DefaultAzureCredential();
+const appConfig = await load(endpoint, credential, {
+    keyVaultOptions: {
+        credential: credential,
+        parallelSecretResolutionEnabled: true
+    }
+});
+```
+
+> [!NOTE]
+> When resolving secret in parallel, you may encounter the [service limit](/azure/key-vault/general/service-limits#secrets-managed-storage-account-keys-and-vault-transactions) of Azure Key Vault.
+> To handle throttling effectively, implement the [client-side throttling best practices](/azure/key-vault/general/overview-throttling#how-to-throttle-your-app-in-response-to-service-limits) by configuring appropriate retry options for the `SecretClient`. You can either register custom `SecretClient` instances or configure `clientOptions` via the `AzureAppConfigurationOptions.keyVaultOptions`.
+
+
+## Snapshot
+
+[Snapshot](./concept-snapshots.md) is a named, immutable subset of an App Configuration store's key-values. The key-values that make up a snapshot are chosen during creation time through the usage of key and label filters. Once a snapshot is created, the key-values within are guaranteed to remain unchanged.
+
+You can use snapshot selector to load key-values or feature flags from a snapshot:
+
+```typescript
+const appConfig = await load(endpoint, credential, {
+    selectors: [
+        { snapshotName: "MySnapshot" }, // load key-values from snapshot
+        { keyFilter: "test*", labelFilter: "test" }
+    ],
+    featureFlagOptions: {
+        enabled: true,
+        selectors: [
+            { snapshotName: "MySnapshot" }, // load feature flags from snapshot
+            { keyFilter: "*", labelFilter: "test" }
+        ]
+    }
+});
+```
+
+## 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.
+
+You can customize this behavior via the `AzureAppConfigurationOptions.startupOptions`:
+
+```typescript
+const appConfig = await load(endpoint, credential, { 
+    startupOptions: { 
+        timeoutInMs: 300_000
+    }
+});
+```
+
 ## Geo-replication
 
 For information about using geo-replication, go to [Enable geo-replication](./howto-geo-replication.md).

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -70,49 +70,36 @@ You can create an Azure support request to increase the adjustable limits from t
 1. Navigate to **Help** then **Support + troubleshooting**.   
 1. Under the **How can we help you** heading, enter "regional capacity quota" in the text field then select **Go**. 
 
-    :::image type="content" source="./media/azure-netapp-files-resource-limits/support-how-can-we-help.png" alt-text="Screenshot that shows the How can we help heading." lightbox="./media/azure-netapp-files-resource-limits/support-how-can-we-help.png":::
+    ![Screenshot that shows the How can we help heading.](./media/azure-netapp-files-resource-limits/support-how-can-we-help.png)
 
-    1. Under the **Current selection** heading, search for "Azure NetApp Files" in the text field for **Which service are you having an issue with?**.
-    1. Select **Azure NetApp Files** then **Next**. 
+1. Under the **Current selection** heading, search for "Service and subscription limits (Quotas)" in the text field for **Which service are you having an issue with?**.
+    1. Select **Service and subscription limits (Quotas)** then select **Next**. 
 
-        :::image type="content" source="./media/azure-netapp-files-resource-limits/support-service.png" alt-text="Screenshot of choosing a service option." lightbox="./media/azure-netapp-files-resource-limits/support-service.png":::
-    
-    1. Under **Which resource are you having an issue with?**, locate and select your subscription. Then locate and select your resource (the NetApp account).
-    
-        :::image type="content" source="./media/azure-netapp-files-resource-limits/support-resource.png" alt-text="Screenshot with the option to select your subscription and resource." lightbox="./media/azure-netapp-files-resource-limits/support-resource.png":::
-    
-    1. Under **Are you having one of the following issues?**, select **Storage: Azure NetApp Files limits** then **Next**.
-    
-        :::image type="content" source="./media/azure-netapp-files-resource-limits/support-issue.png" alt-text="Screenshot showing the option to choose Azure NetApp Files limits as an issue." lightbox="./media/azure-netapp-files-resource-limits/support-issue.png":::
-    
-    1. Select **Create a support request**. 
-
-1. Under the **Problem description** tab, provide the required information:
-    1. For **Issue Type**, select **Service and Subscription Limits (Quotas)**.
+1. Select **Create a support request**. 
+    1. For **Issue type**, select **Service and Subscription Limits (Quotas)**.
     2. For **Subscription**, select your subscription. 
-    3. For **Quota Type**, select **Storage: Azure NetApp Files limits**.  
+    3. For **Quota type**, select **Storage: Azure NetApp Files limits**.
+    4. Select **Next**.
 
     ![Screenshot that shows the Problem Description tab.](./media/shared/support-problem-descriptions.png)
 
 1. Under the **Additional details** tab, select **Enter details** in the Request Details field.  
 
     ![Screenshot that shows the Details tab and the Enter Details field.](./media/shared/quota-additional-details.png)
 
-1. To request limit increase, provide the following information in the Quota Details window that appears:
-    1. In **Quota Type**, select the type of resource you want to increase.  
-        For example:   
-        * *Regional Capacity Quota per Subscription (TiB)*
-        * *Number of NetApp accounts per Azure region per subscription*
-        * *Number of volumes per subscription*
-
-    2. In **Region Requested**, select your region.   
-        The current and default sizes are displayed under Quota State.
-    
-    3. Enter a value to request an increase for the quota type you specified.
+1. To request limit increase, provide the following information in the Quota details window that appears:
+    1. For **Quota type**, search and select **Regional Capacity Quota per Subscription (TiB)**. 
+    2. For **Region requested**, select your region.   
+    3. For **Quota State**, enter the new request value for the quota type you specified.
+    4. Select **Save and continue**. 
 
     ![Screenshot that shows how to display and request increase for regional quota.](./media/azure-netapp-files-resource-limits/quota-details-regional-request.png)
 
-1. Select **Save and continue**. Select **Review + create** to create the request.
+1. Enter the support preference details in the New support request window that appears and select **Next**.
+2. Review the details and select **Create** to create the request.
+
+>[!NOTE]
+> After the regional capacity quota limit has been increased, perform the capacity pool create and resize operation.
 
 ## Next steps  
 

articles/data-factory/connector-greenplum.md

@@ -66,14 +66,14 @@ The following sections provide details about properties that are used to define
 
 ## Linked service properties
 
-The Greenplum connector now supports version 2.0 (Preview). Refer to this [section](#upgrade-the-greenplum-connector) to upgrade your Greenplum connector version from version 1.0. For the property details, see the corresponding sections.
+The Greenplum connector now supports version 2.0. Refer to this [section](#upgrade-the-greenplum-connector) to upgrade your Greenplum connector version from version 1.0. For the property details, see the corresponding sections.
 
-- [Version 2.0 (Preview)](#version-20-preview)
+- [Version 2.0](#version-20)
 - [Version 1.0](#version-10)
 
-### Version 2.0 (Preview)
+### Version 2.0
 
-The Greenplum linked service supports the following properties when apply version 2.0 (Preview):
+The Greenplum linked service supports the following properties when apply version 2.0:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
@@ -282,7 +282,7 @@ To copy data from Greenplum, set the source type in the copy activity to **Green
 
 When you copy data from Greenplum, the following mappings apply from Greenplum's data types to the internal data types used by the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
 
-|Greenplum data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
+|Greenplum data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
 |:---|:---|:---|
 |SmallInt|Int16|Int16|
 |Integer|Int32|Int32|
@@ -342,15 +342,15 @@ To learn details about the properties, check [Lookup activity](control-flow-look
 
 Here are steps that help you upgrade your Greenplum connector:
 
-1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [linked service version 2.0 (Preview) properties](#version-20-preview).
+1. In **Edit linked service** page, select version 2.0 and configure the linked service by referring to [linked service version 2.0 properties](#version-20).
 
-2. The data type mapping for the Greenplum linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Greenplum](#data-type-mapping-for-greenplum).
+2. The data type mapping for the Greenplum linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Greenplum](#data-type-mapping-for-greenplum).
 
-## Differences between Greenplum version 2.0 (Preview) and version 1.0
+## Differences between Greenplum version 2.0 and version 1.0
 
-The Greenplum connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 (Preview) and version 1.0.
+The Greenplum connector version 2.0 offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 and version 1.0.
 
-| Version 2.0 (Preview) | Version 1.0 |
+| Version 2.0| Version 1.0 |
 | --- | --- |
 | The following mappings are used from Greenplum data types to interim service data type. <br><br> Decimal (Precision > 28) -> Decimal <br> Money -> Decimal <br> Timestamp with time zone -> DateTimeOffset <br>Time with time zone -> DateTimeOffset <br>Interval -> TimeSpan | The following mappings are used from Greenplum data types to interim service data type. <br><br> Decimal (Precision > 28) -> String <br> Money -> String <br> Timestamp with time zone ->String <br>Time with time zone -> String <br>Interval -> String | 
 

articles/data-factory/connector-presto.md

@@ -62,14 +62,14 @@ The following sections provide details about properties that are used to define
 
 ## Linked service properties
 
-The Presto connector now supports version 2.0 (Preview). Refer to this section to upgrade your Presto connector version from version 1.0. For the property details, see the corresponding sections.
+The Presto connector now supports version 2.0. Refer to this section to upgrade your Presto connector version from version 1.0. For the property details, see the corresponding sections.
 
-- [Version 2.0 (Preview)](#version-20-preview)
+- [Version 2.0](#version-20)
 - [Version 1.0](#version-10)
 
-### Version 2.0 (Preview)
+### Version 2.0 
 
-The Presto linked service supports the following properties when apply version 2.0 (Preview):
+The Presto linked service supports the following properties when apply version 2.0:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
@@ -235,7 +235,7 @@ To copy data from Presto, set the source type in the copy activity to **PrestoSo
 
 When you copy data from Presto, the following mappings apply from Presto's data types to the internal data types used by the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
 
-| Presto data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
+| Presto data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
 |:--- |:--- |:--- |
 | ARRAY | String | String |
 | BIGINT | Int64 | Int64 |
@@ -271,21 +271,21 @@ To learn details about the properties, check [Lookup activity](control-flow-look
 
 Here are steps that help you upgrade the Presto connector:
 
-1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [linked service version 2.0 (Preview) properties](#version-20-preview).
+1. In **Edit linked service** page, select version 2.0 and configure the linked service by referring to [linked service version 2.0 properties](#version-20).
 
-2. The data type mapping for the Presto linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Presto](#data-type-mapping-for-presto).
+2. The data type mapping for the Presto linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Presto](#data-type-mapping-for-presto).
 
-## Differences between Presto connector version 2.0 (Preview) and version 1.0
+## Differences between Presto connector version 2.0 and version 1.0
 
-The Presto connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 (Preview) and version 1.0.
+The Presto connector version 2.0 offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 and version 1.0.
 
-| Version 2.0 (Preview)  | Version 1.0 | 
+| Version 2.0  | Version 1.0 | 
 | :----------- | :------- |
 | `serverVersion` is not supported. | `serverVersion` is supported. |
 | The default value of `port` is 8443. | The default value of `port` is 8080. |
 | The default value of `enableSSL` is true.<br><br> `enableServerCertificateValidation` is supported. <br><br>`trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are not supported.| The default value of `enableSSL` is false.<br><br>`enableServerCertificateValidation` is not supported. <br><br> `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` is supported. |
 | The default value of `timeZoneID` is the Presto system time zone. | The default value of `timeZoneID` is the Azure Data Factory time zone. |
-| The following mappings are used from Presto data types to interim service data type.<br><br>DATE -> Date <br>DECIMAL (Precision >= 28) -> Decimal <br> DOUBLE -> Double <br>INTERVAL_DAY_TO_SECOND -> TimeSpan <br>INTERVAL_YEAR_TO_MONTH -> String<br>IPADDRESS -> String<br>TIME -> Time<br>TIMESTAMPWITHTIMEZONE -> Datetimeoffset<br>TINYINT -> SByte<br>UUID -> Guid| The following mappings are used from Presto data types to interim service data type.<br><br>DATE -> Datetime <br>DECIMAL (Precision >= 28) -> String <br>DOUBLE -> Decimal <br>TIME -> TimeSpan<br>TINYINT -> Int16<br> Other mappings supported by version 2.0 (Preview) listed left are not supported by version 1.0. |  
+| The following mappings are used from Presto data types to interim service data type.<br><br>DATE -> Date <br>DECIMAL (Precision >= 28) -> Decimal <br> DOUBLE -> Double <br>INTERVAL_DAY_TO_SECOND -> TimeSpan <br>INTERVAL_YEAR_TO_MONTH -> String<br>IPADDRESS -> String<br>TIME -> Time<br>TIMESTAMPWITHTIMEZONE -> Datetimeoffset<br>TINYINT -> SByte<br>UUID -> Guid| The following mappings are used from Presto data types to interim service data type.<br><br>DATE -> Datetime <br>DECIMAL (Precision >= 28) -> String <br>DOUBLE -> Decimal <br>TIME -> TimeSpan<br>TINYINT -> Int16<br> Other mappings supported by version 2.0 listed left are not supported by version 1.0. |  
 
 ## Related content
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).