Azure Purview Pricing example
Azure Purview pricing?
Note: Billing for Azure Purview will commence November 1, 2021.
Updated October 31st, 2021
Pricing for Elastic Data Map and Scanning for Other Sources are changed and updated in the blog below.
Since my last post on Azure Purview announcements and new functionalities I got some questions regarding pricing. In the meantime the pricing page has been updated and I’ve created also a new Azure Purview instance in my subscription(after August 18th). Currently most of the Azure Purview components are still free until further Notice. To get more details I still recommend everyone to watch the Azure Purview event from September 28th 2021, https://azuredatagovernance.eventcore.com/
Updated September 29th, 2021
Yesterday Microsoft announced the General Availability of Azure Purview, more on the announcement can be found in the blog from Rohan Kumar
Since September 28, 2021, the price of Azure Purview has been adjusted. The main change is that the use of the Elastic Data Map will remain free until November 1, 2021. To encourage trial of the Elastic Data Map, we are providing all customers free usage of Data Map from August 16, 2021 to October 31, 2021. I’ve updated the pricing details below.
As a small recap:
Azure Purview Elastic Data Map
|Capacity Unit||€0.353 per 1 Capacity Unit Hour|
Billing for Data Map capacity unit consumption will commence November 1, 2021.
When you have created your Azure Purview after Augusts 18th, you will see that you are currently not charged for the Data Map Units.
As you can see, no charging anymore for Data Map, I’m only charged for my scanning, which I only do manually do save some costs.
Automated Scanning & Classification
|For Power BI online||Free for a limited time|
|For SQL Server on-prem||Free for a limited time|
|For other data sources||€0.540 per 1 vCore Hour|
|Resource Set||€0.18 per 1 vCore Hour|
Billing for scanning duration will commence November 1, 2021.
Based on the example which is published on the pricing page, I’ve done a Calculation:
Data Map can scale capacity elastically based on the request load. Request load is measured in terms of data map operations per second. As a cost control measure, a Data Map is configured by default to elastically scale up to a peak of 8 times the steady state capacity.
For dev/trial usage:
Data Map (Always on): 1 capacity unit x Price per capacity unit per hour x 730 hours per month
Scanning (Pay as you go): Total duration (in minutes) of all scans in a month / 60 min per hour x 32 vCore per scan x €0.540 per vCore per hour
Resource Set: Total duration (in hours) of processing resource set data assets in a month * Price per vCore per hour
The total cost per month for Azure Purview = cost of Data Map + cost of Scanning + cost of Resource Set
Assuming above Scenario that we only use 1 Capacity Unit and use not more then 2 GB of Metadata storage and we scan our data once a week for 2 hours.
Data Map 1 CPU x €0.353 X 730 hours = €257,69
Scanning 4 scans x 2 hours x 32 VCore x €0.540 per vCore per hour = €138,24
Resource Set 4 scans x 1 hour x €0.18 per vCore per hour €0,72
In Total €396,65including 4 scans. If you leave Azure Purview as is and no scanning you base fee will be €257,69.
Like always, in case you have questions, leave them in the comments or send me a message.
where do you get that detailed breakdown of activity/cost on your purview account
You can select the details in the cost analysis by selectin table view. Create a filter based on your Purview account. In the table view group by MeterSubCategory.
Let me if it works for you
just wondering where the 32vCore comes from?
Great questions, just used it as an example. When scanning data you will see that the capacity units will always go up. I did run a scan and check in the cost analysis how much I spend on that scan per Vcore and used the outcome for the example
With best regards,