Skip to content

Commit 4e87939

Browse files
committed
Review
1 parent a89ad11 commit 4e87939

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/purview/how-to-link-azure-data-factory.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: jingwang
66
ms.service: purview
77
ms.subservice: purview-data-catalog
88
ms.topic: how-to
9-
ms.date: 11/01/2021
9+
ms.date: 12/05/2022
1010
---
1111
# How to connect Azure Data Factory and Microsoft Purview
1212

@@ -52,7 +52,7 @@ Follow the steps below to connect an existing data factory to your Microsoft Pur
5252

5353
Some Data Factory instances might be disabled if the data factory is already connected to the current Microsoft Purview account, or the data factory doesn't have a managed identity.
5454

55-
A warning message will be displayed if any of the selected Data Factories are already connected to other Microsoft Purview account. By selecting OK, the Data Factory connection with the other Microsoft Purview account will be disconnected. No additional confirmations are required.
55+
A warning message will be displayed if any of the selected Data Factories are already connected to other Microsoft Purview account. When you select OK, the Data Factory connection with the other Microsoft Purview account will be disconnected. No other confirmations are required.
5656

5757
:::image type="content" source="./media/how-to-link-azure-data-factory/warning-for-disconnect-factory.png" alt-text="Screenshot showing warning to disconnect Azure Data Factory.":::
5858

@@ -61,7 +61,7 @@ Follow the steps below to connect an existing data factory to your Microsoft Pur
6161
6262
### How authentication works
6363

64-
Data factory's managed identity is used to authenticate lineage push operations from data factory to Microsoft Purview. When connecting data factory to Microsoft Purview on UI, it adds the role assignment automatically.
64+
Data factory's managed identity is used to authenticate lineage push operations from data factory to Microsoft Purview. When you connect your data factory to Microsoft Purview on UI, it adds the role assignment automatically.
6565

6666
Grant the data factory's managed identity **Data Curator** role on Microsoft Purview **root collection**. Learn more about [Access control in Microsoft Purview](../purview/catalog-permissions.md) and [Add roles and restrict access through collections](../purview/how-to-create-and-manage-collections.md#add-roles-and-restrict-access-through-collections).
6767

@@ -127,7 +127,7 @@ An example of this pattern would be the following:
127127

128128
### Data movement with 1:1 lineage and wildcard support
129129

130-
Another common scenario for capturing lineage, is using a wildcard to copy files from a single input dataset to a single output dataset. The wildcard allows the copy activity to match multiple files for copying using a common portion of the file name. Microsoft Purview captures file-level lineage for each individual file copied by the corresponding copy activity.
130+
Another common scenario for capturing lineage is using a wildcard to copy files from a single input dataset to a single output dataset. The wildcard allows the copy activity to match multiple files for copying using a common portion of the file name. Microsoft Purview captures file-level lineage for each individual file copied by the corresponding copy activity.
131131

132132
An example of this pattern would be the following:
133133

0 commit comments

Comments
 (0)