Azure Purview Costs in Public Preview explained

Why are you potentially charged for Azure Purview during the public preview?

Since I published my post that Azure Purview started billing as of January 21th, I got a lot of questions how billing was working.

As a small recap:

Azure Purview Data Map

Capacity Unit €0.289 per 1 Capacity Unit Hour
Provisioned API throughput. 1 capacity unit = 1 API/sec
Includes 4 capacity units for free until February 28, 2021.
Metadata Storage Free

When you have created your Azure Purview with 4 capacity Units it looks like Azure Purview is free, but that’s not entirely true. Below is an overview of my costs of Azure Purview (4 capacity units) from the last 10 days of January.

Azure Purview Costs

My costs are rising every day, to save some money I changed my weekly scans to manual scans. But that’s only a small amount of the total.

Looking into detail you will see that you are charged for around 25 a day, what will be 750 a Month.

When we do the calculation from the table in the beginning of this Article.  We have 4 Capacity units, each unit cost €0.289, 24 hrs a day. 4x€0.289X24 =€27,74. So that means that we are charged for our 4 Capacity units, which should be for free until February 28, 2021. Strange

Azure Purview Costs Detail


After I had some contact with the Product Team I got the following answer/explanation back:

During Preview, you can pick from two sizes for the Data Map – 4 Capacity Units for trials/dev or 16 Capacity units for actual usage.

Till Feb 28th, 2021, use of the 4 CU Data Map and 16 vCore-hour is as a free offer.

This offer is only available for customers with the following subscription offer types:

  • Pay-As-You-Go (MS-AZR-0003P),
  • Microsoft Azure Enterprise (MS-AZR-0017P)
  • Microsoft Azure Plan (MS-AZR-0017G)
  • Azure in CSP (MS-AZR-0145P)
  • Enterprise Dev/Test (MS-AZR-0148P)

Free quantities are applied at the enrollment level for enterprise customers. Free quantities are applied at the subscription level for pay-as-you-go customers.

For comparison, customers can get started with Azure Purview for as low as $18k a year, where as typical boxed-software Data Catalogs typically start at $25-50k for software and then require VM costs + devops maintenance costs and can’t be scaled up/down for scanning. The good news is that development to auto-scale, smaller starting size and smaller increments of the dedicated capacity of the Data Map is in progress so by GA, you’ll be able to try Azure Purview accounts for a fraction of the current cost.

Unfortunately, MSDN subscriptions and free trial subscriptions don’t get the free offer benefit, hence you’re seeing this show up. I recommend trying Azure Purview in one of your Azure subscriptions that’s eligible for the free offer.

Useful links

Check my previous and updated post for more price details on scanning  Azure Purview Public Preview Starts billing


Hopefully this article explains a bit the current costs you see for Azure Purview right now.

Like always, in case you have questions, leave them in the comments or send me a message.

Feel free to leave a comment


Submit a Comment

Your email address will not be published. Required fields are marked *

eighteen + seven =

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

Exploring Azure Synapse Analytics Studio

Azure Synapse Workspace Settings In my previous article, I walked you through "how to create your Azure Synapse Analytics Workspace". It's now time to explore the brand new Synapse Studio. Most configuration and settings can be done through the Synapse Studio. In your...

Azure Data Factory: How to assign a Customer Managed Key

Customer key With this new functionality you can add extra security to your Azure Data Factory environment. Where the data was first encrypted with a randomly generated key from Microsoft, you can now use the customer-managed key feature. With this Bring Your Own Key...

Azure DevOps and Azure Feature Pack for Integration Services

Azure Feature Pack for Integration ServicesAzure Blob Storage A great addition for SSIS is using extra connectors like  Azure Blob Storage or Azure Data Lake Store which are added by the Azure Feature Pack. This Pack needs to be installed on your local machine. Are...

Azure Data Factory Naming Conventions

Naming Conventions More and more projects are using Azure Data Factory, the more important it is to apply a correct naming convention. When using naming conventions you create recognizable results across different projects, but you also create clarity for your...

Azure Data Factory Let’s get started

Creating an Azure Data Factory Instance, let's get started Many blogs nowadays are about which functionalities we can use within Azure Data Factory. But how do we create an Azure Data Factory instance in Azure for the first time and what should you take into account? ...

Create an Azure Synapse Analytics SQL Pool

Adding a new SQL Pool There are 2 options to create a SQL Pool. Go to your Synapse Workspace in de Azure Portal and add a new SQL Pool. Or go to the Management Tab in your Azure Synapse Workspace and add a new Pool. Creating a new SQL Pool SQL Pool Name (SQL pool name...

Create an Azure Synapse Analytics Apache Spark Pool

Adding a new Apache Spark Pool There are 2 options to create an Apache Spark Pool.Go to your Azure Synapse Analytics Workspace in de Azure Portal and add a new Apache Spark Pool. Or go to the Management Tab in your Azure Synapse Analytics Workspace and add a new...

Azure SQL Data Warehouse: Reserved Capacity versus Pay as You go

How do I use my Reserved Capacity correctly? Update 11-11-2020: This also applies to Azure Synapse SQL Pools. In my previous article you were introduced, how to create a Reserved Capacity for an Azure SQL Datawarehouse (SQLDW). Now it's time to take a look at how this...

Scale your SQL Pool dynamically in Azure Synapse

Scale your Dedicated SQL Pool in Azure Synapse Analytics In my previous article, I explained how you can Pause and Resume your Dedicated SQL Pool with a Pipeline in Azure Synapse Analytics. In this article I will explain how to scale up and down a SQL Pool via a...

How to setup Code Repository in Azure Data Factory

Why activate a Git Configuration? The main reasons are: Source Control: Ensures that all your changes are saved and traceable, but also that you can easily go back to a previous version in case of a bug. Continuous Integration and Continuous Delivery (CI/CD): Allows...