Overview of pricing for Microsoft Purview (formerly Azure Purview)

Microsoft Purview, formally known as Azure Purview, provides a single pane of glass for managing data governance by enabling automated scanning and classifying data at scale through the Microsoft Purview governance portal.

For specific price details, see the Microsoft Purview (formerly Azure Purview) pricing page. This article will guide you through the features and factors that will affect pricing.

Why do you need to understand the components of pricing?

  • While the pricing for Microsoft Purview (formerly Azure Purview) is on a subscription-based Pay-As-You-Go model, there are various dimensions that you can consider while budgeting
  • This guideline is intended to help you plan the budgeting for Microsoft Purview in the governance portal by providing a view on the control factors that impact the budget

Factors impacting Azure Pricing

There are direct and indirect costs that need to be considered while planning budgeting and cost management.

Direct costs impacting Microsoft Purview pricing are based on these applications:

Indirect costs

Indirect costs impacting Microsoft Purview (formerly Azure Purview) pricing to be considered are:

  • Managed resources

    • When an account is provisioned, a storage account is created in the subscription in order to cater to secured scanning, which may be charged separately.
    • An Event Hubs namespace can be enabled at creation or enabled in the Azure portal on the managed resources page of the account to enable monitoring with Atlas Kafka topics events. This will be charged separately if it's enabled.
  • Azure private endpoint

    • Azure private end points are used for Microsoft Purview (formerly Azure Purview), where it's required for users on a virtual network (VNet) to securely access the catalog over a private link
    • The prerequisites for setting up private endpoints could result in extra costs
  • Self-hosted integration runtime related costs

    • Self-hosted integration runtime requires infrastructure, which results in extra costs
    • It's required to deploy and register Self-hosted integration runtime (SHIR) inside the same virtual network where Microsoft Purview ingestion private endpoints are deployed
    • Other memory requirements for scanning
      • Certain data sources such as SAP require more memory on the SHIR machine for scanning
  • Virtual Machine Sizing

    • Plan virtual machine sizing in order to distribute the scanning workload across VMs to optimize the v-cores utilized while running scans
  • Microsoft 365 license

    • Microsoft Purview Information Protection sensitivity labels can be automatically applied to your Azure assets in the Microsoft Purview Data Map.
    • Microsoft Purview Information Protection sensitivity labels are created and managed in the Microsoft Purview compliance portal.
    • To create sensitivity labels for use in Microsoft Purview, you must have an active Microsoft 365 license, which offers the benefit of automatic labeling. For the full list of licenses, see the Sensitivity labels in Microsoft Purview FAQ.
  • Azure Alerts

    • Azure Alerts can notify customers of issues found with infrastructure or applications using the monitoring data in Azure Monitor
    • The pricing for Azure Alerts is available here
  • Cost Management Budgets & Alerts

    • Automatically generated cost alerts are used in Azure to monitor Azure usage and spending based on when Azure resources are consumed
    • Azure allows you to create and manage Azure budgets. Refer tutorial
  • Multi-cloud egress charges

    • Consider the egress charges (minimal charges added as a part of the multi-cloud subscription) associated with scanning multi-cloud (for example AWS, Google) data sources running native services excepting the S3 and RDS sources

Next steps