There have been some exciting changes to Azure Purview announced. These changes relate to charging and permissions.
The data map is the foundation for data discovery. The data map has two components the throughput created by CRUD operations and storage of the metadata.
The data map can now grow elastically starting at one capacity unit. A capacity unit includes a throughput of 25 operations/sec and the metadata storage scales in increments of 2 GB. Purview Data Map can automatically scale up and down within limits . This new charging model makes Purview much more user friendly and less costly to set up and run.
Access Control in Azure Purview
Note: only applies for Purview accounts created on or after 18 August 18 2021,
A collection is a tool to group assets, sources, and other artifacts into a hierarchy for discoverability and to manage access control. Collections are used to organise and manage assets.
The are various roles that exist:
- Collection admins - can edit Purview collections, their details, and add sub collections. They can also add users into other Purview roles on collections where they're admins.
- Data source admins - can manage data sources and data scans.
- Data curators - can create, read, modify, and delete catalog data assets and set up relationships between assets.
- Data readers - can access but not modify the data.
There is a great video to watch from W Strasser explaining this new data plane RBAC (role based access control) catalog permission. Being able to fine tune the access to the collections brings with it great advantages. Currently collection names can't be updated or deleted.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.