Automatically scale your catalog with elastic Data Map in Azure Purview

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

Azure Purview continues to evolve for customers to help them govern constantly growing data estates with the new elastic Data Map. Customers can provision a Purview account with no upfront commitment for Data Map platform cost and continue to grow elastically based on consumption to fully govern their enterprise data present in analytics, software as a service (SaaS), and operation systems in hybrid, on-premises, and multi-cloud environments


Customers can provision the new Azure Purview account with Data Map platform size of one capacity unit and elastically grow in increments of one capacity unit based on usage and request load. The elastic Data Map automatically scales up and down the capacity units within the elasticity window based on consumption.

 

Capacity unit (CU)
The capacity unit in Purview includes operations throughput and storage. One Data Map CU constitutes 25 operations/second throughput and 2 GB of metadata storage (learn more).

ChandruS_0-1633653609138.png

 

Data Map billing
Billing meters for the Purview Data Map are emitted in capacity units by hour. Each CU comprises 25 operations/second and 2 GB metadata storage, with incremental, consumption-based billing for each extra capacity unit by hour (learn more with a pricing example).

ChandruS_1-1633653609152.png

 

ChandruS_2-1633653609159.png

 

What’s next with elastic Data Map?

  1. Data source registration: The Data Map allows authorized users to register multiple Data Sources (learn more) and group the data sources into Collections (learn more), enabling a hierarchical structure of your data estate based on your organization’s plans to govern your data with Azure Purview.

ChandruS_3-1633653609177.png

 

  1. Enhanced scanning and ingestion: Configure scans with custom schedules to control the population of data assets and classification and lineage across both the scanning and ingestion processes (learn more).

 

ChandruS_4-1633653609200.png

 

  1. Advanced resource set: You can reduce the size of the Data Map by processing partitioned files in a data lake such that they’re treated as a single data asset called a resource set (learn more).
  2. Increase data elasticity window with support ticket: Data Map operations throughput can automatically scale up and down within the elasticity window (current limits are 1-8 CU). For additional throughput, create a support ticket (learn more). In the support portal, select Service and subscription limits (quota) and complete the on-screen instructions by choosing the Purview account that requires additional operations throughput.

ChandruS_5-1633653609204.jpeg

 

Summary
Elastic Data Map provides a low-cost barrier for customers to start their data governance journey with a pay-as-you-go model starting with one capacity unit. Customers don’t need to worry about choosing the correct Data Map size for their data estate at provision time and dealing with platform migrations in the future because of size limits.

 

Get started today!

  • Quickly and easily create an Azure Preview account to try the generally available features.
  • Read documentation on the Azure Purview Elastic Data Map

 

 

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.