Skip to content

Commit 3d9a23f

Browse files
authored
Update concept-guidelines-pricing.md
1 parent c94b655 commit 3d9a23f

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

articles/purview/concept-guidelines-pricing.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: athenads
55
ms.author: athenadsouza
66
ms.service: purview
77
ms.topic: conceptual
8-
ms.date: 10/03/2021
8+
ms.date: 04/06/2022
99
ms.custom: ignite-fall-2021
1010
---
1111

@@ -64,9 +64,18 @@ Direct costs impacting Azure Purview pricing are based on the following three di
6464

6565
- 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
6666

67+
#### Automated scanning, classification and ingestion
6768

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
6974

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
7079
- 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
7180

7281
- 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
8998

9099
- Align your scan schedules with Self-Hosted Integration Runtime (SHIR) VMs (Virtual Machines) size to avoid extra costs linked to virtual machines
91100

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.
92104

93105
#### Advanced resource sets
94106

0 commit comments

Comments
 (0)