Skip to main content

Purview Data Governance Retirement Checklist and Timeline

Emily Winks, Data Governance Expert, Atlan
Data Governance Expert
Updated:
|
Published:
14 min read

Key takeaways

  • Purview Data Governance support ends November 12, 2027. No new accounts, and existing features are in maintenance mode.
  • Microsoft's November 17, 2026 post announces a strategic partnership with Atlan, its preferred data governance partner.
  • Purview Data Security and Compliance is not affected. Only the data governance side moves.
  • Start your assessment now, then work in five dated phases that finish before the end-of-support date.

What is the Purview Data Governance retirement timeline?

Microsoft announced the retirement on November 12, 2026, and transition support began that day. Support for Purview Data Governance ends on November 12, 2027, and until then existing capabilities stay in maintenance mode with no new accounts. Plan the year in five phases: assess, decide, move, run both systems side by side, and switch. Each phase below has a done-when line. In its November 17, 2026 post, Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner.

The dated milestones:

  • November 12, 2026: Microsoft announces the retirement and transition support begins
  • Now: no new accounts, existing capabilities in maintenance mode
  • Through November 12, 2027: maintenance mode continues
  • November 12, 2027: support for Purview Data Governance ends

See where your governance has gaps


Support for Purview Data Governance ends on November 12, 2027, a date Microsoft announced on November 12, 2026. A dated timeline, an assessment checklist, a plan with a done-when test for each phase, and board talking points follow. In its November 17, 2026 post, Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner. For what is retiring and what stays, read the retirement guide.

Build Your Purview Migration Checklist


Give it what your team built in Purview Data Governance and where your data lives. It returns an object-by-object checklist, the prerequisites, and a five-phase plan with a done-when line for each phase. Read the skill.

Paste into a new chat

Use the skill at https://atlan.com/skills/purview-data-governance-migration-checklist.md to build a migration checklist for our Purview Data Governance work. Ask me for whatever it needs.

Run once in a terminal

curl -fsSL --create-dirs \
  -o ~/.agents/skills/purview-data-governance-migration-checklist/SKILL.md \
  https://atlan.com/skills/purview-data-governance-migration-checklist.md

For an agent

curl -fsSL https://atlan.com/skills/purview-data-governance-migration-checklist.md

If your team runs data governance on Microsoft Purview, you have a year to move the glossaries, domains, and data products your stewards built, and a late start leaves no room for review. Start the assessment now: it is read-only, and the date does not move. The hard part is the order of work, which is what to confirm with Microsoft, what to inventory, who decides where it lands, and when each piece must finish. For the migration itself, use the five-step migration plan.


What is the Purview Data Governance retirement timeline?

Microsoft Purview data governance did not retire in November 2026. The announcement came then, and support ends a year later.

In Microsoft’s words, “Purview Data Governance will be retired a year from now,” and “Support for Purview Data Governance will end Nov. 12, 2027,” per the November 12 announcement.

Date What happens Source
November 12, 2026 Microsoft announces the retirement. Transition support begins. Microsoft Security Community Blog
November 17, 2026 Microsoft states that the OneLake catalog is now its data governance product. Microsoft Fabric Community Blog
Now to November 12, 2027 No new accounts. Existing capabilities remain in maintenance mode. Microsoft Learn, Unified Catalog
November 12, 2027 Support for Purview Data Governance ends. Microsoft Security Community Blog

The Microsoft Learn banner that carries these dates appears on the Unified Catalog page and on the Data Map overview, and it points to Microsoft’s announcement for timelines, transition guidance, and next steps. Microsoft’s post says detailed transition guidance is available through your account team, so if you hold a contract or work in a regulated industry, ask for it now.


What does the retirement change for your team?

Your governance work gets a new home and an end date. Per Microsoft’s November 12 post, Fabric is now its data governance solution, and its November 17 post names the OneLake catalog as Microsoft’s data governance product.

Microsoft describes the OneLake catalog as “a new model, not a feature-for-feature replacement for Purview Data Governance.”

What stays is just as specific. Microsoft says Purview Data Security and Compliance, including Information Protection, Data Loss Prevention, Insider Risk Management, and Data Security Posture Management, is not affected and continues to protect your data in Fabric. The retirement guide and what stays in Microsoft Purview after retirement cover the split.

For a governance team, the work at risk is what people built by hand. Microsoft’s Learn page lists what Unified Catalog holds: governance domains, data products, glossary terms, critical data elements, objectives and key results (OKRs), access policies, data quality rules, and health controls and actions. The Unified Catalog explainer walks through each, and classic versus Unified Catalog helps if your glossary still lives in the classic experience. The Data Map is a separate case, covered in what happens to the Data Map. Treat it as its own item in your inventory.


Where do the OneLake catalog and Atlan fit?

The OneLake catalog governs data that lives in or is connected to OneLake, the unified data lake included with every Fabric tenant. Microsoft lists the routes in as native items, federated catalogs, IQ Shares, Shortcuts, and Mirrored databases, in both Delta Lake and Apache Iceberg formats.

The November 12 post adds that governance is included in Fabric capacity rather than billed through separate meters. If nearly all your data sits in Fabric, the OneLake catalog may be all you need.

