Definitions help, but every real project eventually reaches the same practical question: where do I click? Microsoft Purview is reached through a single web address, purview.microsoft.com, but it is not a single flat tool where everyone sees everything. It is better understood as a shared building with many secured departments: data governance, information protection, data loss prevention, insider risk management, communication compliance, eDiscovery, audit, and compliance assessment. Your sign-in gets you through the front door; your assigned roles decide which doors open after that.

One address, many workspaces

The Microsoft Purview portal is the main web experience for the Purview capabilities covered in this series. The address is purview.microsoft.com. From there, a person with a Microsoft 365 work account can open the parts of Purview that their organization has licensed, configured, and permitted them to use.

This matters because Purview is not just one job. It helps organizations govern data, protect sensitive information, reduce data leakage, investigate events, manage legal discovery, and track compliance work. Those jobs are related, but they are not identical. The portal brings them into one place without pretending they are the same task.

A useful mental model is a large office building. The lobby is shared, the signs use a common style, and the departments are in one place. But the records room, legal archive, security office, and compliance desk still have different owners and different access rules.

What a first-time visitor usually sees

A first visit normally begins with a home or Overview experience rather than a blank administrative console. That landing area is meant to provide orientation: recommendations, status signals, and a broad sense of what needs attention. It is especially helpful because most people do not arrive already knowing whether their next step belongs in data governance, data loss prevention, audit, or another workspace.

The left navigation groups Purview capabilities by the kind of work being done. Data governance is where teams work with the Data Map and the Unified Catalog to discover, describe, and understand data. Information protection is where sensitivity labels and classification-related controls live. Data loss prevention, often shortened to DLP, is where policies are built to reduce inappropriate sharing or movement of sensitive data.

Other areas support risk and investigation work. Insider risk management and communication compliance focus on risky behavior and communications rather than only on the data object itself. eDiscovery supports legal discovery and case work. Audit supports forensic logging and event review. Compliance Manager helps turn regulatory or control requirements into tracked assessment work.

  • Start at Overview if you are unsure where to go.
  • Use the left navigation as a job map, not as a list to memorize.
  • Expect some items to be missing if you do not have the needed role.
  • Remember that a portal can be visible even when a specific action inside it is not permitted.

The departments behind the menu

The main Purview workspaces are easier to understand when grouped by purpose. Data governance is about knowing what data exists, where it lives, what it means, and how it relates to other data. In Purview, that includes the Data Map and the Unified Catalog, which later articles will examine in detail.

Information protection is about marking and handling sensitive information. Sensitivity labels are central here because they let organizations classify content in a way people and systems can recognize. Data loss prevention uses those signals, and other conditions, to warn, block, or audit risky actions such as sharing sensitive content outside approved boundaries.

The investigation and compliance areas serve a different rhythm of work. eDiscovery is used when legal or regulatory teams need to find, preserve, review, or export content for a matter. Audit keeps records of activities that may later need to be examined. Compliance Manager helps teams organize assessments, improvement actions, and compliance posture in a more structured way.

The main Purview workspaces are grouped by the kind of work.Portal WorkspacesPurview portalData governanceInfo protectionLoss preventionInvestigation
The main Purview workspaces are grouped by the kind of work.

Why two people do not see the same portal

Purview access is controlled through roles and role groups. A role is a named set of permissions. A role group is a collection of roles assigned to people who need to perform a job. This is why a compliance administrator, an eDiscovery manager, and a communication compliance investigator can sign in to the same portal and see different options.

This is not a defect or a licensing trick. It is a security design choice. Compliance and security systems often contain sensitive information about employees, legal matters, investigations, policy violations, and business risk. Giving broad access casually can create the very governance problem the tool is meant to reduce.

The guiding principle is least privilege, which means each person receives only the access required for their work and no more. A business user may only need to view or apply sensitivity labels. A legal operations user may need access to eDiscovery cases. A compliance administrator may need broader configuration rights, but that membership should be limited and reviewed.

⚠️
Do not ask for everything. If you are learning Purview, ask for the specific role needed for the task you are practicing, not global access to the whole portal.
Roles are granted only when a job genuinely requires them.Least PrivilegeGrant access?NeededNot neededNarrow roleDeny broad
Roles are granted only when a job genuinely requires them.

The beginner path: learn one room at a time

A newcomer should resist the urge to tour every workspace on day one. Purview is broad because the business problems are broad. Trying to understand legal hold, data cataloging, sensitivity labels, audit search, and data loss prevention policies in one sitting usually produces confusion rather than fluency.

