How to Automatically Fetch Microsoft Purview Glossary Links for Table Columns and Store Them in Dedicated SQL Pool Using Synapse Pipelines

Question

How to Automatically Fetch Microsoft Purview Glossary Links for Table Columns and Store Them in Dedicated SQL Pool Using Synapse Pipelines

Mallikarjun appani 6

Looking for a supported way to programmatically retrieve Purview glossary hyperlinks mapped to each column and persist them into a Dedicated SQL table or CSV using Synapse pipelines.

2 answers

Your answer

Answer 1

Smaran Thoomu 33,840 Microsoft External Staff Moderator

Hi Mallikarjun appani
Good question.

The /resource/{guid} link is mainly a portal-internal link. It doesn’t always work if you open it directly, especially if the tenant or Purview account context isn’t already loaded. That’s why you’re seeing the Axios/network error - it’s a portal routing behavior, not an issue with your API call.

Right now there isn’t a guaranteed “shareable deep link” format for glossary terms. The stable part you can rely on is the term GUID from the API.

What most teams do is:

Store the term GUID and term name in SQL/CSV
Let users navigate to the glossary inside Purview and search by name or ID if needed

So, for programmatic use, treat the GUID as the real reference, not the portal URL.

Hope that clarifies it.

Mallikarjun appani 6 Reputation points

2026-02-09T15:24:48.3333333+00:00

Thank you for the clarification—this helps a lot.

I have one follow-up question regarding authentication. In our setup, Azure Purview and Azure Synapse are in different subscriptions, and because of this, I’m unable to see the System Assigned Managed Identity of the Synapse workspace in the Purview Data Map while trying to grant access.

Could you please advise on:

How to grant Purview access to a Synapse Managed Identity across subscriptions, or

Whether there are any additional steps or prerequisites required for cross-subscription visibility (such as tenant-level settings or role assignments)?

Any guidance on enabling this cross-subscription integration would be greatly appreciated.

Thank you for your support.
Smaran Thoomu 33,840 Reputation points Microsoft External Staff Moderator

2026-02-12T08:16:08.8133333+00:00
Mallikarjun appani Good question - this comes up often with cross-subscription setups.

If Microsoft Purview and Azure Synapse Analytics are in different subscriptions, that by itself is OK. The important requirement is that they are in the same Entra ID (Azure AD) tenant.

A Synapse managed identity won’t show up in Purview automatically - you don’t “discover” it from Purview. Instead, you grant it access like any other identity.

What to check

Same tenant

Both subscriptions must belong to the same Entra ID tenant. If they’re in different tenants, the managed identity won’t be selectable.

Grant access manually

In Purview:

Go to Collection → Role assignments

Add role assignment

Search for the Synapse workspace name (this represents its managed identity)

Assign a role like Data Curator or Data Reader as needed

You may need Owner/User Access Admin rights to do this.

If you can’t find the identity

Sometimes it doesn’t appear in search right away. In that case:

Go to Entra ID → Enterprise applications

Find the Synapse workspace managed identity

Copy the Object ID

Use that identity when assigning roles

Cross-subscription works fine. Cross-tenant does not. Access is controlled by Entra ID roles, not subscription boundaries.

Once the role is assigned, Synapse pipelines should be able to call Purview APIs.

Hope this helps. If it still doesn’t show up, let me know whether both subscriptions are under the same tenant.

Answer 2

Hi Mallikarjun appani,
Thankyou for reaching Microsoft Q&A!

In Microsoft Purview, when a glossary term is assigned to a column, the mapping is stored on the column entity in the meanings attribute. Each entry contains a termGuid, which is what the Purview portal uses to open the glossary term page.

The required flow in Azure Synapse Analytics is:

Call the Purview search API to get table GUIDs. For each table, call the entity API and read its column entities from referredEntities. Check each column for meanings.termGuid. For every termGuid, call the glossary term API and construct the hyperlink as:

https://web.purview.azure.com/resource/{termGuid}

Persist the results into a table in Azure Synapse Dedicated SQL Pool (or CSV) using a Copy activity.

Use Synapse Managed Identity with Data Curator role in Purview for authentication.

There is no native export for column-to-glossary links, so this REST API method is the only supported approach.

Mallikarjun appani 6 Reputation points

2026-02-05T17:23:17.2166667+00:00

Hi @Anonymous
Is the https://web.purview.azure.com/resource/{guid} URL expected to work when opened directly in the browser?
Is there a more reliable or supported way to generate user-clickable glossary links for documentation, SQL tables, or Power BI reports?

Purview glossary deep link https://web.purview.azure.com/resource/{guid} throws Axios Network Error when opened directly.

Share via

How to Automatically Fetch Microsoft Purview Glossary Links for Table Columns and Store Them in Dedicated SQL Pool Using Synapse Pipelines

2 answers

Your answer