Many teams run data elsewhere too. Per Microsoft’s November 17 post, OneLake and Fabric customers can use Atlan to extend governance beyond OneLake. The post describes Atlan as providing granular, cross-estate lineage, the map of how data flows from source to report, and richer governance constructs such as usage and popularity stats across heterogeneous, non-Microsoft data sources. It also describes Atlan as supporting customers moving from Purview Data Governance to Fabric with tooling to carry their existing metadata, the descriptions, owners, and tags attached to each asset, forward.

OneLake native governance beside a third-party catalog, Atlan

OneLake catalog governance, extended by a third-party catalog like Atlan. Source: Microsoft

To compare the options, see Microsoft Purview and Atlan, coexist, extend or replace Purview, Microsoft Fabric governance, and Purview alternatives. The Microsoft and Atlan governance page covers the partnership, and partners after the Purview retirement covers who else Microsoft names. Best data catalogs for Microsoft Fabric compares the field. If your data sits mostly outside Fabric, plan for both from the start.


What goes on a Purview Data Governance retirement assessment checklist?

An assessment answers one question: what do we have, who owns it, and what must move by November 12, 2027. The checklist below is ours, built from the objects Microsoft’s Learn pages list.

Area What to confirm Why it matters
Contract and regulation Any contractual or regulatory duty tied to your Purview Data Governance use Microsoft assesses these cases individually
Glossaries Every glossary, category, and term, with status, synonyms, and linked assets The definitions your teams and AI agents rely on
Domains and data products Governance domains, sub-domains, and data products, drafts included Drafts may need publishing before they move
Custom attributes and critical data elements Definitions, values, and where each is used They map to custom metadata in the new home
Classifications Your own and Microsoft’s built-in ones They become tags or labels in the new home
Lineage Hand-drawn lineage versus scanned lineage Scanned lineage is rebuilt from sources; hand-drawn lineage is yours
Data quality rules Rules, thresholds, and covered assets Set up again in the new home
People Owners, stewards, and experts, with leavers removed Owners move only when they match a real user by email
Dependants Teams, reports, and processes that read Purview governance daily (our judgement) They need a new place to read from before the switch
Destination OneLake catalog alone, a wider catalog, or both Decided in Step 2 below

Run the first pass yourself


Start with exports and your own list, then read the rest through Microsoft’s REST APIs. Check terms against the glossary required fields, confirm owners with the owners and stewards guide, and decide how domains map using the data domain guide.

Keep data products whole and review classification tools before you decide what becomes a tag. A glossary that stays up to date is easier to move than one nobody edits.


How do you plan the year, quarter by quarter?

Five phases fit the year, with two weeks of slack before the deadline. The calendar is a planning suggestion, not a Microsoft requirement, so pull a phase earlier when your estate is small.

Phase Window
1. Assess November to December 2026
2. Decide January to February 2027
3. Move March to May 2027
4. Run side by side June to August 2027
5. Switch and close September to October 2027

Step 1: Assess your estate (November to December 2026)

Assessment turns a vague deadline into a list of objects, owners, and open questions.

  • Raise your contract and regulatory questions with your Microsoft account team.
  • Work through the checklist and record what your team built.
  • Export what you can and read the rest through Microsoft’s Learn REST APIs, which change nothing in Purview.

Done when: your governance lead holds the inventory, a list of decisions, and a dated plan.


Step 2: Decide where each piece lands (January to February 2027)

Decide before anything moves, because each destination changes the work.

  • Choose the OneLake catalog, a wider catalog, or both.
  • Name one owner for each object type.
  • Approve how glossaries, domains, data products, custom attributes, and classifications map to the destination.

Done when: every object type in scope has an approved mapping and a named owner.


Step 3: Move and validate (March to May 2027)

Move the approved governance, then check it against the plan.

Done when: the validation report matches the approved plan.


Step 4: Run both systems side by side (June to August 2027)

Parallel running shows gaps while you can still fix them.

Done when: stewards work only in the new home, and no team reads Purview governance every day.


Step 5: Switch and close (September to October 2027)

Set the switch date early enough to leave room before the deadline.

  • Pick the switch date and run a final refresh.
  • Archive exports of anything you leave behind.
  • Check regulated teams against a readiness checklist.

Done when: nothing in daily use reads Purview Data Governance, and exports are archived at least two weeks before November 12, 2027.


Should you wait before replacing Purview Data Governance?

Part of the answer is sourced, and part is judgement. Sourced: the end date is fixed, transition support has begun, and Microsoft asks regulated customers to engage their account team early.

Start the assessment now. It reads your estate and writes nothing back, so it commits you to nothing, and the inventory is the one piece of work every destination needs.

Hold the destination decision for a few weeks if you must. Two things can change it: what your Microsoft account team tells you about your contract, and how much of your data lives outside Fabric. Microsoft says the OneLake catalog governs data in or connected to OneLake, and that customers can use Atlan to extend governance beyond OneLake. If your estate spans other platforms alongside Fabric, the second half of that sentence is your situation.


What is the risk of staying on Purview until support ends?

