Guide · Purview to OneLake Migration

How to find what reads your Purview catalog through its API

Updated 2026-11-21Python and DuckDBRuns shown on generated records, PDF by email

The short answer

The Purview catalog keeps no record of who reads the catalog. Microsoft Entra sign-in logs record each app, managed identity and person that gets a token for Purview. Export those sign-ins from Log Analytics. Record an owner and a planned action for each caller. One Python and DuckDB script then lists the callers and runs four checks.

Why find the readers first

Microsoft announced on November 12, 2026 that Purview Data Governance is retiring: “Support for Purview Data Governance will end Nov. 12, 2027” (Microsoft Security blog, read 2026-11-21). Microsoft's transition guide (read 2026-11-21) lists APIs and reports among the things to inventory, and says not to assume compatibility with existing Purview API integrations.

Every report, pipeline or script that reads the catalog through its API breaks at the switch-off unless someone moves it first. The catalog itself does not record who reads it: as of 2026-11-21, the log categories Microsoft lists for a Purview account cover data sensitivity, scan status and security events such as role assignments. Your Microsoft Entra sign-in logs do record each app, managed identity and person that gets a token for Purview, so those logs are where the reader list comes from.

What you will have at the end

  • A reader list, readers.csv: one row per app, managed identity or person that signed in to Purview, with sign-in counts, first and last seen, and the owner and planned action you record.
  • Four checks, each one PASS or FAIL: every caller has an owner, every active caller has a planned action, no caller only fails, and no person calls the API directly.

Step 1. Export the sign-ins

The sign-ins live in four Log Analytics tables once your Entra logs are sent to a Log Analytics workspace (read 2026-11-21): AADServicePrincipalSignInLogs for apps, AADManagedIdentitySignInLogs for managed identities, SigninLogs for people who sign in themselves, and AADNonInteractiveUserSignInLogs for sign-ins a tool makes on a person’s behalf, for example a client app that uses a refresh token to get an access token (all read 2026-11-21). The third query reads both people tables. Microsoft Entra ID keeps sign-ins for 7 days on Microsoft Entra ID Free and 30 days on P1 and P2, according to Microsoft's retention page (read 2026-11-21), so send the logs to a workspace early, and set the query time range to cover as many months as the workspace holds.

We did not run these queries. We have no tenant to run them against, so they are written from Microsoft's table references, and the runs further down use generated records in the same shape. Run each query in the workspace, check the resource name your tenant shows for Purview, and export each result as CSV with the file name given. Each query writes TimeGenerated as ISO 8601 text, so the CSV reads the same whatever regional format and time zone the portal shows.

// Not run by us: written from Microsoft's Azure Monitor table references (read 2026-11-21).
// 1. Apps (service principals). Export the result as service-principals.csv
AADServicePrincipalSignInLogs
| where ResourceDisplayName has "Purview"
| extend TimeGenerated = tostring(TimeGenerated)   // ISO 8601 text, the same in every regional format
| project TimeGenerated, ServicePrincipalId, ServicePrincipalName, AppId, ResourceDisplayName, ResultType, IPAddress

// 2. Managed identities. Export the result as managed-identities.csv
AADManagedIdentitySignInLogs
| where ResourceDisplayName has "Purview"
| extend TimeGenerated = tostring(TimeGenerated)   // ISO 8601 text, the same in every regional format
| project TimeGenerated, ServicePrincipalId, ServicePrincipalName, AppId, ResourceDisplayName, ResultType, IPAddress

// 3. People, signed in themselves or through a tool on their behalf. Export the result as users.csv
union SigninLogs, AADNonInteractiveUserSignInLogs
| where ResourceDisplayName has "Purview"
| extend TimeGenerated = tostring(TimeGenerated)   // ISO 8601 text, the same in every regional format
| project TimeGenerated, UserId, UserPrincipalName, AppDisplayName, ResourceDisplayName, ResultType, IPAddress

Then write owners.csv with the columns caller_id (the service principal id or user id from the exports), owner and planned_action, for example “repoint to the new catalog” or “retire”.

Step 2. Build the reader list

