Merge pull request #276422 from MicrosoftDocs/main

ttorble · web-flow · commit 74706eaec15a · 2024-05-27T12:25:48.000+01:00
Publish to live, Monday 4 AM PST, 5/27
diff --git a/articles/ai-services/speech-service/batch-synthesis-properties.md b/articles/ai-services/speech-service/batch-synthesis-properties.md
@@ -108,7 +108,6 @@ Here are examples that can result in the 400 error:
 - The number of requested text inputs exceeded the limit of 10,000.
 - You tried to use an invalid deployment ID or a custom voice that isn't successfully deployed. Make sure the Speech resource has access to the custom voice, and the custom voice is successfully deployed. You must also ensure that the mapping of `{"your-custom-voice-name": "your-deployment-ID"}` is correct in your batch synthesis request.
 - You tried to use a _F0_ Speech resource, but the region only supports the _Standard_ Speech resource pricing tier.
-- You tried to create a new batch synthesis job that would exceed the limit of 300 active jobs. Each Speech resource can have up to 300 batch synthesis jobs that don't have a status of "Succeeded" or "Failed".
 
 ### HTTP 404 error
 
diff --git a/articles/ai-services/speech-service/batch-synthesis.md b/articles/ai-services/speech-service/batch-synthesis.md
@@ -348,7 +348,6 @@ Here are examples that can result in the 400 error:
 - The number of requested text inputs exceeded the limit of 10,000.
 - You tried to use an invalid deployment ID or a custom voice that isn't successfully deployed. Make sure the Speech resource has access to the custom voice, and the custom voice is successfully deployed. You must also ensure that the mapping of `{"your-custom-voice-name": "your-deployment-ID"}` is correct in your batch synthesis request.
 - You tried to use a _F0_ Speech resource, but the region only supports the _Standard_ Speech resource pricing tier.
-- You tried to create a new batch synthesis job that would exceed the limit of 300 active jobs. Each Speech resource can have up to 300 batch synthesis jobs that don't have a status of "Succeeded" or "Failed".
 
 ### HTTP 404 error
 
diff --git a/articles/ai-services/speech-service/text-to-speech-avatar/custom-avatar-record-video-samples.md b/articles/ai-services/speech-service/text-to-speech-avatar/custom-avatar-record-video-samples.md
@@ -93,6 +93,7 @@ This video clip is important if you build a real-time conversation with the cust
   - Maintain status 0, don't speak, but still feel relaxed.
   - Even remaining in status 0, don't keep completely still; you can move a little bit but not too much. Perform like you're waiting.
   - Maintain a smile as if listening or waiting patiently.
+  - Avoid nodding frequently.
   - Length: 1 minute.
     
 **Samples of silent status:** 
diff --git a/articles/data-factory/connector-google-bigquery-legacy.md b/articles/data-factory/connector-google-bigquery-legacy.md
@@ -8,16 +8,16 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 03/12/2024
+ms.date: 05/22/2024
 ---
 
 # Copy data from Google BigQuery using Azure Data Factory or Synapse Analytics (legacy)
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 This article outlines how to use Copy Activity in Azure Data Factory and Synapse Analytics pipelines to copy data from Google BigQuery. It builds on the [Copy Activity overview](copy-activity-overview.md) article that presents a general overview of the copy activity.
 