Nothing stops on day one. Microsoft’s Learn banner says existing capabilities remain in maintenance mode through November 12, 2027, and the November 17 post says new data governance innovation lands in the OneLake catalog.

After the support date, ask your account team what changes for your tenant. The risks below are our judgement, not Microsoft statements.

Moving governance needs stewards to review decisions, owners to match real people, and downstream teams to repoint, and each takes weeks. Teams that start late find them all landing at once. Your glossary also keeps changing while you plan, so a long gap between the first snapshot and the switch means more edits to reconcile.

AI work adds a third risk. Agents that read your glossary and definitions need a source that will still be supported, and building them on a retiring one means building twice. Contract and regulatory cases take time on Microsoft’s side, and your own legal and risk reviews add more. Start well before the final months and none of these risks needs to bite.


What do you tell your board about the retirement?

What changed: Microsoft will end support for Purview Data Governance on November 12, 2027, and has named Fabric and the OneLake catalog as its data governance solution. Purview security and compliance, including data loss prevention and insider risk management, is not affected.

The glossary, domains, and data products our teams built need a new home.

What waiting costs: nothing breaks on day one, because existing capabilities stay in maintenance mode. The cost is time. Each month of delay removes a month of room for review, validation, and parallel running, and regulated cases need extra lead time. Governance in Fabric is included in Fabric capacity per Microsoft, so ask your account team for line items before you size a budget.

The plan: five phases, from assessment in November and December 2026 to a switch in September and October 2027, each with a named owner and a done-when test. We report at the end of each phase. Ask the board to back the plan, not to wait for a better date.


FAQs about the Purview Data Governance retirement

1. Was Microsoft Purview data governance retired in November 2026?


Microsoft announced the retirement on November 12, 2026, but the service did not end that day. Transition support began on the announcement date, no new accounts can be created, and existing capabilities remain in maintenance mode through November 12, 2027, when support for Purview Data Governance ends.

2. What is the Purview retirement timeline?


November 12, 2026: announcement and the start of transition support. From then to November 12, 2027: no new accounts, with existing capabilities in maintenance mode. November 12, 2027: support ends.

3. What goes on a Purview retirement assessment checklist?


Cover contract and regulatory obligations, an inventory of what your team built, owners and stewards, the people and systems that read from Purview daily, the destination you will choose, and the date each piece must move.

4. I run data governance in Purview. What does this change mean for my team?


Your team needs a new home for governance work before November 12, 2027. Microsoft names Fabric and the OneLake catalog as its data governance solution, and says the OneLake catalog is a new model, not a feature-for-feature replacement for Purview Data Governance. Purview Data Security and Compliance is not affected.

5. Should we wait before replacing Purview Data Governance?


Do not wait to start the assessment, because it is read-only and changes nothing in Purview. It is reasonable to hold the choice of destination for a few weeks while you get answers from your Microsoft account team. That is our judgement, not a Microsoft instruction. The end-of-support date does not move.

6. What is the risk of staying on Purview until support ends?


Microsoft says existing capabilities stay in maintenance mode until November 12, 2027, so nothing stops on day one. The risk is compression. Stewards review the move, owners leave, and regulated teams need individual assessments. A team that starts in the final months has little room for any of that. This is our judgement, not a Microsoft statement.

7. What do I tell my board about the Purview Data Governance retirement?


Say three things. Microsoft will end support for Purview Data Governance on November 12, 2027, and Purview security and compliance is not affected. Waiting shrinks the time to move the governance your team built, which is a judgement, not a Microsoft claim. The plan has five dated phases, a named owner for each, and a done-when test for each.

8. What should regulated teams do first?


Talk to your Microsoft account team early. Microsoft asks customers with contractual obligations and in highly regulated industries to engage early, because those scenarios are assessed individually.

9. Which data governance partner does Microsoft prefer?


In its November 17, 2026 post, Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner. Microsoft says OneLake and Fabric customers can use Atlan to extend governance beyond OneLake.


Sources

  1. A next step in the evolution of the Microsoft Data Governance strategy, Microsoft Security Community Blog, November 12, 2026
  2. OneLake: the unified foundation for data, context, governance, and AI, Microsoft Fabric Community Blog, November 17, 2026
  3. Learn about Microsoft Purview Unified Catalog, Microsoft Learn
  4. Microsoft Purview Data Map overview, Microsoft Learn
  5. OneLake, the unified data lake, Microsoft Fabric, Microsoft Learn

Share this article

signoff-panel-logo

Atlan is the Context Layer for AI. It translates business knowledge, including data definitions, working procedures, and governance policies, into context AI can actually use. This knowledge lives in a single Enterprise Data Graph that every team and AI agent can reach.

In Atlan's AI Labs benchmark, adding this context improved AI's text-to-SQL accuracy by 38%.

Atlan is recognized as a Leader across multiple Gartner reports and Forrester Waves, and is trusted by over 400 enterprises representing $10T+ in market cap, including Mastercard, Workday, General Motors, CME Group, HubSpot, FOX, Virgin Media O2, and Elastic.

Bridge the context gap.
Ship AI that works.