Download find_catalog_readers.py, install DuckDB (pip install duckdb) and run the script on the folder with the four CSVs:

python3 find_catalog_readers.py purview-signins --as-of 2026-11-21 --active-days 30
CheckWhat a failure means
Every caller that signed in has an ownerNobody is answerable for moving that integration, so the integration breaks at the switch-off.
Every active caller has a planned actionA caller that signed in during the last --active-days days still depends on Purview and has no plan.
No caller has only failed sign-insAn integration fails every time, so whatever depended on it has already stopped working.
No person calls the API directlySomeone reads the catalog with a script or a tool such as the Azure CLI; that use is easy to miss because no app registration shows it.

Run 1. Generated sign-ins, clean

The script writes generated exports when you ask for them: three apps and two managed identities that signed in to Purview between September 1 and November 21, 2026, and an owners file, with a fixed seed.

python3 find_catalog_readers.py --make-demo demo
Wrote generated sign-in exports to demo: 75 service principal, 50 managed identity and 0 user sign-ins, 5 owner rows (seed 276)
python3 find_catalog_readers.py demo --as-of 2026-11-21
Python 3.14.8 duckdb 1.5.6
Sign-ins: 125 from 5 callers, 2026-09-01 to 2026-11-21; resources: Microsoft Purview

  Kind              Caller                             Sign-ins    OK Last seen   Owner                      Active
  app               adf-lineage-push                         25    25 2026-11-21  team-adf@example.com       yes
  managed identity  func-steward-alerts                      25    25 2026-11-21  team-func@example.com      yes
  managed identity  logicapp-access-requests                 25    25 2026-11-19  team-logicapp@example.com  yes
  app               powerbi-catalog-refresh                  25    25 2026-11-20  team-powerbi@example.com   yes
  app               glossary-sync-to-wiki                    25    25 2026-10-11  team-glossary@example.com  no

Checks (active means signed in within 30 days of 2026-11-21)
  PASS  Every caller that signed in has an owner in owners.csv
  PASS  Every active caller has a planned action
  PASS  No caller has only failed sign-ins (a broken integration nobody noticed)
  PASS  No person calls the API directly from a script or tool

Wrote readers.csv (5 callers) to .
RESULT: 5 callers read the catalog; 0 findings to settle before the switch-off.

How to read it

Each row is one caller. An active caller still depends on Purview and needs its planned action done before the switch-off. The glossary sync app last signed in on October 11, so the app is no longer active; its planned action is to retire the app.

Run 2. The same sign-ins with four planted problems

python3 find_catalog_readers.py --make-demo demo-planted --plant-errors
Wrote generated sign-in exports to demo-planted: 81 service principal, 50 managed identity and 4 user sign-ins, 5 owner rows (seed 276)
Planted one error for each check: NO_OWNER, NO_PLAN, ONLY_FAILURES, PERSON_DIRECT
python3 find_catalog_readers.py demo-planted --as-of 2026-11-21 --tag planted
Python 3.14.8 duckdb 1.5.6
Sign-ins: 135 from 7 callers, 2026-09-01 to 2026-11-21; resources: Microsoft Purview

  Kind              Caller                             Sign-ins    OK Last seen   Owner                      Active
  app               adf-lineage-push                         25    25 2026-11-21  -                          yes
  managed identity  func-steward-alerts                      25    25 2026-11-21  team-func@example.com      yes
  managed identity  logicapp-access-requests                 25    25 2026-11-19  team-logicapp@example.com  yes
  app               powerbi-catalog-refresh                  25    25 2026-11-20  team-powerbi@example.com   yes
  app               nightly-term-export                       6     0 2026-11-14  team-nightly@example.com   yes
  person            data.steward@example.com                  4     4 2026-11-16  -                          yes
  app               glossary-sync-to-wiki                    25    25 2026-10-11  team-glossary@example.com  no

