Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The modern governance experience is available in the Microsoft Purview portal for anyone who didn't create a Microsoft Purview account in the Azure portal before, and for existing customers. This article explains how to use this new experience.
The new governance experience
The Microsoft Purview portal, https://purview.microsoft.com, is a single, organization-wide instance of Microsoft Purview that's the next step towards unifying your organization's governance, policy, compliance, risk, and security. It's a prerequisite to a single platform used to manage and govern any data, both structured and unstructured, across your data estate. Including Azure, Microsoft 365, Azure, on-premises, or multicloud and SaaS applications in future.
- If you're a new Microsoft Purview customer, read about the new governance experience for new customers.
- If you're an existing Microsoft Purview customer, read about the new governance experience for existing customers.
Learn more about all the governance, data security, and risk and compliance features available in the Microsoft Purview portal.
How to use the new experience
If you're a new Microsoft Purview governance customer (if your organization doesn't have any Microsoft Purview accounts in any Azure subscriptions under your Microsoft Entra tenant), you can start using the Microsoft Purview portal right now for your governance journey.
If your organization already has Microsoft Purview accounts in Azure, after your organization is enabled, getting started with the new experience depends on your organization's current structure:
- You only have one Microsoft Purview account:
- You have multiple Microsoft Purview accounts
For more information, visit the new experience FAQ.
One Microsoft Purview account
Your account has disabled all public network access
If your Microsoft Purview account had disabled all public network access and is using private endpoints, you need to make some changes before you upgrade it. You can continue to use ingestion private endpoints, but not account or portal private endpoints. The new experience uses a new private endpoint called a platform private endpoint.
To check your current public network settings:
- Go to the Azure portal.
- Search for your Microsoft Purview account.
- Select Networking under the Settings menu.
- If your firewall is set to Disabled from all networks, you need to follow the next steps to upgrade. If your firewall is set to Enabled from all networks or Disabled for ingestion only, you should be able to upgrade without these steps.
To upgrade an account using private endpoints, you need to:
- Confirm that your firewall allows these global and tenant-specific endpoints (replacing the
accountnameandtenantidwith your values):api.purview-service.microsoft.comaccountname.purview.azure.comtenantid-api.purview-service.microsoft.com
- After upgrading to the new experience, you can follow this guide to set up private endpoints for governance solutions in the Microsoft Purview portal.
Important
- Currently, Azure Data Factory, Azure Machine Learning, and Azure Synapse lineage connections are not supported with the platform private endpoint, and might not work after switching. If your production replies on these lineage connections, wait until these connections are supported. (Azure Synapse is supported as a data source using a managed Virtual Network Integration Runtime and platform private endpoint.)
- Scans that run after upgrading but before you set up the platform private endpoints might fail and need to be re-run after private endpoint set up.
Your region matches your tenant region
If your Microsoft Purview account's region matches your Microsoft Entra tenant region, and you set your networking settings to either enabled from all networks or disabled for ingestion only, you can use the new experience; no upgrade is required.
Your region doesn't map to your tenant region
A Microsoft Purview Admin selects the Upgrade button in the Azure portal, Microsoft Purview portal, or upgrade email.
Note
If you don't have access to the Microsoft 365 role groups to assign users to the Microsoft Purview Admin role, contact support.
If your account is in a different region than your tenant, an admin confirms setup, as seen in this image:
After confirmation, the new portal launches.
Multiple Microsoft Purview accounts
The new experience requires a single, tenant-level or organization-wide account as the primary account for your organization. If you have multiple Purview accounts in your tenant, you can upgrade one account to the new experience and merge up to four other accounts into your primary account as domains.
If your Microsoft Purview account disables public network access and uses account or portal private endpoints, follow the steps at Disabled all public network access to upgrade.
A Microsoft Purview Admin selects the Upgrade button in the Azure portal, Microsoft Purview portal, or upgrade email.
Select an existing account to upgrade it as your organization-wide account. See How to choosing a primary account.
Note
Upgrading one account doesn't affect your other Microsoft Purview accounts or their data. After upgrading, you can merge your secondary accounts into your primary account as domains.
If you don't have access to the Microsoft 365 role groups to assign users to the Microsoft Purview Admin role, contact support.
If the account you select is in a different region than your tenant, an admin needs to confirm setup.
After confirmation, the new portal launches.
You can take the tour and begin exploring the new Purview experience.
Merge your secondary accounts into your primary account as domains.
Disabled all public network access
If your Microsoft Purview account had disabled all public network access and is using private endpoints, you need to make some changes before you upgrade it. You can continue to use ingestion private endpoints, but not account or portal private endpoints. The new experience uses a new private endpoint called a platform private endpoint.
To check your current public network settings:
- Go to the Azure portal.
- Search for your Microsoft Purview account.
- Select Networking under the Settings menu.
- If your firewall is set to Disabled from all networks, you need to follow the next steps to upgrade. If your firewall is set to Enabled from all networks or Disabled for ingestion only, you should be able to upgrade without these steps.
To upgrade an account using private endpoints, you need to:
- Confirm that your firewall allows these global and tenant-specific endpoints (replacing the
accountnameandtenantidwith your values):api.purview-service.microsoft.comaccountname.purview.azure.comtenantid-api.purview-service.microsoft.com
- After upgrading to the new experience, you can follow this guide to set up private endpoints for governance solutions in the Microsoft Purview portal.
Important
- Currently, Azure Data Factory, Azure Machine Learning, and Azure Synapse lineage connections are not supported with the platform private endpoint, and might not work after switching. If your production replies on these lineage connections, wait until these connections are supported. (Azure Synapse is supported as a data source using a managed Virtual Network Integration Runtime and platform private endpoint.)
- Scans that run after upgrading but before you set up the platform private endpoints might fail and need to be re-run after private endpoint set up.
Why upgrade to the new experience
If you're already using the classic Microsoft Purview governance portal, upgrading your Microsoft Purview account to the new experience offers several benefits, including:
Prerequisites for unified experience: The upgrade is a prerequisite and one step to bring your environment closer to use data governance, security, risk, and compliance capabilities under the same platform.
Improved user experience: The new experience provides a more streamlined and intuitive user interface, making it easier for users to access and manage their data assets in the new Microsoft Purview portal.
Enhanced features: Upgrading unlocks new features and capabilities, such as live view, preset scans, and more.
Consolidated management: The enhanced experience offers a centralized management interface for all your Microsoft Purview resources, simplifying administration tasks.
Access to new capabilities: All new Microsoft Purview features are only available in the upgraded tenant level account.
After upgrading an existing account to the new experience, here's what to expect:
Account consolidation: You access all other Microsoft Purview accounts in your tenant through the classic portal. Be prepared to merge those accounts with the primary account when the feature becomes available. Microsoft notifies customers who need to perform other steps to merge these accounts.
Roles and permissions: Fine grained access control via roles and permissions at collection scopes continues to function as-is after your accounts are upgraded. In addition, there are new tenant-level roles that you can manage in the new portal. For more information, see our tenant-level permissions documentation.
Adapting to new features: Educate users within your organization on the new features and capabilities introduced in the upgraded account, enabling them to maximize the benefits of these enhancements. This education includes understanding and using the following features:
Accessing support
With the free version of Microsoft Purview governance solutions, you can't open support tickets for Microsoft Purview. You need to upgrade to enterprise access for support.
How to choose a primary account
If you have a single Microsoft Purview account, your account is likely automatically upgraded. When you have multiple Microsoft Purview accounts under the same Microsoft Entra tenant, consider the following factors while selecting an account for the upgrade. Select an account as primary tenant-level account by following guidelines below:
Data assets: Choose the account with the most valuable or frequently used data assets, as this account becomes the primary data map after the upgrade.
Account usage: Evaluate how each account is currently used and its role within your organization. Select accounts that are considered production for this purpose.
Permissions and access controls: Consider the existing permissions and access controls for each account, as they're carried over to the upgraded environment (as an isolated domain).
System Assigned Managed Identity (SAMI) and User Assigned Managed Identity (UAMI): The existing system and user assigned managed identities for the primary upgraded account can be used across all domains in the Microsoft Purview instance.
Other considerations
You can access the upgraded account through current endpoints and new endpoints, so there's no immediate effect if you use Microsoft Purview APIs. Any updates you perform in the upgraded account also reflect in the classic portal for the same Microsoft Purview account.
New Microsoft Purview features are only available for the upgraded account.
For other accounts in your tenant, you can continue to access through the classic governance portal.
Regions
Note
The regions listed here are for the single, organization-wide instance of Microsoft Purview that uses the Microsoft Purview portal.
Regions available for Microsoft Purview Unified Catalog are different. Visit Supported regions for Unified Catalog.
This table lists the regions that you can use to access Microsoft Purview in the new portal:
| Purview Account Location | Mapped Microsoft Entra Country/Region | Tenant Location Code |
|---|---|---|
| Australia East | Australia | AU |
| Fiji | FJ | |
| New Zealand | NZ | |
| Brazil South | Argentina | AR |
| Bolivia (Plurinational State of) | BO | |
| Bonaire Sint Eustatius and Saba | BQ | |
| Brazil | BR | |
| Chile | CL | |
| Colombia | CO | |
| Curaçao | CW | |
| Ecuador | EC | |
| Falkland Islands (the) | FK | |
| French Guiana | GF | |
| Guyana | GY | |
| Peru | PE | |
| Paraguay | PY | |
| Suri | SR | |
| Sint Maarten (Dutch part) | SX | |
| Uruguay | UY | |
| Venezuela (Bolivarian Republic of) | VE | |
| Canada Central | Canada | CA |
| Central India | India | IN |
| Sri Lanka | LK | |
| Nepal | NP | |
| Central US | United States of America (the) | US |
| East US | Antigua and Barbuda | AG |
| Anguilla | AI | |
| Aruba | AW | |
| Barbados | BB | |
| Bermuda | BM | |
| Bahamas (the) | BS | |
| Cuba | CU | |
| Dominica | DM | |
| Dominican Republic (the) | DO | |
| Grenada | GD | |
| Guadeloupe | GP | |
| Haiti | HT | |
| Jamaica | JM | |
| Saint Kitts and Nevis | KN | |
| Cayman Islands (the) | KY | |
| Saint Lucia | LC | |
| Martinique | MQ | |
| Panama | PA | |
| Puerto Rico | PR | |
| Trinidad and Tobago | TT | |
| Saint Vincent and the Grenadines | VC | |
| Virgin Islands (British) | VG | |
| Virgin Islands (U.S.) | VI | |
| United States of America (the) | US | |
| East US 2 | United States of America (the) | US |
| France Central | France | FR |
| Germany West Central | Germany | DE |
| Japan East | Japan | JP |
| Korea Central | Korea (the Republic of) | KR |
| North Europe | Finland | FI |
| Faroe Islands (the) | FO | |
| Ireland | IE | |
| Iceland | IS | |
| Moldova (the Republic of) | MD | |
| Sweden | SE | |
| Qatar Central | Qatar | QA |
| South Africa North | Angola | AO |
| Burkina Faso | BF | |
| Burundi | BI | |
| Benin | BJ | |
| Botswana | BW | |
| Congo (the Democratic Republic of the) | CD | |
| Central African Republic (the) | CF | |
| Congo (the) | CG | |
| Côte d'Ivoire | CI | |
| Cameroon | CM | |
| Cabo Verde | CV | |
| Djibouti | DJ | |
| Algeria | DZ | |
| Egypt | EG | |
| Eritrea | ER | |
| Ethiopia | ET | |
| Gabon | GA | |
| Ghana | GH | |
| Gambia (the) | GM | |
| Guinea | GN | |
| Equatorial Guinea | GQ | |
| Guinea-Bissau | GW | |
| Kenya | KE | |
| Comoros (the) | KM | |
| Liberia | LR | |
| Lesotho | LS | |
| Libya | LY | |
| Morocco | MA | |
| Madagascar | MG | |
| Mali | ML | |
| Mauritania | MR | |
| Mauritius | MU | |
| Malawi | MW | |
| Mozambique | MZ | |
| Namibia | NA | |
| Niger (the) | NE | |
| Nigeria | NG | |
| Réunion | RE | |
| Rwanda | RW | |
| Seychelles | SC | |
| Sudan (the) | SD | |
| Saint Helena Ascension and Tristan da Cunha | SH | |
| Sierra Leone | SL | |
| Senegal | SN | |
| Somalia | SO | |
| South Sudan | SS | |
| São Tomé and Príncipe | ST | |
| Eswatini | SZ | |
| Chad | TD | |
| Togo | TG | |
| Tunisia | TN | |
| Tanzania United Republic of | TZ | |
| Uganda | UG | |
| Mayotte | YT | |
| South Africa | ZA | |
| Zambia | ZM | |
| Zimbabwe | ZW | |
| Southeast Asia | Armenia | AM |
| American Samoa | AS | |
| Brunei Darussalam | BN | |
| Cocos (Keeling) Islands (the) | CC | |
| Cook Islands (the) | CK | |
| China | CN | |
| Christmas Island | CX | |
| Micronesia (Federated States of) | FM | |
| Guam | GU | |
| Hong Kong SAR | HK | |
| Indonesia | ID | |
| Cambodia | KH | |
| Kiribati | KI | |
| Lao People's Democratic Republic (the) | LA | |
| Marshall Islands (the) | MH | |
| Myanmar | MM | |
| Macao SAR | MO | |
| Northern Mariana Islands (the) | MP | |
| Malaysia | MY | |
| New Caledonia | NC | |
| Norfolk Island | NF | |
| Nauru | NR | |
| Niue | NU | |
| French Polynesia | PF | |
| Papua New Guinea | PG | |
| Philippines (the) | PH | |
| Pitcairn | PN | |
| Palau | PW | |
| Solomon Islands | SB | |
| Singapore | SG | |
| Thailand | TH | |
| Tokelau | TK | |
| Tonga | TO | |
| Tuvalu | TV | |
| Taiwan (Province of China) | TW | |
| United States Minor Outlying Islands (the) | UM | |
| Viet Nam | VN | |
| Vanuatu | VU | |
| Wallis and Futuna | WF | |
| Samoa | WS | |
| South Central US | United States of America (the) | US |
| Switzerland North | Switzerland | CH |
| UAE North | United Arab Emirates (the) | AE |
| UK South | United Kingdom of Great Britain and Northern Ireland (the) | GB |
| West Central US | United States of America (the) | US |
| West Europe | Andorra | AD |
| Albania | AL | |
| Austria | AT | |
| Åland Islands | AX | |
| Azerbaijan | AZ | |
| Bosnia and Herzegovina | BA | |
| Belgium | BE | |
| Bulgaria | BG | |
| Bahrain | BH | |
| Belarus | BY | |
| Cyprus | CY | |
| Czechia | CZ | |
| Denmark | DK | |
| Estonia | EE | |
| Spain | ES | |
| Georgia | GE | |
| Guernsey | GG | |
| Gibraltar | GI | |
| Greece | GR | |
| Croatia | HR | |
| Hungary | HU | |
| Israel | IL | |
| Isle of Man | IM | |
| Italy | IT | |
| Jersey | JE | |
| Jordan | JO | |
| Kuwait | KW | |
| Kazakhstan | KZ | |
| Lebanon | LB | |
| Liechtenstein | LI | |
| Lithuania | LT | |
| Luxembourg | LU | |
| Latvia | LV | |
| Monaco | MC | |
| Montenegro | ME | |
| Republic of North Macedonia | MK | |
| Malta | MT | |
| Netherlands (the) | NL | |
| Norway | NO | |
| Oman | OM | |
| Pakistan | PK | |
| Poland | PL | |
| Portugal | PT | |
| Romania | RO | |
| Serbia | RS | |
| Russian Federation (the) | RU | |
| Saudi Arabia | SA | |
| Slovenia | SI | |
| Svalbard and Jan Mayen | SJ | |
| Slovakia | SK | |
| San Marino | SM | |
| Türkiye | TR | |
| Ukraine | UA | |
| Holy See (the) | VA | |
| Yemen | YE | |
| West US | United States of America (the) | US |
| West US 2 | United States of America (the) | US |
| West US 3 | Costa Rica | CR |
| Guatemala | GT | |
| Honduras | HN | |
| Mexico | MX | |
| Nicaragua | NI | |
| El Salvador | SV | |
| New Mexico | NM | |
| United States of America (the) | US |
For information about all available Microsoft Purview regions, see Azure products by regions.
Important
Microsoft 365 GCC regions aren't currently supported.