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/purview/concept-guidelines-pricing.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: athenads
5
5
ms.author: athenadsouza
6
6
ms.service: purview
7
7
ms.topic: conceptual
8
-
ms.date: 10/03/2021
8
+
ms.date: 04/06/2022
9
9
ms.custom: ignite-fall-2021
10
10
---
11
11
@@ -64,9 +64,18 @@ Direct costs impacting Azure Purview pricing are based on the following three di
64
64
65
65
- If the number of assets reduces in the data estate, and are then removed in the data map through subsequent incremental scans, the storage component automatically reduces and so the data map scales down
66
66
67
+
#### Automated scanning, classification and ingestion
67
68
68
-
#### Automated scanning & classification
69
+
There are two major automated processes that can trigger ingestion of metadata into Azure Purview:
70
+
1. Automatic scans using native [connectors](/azure-purview-connector-overview.md). This process includes three main steps:
71
+
- Metadata scan
72
+
- Automatic classification
73
+
- Ingestion of metadata into Azure Purview
69
74
75
+
2. Automated ingestion using Azure Data Factory and/or Azure Synapse pipelines. This process includes:
76
+
- Ingestion of metadata and lineage into Azure Purview if Azure Purview account is connected to any Azure Data Factory or Azure Synapse pipelines.
77
+
78
+
##### 1. Automatic scans using native connectors
70
79
- A **full scan** processes all assets within a selected scope of a data source whereas an **incremental scan** detects and processes assets, which have been created, modified, or deleted since the previous successful scan
71
80
72
81
- All scans (full or Incremental scans) will pick up **updated, modified, or deleted** assets
@@ -89,6 +98,9 @@ Direct costs impacting Azure Purview pricing are based on the following three di
89
98
90
99
- Align your scan schedules with Self-Hosted Integration Runtime (SHIR) VMs (Virtual Machines) size to avoid extra costs linked to virtual machines
91
100
101
+
##### 2. Automated ingestion using Azure Data Factory and/or Azure Synapse pipelines
102
+
103
+
- metadata and lineage is ingested from Azure Data Factory or Azure Synapse pipelines every time the pipelines run in the source system.
0 commit comments