Checks (active means signed in within 30 days of 2026-11-21)
  FAIL  Every caller that signed in has an owner in owners.csv  (2)
  FAIL  Every active caller has a planned action  (3)
  FAIL  No caller has only failed sign-ins (a broken integration nobody noticed)  (1)
  FAIL  No person calls the API directly from a script or tool  (1)
  NO_OWNER       app: adf-lineage-push: no row in owners.csv
  NO_OWNER       person: data.steward@example.com: no row in owners.csv
  NO_PLAN        app: adf-lineage-push: last signed in 2026-11-21, no planned action
  NO_PLAN        managed identity: func-steward-alerts: last signed in 2026-11-21, no planned action
  NO_PLAN        person: data.steward@example.com: last signed in 2026-11-16, no planned action
  ONLY_FAILURES  app: nightly-term-export: 6 sign-ins, none succeeded
  PERSON_DIRECT  person: data.steward@example.com: signs in through Azure CLI

Wrote readers-planted.csv (7 callers) to .
RESULT: 7 callers read the catalog; 7 findings to settle before the switch-off.
CheckThe problem planted in run 2
OwnersThe adf-lineage-push app's row removed from owners.csv.
Planned actionsThe func-steward-alerts managed identity's planned action left blank.
Only failuresA nightly-term-export app whose six sign-ins all failed.
People calling directlyA data steward signing in to Purview through the Azure CLI.

The four planted problems give seven findings, because two of the problems trip more than one check: the adf-lineage-push app has no owner row, so the app also has no planned action, and the data steward trips three checks: no owner row, no planned action and a direct sign-in through the Azure CLI.

Run the reader list on your own logs

Save the results of the three queries in step 1 as service-principals.csv, managed-identities.csv and users.csv in one folder named purview-signins, and save owners.csv in the same folder. Then run python3 find_catalog_readers.py purview-signins --as-of followed by today's date, for example 2026-11-21. You do not edit the script.

We also tested a run on a second set of generated sign-ins, saved the way you would save your own exports: other app names, upper-case ids, an empty IP address, the time column as the Log Analytics portal exports it in US format, a person who signs in through two tools, a person who uses only the Purview portal, two owner rows for one app, and one planted problem for each check. All four checks failed as planted; the app with no owner also had no planned action, and nothing else was flagged.

Download find_catalog_readers.py · Get the full guide (PDF)

Result from run 1: readers.csv.

Get the full guide as a PDF

We'll email you a link to it. Please use your work email.

Limits

  • The runs on this page use generated records, not a real tenant, and the queries in step 1 were not run. The column names come from Microsoft's table references, read on 2026-11-21.
  • A sign-in shows that a caller got a token for Purview, not which API the caller then used or what the caller read. A caller that reuses one token for many calls shows as one sign-in.
  • The list covers what your workspace kept. A caller that last signed in before the logs reached the workspace does not appear.
  • The queries match resources whose display name contains “Purview”. Check the name your tenant shows; a different name needs a different filter.
  • The check on people flags a person whose sign-in app name contains CLI, PowerShell, Python, SDK, Postman, Graph Explorer or Visual Studio. A person who signs in only through the Purview portal is not flagged. Add the app names your tenant shows in users.csv to SCRIPT_CLIENTS at the top of the script.
  • The script counts a sign-in as successful when ResultType is 0, as Microsoft's SigninLogs reference describes. Check that your exports use the same code.
  • Dates are as of 2026-11-21. This guide is about Purview Data Governance, whose support ends on November 12, 2027.

Tested on

Tested on

Platform
DuckDB 1.5.6, run from Python 3.14.8
Edition
Open-source DuckDB library (pip install duckdb)
Date
2026-11-21
Records
Generated: invented sign-ins of three apps and two managed identities, September 1 to November 21, 2026, fixed seed 276, in the columns of Microsoft's table references. Not a run against a tenant.
Code
find_catalog_readers.py
Results
readers.csv

When this is not enough

The reader list names the callers. Each one then needs a decision: repoint the integration to the new catalog, rebuild it on the new APIs, or retire it, and a date before the switch-off for each.

Moving your whole Purview governance catalog, not only the list of readers?

Purview to OneLake Migration is in early access. The offering starts with the four-day Catalog Transition Assessment: one fixed fee of $12,000, and no commitment to anything else. You get an inventory of every object in your Purview governance catalog and a decision for each object. AI does the first pass, and your stewards sign every domain.

See Purview to OneLake Migration