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/data-factory/connector-deprecation-plan.md
+26-18Lines changed: 26 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,46 +7,54 @@ ms.service: azure-data-factory
7
7
ms.subservice: data-movement
8
8
ms.topic: concept-article
9
9
ms.custom: references_regions
10
-
ms.date: 10/11/2023
10
+
ms.date: 08/23/2024
11
11
---
12
12
13
13
# Planned connector deprecations for Azure Data Factory
14
14
15
15
This article describes future deprecations for some connectors of Azure Data Factory.
16
16
17
17
> [!NOTE]
18
-
> "Deprecated" means we intend to remove the connector from a future release. Unless they are in *Preview*, connectors remain fully supported until they are officially removed. This deprecation notification can span a few months or longer. After removal, the connector will no longer work. This notice is to allow you sufficient time to plan and update your code before the connector is removed.
18
+
> "Deprecated" means we intend to remove the connector from a future release. Unless they are in *Preview*, connectors remain fully supported until they are officially deprecated. This deprecation notification can span a few months or longer. After removal, the connector will no longer work. This notice is to allow you sufficient time to plan and update your code before the connector is deprecated.
19
19
20
20
## Legacy connectors with updated connectors or drivers available now
21
21
22
-
The following legacy connectors are deprecated, but new updated versions are available in Azure Data Factory. You can update existing data sources to use the new connectors moving forward.
22
+
The following legacy connectors or legacy driver versions will be deprecated, but new updated versions are available in Azure Data Factory. You can update existing data sources to use the new connectors moving forward.
## Use the generic ODBC connector to replace deprecated connectors
34
-
35
-
If legacy connectors are deprecated with no updated connectors available, you can still use the generic [ODBC Connector](connector-odbc.md), which enables you to continue using these data sources with their native ODBC drivers. This can enable you to continue using them indefinitely into the future.
## Connectors to be deprecated on December 31, 2024
38
35
39
-
The following connectors are scheduled for deprecation at the end of December 2024 and have no updated replacement connectors. You should plan to migrate to alternative solutions for linked services that use these connectors before the deprecation date.
36
+
The following connectors are scheduled for deprecation on December 31, 2024. You should plan to migrate to alternative solutions for linked services that use these connectors before the deprecation date.
40
37
41
-
-[Amazon Marketplace Web Service (MWS)](connector-amazon-marketplace-web-service.md)
38
+
(connector-amazon-marketplace-web-service.md)
42
39
-[Azure Database for MariaDB](connector-azure-database-for-mariadb.md)
43
40
-[Concur (Preview)](connector-concur.md)
44
41
-[Hbase](connector-hbase.md)
45
42
-[Magento (Preview)](connector-magento.md)
46
43
-[Marketo (Preview)](connector-marketo.md)
47
44
-[Paypal (Preview)](connector-paypal.md)
48
45
-[Phoenix (Preview)](connector-phoenix.md)
49
-
-[Zoho (Preview)](connector-zoho.md)
46
+
47
+
48
+
## Connectors deprecated
49
+
50
+
The following connector was deprecated.
51
+
52
+
-[Amazon Marketplace Web Service (MWS)](connector-amazon-marketplace-web-service.md)
53
+
54
+
## Options to replace deprecated connectors
55
+
56
+
If legacy connectors are deprecated with no updated connectors available, you can still use the
57
+
[ODBC Connector](connector-odbc.md) which enables you to continue using these data sources with their native ODBC drivers, or other alternatives. This can enable you to continue using them indefinitely into the future.
0 commit comments