Go Up to Administrator Guide
Note: In order to view this page, your user account must have the proper license and
permissions .
Microsoft Purview is a popular Data Governance tool that allows users to manage a business glossary and catalog of data assets. ER/Studio Team Server includes integration with Purview that allows you to:
- Create a new Purview integration feature
- Set up the connection to Purview
- Configure Property Mappings
- Manage Purview Glossary synchronization
- Manage publishing Logical and Physical Data Models
Synchronizing Business Terms keeps selected business glossaries in Purview and Team Server in harmony. Purview business terms are then available for Data Architect users to map to data models. Various settings allow you to choose which tool is the master and where you can create terms.
You can automatically or manually publish logical and physical data models from Team Server with mappings to business terms to Purview.
The Purview Integration page allows you to manage the following areas:
- Connection. Allows you to set up the connection with Microsoft Purview.
- Property Mappings. Allows you to configure property mappings for the integration.
- Glossary. Allows you to manage the Business Glossary synchronization.
- Logical Data Models. Allows you to manage and publish Logical data models from Team Server to Purview.
- Physical Data Models. Allows you to manage and publish Physical data models from Team Server to Purview.
Pre-Requisites
Before using Microsoft Purview with ER/Studio Team Server, you must register the application with Microsoft Entra ID and then create a service principal. For more information about these tasks, see Registering the Application to Use Purview with Team Server.
Getting Started
My Settings > Purview
Before synchronizing Business Terms and publishing Models, please consider the following steps:
| Step |
Action
|
| REVIEW |
|
| SET UP |
- User accounts that you want to have access to the Purview integration.
- The following global permissions need to be set for the Purview account:
- Catalog Author
- Data Steward Author
- and for each community and/or domain the user needs the following permissions:
- Data Steward
- Technical Steward
- Recommendation - with that user, try logging in to Purview and performing the basic operations of create, read, update and delete on objects in the domains in the scope of the integration.
- Team Server User and Group permissions through user and group permissions
- Ensure Communication with Purview by making sure your Team Server server has an uninhibited link to the Purview server. You may want to work with your network team to manage the firewall to allow https traffic between the servers. We find most problems are caused by issues in communication. A simple test is to open a browser session on your Team Server server machine and attempt to connect to your Purview instance using the username and password you have selected for the integration.
|
| MANAGE GLOSSARIES |
- Decide whether Purview or Team Server is the master for glossary changes. You may want to consider a process similar to the following steps:
- Make Team Server the master for changes to properties and relationships.
- Harvest a business glossary from a logical data model.
- Map this glossary to a blank glossary in Purview.
- Synchronize the glossaries.
- Make Purview the master, but allow new terms from Team Server.
- Specify a backlink from Purview objects to ER/Studio objects. First create a characteristic in Purview called "ER/Studio URL" of type rich text, and then make sure you add this characteristic to the object types in Purview for which you want backlinks to Team Server.
- Set the synchronization frequency to zero while you continue to set up and test.
- Consider which properties of business terms in Purview you want to map to which terms in Purview. You may need to create Custom Properties in Team Server for the appropriate data types to match those in Purview.
- Map the properties for business terms to your new properties or use the Auto Create button to create them in Team Server.
- Select which relationships in Team Server map to which relationships between business terms in Purview. You may wish to create additional relationships in Purview to receive the main relationship types in Team Server.
- Run the synchronization manually. After the first run, test the outcome of the process, and then modify settings as required.
- Once everything is working as you expect, set the synchronization frequency to the appropriate period of time.
|
| MANAGE DATA MODEL PUBLISHING |
- Map the properties for entities, attributes, tables, and columns to your new properties or use the Auto Create button to create them in Team Server.
- Create domains in the community of your choice of type Logical Data Dictionary for logical data models and Physical Data Dictionary for physical data models in Purview.
- Select the logical and physical data models published to Team Server you want to map to Purview domains. You must choose whether to manually push models to Purview through the Purview admin console in Team Server, or automatically push the models as they are published to Team Server.
|
Permissions
My Settings > Admin > Permissions
For users and groups, the Purview Administration permission must be checked under List/View in order for a user to see the Purview Integration page. In addition, the Update/Delete option also must be checked for a user to make changes to the Purview page. Users who have List/View but not Update/Delete have read-only access to the Purview Integration page.
For more information about this feature, see:
Configuration
My Settings > Purview
For more information about this feature, see Managing Purview Integration.
See Also
