Merge pull request #293612 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 1/27

Author: ttorble

articles/communication-services/how-tos/router-sdk/subscribe-events.md

@@ -240,7 +240,7 @@ dotnet run
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ]
   },
@@ -260,8 +260,8 @@ dotnet run
 | channelReference | `string` | ❌ |
 |channelId | `string` | ❌ |
 | classificationPolicyId | `string` | ❌ | |
-| queueId | `string` | ✔️ | | `null` when `classificationPolicy` is not used for queue selection
-| priority | `int` | ✔️ | | `null` when `classificationPolicy` is not used for applying priority on job
+| queueId | `string` | ❌ | |
+| priority | `int` | ❌ | |
 | labels | `Dictionary<string, object>` | ✔️ | | Based on user input
 | tags | `Dictionary<string, object>` | ✔️ | | Based on user input
 | attachedWorkerSelectors | `List<WorkerSelector>` | ✔️ | | List of worker selectors attached by a classification policy
@@ -296,15 +296,15 @@ dotnet run
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ],
     "attachedWorkerSelectors": [
       {
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ]
   },
@@ -594,20 +594,20 @@ dotnet run
       "Segment": "Enterprise",
       "Token": "FooToken"
     },
-    "requestedWorkerSelectorsExpired": [
+    "expiredRequestedWorkerSelectors": [
       {
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ],
-    "attachedWorkerSelectorsExpired": [
+    "expiredAttachedWorkerSelectors": [
       {
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ]
   },
@@ -628,8 +628,8 @@ dotnet run
 | channelId | `string` | ❌ |
 | labels | `Dictionary<string, object>` | ✔️ | | Based on user input
 | tags | `Dictionary<string, object>` | ✔️ | | Based on user input
-| requestedWorkerSelectorsExpired | `List<WorkerSelector>` | ✔️ | | Based on user input while creating a job
-| attachedWorkerSelectorsExpired | `List<WorkerSelector>` | ✔️ | | List of worker selectors attached by a classification policy
+| expiredRequestedWorkerSelectors | `List<WorkerSelector>` | ✔️ | | Based on user input while creating a job
+| expiredAttachedWorkerSelectors | `List<WorkerSelector>` | ✔️ | | List of worker selectors attached by a classification policy
 
 ### Microsoft.Communication.RouterJobUnassigned
 
@@ -708,15 +708,15 @@ dotnet run
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ],
     "attachedWorkerSelectors": [
       {
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ],
     "scheduledOn": "2022-02-17T00:55:25.1736293Z",
@@ -775,15 +775,15 @@ dotnet run
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ],
     "attachedWorkerSelectors": [
       {
         "key": "string",
         "labelOperator": "equal",
         "value": 5,
-        "ttl": "P3Y6M4DT12H30M5S"
+        "ttlSeconds": 60.0
       }
     ],
     "scheduledOn": "2022-02-17T00:55:25.1736293Z",
@@ -890,6 +890,16 @@ dotnet run
       "Segment": "Enterprise",
       "Token": "FooToken"
     },
+    "workerLabels": {
+      "Locale": "en-us",
+      "Segment": "Enterprise",
+      "Token": "FooToken"
+    },
+    "workerTags": {
+      "Locale": "en-us",
+      "Segment": "Enterprise",
+      "Token": "FooToken"
+    },
     "channelReference": "test-abc",
     "channelId": "FooVoiceChannelId",
     "queueId": "625fec06-ab81-4e60-b780-f364ed96ade1",
@@ -912,6 +922,8 @@ dotnet run
 | jobPriority| `int` | ❌ |
 | jobLabels | `Dictionary<string, object>` | ✔️ | | Based on user input
 | jobTags | `Dictionary<string, object>` | ✔️ | | Based on user input
+| workerLabels | `Dictionary<string, object>` | ✔️ | | Based on user input
+| workerTags | `Dictionary<string, object>` | ✔️ | | Based on user input
 | channelReference | `string` | ❌ |
 |channelId | `string` | ❌ |
 | queueId | `string` | ❌ |
@@ -1235,7 +1247,7 @@ public class WorkerSelector
     public object Value { get; set; }
     public double? TTLSeconds { get; set; }
     public WorkerSelectorState State { get; set; }
-    public DateTimeOffset? ExpireTime { get; set; }
+    public DateTimeOffset? ExpirationTime { get; set; }
 }
 
 public enum WorkerSelectorState

articles/data-factory/connector-azure-database-for-mariadb.md