->[!Important]
->The service has released a new Google BigQuery connector which provides better native Google BigQuery support, refer to [Google BigQuery](connector-google-bigquery.md) article on details.
+>[!IMPORTANT]
+>The new Google BigQuery connector provides improved native Google BigQuery support. If you are using the legacy Google BigQuery connector in your solution, please [upgrade your Google BigQuery connector](connector-google-bigquery.md#upgrade-the-google-bigquery-linked-service) before **October 31, 2024**. Refer to this [section](connector-google-bigquery.md#differences-between-google-bigquery-and-google-bigquery-legacy) for details on the difference between the legacy and latest version. 
 
 ## Supported capabilities
 
diff --git a/articles/data-factory/connector-google-bigquery.md b/articles/data-factory/connector-google-bigquery.md
@@ -8,7 +8,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 04/17/2024
+ms.date: 05/22/2024
 ---
 
 # Copy data from Google BigQuery using Azure Data Factory or Synapse Analytics
@@ -17,8 +17,8 @@ ms.date: 04/17/2024
 
 This article outlines how to use Copy Activity in Azure Data Factory and Synapse Analytics pipelines to copy data from Google BigQuery. It builds on the [Copy Activity overview](copy-activity-overview.md) article that presents a general overview of the copy activity.
 
->[!Important]
->The new Google BigQuery connector provides improved native Google BigQuery support. If you are using the legacy Google BigQuery connector in your solution, supported as-is for backward compatibility only, refer to [Google BigQuery connector (legacy)](connector-google-bigquery-legacy.md) article.
+>[!IMPORTANT]
+>The new Google BigQuery connector provides improved native Google BigQuery support. If you are using the legacy Google BigQuery connector in your solution, please [upgrade your Google BigQuery connector](#upgrade-the-google-bigquery-linked-service) before **October 31, 2024**. Refer to this [section](#differences-between-google-bigquery-and-google-bigquery-legacy) for details on the difference between the legacy and latest version. 
 
 ## Supported capabilities
 
diff --git a/articles/data-factory/connector-mariadb.md b/articles/data-factory/connector-mariadb.md
@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 04/17/2024
+ms.date: 05/22/2024
 ms.author: jianleishen
 ---
 
@@ -16,6 +16,9 @@ ms.author: jianleishen
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from MariaDB. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 
+>[!IMPORTANT]
+>MariaDB connector using the recommended driver version provides improved native MariaDB support. If you are using it with the legacy driver version, please [upgrade your driver version](#upgrade-the-mariadb-driver-version) before **October 31, 2024**. Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between the legacy and recommended version.  
+
 ## Supported capabilities
 
 This MariaDB connector is supported for the following capabilities:
@@ -294,9 +297,9 @@ Here are steps that help you upgrade your MariaDB driver version:
 
 1. The latest driver version v2 supports more MariaDB versions. For more information, see [Supported capabilities](connector-mariadb.md#supported-capabilities). 
 
-## Differences between MariaDB using the recommended driver version and using the legacy driver version
+## Differences between the recommended and the legacy driver version
 
-The table below shows the data type mapping differences between MariaDB connector using the recommended driver version and using the legacy driver version.
+The table below shows the data type mapping differences between MariaDB using the recommended and the legacy driver version.
 
 |MariaDB data type |Interim service data type (using the recommended driver version) |Interim service data type (using the legacy driver version)|
 |:---|:---|:---|
diff --git a/articles/data-factory/connector-mysql.md b/articles/data-factory/connector-mysql.md
@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 04/17/2024
+ms.date: 05/22/2024
 ms.author: jianleishen
 ---
 
@@ -20,6 +20,9 @@ This article outlines how to use the Copy Activity in Azure Data Factory and Syn
 >[!NOTE]
 >To copy data from or to [Azure Database for MySQL](../mysql/overview.md) service, use the specialized [Azure Database for MySQL connector](connector-azure-database-for-mysql.md).
 
+>[!IMPORTANT]
+>MySQL connector using the recommended driver version provides improved native MySQL support. If you are using it with the legacy driver version, please [upgrade your driver version](#upgrade-the-mysql-driver-version) before **October 31, 2024**. Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between the legacy and recommended version. 
+
 ## Supported capabilities
 
 This MySQL connector is supported for the following capabilities:
@@ -323,9 +326,9 @@ Here are steps that help you upgrade your MySQL driver version:
 
 1. The latest driver version v2 supports more MySQL versions. For more information, see [Supported capabilities](connector-mysql.md#supported-capabilities).
 
-## Differences between MySQL using the recommended driver version and using the legacy driver version
+## Differences between the recommended and the legacy driver version
 
-The table below shows the data type mapping differences between MySQL connector using the recommended driver version and using the legacy driver version.
+The table below shows the data type mapping differences between MySQL using the recommended and the legacy driver version.
 
 |MySQL data type |Interim service data type (using the recommended driver version) |Interim service data type (using the legacy driver version)|
 |:---|:---|:---|
diff --git a/articles/data-factory/connector-postgresql-legacy.md b/articles/data-factory/connector-postgresql-legacy.md
@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 03/07/2024
+ms.date: 05/22/2024
 ms.author: jianleishen
 ---
 # Copy data from PostgreSQL using Azure Data Factory or Synapse Analytics (legacy)
@@ -16,7 +16,7 @@ ms.author: jianleishen
 This article outlines how to use the Copy Activity in Azure Data Factory and Synapse Analytics pipelines to copy data from a PostgreSQL database. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 
 >[!IMPORTANT]
->The service has released a new PostgreSQL connector which provides better native PostgreSQL support, refer to [PostgreSQL connector](connector-postgresql.md) article on details.
+>The new PostgreSQL connector provides improved native PostgreSQL support. If you are using the legacy PostgreSQL connector in your solution, please [upgrade your PostgreSQL connector](connector-postgresql.md#upgrade-the-postgresql-linked-service) before **October 31, 2024**. Refer to this [section](connector-postgresql.md#differences-between-postgresql-and-postgresql-legacy) for details on the difference between the legacy and latest version. 
 
 ## Supported capabilities
 
diff --git a/articles/data-factory/connector-postgresql.md b/articles/data-factory/connector-postgresql.md
@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 04/17/2024
+ms.date: 05/22/2024
 ms.author: jianleishen
 ---
 # Copy data from PostgreSQL using Azure Data Factory or Synapse Analytics
@@ -16,7 +16,7 @@ ms.author: jianleishen
 This article outlines how to use the Copy Activity in Azure Data Factory and Synapse Analytics pipelines to copy data from a PostgreSQL database. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 
 >[!IMPORTANT]
->The new PostgreSQL connector provides improved native PostgreSQL support and better performance. If you are using the legacy PostgreSQL connector in your solution, supported as-is for backward compatibility only, refer to [PostgreSQL connector (legacy)](connector-postgresql-legacy.md) article.
+>The new PostgreSQL connector provides improved native PostgreSQL support. If you are using the legacy PostgreSQL connector in your solution, please [upgrade your PostgreSQL connector](#upgrade-the-postgresql-linked-service) before **October 31, 2024**. Refer to this [section](#differences-between-postgresql-and-postgresql-legacy) for details on the difference between the legacy and latest version. 
 
 ## Supported capabilities
 
diff --git a/articles/data-factory/connector-snowflake-legacy.md b/articles/data-factory/connector-snowflake-legacy.md
@@ -8,7 +8,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 02/06/2024
+ms.date: 05/22/2024
 ---
 
 # Copy and transform data in Snowflake using Azure Data Factory or Azure Synapse Analytics (legacy)
@@ -18,7 +18,7 @@ ms.date: 02/06/2024
 This article outlines how to use the Copy activity in Azure Data Factory and Azure Synapse pipelines to copy data from and to Snowflake, and use Data Flow to transform data in Snowflake. For more information, see the introductory article for [Data Factory](introduction.md) or [Azure Synapse Analytics](../synapse-analytics/overview-what-is.md).
 
 >[!IMPORTANT]
->The service has released a new Snowflake connector which provides better native Snowflake support, refer to [Snowflake connector](connector-snowflake.md) article on details.
+>The new Snowflake connector provides improved native Snowflake support. If you are using the legacy Snowflake connector in your solution, please [upgrade your Snowflake connector](connector-snowflake.md#upgrade-the-snowflake-linked-service) before **October 31, 2024**. Refer to this [section](connector-snowflake.md#differences-between-snowflake-and-snowflake-legacy) for details on the difference between the legacy and latest version. 
 
 ## Supported capabilities
 
diff --git a/articles/data-factory/connector-snowflake.md b/articles/data-factory/connector-snowflake.md
@@ -8,7 +8,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 04/11/2024
+ms.date: 05/22/2024
 ---
 
 # Copy and transform data in Snowflake using Azure Data Factory or Azure Synapse Analytics
@@ -18,7 +18,7 @@ ms.date: 04/11/2024
 This article outlines how to use the Copy activity in Azure Data Factory and Azure Synapse pipelines to copy data from and to Snowflake, and use Data Flow to transform data in Snowflake. For more information, see the introductory article for [Data Factory](introduction.md) or [Azure Synapse Analytics](../synapse-analytics/overview-what-is.md).
 
 >[!IMPORTANT]
->The new Snowflake connector provides improved native Snowflake support. If you are using the legacy Snowflake connector in your solution, supported as-is for backward compatibility only, refer to [Snowflake connector (legacy)](connector-snowflake-legacy.md) article.
+>The new Snowflake connector provides improved native Snowflake support. If you are using the legacy Snowflake connector in your solution, please [upgrade your Snowflake connector](#upgrade-the-snowflake-linked-service) before **October 31, 2024**. Refer to this [section](#differences-between-snowflake-and-snowflake-legacy) for details on the difference between the legacy and latest version. 
 
 ## Supported capabilities
 
diff --git a/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md b/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md
@@ -257,29 +257,17 @@ To provision or reconfigure your Azure-SSIS IR with custom setups using Azure Po
 
 ### Standard custom setup samples
 
-To view and reuse some samples of standard custom setups, complete the following steps.
+1. You can view and reuse some [samples of standard custom setups](https://github.com/Azure/Azure-DataFactory/tree/main/SamplesV2/SQLServerIntegrationServices/publicpreview/CustomSetupScript):
 
-1. Connect to our Public Preview blob container using Azure Storage Explorer.
-
-   a. Under **Local and Attached**, right-click **Storage Accounts**, and then select **Connect to Azure Storage**.
-
-      :::image type="content" source="media/how-to-configure-azure-ssis-ir-custom-setup/custom-setup-image1.png" alt-text="Connect to Azure Storage":::
-
-   b. Select **Blob container**, select **Shared access signature URL (SAS)**, and then select **Next**.
-
-   c. In the **Blob container SAS URL** text box, enter the SAS URI for our Public Preview blob container below, select **Next**, and then select **Connect**.
-
-      `https://ssisazurefileshare.blob.core.windows.net/publicpreview?sp=rl&st=2020-03-25T04:00:00Z&se=2025-03-25T04:00:00Z&sv=2019-02-02&sr=c&sig=WAD3DATezJjhBCO3ezrQ7TUZ8syEUxZZtGIhhP6Pt4I%3D`
-
-   d. In the left pane, select the connected **publicpreview** blob container, and then double-click the *CustomSetupScript* folder. In this folder are the following items:
+    a. In this folder are the following items:
 
       * A *Sample* folder, which contains a custom setup to install a basic task on each node of your Azure-SSIS IR. The task does nothing but sleep for a few seconds. The folder also contains a *gacutil* folder, whose entire content (*gacutil.exe*, *gacutil.exe.config*, and *1033\gacutlrc.dll*) can be copied as is to your blob container.
 
       * A *UserScenarios* folder, which contains several custom setup samples from real user scenarios. If you want to install multiple samples on your Azure-SSIS IR, you can combine their custom setup script (*main.cmd*) files into a single one and upload it with all of their associated files into your blob container.
 
         :::image type="content" source="media/how-to-configure-azure-ssis-ir-custom-setup/custom-setup-image11.png" alt-text="Contents of the public preview blob container":::
 
-   e. Double-click the *UserScenarios* folder to find the following items:
+    b. Double-click the *UserScenarios* folder to find the following items:
 
       * A *.NET FRAMEWORK 3.5* folder, which contains a custom setup script (*main.cmd*) to install an earlier version of the .NET Framework on each node of your Azure-SSIS IR. This version might be required by some custom components.
 
@@ -339,7 +327,7 @@ To view and reuse some samples of standard custom setups, complete the following
 
         :::image type="content" source="media/how-to-configure-azure-ssis-ir-custom-setup/custom-setup-image12.png" alt-text="Folders in the user scenarios folder":::
 
-   f. To reuse these standard custom setup samples, copy the content of selected folder to your blob container.
+    c. To reuse these standard custom setup samples, copy the content of selected folder to your blob container.
 
 1. When you provision or reconfigure your Azure-SSIS IR on ADF UI, select the **Customize your Azure-SSIS Integration Runtime with additional system configurations/component installations** check box on the **Advanced settings** page of **Integration runtime setup** pane. Next, enter the SAS URI of your blob container in the **Custom setup container SAS URI** text box.
    
diff --git a/articles/load-testing/how-to-export-test-results.md b/articles/load-testing/how-to-export-test-results.md
diff --git a/articles/load-testing/media/how-to-export-test-results/download-dashboard.png b/articles/load-testing/media/how-to-export-test-results/download-dashboard.png
diff --git a/articles/sentinel/cef-syslog-ama-overview.md b/articles/sentinel/cef-syslog-ama-overview.md
diff --git a/articles/sentinel/connect-cef-syslog-ama.md b/articles/sentinel/connect-cef-syslog-ama.md
