Skip to content

Commit 77024ca

Browse files
Clare Zheng (Shanghai Wicresoft Co Ltd)Clare Zheng (Shanghai Wicresoft Co Ltd)
authored andcommitted
Update according to feedback
1 parent e88c5c7 commit 77024ca

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/data-factory/connector-deprecation-frequently-asked-questions.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Data Factory Connector V1 Deprecation – External FAQ
2+
title: Connector Deprecation FAQ
33
description: Get answers to frequently asked questions about connector deprecation.
44
author: KrishnakumarRukmangathan
55
ms.author: krirukm
@@ -10,7 +10,7 @@ ms.custom: references_regions
1010
ms.date: 10/17/2024
1111
---
1212

13-
# Azure Data Factory Connector V1 Deprecation – External FAQ
13+
# Connector Deprecation FAQ
1414

1515
## 1. Why does Azure Data Factory (ADF) release new connectors and ask users to upgrade their existing connectors?
1616

@@ -21,10 +21,9 @@ At Azure Data Factory (ADF), we are committed to continually enhancing our platf
2121
- Better supportability, ensuring quicker response times and bug fixes.
2222
- Enhanced security through a more robust application model
2323

24-
2524
## 2. Which users should be concerned about this?
2625

27-
If your data factory includes any of the connectors listed in the parent article announcing the **End of Support**, you should plan to migrate to the newer version of the connector or explore alternative solutions before the deprecation/disabled date.
26+
If your data factory includes any of the connectors listed in the [parent article](connector-deprecation-plan.md) announcing the **End of Support**, you should plan to migrate to the newer version of the connector or explore alternative solutions before the deprecation/disabled date.
2827

2928
Alternatively, you can check if you have any impacted objects in your data factory by navigating to **Manage → Linked Services** page. If you have any legacy connectors, an alert icon will be displayed beside those linked services.
3029

@@ -67,7 +66,7 @@ There are three key deadlines outlined in our documentation:
6766

6867
## 6. What should I do if I encounter the feature gaps and errors/ bugs that are preventing me from migrating to the new connectors?
6968

70-
If you encounter any feature gaps while migrating from legacy connectors, please review our connector documentation to check if it’s a known limitation. Additionally, send us an email at [email protected] with a description of the feature gap.
69+
If you encounter any feature gaps while migrating from legacy connectors, please review our connector documentation to check if it’s a known limitation. Additionally, send us an email at **[email protected]** with a description of the feature gap.
7170

7271
If you encounter any errors or bugs while migrating from legacy connectors, please contact our Microsoft support team and open a support ticket. Be sure to include detailed information about the connector, the error encountered, and your use case.
7372

0 commit comments

Comments
 (0)