A unified data governance solution that helps manage, protect, and discover data across your organization
Hi Sara,
This issue occurs because Business Glossary access in Microsoft Purview is controlled by Data Map collection permissions, specifically at the Root Collection level.
Azure RBAC roles (such as Contributor or Domain Admin) and collection‑level roles alone do not grant access to Business Glossary APIs. If the user is not explicitly assigned as a Data Curator or Data Reader on the Root Collection, Purview returns a 403 “Not authorized to access account” error.
Microsoft confirms that collections are the security boundary for metadata access, including glossary terms.
Step‑by‑Step Resolution
- Open the Microsoft Purview Governance Portal https://purview.microsoft.com
Go to Data Map → Collections
Select the Root Collection (the top‑level collection with the same name as the Purview account)
Under Role assignments, explicitly add your user with one of the following roles:
- Data Curator (to create or edit glossary terms), or
Data Reader (to view glossary terms)
Save the changes
Sign out and sign back in to the Purview portal
After these steps, the 403 error is resolved, and the new Business Glossary terms become visible.
Reference Links:
Data governance roles and permissions in Microsoft Purview https://learn.microsoft.com/en-us/purview/data-governance-roles-permissions [Access Den...ogin Error]
Access control in the Microsoft Purview governance portal https://learn.microsoft.com/en-us/purview/data-gov-classic-permissions [Installing...ror ID 204]
Microsoft Purview domains and collections architecture https://learn.microsoft.com/en-us/purview/data-gov-best-practices-domains-collections [Users tab...ermissions]
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.