@ADM Nick Sørensen - Thanks for the question and using MS Q&A platform.
Here is the update from internal team:
The priviledge in question seems to be if the user has access to any federated catalog with USE CATALOG
, without access to any of the underlying schemas. (I.e no USE SCHEMA
and no SELECT
)
All users are granted the "BROWSE" privilege by default on new catalogs that are created using the Catalog Explorer. So try removing the BROWSE privilege and then work with the "USE Catalog" privilege to see if it makes a difference.
Note: The USE CATALOG
privilege on the parent catalog is not required to read an object’s metadata if the user has the BROWSE
privilege on that catalog.
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.