A unified data governance solution that helps manage, protect, and discover data across your organization
Thanks what you observed makes sense. Although Privileged Role Administrator is the documented minimum role, some tenant-level controls can prevent it from unlocking Purview’s Roles and scopes page. Examples include PIM eligibility not being activated, Conditional Access or tenant hardening policies, role assignments scoped below the tenant root, or propagation delays. These controls can cause the portal to require a broader admin context.
Global Administrator succeeds because it bypasses those tenant-level restrictions and therefore is the most reliable way to make the page appear in hardened environments. That said, before leaving someone as Global Admin, you can try these lower-privilege checks: ensure the role is assigned at the tenant root (not just eligible), activate the PIM assignment if applicable, sign out and sign back in, and wait ~10–15 minutes for propagation. If those don’t work, Global Admin is a practical short-term fix.
Hope this helps, Please let us know if you have any questions and concerns.