Allow multiple catalogs per Organisation
I work for an organisation that has multiple, distinct areas. My area would like to set up a catalog separate to the rest of the organisation, but still able to integrate with our Azure tenancy. Right now we can't due to the limit of one catalog per organisation.
Our use case is perspectives, or a catered sub catalog for specific user roles
Enabling developers to practice in a non-prod environment would increase adoption.
Each developer has to create their own Azure *tenant* to do any playing around with it?
We'd like to use one for a data dictionary and the other for an Information asset register. We considered combining but think that would make the combined dictionary and the register both overly bloated.
Why not use tags to control who needs to access what data within the Catalog?
Greg Ramey commented
In an organization that regularly performs acquisition and divestiture activities this would be essential for adoption.