---
title: "What Happens to the Purview Data Map After the Retirement?"
url: "https://atlan.com/know/ai-agent/microsoft/purview-data-map-after-retirement/"
description: "Microsoft's Learn page puts the Purview Data Map in maintenance mode through November 12, 2027. See what the Data Map holds and what to inventory now."
author: "Emily Winks"
author_role: "Data Governance Expert"
published: "2026-11-18"
updated: "2026-11-19"
---

## What happens to the Purview Data Map after the retirement?

The Data Map page on Microsoft Learn says Unified Catalog and classic Purview data governance capabilities are being retired, new accounts can no longer be created, and existing capabilities stay in maintenance mode through November 12, 2027. Microsoft's November 12 post does not name the Data Map, so confirm the details with your Microsoft account team. In its November 17, 2026 post, Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner.

What to capture first:

- **Scans**: sources, scan rules, and schedules
- **Classifications**: your own and the built-in ones applied to assets
- **Lineage**: what scans captured and what your team added by hand
- **Custom types**: type definitions and the assets built on them

## Key takeaways

- Microsoft's Data Map page says classic Purview data governance is in maintenance mode through November 12, 2027.
- Microsoft's November 12 post does not name the Data Map, so confirm specifics with your Microsoft account team.
- Microsoft's November 17, 2026 post announces a strategic partnership with Atlan, its preferred data governance partner.
- Inventory scans, classifications, lineage, and custom types now, while the Data Map still runs.

---

The Purview Data Map is the store of scanned metadata, classifications, and lineage behind Microsoft Purview governance. Microsoft's Learn page for the [Data Map](https://learn.microsoft.com/en-us/purview/data-map) says classic Purview data governance capabilities are being retired. New accounts can no longer be created, and existing capabilities stay in maintenance mode through November 12, 2027. In its [November 17, 2026 post](https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/onelake-the-unified-foundation-for-data-context-governance-and-ai/5423035), Microsoft announced a strategic partnership with Atlan and calls Atlan its preferred data governance partner.

### Map Your Catalog Coverage

Give it every system in your estate and which catalog governs each today. It returns a coverage table and the specific gap ranked by what breaks first. [Read the skill](/skills/catalog-coverage-gap-map.md).

*Paste into a new chat*

```
Use the skill at https://atlan.com/skills/catalog-coverage-gap-map.md to map catalog coverage across our data estate. Ask me for whatever it needs.
```

*Run once in a terminal*

```
curl -fsSL --create-dirs \
  -o ~/.agents/skills/catalog-coverage-gap-map/SKILL.md \
  https://atlan.com/skills/catalog-coverage-gap-map.md
```

*For an agent*

```
curl -fsSL https://atlan.com/skills/catalog-coverage-gap-map.md
```


    Human
    Agent


  ClaudeChatGPTGeminiCursorOther
  Copy