Begin with the Overview page. Then confirm which role you have been assigned and choose one workspace that matches it. If your role is related to information protection, start with sensitivity labels and classification. If your role is related to eDiscovery, start with cases, holds, and searches. If your role is related to data governance, start with the catalog and data assets.

The key is to connect each menu item to a real job. Ask: am I trying to find data, classify data, protect data, investigate activity, or measure compliance work? That question is more useful than memorizing the navigation.

  1. Open purview.microsoft.com with your Microsoft 365 work account.
  2. Start from Overview and read the recommendations before changing anything.
  3. Confirm your assigned role or role group with an administrator.
  4. Choose one workspace that matches your job.
  5. Practice read-only exploration before creating policies, cases, or labels.
Beginners learn one room; practitioners audit access first.Two Learning PathsBeginner pathPractitioner pathStart at OverviewAudit who has rolesFocus one roomFind risky accessGoal: fluencyGoal: reduce risk
Beginners learn one room; practitioners audit access first.

The practitioner path: audit access before changing policy

An experienced practitioner or consultant should start differently. Before tuning a data loss prevention rule or designing a labeling scheme, inspect who already holds powerful roles. Broad role groups such as Compliance Administrator or Organization Management deserve special attention because they can grant wide access across sensitive areas.

This first review often reveals practical risk. Former project members may still have elevated access. Administrators may have been added temporarily and never removed. A team may have given a broad role to solve a short-term problem when a narrower role would have been better. These are governance findings, not merely housekeeping tasks.

Leaders also have decisions to make here. They must decide who owns each workspace, who approves privileged access, how often role membership is reviewed, and whether operational teams can separate duties. For example, the person who creates communication compliance policies may not be the same person who investigates alerts, depending on the organization’s legal, human resources, and privacy requirements.

📌
Leadership decision. Purview design is not only a technical setup; it is also an operating model for who may govern, protect, investigate, and approve.
Practitioners inspect and remediate access before changing policy.Audit Before TuningInspect rolesFind riskRemediateTune policy
Practitioners inspect and remediate access before changing policy.

Old bookmarks and changing names

Some organizations still have documentation, screenshots, or bookmarks that point to older Microsoft compliance administration experiences. Microsoft has consolidated administration around purview.microsoft.com, and older addresses may redirect to the newer portal experience.

Do not let an old screenshot convince you that you are in the wrong product. The underlying capability may be the same even if the navigation, name, or landing page has changed. This is common in cloud services, where portals evolve while the core administrative jobs remain recognizable.

For this series, the important habit is simple: treat the Purview portal as the home base. Later topics may go deep into the Data Map, Unified Catalog, sensitivity labels, data loss prevention, audit, eDiscovery, or Compliance Manager, but they are all departments in the same building.

✅
Stable habit. When in doubt, start at purview.microsoft.com and navigate from the current portal rather than relying on an old bookmark.

Key takeaways

  • The Microsoft Purview portal lives at purview.microsoft.com and acts as the shared front door for the Purview capabilities in this series.
  • The portal is organized by work area: data governance, information protection, data loss prevention, risk and communication review, eDiscovery, audit, and compliance assessment.
  • What you see is controlled by roles and role groups, so two people can sign in to the same portal and have very different menus and permissions.
  • Least privilege is the right default because Purview can expose sensitive legal, compliance, security, and employee-risk information.
  • Beginners should start from Overview and learn one assigned workspace at a time; practitioners should begin by reviewing powerful role assignments.
  • Older compliance portal bookmarks or screenshots may not match the current experience, but purview.microsoft.com is the practical home base.

Glossary

Microsoft Purview portal
The web portal at purview.microsoft.com where Microsoft Purview governance, protection, risk, investigation, audit, and compliance capabilities are accessed.
Data governance
The discipline of understanding what data exists, where it is, what it means, who owns it, and how it should be used.
Data Map
A Microsoft Purview capability used to scan and organize information about data assets across a data estate.
Unified Catalog
A Microsoft Purview catalog experience that helps people discover, understand, and work with governed data assets.
Sensitivity label
A label applied to content to indicate its sensitivity and support protection, handling, or policy decisions.
Data loss prevention
A set of policies and controls designed to reduce inappropriate sharing, transfer, or exposure of sensitive information.
eDiscovery
The process and tooling used to find, preserve, review, and export content for legal or regulatory matters.
Role group
A named collection of permissions assigned to users so they can perform a specific administrative or investigative job.
Least privilege
The security principle of granting people only the access they need to do their work and no more.