Purview → Fabric OneLake Catalog: Sync Overview & Roadmap¶
Last reviewed: 2026-09-29 (published Fabric API spec). Tenant verification: 2026-09-23, against a live Purview tenant (
kaydemopurview, test data only) and themicrosoft/fabric-rest-api-specsOpenAPI specs (includingontology/anddataAgent/). Fabric GPS roadmap checked: 2026-09-29. See "Re-check checklist" below for what to re-verify and when.Microsoft Purview's standalone data governance experience is being retired in favor of governance capabilities built directly into Microsoft Fabric (OneLake catalog, Fabric domains/tags, Fabric admin APIs). This page is the single at-a-glance status board for what
pvw-clican already sync from Purview Unified Catalog (UC) into Fabric today, what's blocked and why, and what to watch on the Fabric roadmap.For hands-on usage see the Fabric Sync Guide (commands, options, permissions, scheduling). For the exhaustive implementation-level detail behind each row below, see the Fabric Sync Feature Parity Map. This page is the summary; those two are the source of truth.
WARNING: The sync is experimental and must not be used in production. Use only non-production data and resources when assessing or applying changes.
Get the live version from the CLI¶
The table below is a snapshot. The CLI renders the same data live, straight from
purviewcli/sync/capabilities.py — the single source
of truth both this page and the CLI draw from — so it can never silently drift from what's
actually implemented:
pvw fabric sync capabilities # table
pvw fabric sync capabilities --output json # machine-readable
pvw fabric sync capabilities --status planned # only "planned/TBD" rows
To consult current Fabric data-governance roadmap announcements, rather than the verified sync-status board above:
pvw fabric sync roadmap # live Fabric GPS results
pvw fabric sync roadmap --status planned
pvw fabric sync roadmap --output json # checked_at, source, note, items
This read-only command queries the Fabric GPS roadmap API
across the Administration, Governance and Security and IQ product categories,
following all pages and filtering feature names for governance topics (OneLake
catalog, Ontology, Fabric Graph, labels, lineage, quality, and related topics).
Results include the roadmap's last_modified date, release status, and target
date. It requires network access but no Fabric/Purview credentials. GPS is a
roadmap mirror, not proof that an API is available or that sync is implemented:
verify the published spec and tenant behavior before changing a capability's
status. The command does not alter the capability board or sync data.
Fabric GPS snapshot (2026-09-25)¶
At 18:39 UTC, pvw fabric sync roadmap --output json returned 53 matching
announcements: 42 Shipped and 11 Planned (25 under IQ, 28 under
Administration, Governance and Security). These are feature-name matches
from those two product categories, not the entire Fabric roadmap and not an
API-availability audit. Relevant planned items included:
| Roadmap item | Roadmap status / target | Impact to re-check |
|---|---|---|
| Ontology item GA; Public query API for Ontology | Planned / Q4 2026 | Ontology definition management already has a published REST spec; the query API is a distinct future feature. Re-check relationships and tenant behavior before attempting structured governance sync. |
| Ontology Versioning; Full Ontology canvas experience | Planned / Q3 2026 | Re-check maturity of Ontology definitions; neither changes the current tag mapping by itself. |
| OneLake catalog Search API expansion to OneLake and Semantic model tables | Planned / Q3 2026 | Re-check POST /v1/catalog/search result shapes before extending asset matching below Fabric items. |
Govern Skills for Fabric was marked Shipped (Q3 2026); it does not
establish a Purview-to-Fabric metadata mapping. Run the command again for
current statuses; this dated snapshot does not update automatically.
API spec changes (2026-09-29)¶
The Fabric REST spec update
adds Workspace results alongside FabricItem to POST /v1/catalog/search.
Sync now excludes workspace results when discovering item targets, while
preserving other previously recognized catalog entries. The spec also
documents WorkspaceId server-side filtering (up to 12 GUIDs per filter);
sync retains its existing client-side workspace filter until that new
request behavior is validated in a tenant. This is a spec-based compatibility
guard, not a new live-tenant verification.
Ontology responses now include read-only properties.generation (1 or 2).
Creating an Ontology without a definition defaults to generation 2; a provided
definition determines its generation. This is relevant to a future mapping but
does not enable Ontology writes in this sync. Fabric GPS still lists the
Ontology query API and GA as Planned (Q4 2026) and the catalog table-search
expansion as Planned (Q3 2026). Ontology Health has shifted to Q1 2027.
Status legend¶
| Status | Meaning |
|---|---|
| ✅ Supported | Live-verified against a real tenant; ships in pvw fabric sync today. |
| 🟡 Partial | Some of the concept is portable (e.g. just a name-as-tag); the rest has no Fabric equivalent yet. |
| 🔜 Planned / TBD | Believed technically possible once a specific, currently-missing API exists; not started. Re-check the Fabric roadmap before starting. |
| ⛔ Not supported | No known path today — blocked on a Fabric or Purview product decision, not just an API gap. |
Sync status by capability¶
| Purview UC capability | Fabric target | Status | Notes |
|---|---|---|---|
| Data asset display name / description | Item displayName / description |
✅ Supported | Always on; additive-only, dry-run by default. |
| Governance domain | Fabric domain + workspace assignment | ✅ Supported | Matched/created by name; always on. |
| Glossary term name | Namespaced Fabric tag purview:term:<name> |
🟡 Partial | Only the name is portable — no hierarchy, definitions, or relationships. |
| Data product name | Namespaced Fabric tag purview:data_product:<name> |
🟡 Partial | Name only; Fabric has no first-class "data product" object yet. |
| Critical Data Element (CDE) name | Namespaced Fabric tag purview:cde:<name> |
🟡 Partial | Name only. |
Data Map classifications (e.g. MICROSOFT.PERSONAL.EMAIL) |
Namespaced Fabric tag purview:classification:<name> |
✅ Supported | Opt-in via --sync-classifications; requires a resolvable Data Map link + known type mapping. |
| Data Map labels (free-text) | Namespaced Fabric tag purview:label:<name> |
✅ Supported | Opt-in via --sync-classifications; same source/limitations as classifications. |
| Sensitivity label (MIP) | Item sensitivityLabel.id + admin bulkSetLabels/bulkRemoveLabels |
🔜 Planned / TBD | Fabric side is ready (verified 2026-09-22): Get/List/Create Item return sensitivityLabel.id, Create accepts sensitivityLabelSettings.labelId, and admin bulk set/remove label APIs exist. Still blocked on the Purview read side — no confirmed per-asset API returns an asset's applied MIP label ID (only tenant-wide aggregate reports). |
| Data quality rules / scores | (no Fabric OneLake catalog field identified) | 🔜 Planned / TBD | Watch Fabric's data-quality feature area on the roadmap for a documented per-item API. |
| Lineage | (no confirmed mapping) | 🔜 Planned / TBD | Fabric's lineage model differs structurally from Purview's Atlas process/relationship graph. Needs its own design once/if a compatible ingestion API ships. |
| Data Products as first-class Fabric objects | (no Fabric object exists) | ⛔ Not supported | Fabric has no native "data product" concept beyond tags today; re-evaluate if that changes. |
| RBAC → ABAC access policies | (no confirmed Fabric equivalent) | ⛔ Not supported | Purview's attribute-based access policies have no matching Fabric item/workspace policy API today. |
| Custom / managed attributes | (no confirmed Fabric field) | 🔜 Planned / TBD | Present in Purview UC domain responses (managedAttributes); no confirmed arbitrary-property field on Fabric items yet. |
| Full glossary hierarchy (parent/child terms, relationships) | (no Fabric equivalent) | ⛔ Not supported | Only the term's name is portable as a tag today; Fabric Ontology (next row) is the eventual candidate target, but not until relationships/hierarchy ship in its public API. |
| Structured governance model (typed entity properties, relationships) | Fabric Ontology item (EntityTypes with typed properties) |
🔜 Planned / TBD | API spec and roadmap checked 2026-09-29: Ontology definition-management REST APIs expose typed EntityType properties and read-only properties.generation (1 or 2); creation without a definition defaults to generation 2. Data Agent accepts Ontology as a datasource. The separate public query API and Ontology GA remain Planned (Q4 2026), with versioning and the full canvas Planned (Q3 2026). Relationships/hierarchy are not yet confirmed in the published spec; no structured sync has been implemented. |
Re-check checklist¶
Run through this list periodically (e.g. quarterly, or whenever Microsoft announces a Fabric governance update) to see if any 🔜/⛔ row can move to ✅/🟡. Each item links directly to where the answer would show up — no need to rediscover these sources from scratch:
| # | Re-check this | Where to look | Unblocks |
|---|---|---|---|
| 1 | Does Purview expose a per-asset sensitivity-label read API yet (Data Map entity attribute, UC data asset field, or a new endpoint)? (Fabric's side is already confirmed ready as of 2026-09-22 — this is the only remaining blocker.) | Purview REST API reference, Fabric GPS roadmap API | Sensitivity label (MIP) sync |
| 2 | Has Fabric shipped a documented data-quality API for attaching scores/rules to catalog items? (As of 2026-09-22 only transformation-level checks exist: shortcut-transformation corrupt rows, MLV column checks — neither is catalog metadata.) | Fabric GPS roadmap API, Fabric REST API reference | Data quality rules / scores sync |
| 3 | Has Fabric shipped a lineage-ingestion API compatible with Purview's process/relationship entities? | Fabric GPS roadmap API, Fabric REST API reference | Lineage sync |
| 4 | Has Fabric introduced a native data-product object (beyond tags)? | Fabric GPS roadmap API, Microsoft Fabric blog | Data Products as first-class Fabric objects |
| 5 | Does Fabric support arbitrary custom/managed properties on items (beyond tags/sensitivity labels)? | fabric-rest-api-specs — platform definitions, Fabric REST API reference — Items |
Custom / managed attributes sync |
| 6 | Has Fabric added an attribute-based access policy API at the item/workspace level? (As of 2026-09-22, "Outbound Access Protection" items are network-egress controls, not ABAC.) | Fabric GPS roadmap API | RBAC → ABAC policy sync |
| 7 | Does the published Ontology definition-management API expose relationships/hierarchy between entity types and define compatible generation 2 parts? Has Ontology GA shipped (Planned Q4 2026 on Fabric GPS as of 2026-09-29)? The separate public query API is also Planned for Q4 2026. | fabric-rest-api-specs — ontology, Fabric GPS roadmap API |
Structured governance model (typed entities/relationships), full glossary hierarchy |
Useful sources for re-checking¶
microsoft/fabric-rest-api-specs— the authoritative OpenAPI specs. Best signal for "does this API actually exist?", and fetchable without a browser (raw JSON). Example:gh api "search/code?q=sensitivityLabel+repo:microsoft/fabric-rest-api-specs".- Fabric GPS roadmap API — a queryable JSON/RSS mirror of the Fabric roadmap (
/api/releases?q=...&product_name=...&release_status=...). Useful because roadmap.fabric.microsoft.com itself is a JS-rendered SPA that can't be read without a browser. - Fabric roadmap — the official source (requires a browser to read).
How this table is kept current¶
This page reflects the same facts recorded in
fabric-sync-feature-parity.md and in
purviewcli/sync/capabilities.py (the CLI's source
of truth), summarized for a quick read. It should be revisited:
- Whenever the "Re-check checklist" above turns up a new API.
- Whenever this project live-verifies a new Purview or Fabric API shape (see the "Verification status" section of the Fabric Sync Guide for the project's live-verify-first convention).
When a 🔜/⛔ row becomes possible:
- Live-verify the exact request/response shape against a real tenant first — never assume a shape from documentation alone.
- Update the row in
purviewcli/sync/capabilities.pyfirst (the CLI's source of truth), then mirror the change here and infabric-sync-feature-parity.md, recording what was verified and against what. Update the relevant roadmap and API/tenant review dates at the top of this page independently. - Extend
purviewcli/sync/models.py,service.py,purview_to_fabric.py,execution.py,fabric_client.py, andcli/fabric.py, following the same additive, opt-in pattern used for--sync-classifications.
Note: the specific "not yet possible" reasons above reflect this project's most recent live-tenant verification and public API research; they are not a live feed from Microsoft's roadmap site. Treat any 🔜 row as "worth re-checking," not as a committed Microsoft ship date.