The [retirement guide](https://atlan.com/know/purview-data-governance-retirement/) covers the full announcement. If your team runs data governance on Purview, you have about a year to decide what happens to that record. Miss something, and the work your stewards did can disappear.

Below is what Microsoft's sources say about the Data Map, and no more.

The Data Map is where Purview scans land. It holds the technical record of your estate. Your team's curation sits on top of that record. Capture that part before the clock runs out.

| Quick fact | What Microsoft says | Source |
|---|---|---|
| Status | Classic data governance capabilities are being retired | Data Map Learn page |
| New accounts | You can no longer create them | Data Map Learn page |
| Existing capabilities | Maintenance mode through November 12, 2027 | Data Map Learn page |
| Support for Purview Data Governance | Ends November 12, 2027 | November 12, 2026 post |
| Data Map named in the post | No | November 12, 2026 post |

---

## What do Microsoft's sources say about the Data Map?

Two Microsoft sources matter, and they use different words.

The Learn page for the Data Map carries a notice.

It says Unified Catalog and classic Purview data governance capabilities, formerly Azure Purview, are being retired.

Microsoft is consolidating its data governance capabilities in Microsoft Fabric. You can no longer create new accounts. Existing capabilities remain in maintenance mode through November 12, 2027. The same notice appears on Microsoft's Learn page for [custom types](https://learn.microsoft.com/en-us/purview/data-gov-api-custom-types).

[Microsoft's November 12, 2026 announcement](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227) uses a different name. It says Purview Data Governance will be retired a year from now and that support ends on November 12, 2027. The post does not mention the Data Map, Unified Catalog, classic data governance, or glossaries.

| Source | What it says | What it leaves open |
|---|---|---|
| Data Map Learn page | Classic data governance capabilities are being retired, no new accounts, maintenance mode through November 12, 2027 | What maintenance mode covers, day to day |
| November 12, 2026 post | Support for Purview Data Governance ends November 12, 2027 | Whether and how the Data Map is named in that retirement |
| November 17, 2026 post | Purview Data Governance will be retired and the OneLake catalog is Microsoft's data governance product | The Data Map, which the post does not name |

The sources use different words, and that is fine.

Treat the banner wording as the answer, and confirm Data Map specifics with your Microsoft account team. Microsoft asks two groups to engage that team early: customers with contractual obligations, and customers in highly regulated industries. Those cases are assessed individually.

---

## How does the Data Map work, and what does it hold?

The Data Map is the foundation for data discovery and governance in Purview. Per Microsoft, it captures metadata about your data in analytics, SaaS, and operational systems.

That metadata spans hybrid, on-premises, and multicloud environments. Built-in scanning and classification keep it current.

Microsoft's Learn page sorts what it stores into four kinds of metadata:

| Kind of metadata | What Microsoft says it includes |
|---|---|
| Technical | Schemas, data types, and columns discovered through scanning |
| Business | Metadata promoted from Power BI datasets, descriptions from SQL tables, and descriptions and glossary terms added by hand |
| Semantic | Collection mappings to data sources, and classifications |
| Operational | Data Factory copy and data flow activity run statuses and run times |

Lineage lives there too. Microsoft's capacity guidance says scanning and ingestion fill in data assets, classifications, and lineage. It also lists owner, steward, parent, and lineage relationships among Data Map operations.

Teams can also add their own metadata types. Microsoft's custom types tutorial explains that Purview relies on the type system from Apache Atlas, which is the open-source metadata model behind it, and that custom types exist for metadata with no built-in type. If your team defined any, they are part of what you carry forward.

The Data Map also has a size and a bill.

Each account starts at one capacity unit. That unit includes 25 operations per second and 10 GB of metadata storage. It autoscales to 10 units by default. Microsoft bills it by the hour.

---

## How does the OneLake catalog differ from the Data Map, and where does Atlan fit?

Microsoft's answer to where governance lives next is the OneLake catalog. In its November 17, 2026 post, Microsoft says the OneLake catalog is now its data governance product.

It governs data that lives in or is connected to OneLake. That means native items, federated catalogs, IQ Shares, Shortcuts, and Mirrored databases. 

The November 12 post adds that shortcuts, mirroring, and supported connectors reach data in Fabric, Azure, and third-party sources. The data stays where it is. Microsoft calls it "a new model, not a feature-for-feature replacement for Purview Data Governance." Expect a different shape from the Data Map. The [OneLake catalog explained](https://atlan.com/know/microsoft-fabric/onelake-catalog/) walks through its Explore, Govern, and Secure experiences.

![OneLake native governance beside a third-party catalog, Atlan](/img/microsoft-onelake-atlan-governance-diagram.webp "OneLake and Atlan governance diagram"){width=688 height=395}

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

Microsoft also says OneLake and Fabric customers can use Atlan to extend governance beyond OneLake. Microsoft describes Atlan's cross-estate lineage and richer governance constructs, such as usage and popularity stats, across non-Microsoft data sources.

Microsoft adds that Atlan supports customers moving from Purview Data Governance to Fabric. Its tooling carries their existing metadata forward. The [Microsoft and Atlan landing page](https://atlan.com/partners/microsoft/data-governance-onelake-catalog/) describes how the two work together, and [Microsoft Fabric governance](https://atlan.com/know/ai-agent/microsoft/microsoft-fabric-governance/) covers the split in detail. Teams comparing both products side by side can start with [Microsoft Purview and Atlan](https://atlan.com/know/data-catalog/microsoft-purview-and-atlan/).

---

## What are examples of governance work that depends on the Data Map?

Ask what breaks if the Data Map stopped answering. The list gets concrete fast, and each item below ties to what Microsoft says the Data Map stores.

- **Asset records.** Every table and column your scans found has a record with a schema and data type. Reports, catalogs, and access reviews that point at those records depend on them.
- **Classifications.** Labels applied to assets, whether your own or built in, sit in the Data Map as semantic metadata. Anyone filtering by a classification relies on them.
- **Descriptions and glossary terms.** Business context your stewards attached by hand lives next to the technical record. Scans cannot recreate it, because no source system holds it. A [glossary kept up to date](https://atlan.com/know/how-to-keep-a-business-glossary-up-to-date/) and the [required fields for each term](https://atlan.com/know/faq/business-glossary-required-fields/) help you judge which terms are worth carrying.
- **Lineage.** Scans capture lineage between assets. Your team may also have added lineage the scans could not see.
- **Custom types.** If you modeled a system Purview had no built-in type for, the type definitions and every asset built on them live in the Data Map.
- **Owners.** Stewards and owners recorded on assets are people data. The [owners and stewards guide](https://atlan.com/know/ai-agent/ai-ready-data/ai-ready-data-owners-and-stewards/) covers what each role needs.
- **Integrations.** Anything that calls the Data Map REST API, from scripts to reporting jobs, depends on its endpoints.

### How can you read the Data Map record yourself?

Microsoft's [Data Map REST API for types](https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/type) has operations to read entity, classification, relationship, business metadata, and term template definitions. The [lineage REST API](https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/lineage) reads lineage for an entity. A team that wants a record of what it built can use them.

Domains need a decision too, and the [data domain guide](https://atlan.com/know/data-governance/data-domain-data-governance/) helps you choose.

The split between what scans rebuild and what people curated runs through other Purview pages too. See [Purview Unified Catalog](https://atlan.com/know/ai-agent/microsoft/purview-unified-catalog/) and the [classic versus Unified Catalog comparison](https://atlan.com/know/ai-agent/microsoft/purview-classic-data-catalog-vs-unified-catalog/). For Fabric, read [what Purview governs in Fabric and Power BI](https://atlan.com/know/ai-agent/microsoft/how-does-purview-govern-microsoft-fabric-and-power-bi/) and [Purview Data Governance coverage](https://atlan.com/know/ai-agent/microsoft/purview-data-governance-coverage/).

---

## What can a new catalog rebuild, and what must you move?

Any catalog you pick can crawl your sources directly. Its connectors read assets and technical metadata from the systems where data runs, so a new catalog does not need the Data Map to see your estate.

Lineage is crawled from those sources down to columns where the source exposes them. Check how many of your sources the destination connects to, and whether it reads Fabric items such as lakehouses, warehouses, semantic models, and reports.

Scans cannot rebuild what your people curated. Descriptions, glossary terms, owners, and lineage drawn by hand live only in the Data Map. Microsoft's custom types page says Purview relies on the Apache Atlas type system, so custom types and classifications can be read through the Data Map type API in a form that maps to other catalogs built on the same model.

For governance your team built in Purview Data Governance, ask the destination three things. Does it read Purview with read-only access? Does it show what would be dropped before it writes? Does it wait for your governance lead's approval? In its [November 17, 2026 post](https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/onelake-the-unified-foundation-for-data-context-governance-and-ai/5423035), Microsoft says Atlan supports customers transitioning from Purview Data Governance to Fabric with tooling to carry their existing metadata forward. The [migration plan](https://atlan.com/know/ai-agent/microsoft/how-to-migrate-from-purview-data-governance/) walks through the steps, and [Microsoft's governance tools](https://atlan.com/know/data-governance/microsoft-data-governance-tools/) shows the wider stack.

---

## What should you inventory before maintenance mode ends?

Capture the list below while the Data Map still runs. Each line maps to something Microsoft says the Data Map stores or exposes through its API.

1. **Accounts and collections.** Note which accounts exist and how collections map to your data sources.
2. **Registered sources, scan rules, and schedules.** These tell a new catalog what to crawl and how often.
3. **Classifications.** Export the definitions, and note which assets carry your own versus built-in ones.
4. **Custom type definitions.** Read entity, relationship, and enum definitions through the type API, and list the assets built on them.
5. **Business metadata and term template definitions.** The type API returns both.
6. **Glossary terms and descriptions.** Note the ones your stewards wrote by hand.
7. **Lineage.** Separate what scans captured from what your team added.
8. **Owners and stewards.** Check who has left before anything moves.
9. **Downstream callers.** List every job, script, and report that calls the Data Map REST API.
10. **Capacity and billing metrics.** Microsoft exposes Data Map capacity units and storage size in the Azure portal, which tells you the size of what you hold.

Write each line down with an owner and a date. 

A list with names on it gets finished. A list without them gets read once.

The Data Map itself is not the only thing to inventory. Governance objects such as domains, data products, and glossaries belong to [Unified Catalog](https://learn.microsoft.com/en-us/purview/unified-catalog), per Microsoft, and the [move guide](https://atlan.com/know/ai-agent/microsoft/move-purview-domains-data-products-glossary/) covers them.

---

## How should you plan the timeline?

Transition support began on November 12, 2026, and support ends on November 12, 2027. That is about a year, and approvals shrink it.

Start with the inventory above.

Reading definitions and lineage through the REST APIs changes nothing in your estate. Your team can begin today. Then take two questions to your Microsoft account team: what maintenance mode covers for the Data Map in your tenant, and what applies to your contractual or regulatory obligations. Microsoft says these cases need to be assessed individually.

Keep the scope straight while you plan.

Microsoft says Purview Data Security and Compliance is not affected and continues to protect your data in Fabric. That includes four capabilities: Information Protection, Data Loss Prevention, Insider Risk Management, and Data Security Posture Management. Your Data Map inventory belongs to the governance side. Those four do not need to move.

Next, decide where governance lives. Microsoft says the OneLake catalog covers data in or connected to OneLake, and names Atlan for extending governance beyond OneLake. Both can run alongside Purview while you move, and a rerun of your load should add only new items.

The [retirement checklist](https://atlan.com/know/ai-agent/microsoft/purview-data-governance-retirement-checklist/) turns this into dated steps, and [what stays in Microsoft Purview](https://atlan.com/know/ai-agent/microsoft/what-stays-in-microsoft-purview-after-retirement/) lists what Microsoft says is not affected.

For the full set of options, see [Purview Data Governance alternatives](https://atlan.com/purview-alternatives/), the [data governance partners](https://atlan.com/know/ai-agent/microsoft/microsoft-data-governance-partners-after-purview-retirement/) guide, [coexist, extend, or replace Purview](https://atlan.com/know/ai-agent/microsoft/coexist-extend-replace-purview/), and [what Microsoft Purview is](https://atlan.com/know/ai-agent/microsoft/what-is-microsoft-purview/).

Regulated teams can use a [readiness checklist](https://atlan.com/know/finserv/data-governance-migration-readiness-checklist/) to set the bar, and [Fabric governance evaluation questions](https://atlan.com/know/ai-agent/microsoft/fabric-governance-evaluation-questions/) help you test each option. Moving workloads too? Check [Snowflake to Fabric lineage](https://atlan.com/know/ai-agent/microsoft/snowflake-to-fabric-migration-lineage/) and [Synapse to Fabric metadata](https://atlan.com/know/ai-agent/microsoft/synapse-to-fabric-migration-metadata/). If Fabric is your destination, [catalogs for Microsoft Fabric](https://atlan.com/best-data-catalogs-for-microsoft-fabric/) compares the choices.

---

## FAQs about the Purview Data Map after retirement

Every answer here uses only what Microsoft's sources say.

### 1. Is the Purview Data Map reaching end of life?

Microsoft's Learn page for the Data Map says classic Purview data governance capabilities are being retired. You can no longer create new accounts. Existing capabilities stay in maintenance mode through November 12, 2027. The page gives no separate date for the Data Map. Confirm Data Map specifics with your Microsoft account team.

### 2. Does Microsoft's November 12 post name the Data Map?

No. The November 12, 2026 post says support for Purview Data Governance ends on November 12, 2027. It does not mention the Data Map, Unified Catalog, glossaries, or data products. The Learn banner is the only Microsoft wording on the Data Map. Ask your Microsoft account team how the retirement applies to yours.

### 3. What does the Purview Data Map hold?

Microsoft describes four kinds of metadata. Technical metadata covers schemas, data types, and columns from scans. Business metadata covers descriptions and glossary terms. Semantic metadata covers collection mappings and classifications. Operational metadata covers Data Factory run statuses and times. The Data Map also holds lineage and any custom types your team made.

### 4. What can a new catalog rebuild from your sources, and what must you move?

A new catalog can read assets, technical metadata, and scanned lineage from the source systems again. It cannot rebuild what people curated: descriptions, glossary terms, owners, and lineage drawn by hand. Export those from Purview before support ends, then check what landed against your list.

### 5. 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.

### 6. What should you do before maintenance mode ends?

List what the Data Map holds. That means scan setups, classifications, custom types, glossary terms, and lineage added by hand. Then confirm the details with your Microsoft account team. This matters most if you have contractual obligations or work in a regulated industry. Microsoft says those cases are assessed individually.

### 7. Is Purview Data Security and Compliance also retiring?

No. 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.

### 8. Is the OneLake catalog enough to replace Purview Data Governance?

Microsoft calls it a new model, not a feature-for-feature replacement. It governs data in or connected to OneLake. If your data sits mostly there, it may cover what you need. For sources beyond OneLake, Microsoft says OneLake and Fabric customers can use Atlan to extend governance. Test your own estate against both before you decide.

---

## Sources

1. [Microsoft Purview Data Map overview, Microsoft Learn](https://learn.microsoft.com/en-us/purview/data-map)
2. [Microsoft Purview Unified Catalog, Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog)
3. [Type definitions and how to create custom types, Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/purview/data-gov-api-custom-types)
4. [Data Map type REST API, Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/type)
5. [Data Map lineage REST API, Microsoft Purview, Microsoft Learn](https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/lineage)
6. [OneLake catalog overview, Microsoft Fabric, Microsoft Learn](https://learn.microsoft.com/en-us/fabric/governance/onelake-catalog-overview)
7. [A next step in the evolution of the Microsoft Data Governance strategy, Microsoft Security Community Blog, November 12, 2026](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227)
8. [OneLake: the unified foundation for data, context, governance, and AI, Microsoft Fabric Community Blog, November 17, 2026](https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/onelake-the-unified-foundation-for-data-context-governance-and-ai/5423035)

## Next steps

- To see Atlan's context layer in action first, watch a recorded demo: [Atlan context layer demos](https://atlan.com/context-layer-demo/)
- To see Atlan working on your own data stack, book a demo: [Book a demo with Atlan](https://atlan.com/forms/talk-to-sales-contact/)
