TL;DR
Microsoft Purview bills two ways at once. Your Microsoft 365 data is covered by per-user licenses such as E3, E5, or the $12 per user per month Purview Suite add-on. Everything outside Microsoft 365 bills through an Azure subscription as pay-as-you-go consumption. Most enterprises end up paying under both models, so a seat count alone will never give you the real number.
Key Takeaways Microsoft Purview licensing runs on two complementary billing models, per-user licensing for Microsoft 365 data and pay-as-you-go consumption for everything else, which Microsoft’s own documentation calls complementary rather than mutually exclusive. Microsoft 365 E5 lists at $60.00 per user per month on an annual commitment and includes every Purview Suite feature; the standalone Purview Suite add-on lists at $12.00 per user per month over an eligible E3 base. Pay-as-you-go meters are priced in units most buyers have never modeled, including assets per day, processing units of compute, text records of 1,000 characters, gigabytes, and outbound requests. Licensing is per user and it follows benefit, not administration; Microsoft’s rule is that any user benefiting from the service requires a license, though visitor and view-only roles do not. Microsoft 365 Business Premium cannot use the E5 Purview Suite add-on and has its own separate SKU, a distinction several widely-read licensing guides still get wrong. Removing a license does not cleanly reverse Purview; applied sensitivity labels persist, encryption behavior splits by storage location, and unlicensed OneDrive accounts go read-only after 60 days. Two Invoices, One Product, and a Bill Nobody Modeled Microsoft’s billing documentation works through a scenario worth sitting with. A tenant has a SQL Server with 100 tables. Fifty carry a Confidential label, twenty carry a General label, while a protection policy covers the Confidential set.
The billable asset count is 50, not 100 and not 70. Purview counts assets by what a policy covers, not by what the scanner found or what the policy matched. That single distinction therefore separates a Purview forecast that holds from one that doubles in month two.
Microsoft Purview licensing has become two procurement conversations wearing one product name, and that is why a single number rarely answers the budget question. In this article, we’ll cover the two billing models, verified 2026 list prices, what each metering unit measures, who genuinely needs a seat, what breaks when a license goes away, and a seven-step assessment to run before the purchase order.
The Two Billing Models Behind Every Microsoft Purview Invoice Purview charges through two mechanisms that operate side by side, although only one of them ever reaches a Microsoft 365 invoice. The first is the per-user subscription model built on Microsoft 365 E3, E5, F5, A5, and G5 plus a set of narrower add-ons, covering Microsoft 365 workloads and Windows or macOS endpoints. The second is pay-as-you-go consumption billed through Azure, covering data outside Microsoft 365 such as Azure SQL, Microsoft Fabric, cloud object storage, third-party applications, and generative AI apps.
Microsoft is unusually direct about how the two relate. The billing-models documentation states that the pay-as-you-go model builds on the per-user model and the two are complementary, not mutually exclusive . Buyers who read that as a choice tend to underbuy one side, so the other arrives as a surprise later.
A hard prerequisite catches finance teams late, although the documentation states it clearly enough. Pay-as-you-go billing is Azure-based, so the Microsoft 365 tenant must be linked to an active Azure subscription before any consumption meter can run. No Azure subscription means no governance over non-Microsoft 365 data, however many E5 seats you hold.
Kanerika Service
Data Governance Delivered on Microsoft Purview
Kanerika designs and runs Purview governance for enterprises through kanGovern, kanComply and kanGuard, covering policy design, classification, and the consumption model behind the bill.
Explore Data Governance What Microsoft Purview Actually Costs in 2026 List prices below were checked against Microsoft’s published pages on 20 August 2026. Every figure is US list, and Microsoft attaches its own caveat that prices may vary based on your agreement.
Table 1. Microsoft Purview per-user list pricing, verified August 2026
Plan or add-on US list price Commitment What it gives you Microsoft 365 E5 $60.00 user/month Annual, paid yearly, auto-renews All Purview Suite features plus the full productivity, identity, endpoint and threat stack Microsoft 365 E5 (no Teams) $51.45 user/month Annual, paid yearly, auto-renews Same Purview coverage, Teams removed from the bundle Microsoft Purview Suite $12.00 user/month Annual, paid yearly, auto-renews Advanced Purview only. Requires Microsoft 365 E3, or Office 365 E3 with EMS E3 Purview Data Governance Pay-as-you-go Consumption Unified Catalog, governed assets, data quality Purview Data Security Pay-as-you-go Consumption Protection for data outside Microsoft 365 Purview Data Compliance Pay-as-you-go Consumption Audit, eDiscovery and lifecycle beyond Microsoft 365
Source: Microsoft Purview pricing , verified 20 August 2026. US list prices shown.
One line on that page matters to anyone modeling a Copilot rollout. Microsoft states that Purview delivers the most value in Microsoft 365 E5, which includes Security Copilot at no additional cost . Read that as bundled entitlement rather than unlimited consumption, since Security Copilot is separately metered in security compute units on the Azure rate card.
E3 vs E5 vs Purview Suite: Where Each Capability Sits Almost every Purview buying conversation collapses into one question, because the routes to the same control differ sharply in cost. Do we upgrade the whole tenant to E5, bolt Purview Suite onto an existing E3 estate, or buy a narrower add-on for one capability? Microsoft’s own FAQ draws the line cleanly, with E3 carrying core capabilities, Purview Suite carrying the advanced set, and E5 carrying both plus the rest of the E5 stack.
Table 2. Purview capability split across E3, Purview Suite, and E5
Capability area Microsoft 365 E3 Purview Suite add-on Microsoft 365 E5 DLP for Exchange, SharePoint, OneDrive Included Included Included Manual and default sensitivity labeling Included Included Included Audit and eDiscovery (Standard) Included Included Included Data Lifecycle Management, Compliance Manager Included Included Included Automatic labeling at scale Not included Included Included Insider Risk Management Not included Included Included Communication Compliance Not included Included Included Records Management Not included Included Included Copilot oversharing and risky-use protection Not included Included Included Productivity, identity, endpoint, threat protection Partial None Included
Source: Microsoft Purview pricing FAQ , verified 20 August 2026.
If you need only one advanced area, three narrower SKUs exist. Microsoft’s licensing guidance lists Information Protection and Governance, Insider Risk Management, and eDiscovery and Audit as separate E5, A5, and G5 add-ons alongside the full Purview Suite.
The Business Premium Trap Most Guides Still Get Wrong Several well-ranked licensing articles tell small and mid-sized businesses that Microsoft 365 Business Premium can take the E5 Compliance or Purview Suite add-on. It cannot. Microsoft’s pricing page states the Purview Suite prerequisite as Microsoft 365 E3, or Office 365 E3 with Enterprise Mobility + Security E3, and Business Premium appears nowhere on that list.
Business Premium customers still have a route forward, because they simply buy a different product. Microsoft’s licensing guidance names a dedicated Microsoft Purview Suite for Business Premium SKU, plus a combined Microsoft Defender and Purview Suites for Business Premium option. Quoting the E5 add-on price to a Business Premium tenant produces a business case that cannot be transacted.
What a Microsoft 365 Copilot License Does Not Buy You Copilot seats are where entitlement assumptions break most often, although the service description is unambiguous. Microsoft’s service description splits Purview DLP for Microsoft 365 Copilot into two tiers, and conflating them is an expensive error.
DLP that safeguards prompts is available to every Microsoft 365 Copilot and Copilot Chat user. DLP that stops Copilot from processing specific files and emails needs Microsoft 365 E5, the Purview Suite, an E5 Information Protection and Governance add-on, or Office 365 E5. A Copilot license alone does not grant it.
The consumption side works in your favor. Microsoft states that Microsoft 365 Copilot experiences are not charged under the pay-as-you-go model, so the AI meters covering other generative AI apps do not apply to Copilot itself.
Talk to Kanerika
Not Sure Which Purview SKU Your Estate Actually Needs?
A short working session with Kanerika maps the controls you need to the minimum valid subscription, scopes the affected user population, and separates the seat model from the consumption model before you commit.
Book a Licensing Review → Pay-as-You-Go Units of Measure, Translated Into Plain English The consumption side is where forecasts fall apart, because the meters use units with no obvious business analogue. Microsoft defines each one precisely, yet almost nobody translates them.
Table 3. Purview pay-as-you-go units, what they measure, and current rates
Unit What it actually measures Published rate (East US, USD) Asset Any item a Purview policy protects, charged per day it is covered. Counted once no matter how many policies apply $0.0165 per asset per day, roughly $0.50 per month DGPU (Data Governance Processing Unit) 60 minutes of managed compute time running across a variable set of nodes $15 Basic, $60 Standard, $240 Advanced, per DGPU DSPU (Data Security Processing Unit) The compute needed to process 10,000 user activities in Insider Risk Management $25 per processing unit Text record Exactly 1,000 characters of message content, rounded up $0.30 per 1K records Standard, $0.50 Premium (Communication Compliance) SCU (Security Compute Unit) A bundled unit of network, processor and storage for Security Copilot, billed as provisioned hourly blocks plus overage Provisioned and overage, capped by admin setting Request Each outbound call a device or browser makes to a website or API. Responses are not counted $0.50 per 10K requests Storage (GB) Gigabytes held per month for investigations and eDiscovery $5 per GB per month for Data Security Investigations
Sources: Microsoft Purview billing models and Azure Purview pricing , verified 20 August 2026. The Azure page is region-gated; the default region shows several meters as unavailable, so these are East US rates in USD.
Three Worked Examples Straight From Microsoft’s Own Documentation Counting rules matter more than rates here, because the rates are small and the counts are not. Microsoft publishes three worked examples, so the counting rules are easy enough to check.
Assets follow policy scope, not scan results. A SQL Server holds 100 tables, 50 labeled Confidential. A policy covering that label produces an asset count of 50, so at $0.0165 per asset per day the scope runs roughly $25 across a 30-day month.Scope multiplies faster than people expect. Ten Fabric workspaces each hold 50 assets. A DLP policy applied to five of them produces an asset count of 250, not 50 and not 500, because scope counts per covered container.Text records round up, always. A 7,500-character message counts as eight text records. A 500-character message counts as one, so a chat-heavy Communication Compliance deployment bills closer to message volume than character volume.Security compute units, meanwhile, round on time rather than volume. Provisioning at 9:05, deprovisioning at 9:35, then provisioning again at 9:45 bills two units inside the 9:00 hour, so a bursty provisioning pattern costs more than a steady one.
Case Study
Rebuilding Data Governance for a Leading Bank on Microsoft Purview
Kanerika implemented Microsoft Purview across a bank’s data estate, establishing centralized classification, lineage, and policy enforcement over sources spanning Microsoft 365 and the wider platform landscape.
Read the Case Study → What Changed in Purview Licensing, and Where to Watch Your Consumption Purview’s commercial model moved fast between 2025 and 2026, and stale guidance is easy to find. Four dated changes therefore matter for anyone budgeting now.
6 January 2025. Microsoft states that pay-as-you-go took effect for Microsoft Purview on this date, moving consumption billing out of free preview.30 June 2025. Tenants without a linked Azure subscription lost their metered capabilities, which is why the Azure link is a prerequisite rather than an optimization.1 October 2025. Microsoft renamed the E5 mini-suites . E5 Compliance became the Microsoft Purview Suite and E5 Security became the Microsoft Defender Suite, so guides still quoting E5 Compliance are naming a retired SKU.April 2026. Insider Risk Management indicators for other generative AI apps moved to pay-as-you-go worldwide. Government clouds run on a separate schedule, with GCC, GCC High, and DoD tracking to March 2027.One capability on the meter list still carries preview status. Microsoft labels Network Data Security as preview in the billing-models documentation, so its behavior and its rate can both change without notice.
Three Places to See What You Are Actually Consuming No single screen shows total Purview consumption, which is why finance teams meet the Azure line late. Microsoft instead documents three separate views.
The Azure portal, under Cost Management and Billing, carries the actual bill for every pay-as-you-go meter. Insider Risk Management publishes its own pay-as-you-go usage reports inside the Purview portal, broken down by data source category and activity indicator. Data governance consumption sits under Settings, Solution settings, Unified Catalog, Usage monitoring, showing governed assets and DGPU consumption by domain, although it does not show the bill. Which Users Actually Need a Microsoft Purview License Microsoft Purview licensing is per user rather than per tenant, and the entitlement follows benefit rather than access. Microsoft’s Purview service description , refreshed on 3 August 2026, states the rule in five words. Any user benefiting from the service requires a license.
That phrasing does real work in a seat count. Licensing the four administrators who configure a DLP policy while leaving 3,000 protected mailboxes unlicensed is a compliance gap, not a saving, even though nothing in the portal blocks it. The documentation therefore draws practical boundaries worth using.
Users with a Purview role assigned in the Microsoft Purview portal need a license. For mailboxes, OneDrive accounts, Teams chats, and managed devices, the owning user needs the license. For SharePoint sites, Microsoft 365 Groups, and Teams channels, owners and members need licenses, while visitor and view-only roles do not. Inactive mailboxes need no usage license, although shared and resource mailboxes do need one for certain advanced features. Two commercial rules sit alongside the technical ones and both show up in audits. Microsoft’s licensing guidance states plainly that pooling connections or rerouting access to reduce the number of users touching a service, commonly called multiplexing, does not reduce the licenses you need. It also blocks license reassignment within 90 days of the last assignment, unless the user has left or is on leave.
Watch on YouTube
Microsoft Enterprise Agreement Explained in Simple Terms
Multiplexing limits and reassignment rules live in the agreement, not the portal. Bhupendra Chopra breaks down how Microsoft Enterprise Agreements actually work and where the commercial levers sit.
What Happens to Labels and Policies When a License Goes Away Downgrade behavior is the most anxious question in Microsoft Purview licensing, although no single Microsoft page answers it. Microsoft describes it across several pages, and the answers are less tidy than most buyers assume.
Applied sensitivity labels persist. Removing a label from a publishing policy stops users from selecting it, but content that already carries the label keeps it , and a container label continues to protect the Team or SharePoint site where an admin applied it.
Deleting a label splits by storage location, and that is the detail that catches people. In SharePoint and OneDrive with labels enabled for Office files, deleting a label that applied encryption removes the encryption. Elsewhere, and for email, encryption remains because Microsoft archives the protection template, so protected content still opens.
The Unlicensed-Account Clock Almost Nobody Models Removing a Microsoft 365 license starts a timer that retention policies do not stop. Microsoft documents that unlicensed OneDrive accounts go read-only after 60 unlicensed days and are archived after 93. They stop being available to eDiscovery at day 275 and become subject to deletion at day 365.
The part that should reach your legal team is what happens when nobody enables billing for unlicensed accounts. Microsoft states that accounts are then subject to deletion 365 days after becoming unlicensed even if retention policies, settings, or holds exist, and that customers should not rely on retention or legal hold alone. If deletion occurs, eDiscovery hold records survive but the held content does not. These rules exclude EDU, GCC, and DoD customers.
The Free 90-Day Trial and What Happens to Your Data Afterward Purview offers a free trial that gets almost no coverage in the ranking licensing guides, which is odd given how directly it answers the pre-purchase scoping problem. Microsoft documents a 90-day trial that auto-applies 25 Purview Suite licenses to an eligible tenant. Eligibility mirrors the paid prerequisite, so you need Microsoft 365 E3, or Office 365 E3 with Enterprise Mobility + Security E3, and Microsoft excludes Government tenants.
Microsoft does not delete trial data the moment the clock runs out. Microsoft says it is usually maintained for 180 days before permanent deletion, with the hedge that individual solutions may state otherwise. Solution-level behavior therefore differs in ways worth planning for.
Files and emails labeled during the trial stay labeled, although you can still remove those labels manually. Existing DLP policies stay switched on unless you turn them off. Once the trial ends you can only delete auto-labeling policies, because editing them stops working. Teams and Devices locations cannot be edited or added to DLP policies afterward. Trials extend once within the final 15 days, up to two periods, otherwise a 30-day wait applies. Used deliberately, the trial is the cheapest answer to the question every buyer asks first. Run classification against real data, count the assets a policy would actually cover, and size the purchase from measurement rather than estimate, since a counted number survives a finance review. A trial scan is only as useful as the taxonomy behind it, so settle your classification best practices before the 90 days start.
Where Microsoft Purview Licensing Spend Usually Leaks Overspend on Purview rarely comes from paying too much per seat. It comes instead from buying the wrong shape of entitlement, then running consumption without a budget attached.
Buying E5 before mapping requirements. A tenant-wide E5 upgrade is right when the wider E5 stack earns its keep. When only a regulated subset needs advanced compliance, Purview Suite over an E3 base is usually cheaper.Licensing administrators instead of beneficiaries. The user-benefit rule turns an apparent saving into an entitlement gap that surfaces during a true-up.Assuming a visible feature is included. Greyed-out portal controls are an entitlement signal, not a bug, so the portal is never a licensing authority. Check the Product Terms.Treating everything in the catalog as billable. Scanned assets and governed assets are different numbers, so only the governed ones meter.Running data-quality rules without a compute budget. Rule count, frequency, run time, and DGPU tier drive cost far more than raw catalog size. The gap between a $15 Basic DGPU and a $240 Advanced DGPU compounds fast at daily cadence.Ignoring AI application traffic. Generative AI usage outside Copilot meters through consumption, and it is the fastest-growing line on the Azure side of the bill.The commercial layer sits on top of all six. Microsoft’s disclaimer that pricing may vary based on your agreement is an invitation to negotiate rather than a footnote. Enterprises renewing an EA or moving to CSP have levers list pricing never reveals, covered in our guide to Microsoft licensing in 2026 and our breakdown of Microsoft licensing optimization .
A Seven-Step Purview Licensing Assessment Before You Buy or Renew A defensible Purview number comes from a sequence, not a spreadsheet template. This is therefore the order we work in when scoping an enterprise estate.
Baseline current licenses. Count E3, E5, F-series, Business Premium, EMS, Copilot and legacy add-ons, with contract channel and renewal date. Assigned and actually required licenses are usually different numbers.Map controls to rights, not SKUs. Start from the control the business needs, then find the minimum valid subscription that grants it. Starting from a bundle guarantees you buy capabilities nobody asked for.Scope the affected user population. Count every user who receives the service, not the administrators who configure it, because an organization-wide policy turns a narrow requirement into a tenant-wide license event.Separate governed assets from scanned assets. Model average governed assets per day rather than treating the month-end catalog as the billable number, since mid-month additions and removals change the charge. Deciding which stores enter that scan scope at all is a discovery exercise, and our comparison of sensitive data discovery tools covers how much of an estate each one can actually reach.Model processing consumption. Estimate DGPU usage from rule count, frequency, run time and performance tier before opening the Azure pricing calculator, which is only as good as the assumptions behind it.Forecast non-Microsoft 365 data. Account for Fabric, cloud databases, third-party and AI apps, audit records, requests, text records and investigation storage separately from the seat model.Price against your real contract. Compare list pricing to your EA, CSP, or MCA terms, then add implementation, classification, stewardship, and monitoring effort to reach total cost of ownership.Decide Where the Control Belongs, Not Only What It Costs Governance architecture belongs in this sequence too. If a meaningful share of your data lives in Databricks, Snowflake, or Fabric, the question is not only what Purview costs, it is which engine should enforce the control in the first place. Our comparison of data access governance tooling works through which engines enforce a policy natively and where a separate layer earns its cost.
How Kanerika Approaches Microsoft Purview Licensing and Governance Kanerika is a Microsoft Solutions Partner for Data and AI with an Analytics Specialization, and one of the earliest Microsoft Purview implementors globally. Purview licensing questions are rarely licensing questions alone. They are governance-design questions with a price attached.
Our kanSuite governance services, kanGovern, kanComply, and kanGuard, run on Microsoft Purview and start from the assessment sequence above. We map the controls a regulator or auditor requires, scope the user population each policy touches, and separate the seat model from the consumption model before anyone names a SKU.
The cross-platform view is deliberate. Kanerika is also a Databricks Consulting Partner and a Snowflake Select Tier Partner, so recommending that governance sit in a platform’s native catalog rather than in Purview is a live option, not a lost sale. For capability detail, start with our guide to Microsoft Purview features, use cases, and setup , data governance with Microsoft Purview , or our Microsoft Purview eDiscovery breakdown.
Wrapping Up Microsoft Purview licensing resolves into four questions. Which controls does the business require, which users receive them, which data sits outside Microsoft 365, and which meters run once policies go live?
Answer those in order and the SKU choice becomes obvious rather than contested. Answer them out of order, starting with a bundle, and you buy entitlements nobody needed while leaving consumption unbudgeted. List price is where a Purview business case starts, never where it ends.
Frequently Asked Questions
Is Microsoft Purview included in Microsoft 365 E5? Yes. Microsoft states that all Microsoft Purview Suite features are included with Microsoft 365 E5, which lists at $60.00 per user per month on an annual commitment. E5 also includes Security Copilot at no additional cost. Data that sits outside Microsoft 365 still bills separately as pay-as-you-go consumption through an Azure subscription.
How much does Microsoft Purview cost per user? The Microsoft Purview Suite add-on lists at $12.00 per user per month on an annual commitment, sitting over a Microsoft 365 E3 base or Office 365 E3 with Enterprise Mobility + Security E3. Microsoft 365 E5 lists at $60.00 per user per month. Microsoft notes that prices may vary based on your agreement.
Can you buy Microsoft Purview without Microsoft 365 E5? Yes. The Purview Suite add-on sits over an eligible E3 base, and three narrower add-ons cover Information Protection and Governance, Insider Risk Management, and eDiscovery and Audit separately. Pay-as-you-go services covering data outside Microsoft 365 need only an active Azure subscription rather than an E5 seat.
Do all users need a Microsoft Purview license or only administrators? Microsoft’s rule is that any user benefiting from the service requires a license, not only the administrators configuring it. Users who own protected mailboxes, OneDrive accounts, devices, or Teams chats need one, as do SharePoint site owners and members. Visitor and view-only roles and inactive mailboxes do not require a license.
Does Microsoft 365 Business Premium include Microsoft Purview features? Business Premium includes some core Purview capabilities but cannot take the E5 Purview Suite add-on, whose prerequisite is Microsoft 365 E3 or Office 365 E3 with Enterprise Mobility + Security E3. Microsoft sells a separate Microsoft Purview Suite for Business Premium SKU, plus a combined Defender and Purview option, for advanced capabilities instead.
Is Microsoft Purview free? No, although a free evaluation path exists. Microsoft offers a 90-day Purview trial that automatically applies 25 Purview Suite licenses to an eligible Microsoft 365 E3 tenant. Trial data is usually retained for around 180 days after the trial ends before permanent deletion, and Microsoft 365 Government tenants are excluded from the trial.
What happens to Purview data if you downgrade or remove a license? Applied sensitivity labels persist on content even after a label is unpublished. Deleting a label removes encryption inside SharePoint and OneDrive where the service can process the content, but leaves encryption in place elsewhere and in email. Removing a Microsoft 365 license is harsher, since unlicensed OneDrive accounts go read-only after 60 days.
What is the difference between Microsoft Purview and Azure Purview? Azure Purview was the earlier standalone data catalog service, now folded into Microsoft Purview. Microsoft still publishes an Azure Purview Classic rate card on its Azure pricing page and describes it as legacy pricing for the previous service, without stating a retirement date. New deployments use the current Unified Catalog consumption model instead.