@@ -7,15 +7,15 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 09/04/2024
+ms.date: 01/26/2025
 ---
 
 # Copy data from Azure Database for MariaDB using Azure Data Factory or Synapse Analytics
 
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 > [!IMPORTANT]
-> This connector will be deprecated on **December 31, 2024**. Please migrate to [Azure Database for MySQL connector](connector-azure-database-for-mysql.md) by that date. You can also refer to this [article](https://techcommunity.microsoft.com/t5/azure-database-for-mysql-blog/migrating-from-azure-database-for-mariadb-to-azure-database-for/ba-p/3838455) for the Azure Database for MariaDB migration guidance.
+> This connector is at [End of Support stage](connector-deprecation-plan.md). Please migrate to [Azure Database for MySQL connector](connector-azure-database-for-mysql.md). You can also refer to this [article](https://techcommunity.microsoft.com/blog/adformysql/migrating-from-azure-database-for-mariadb-to-azure-database-for-mysql/3838455) for the Azure Database for MariaDB migration guidance.
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Azure Database for MariaDB. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 

articles/data-factory/connector-concur.md

@@ -6,15 +6,15 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 09/12/2024
+ms.date: 01/26/2025
 ms.author: jianleishen
 ---
 # Copy data from Concur using Azure Data Factory or Synapse Analytics(Preview)
 
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 > [!IMPORTANT]
-> This connector will be deprecated on **December 31, 2024**. You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver before that date. 
+> This connector is at [End of Support stage](connector-deprecation-plan.md). You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver.
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Concur. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 

articles/data-factory/connector-couchbase.md

@@ -6,14 +6,14 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 11/05/2024
+ms.date: 01/26/2025
 ms.author: jianleishen
 ---
 # Copy data from Couchbase using Azure Data Factory (Preview)
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 > [!IMPORTANT]
-> This connector will be deprecated on **December 31, 2024**. You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver before that date. 
+> This connector is at [End of Support stage](connector-deprecation-plan.md). You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver.
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Couchbase. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 

articles/data-factory/connector-drill.md

@@ -6,15 +6,15 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 09/04/2024
+ms.date: 01/26/2025
 ms.author: jianleishen
 ---
 # Copy data from Drill using Azure Data Factory or Synapse Analytics
 
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 > [!IMPORTANT]
-> This connector will be deprecated on **December 31, 2024**. You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver before that date. 
+> This connector is at [End of Support stage](connector-deprecation-plan.md). You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver.
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Drill. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 

articles/data-factory/connector-google-bigquery-legacy.md

@@ -7,16 +7,16 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 12/02/2024
+ms.date: 01/26/2025
 ---
 
 # 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 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. 
+> [!IMPORTANT]
+> The [Google BigQuery V2 connector](connector-google-bigquery.md) provides improved native Google BigQuery support. If you are using the [Google BigQuery V1 connector](connector-google-bigquery-legacy.md) in your solution, please [upgrade your Google BigQuery connector](connector-google-bigquery.md#upgrade-the-google-bigquery-linked-service) as V1 is at [End of Support stage](connector-deprecation-plan.md). Refer to this [section](connector-google-bigquery.md#differences-between-google-bigquery-and-google-bigquery-legacy) for details on the difference between V2 and V1.
 
 ## Supported capabilities
 

articles/data-factory/connector-google-bigquery.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 11/05/2024
+ms.date: 01/26/2025
 ---
 
 # Copy data from Google BigQuery using Azure Data Factory or Synapse Analytics
@@ -16,8 +16,8 @@ ms.date: 11/05/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, 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. 
+> [!IMPORTANT]
+> The [Google BigQuery V2 connector](connector-google-bigquery.md) provides improved native Google BigQuery support. If you are using the [Google BigQuery V1 connector](connector-google-bigquery-legacy.md) in your solution, please [upgrade your Google BigQuery connector](#upgrade-the-google-bigquery-linked-service) as V1 is at [End of Support stage](connector-deprecation-plan.md). Refer to this [section](#differences-between-google-bigquery-and-google-bigquery-legacy) for details on the difference between V2 and V1.
 
 ## Supported capabilities
 

articles/data-factory/connector-hbase.md

@@ -6,14 +6,14 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 10/28/2024
+ms.date: 01/26/2025
 ms.author: jianleishen
 ---
 # Copy data from HBase using Azure Data Factory or Synapse Analytics
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 > [!IMPORTANT]
-> This connector will be deprecated on **December 31, 2024**. You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver before that date. 
+> This connector is at [End of Support stage](connector-deprecation-plan.md). You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver.
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from HBase. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 
@@ -34,7 +34,7 @@ The service provides a built-in driver to enable connectivity, therefore you don
 
 ## Prerequisites
 
-If your data store is a managed cloud data service, you can use the Azure Integration Runtime. If the access is restricted to IPs that are approved in the firewall rules, you can add [Azure Integration Runtime IPs](azure-integration-runtime-ip-addresses.md) to the allow list. 
+If your data store is a managed cloud data service, you can use the Azure Integration Runtime. If the access is restricted to IPs that are approved in the firewall rules, you can add [Azure Integration Runtime IPs](azure-integration-runtime-ip-addresses.md) to the allowlist. 
 
 You can also use the [managed virtual network integration runtime](tutorial-managed-virtual-network-on-premise-sql-server.md) feature in Azure Data Factory to access the on-premises network without installing and configuring a self-hosted integration runtime.
 

articles/data-factory/connector-magento.md

@@ -6,14 +6,14 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 09/04/2024
+ms.date: 01/26/2025
 ms.author: jianleishen
 ---
 # Copy data from Magento using Azure Data Factory or Synapse Analytics(Preview)
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
 > [!IMPORTANT]
-> This connector will be deprecated on **December 31, 2024**. You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver before that date. 
+> This connector is at [End of Support stage](connector-deprecation-plan.md). You are recommended to migrate to [ODBC connector](connector-odbc.md) by installing a driver.
 
 This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Magento. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 

articles/data-factory/connector-mariadb.md

@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 10/24/2024
+ms.date: 01/26/2025
 ms.author: jianleishen
 ---
 
@@ -15,8 +15,8 @@ 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 the connector with the legacy driver version, please [upgrade it](#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.  
+> [!IMPORTANT]
+> The MariaDB connector version 2.0 provides improved native MariaDB support. If you are using MariaDB connector version 1.0 in your solution, please [upgrade your MariaDB connector](#upgrade-the-mariadb-driver-version) as version 1.0 is at [End of Support stage](connector-deprecation-plan.md). Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between version 2.0 and version 1.0.
 
 ## Supported capabilities