You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/deployment-best-practices.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,21 @@
1
1
---
2
2
title: 'Deployment best practices for Microsoft Purview (formerly Azure Purview)'
3
-
description: This article provides best practices for deploying Microsoft Purview (formerly Azure Purview). The Microsoft Purview Data Map and governance portal enable any user to register, discover, understand, and consume data sources.
3
+
description: This article provides best practices for deploying Microsoft Purview (formerly Azure Purview) in your data estate. The Microsoft Purview Data Map and governance portal enable any user to register, discover, understand, and consume data sources.
4
4
author: shsandeep123
5
5
ms.author: sandeepshah
6
6
ms.service: purview
7
7
ms.topic: conceptual
8
-
ms.date: 07/19/2022
8
+
ms.date: 08/04/2022
9
9
---
10
10
# Microsoft Purview (formerly Azure Purview) deployment best practices
11
11
12
-
This article identifies common considerations that can help you successfully deploy Microsoft Purview (formerly Azure Purview) into production in your data estate. The article is intended to help you strategize and phase your deployment, and is best used in tandem with our [deployment checklist](tutorial-azure-purview-checklist.md).
12
+
This article is a guide to successfully deploying Microsoft Purview (formerly Azure Purview) into production in your data estate. It's intended to help you strategize and phase your deployment from research to hardening your production environment, and is best used in tandem with our [deployment checklist](tutorial-azure-purview-checklist.md).
13
13
14
-
If you are looking for a strictly technical deployment guide, the [deployment checklist](tutorial-azure-purview-checklist.md) is for you.
14
+
If you're looking for a strictly technical deployment guide, use the [deployment checklist](tutorial-azure-purview-checklist.md).
15
15
16
-
If you are creating a plan to deploy Microsoft Purview, and want to consider best practices as you develop your deployment strategy, then this deployment best practices guide is for you! This guide outlines tasks can be completed in phases, over the course of a month or more. Even organizations who have already deployed Microsoft Purview can use this guide to ensure they're getting the most out of their investment.
16
+
If you're creating a plan to deploy Microsoft Purview and want to consider best practices as you develop your deployment strategy, then follow the article below. This guide outlines tasks can be completed in phases over the course of a month or more to develop your deployment process for Microsoft Purview. Even organizations who have already deployed Microsoft Purview can use this guide to ensure they're getting the most out of their investment.
17
17
18
-
A well-planned deployment of a data governance platform (such as Microsoft Purview), can give the following benefits:
18
+
A well-planned deployment of your data governance platform, can give the following benefits:
19
19
20
20
- Better data discovery
21
21
- Improved analytic collaboration
@@ -27,9 +27,9 @@ This guide provides insight on a full deployment lifecycle, from initial plannin
27
27
|-------|-------------|
28
28
|[Identify objectives and goals](#identify-objectives-and-goals)|Consider what your entire organization wants and needs from data governance.|
29
29
|[Gathering questions](#gathering-questions)|What questions might you and your team have as you get started, and where can you look to begin addressing them?|
30
-
|[Deployment models](#deployment-models)|Customize your deployment to your data estate.|
31
-
|[Create a process to move to production](#create-a-process-to-move-to-production)|Create a phased deployment tailored to your data estate.|
32
-
|[Platform hardening](#platform-hardening)|How you can continue to grow your deployment to maturity.|
30
+
|[Deployment models](#deployment-models)|Customize your Microsoft Purview deployment to your data estate.|
31
+
|[Create a process to move to production](#create-a-process-to-move-to-production)|Create a phased deployment strategy tailored to your organization.|
32
+
|[Platform hardening](#platform-hardening)|Continue to grow your deployment to maturity.|
33
33
34
34
Many of Microsoft Purview's applications and features have their own individual best practices pages as well. They're referenced often throughout this deployment guide, but you can find all of them in the table of contents under **Concepts** and then **Best practices and guidelines**.
35
35
@@ -63,7 +63,7 @@ The general approach is to break down those overarching objectives into various
63
63
64
64
### Identify key scenarios
65
65
66
-
Microsoft Purview governance services can be used to centrally manage data governance across an organization’s data estate spanning cloud and on-premises environments. To have a successful implementation, you must identify key scenarios that are critical to the business. These scenarios can cross business unit boundaries or impact multiple user personas either upstream or downstream.
66
+
Microsoft Purview governance services can be used to centrally manage data governance across an organization’s data estate spanning cloud and on-premises environments. To have a successful implementation, you must identify key scenarios that are critical to the business. These scenarios can cross business unit boundaries or affect multiple user personas either upstream or downstream.
67
67
68
68
These scenarios can be written up in various ways, but you should include at least these five dimensions:
69
69
@@ -79,7 +79,7 @@ The scenarios must be specific, actionable, and executable with measurable resul
79
79
|---------|---------|---------|
80
80
|Catalog business-critical assets|I need to have information about each data sets to have a good understanding of what it is. This scenario includes both business and technical metadata data about the data set in the catalog. The data sources include Azure Data Lake Storage Gen2, Azure Synapse DW, and/or Power BI. This scenario also includes on-premises resources such as SQL Server.|Business Analyst, Data Scientist, Data Engineer|
81
81
|Discover business-critical assets|I need to have a search engine that can search through all metadata in the catalog. I should be able to search using technical term, business term with either simple or complex search using wildcard.|Business Analyst, Data Scientist, Data Engineer, Data Admin|
82
-
|Track data to understand its origin and troubleshoot data issues|I need to have data lineage to track data in reports, predictions, or models back to its original source and understand the changes and where the data has resided through the data life cycle. This scenario needs to support prioritized data pipelines Azure Data Factory and Databricks.|Data Engineer, Data Scientist|
82
+
|Track data to understand its origin and troubleshoot data issues|I need to have data lineage to track data in reports, predictions, or models back to its original source. I also need to understand the changes made to the data, and where the data has resided throughout the data life cycle. This scenario needs to support prioritized data pipelines Azure Data Factory and Databricks.|Data Engineer, Data Scientist|
83
83
|Enrich metadata on critical data assets|I need to enrich the data set in the catalog with technical metadata that is generated automatically. Classification and labeling are some examples.|Data Engineer, Domain/Business Owner|
84
84
|Govern data assets with friendly user experience|I need to have a Business glossary for business-specific metadata. The business users can use Microsoft Purview for self-service scenarios to annotate their data and enable the data to be discovered easily via search.|Domain/Business Owner, Business Analyst, Data Scientist, Data Engineer|
85
85
@@ -98,13 +98,14 @@ For other integration scenarios such as ticketing, custom user interface, and or
98
98
99
99
Once your organization agrees on the high-level objectives and goals, there will be many questions from multiple groups. It’s crucial to gather these questions in order to craft a plan to address all of the concerns. Make sure to [include relevant groups](#include-the-right-stakeholders) as you gather these questions. You can use our documentation to start answering them.
100
100
101
-
Some example questions that you may run into during the initial phase. For questions about Microsoft Purview, the questions below link to relevant documentation:
101
+
Some example questions that you may run into during the initial phase:
102
102
103
-
1. What are the main organization data sources and data systems?
103
+
1. What are the main data sources and data systems in our organization?
104
+
1.[What data sources are supported?](microsoft-purview-connector-overview.md)
105
+
1. For data sources that aren't supported yet by Microsoft Purview, what are my options?
104
106
1.[How should we budget for Microsoft Purview?](concept-guidelines-pricing.md)
105
-
1.[What data sources are supported?](microsoft-purview-connector-overview.md) For data sources that aren't supported yet by Microsoft Purview, what are my options?
106
107
1.[How many Microsoft Purview instances do we need?](concept-best-practices-accounts.md)
107
-
1. Who are the users?
108
+
1.[Who will use Microsoft Purview, and what roles will they have?](catalog-permissions.md)
108
109
1.[Who can scan new data sources?](catalog-permissions.md)
109
110
1.[Who can modify content inside of Microsoft Purview?](catalog-permissions.md)
110
111
1. What processes can I use to improve the data quality in Microsoft Purview?
@@ -156,7 +157,7 @@ For more information, see our [accounts architecture best practices guide](conce
156
157
157
158
Some organizations may decide to keep things simple by working with a single production version of Microsoft Purview. They probably don’t need to go beyond discovery, search, and browse scenarios. However, most organizations that want to deploy Microsoft Purview across various business units will want to have some form of process and control.
158
159
159
-
Below we have provided a potential four phase deployment plan that includes tasks, helpful links, and acceptance criteria for each phase:
160
+
Below we've provided a potential four phase deployment plan that includes tasks, helpful links, and acceptance criteria for each phase:
0 commit comments