Services · Microsoft Purview

Microsoft Purview implementation, verified in your tenant.

LensIQ configures Microsoft Purview for Australian regulated organisations: sensitivity labels, data loss prevention, retention and records, insider risk and audit. Each control is then read back from your tenant and compared to the obligation it exists to meet.

Purview tenant reading: DLP policy on and passing, retention policy failing
A policy moves from simulation to enforcement, then the tenant is read. Sample data.

01 · The gap

Design documents describe intent. Tenants enforce configuration.

The two drift apart, and the portal shows each of these as a status, not as a gap against your requirement:

  • A DLP policy left in simulation mode. Simulation runs the policy as if it were enforced and enforces nothing. It gathers matches for up to 15 days before anyone has to decide whether to turn it on.
  • A retention policy scoped to a named group. A static scope reads the group when the policy is created. New starters sit outside it until someone edits the policy. An adaptive scope re-runs its Entra ID query every day.
  • Auto-labelling that never left simulation. A service-side auto-labelling policy labels nothing until it has run at least one simulation and been turned on. Until then the label exists, the policy exists, and the policy has labelled nothing.
  • Audit kept for 180 days. Audit (Standard) keeps records for 180 days. When an investigation needs twelve months, records older than 180 days are already gone: a longer audit retention policy set afterwards does not reach back.

The question an auditor or regulator puts is whether the control is in place, and the answer has to come from the tenant.

The design rail stays level while the tenant rail steps away at four points: simulation never enforced, a retention policy scoped to a named group, auto-labelling with zero items, and 180-day audit. DESIGN TENANT SIMULATION · NEVER ENFORCED NAMED GROUP · NEW STARTERS OUT AUTO-LABEL · 0 ITEMS AUDIT · 180 DAYS
Four settings that look done in the portal and fall short of the requirement.

02 · Method

Scope, read, configure, verify.

  1. Before any access

    Scope and map

    We agree which Purview solutions and obligations are in scope and the access needed. Each sensitivity label, retention label and DLP policy is then mapped to the requirement it is meant to satisfy, such as a record-keeping obligation or an endpoint data-handling rule.

  2. Before any change

    Read

    Control state is read directly from your tenant: policy configuration, DLP and labelling events in Activity explorer, label and sensitive information type counts in Data explorer, and the audit log. You get the configuration report and exception register before anything changes. Design documents are not used as evidence.

  3. Simulation first

    Configure

    Changes are built in your tenant, in production, alongside your team. New DLP and auto-labelling policies run in simulation first and move to enforcement once the matches are reviewed.

  4. Handover

    Verify and hand over

    The deployed state is read again and tested against each requirement. Every remaining exception is listed individually with the source record behind it, and you keep the report, register, rationale and baseline.

03 · Evidence

What a tenant reading looks like.

A sample of the configuration report: three controls, each with its requirement, the deployed setting and a result, and the one exception opened in the register.

Sample reading · not client data

Read complete · 2026-07-05T09:14Z

  1. Sensitivity labels

    Requirement
    Confidential label on finance sites
    Deployed
    Published · all users
    Result
    PASS · 0
  2. DLP · endpoint

    Requirement
    Block USB copy of TFN data
    Deployed
    Enforce mode · all devices
    Result
    PASS · 0
  3. Retention · finance records

    Requirement
    Retain finance mailbox records under the retention schedule
    Deployed
    Scoped to pilot group only
    Result
    FAIL · 1
Sample data. The register entry records the requirement, the deployed setting and the record it was read from.

04 · Scope

Microsoft Purview implementation across the suite.

Microsoft groups Purview into data security, data compliance and data governance. LensIQ implements each group and hands back the configuration, the rationale and the evidence. Licences decide part of the scope: manual labels and retention policies come with Microsoft 365 E3, while auto-labelling, adaptive scopes, Audit (Premium) and Insider Risk Management need E5 or a Purview add-on licence, so licence fit is checked at the first step.

Information protection and data loss prevention

Sensitivity labels. A label taxonomy your staff can apply, published by policy, with labels enabled for Office files in SharePoint and OneDrive. Service-side auto-labelling policies run in simulation, are tuned against the matches, then turned on.

Classifiers. Built-in sensitive information types such as the Australia Tax File Number, custom types for your own identifiers, and Exact Data Match for client records, from a hashed table that can be refreshed daily. Custom patterns can be drafted and tested in the Purview Pattern Builder.

Data loss prevention. Policies for Exchange, SharePoint, OneDrive, Teams and endpoint devices. Each moves from simulation to Block with override, then to Block, with the simulation results kept as evidence.

See it in the Purview portal
DLP policy states in order: off, simulation, block with override, block. Block is the enforced end state. OFF SIMULATION BLOCK WITH OVERRIDE BLOCK OFF SIMULATION BLOCK WITH OVERRIDE BLOCK

Example · Microsoft Learn

Purview DLP simulation for CreditCard_1: 14,625 matches, almost all OneDrive
A sample credit card policy's simulation results: 31,200 items scanned, 14,625 matches by location, and the date the policy turns on. Microsoft keeps a simulation's data for 30 days, so the results are exported with the rule rationale before the policy moves to Block. From Learn about data loss prevention simulation mode, Microsoft Learn.

Retention, records, audit and eDiscovery

Retention and records. A file plan that maps each retention label to the obligation behind it. Labels declare records where the obligation requires it, with disposition review in up to five stages and proof of disposition kept afterwards. Policies use adaptive scopes, so a new starter is covered once the daily query picks them up.

Audit. Audit (Premium) keeps a year of Exchange, SharePoint, OneDrive and Entra ID records by default for E5-licensed users; other users keep 180 days. Audit retention policies go up to 10 years with a per-user add-on and only cover records created after they are set, so they are set before they are needed.

eDiscovery. Cases, custodians and holds configured so a legal or regulator request starts as a search, not a project.

Example · Microsoft Learn

Purview file plan descriptors: Human resources, Recruiting and hiring, Business
File plan descriptors on a retention label: reference ID, business function, category, authority type and the provision or citation behind it. Filled in for every label, they turn the label list into a file plan that can be read against the obligations. From Use file plan to manage retention labels, Microsoft Learn.
See it in the Purview portal

Insider risk and communication compliance

Insider Risk Management. Data leaks and data theft by departing users policies, with the trigger each one waits for: a high-severity DLP alert or custom triggering indicators for the first, the HR connector or the Entra ID account-deleted trigger for the second. Without a trigger, a user is scored only if an admin adds them by hand.

Communication Compliance. Policies across Exchange, Teams and Viva Engage. The financial regulatory compliance template includes a money laundering classifier; it reads English only and Microsoft describes it against US rules such as the Bank Secrecy Act, so its matches are leads for an AML/CTF reviewer, not findings.

Example · Microsoft Learn

Purview insider risk alert, high severity, risk score 87, from an HR connector
An alert from a departing users policy, waiting for review. The HR connector supplied the trigger, the user appears under a pseudonym, and the reviewer confirms the alert to a case or dismisses it, as the triage procedure sets out. From Learn about Insider Risk Management, Microsoft Learn.
See it in the Purview portal

Data governance: Data Map and Unified Catalog

Data sources registered and scanned into Data Map, then organised in Unified Catalog as governance domains with owners and data products. The catalog holds metadata; when a request for a data product is approved, the approver or a named access provider still grants access to each data asset by hand.

Example · Microsoft Learn

Purview Data Map Scope your scan panel with Department 1 selected
Scoping a Data Map scan. Department 1 is selected in full, so the folders above it are partly selected, and assets added under them later are picked up by future scans. From Scans and ingestion in Microsoft Purview Data Map, Microsoft Learn.

05 · In the Purview portal

What the settings look like.

Three more screens from Microsoft Learn, the settings behind three of the four groups above, shown whole as Microsoft publishes them. Data governance has none here: Learn's Data Map settings images still show the classic governance portal.

Information protection and data loss prevention

Purview auto-labelling policy in simulation mode, auto on after 7 days ticked
An auto-labelling policy has to run in simulation before it can label anything. The wizard can turn it on by itself once it has gone 7 days without an edit. From Automatically apply a sensitivity label to Microsoft 365 data, Microsoft Learn.

Retention, records, audit and eDiscovery

Purview Audit New audit retention policy panel for up to ten years
An audit retention policy picks users and record types, a duration and a priority. It keeps what is logged from then on; records already written keep the period they had. From Manage audit log retention policies, Microsoft Learn.

Insider risk and communication compliance

Purview insider risk policy with three health warnings to fix
Policy health in Insider Risk Management. Three warnings on one policy: the HR connector is not working, no indicators are selected, and no devices are onboarded. From Create and manage Insider Risk Management policies, Microsoft Learn.

06 · Obligations

Mapped to the Australian obligation that applies to you.

Compliance Manager has premium assessment templates for Australian regulation; an E5 licence includes up to three of them. LensIQ maps each configured control into the template that applies to you, and the assessment exports with implementation status, test date and result per control.

  • Privacy Act. Assessed against the Australia Privacy Act template. Personal information located with sensitive information types and Data explorer, labelled, and covered by DLP on email, files and devices, as technical measures toward the reasonable steps APP 11 requires.
  • APRA CPS 234. CPS 234 requires a systematic testing program for information security controls, carried out by functionally independent specialists. Each LensIQ re-read is dated evidence per control, with the source record, that feeds your testing program and the Australian Prudential Regulation Authority CPS template in Compliance Manager. Where LensIQ configured a control, whether its re-read counts as independent testing is your call.
  • AML/CTF (Tranche 2). Retention labels mapped to the record-keeping periods in your AML/CTF program, and communications reviewed with Communication Compliance. See AUSTRAC Tranche 2 obligations.
  • Essential Eight. Purview is not an Essential Eight control set. Where you report against it, Compliance Manager's Australia - ASD Essential 8 templates hold the evidence alongside your Purview assessment.

The obligation map sets APP 11, AUSTRAC record keeping, the PSPF and the Essential Eight against the Purview controls that bear on each, with every requirement cited to its source. Open the obligation map

Privacy Act maps to sensitive information types, Data explorer, labels and DLP. APRA CPS 234 maps to dated re-reads. AML/CTF maps to retention labels and communication compliance. Essential Eight maps to template evidence. All of it lands in a Compliance Manager export. PRIVACY ACT APRA CPS 234 AML/CTF · TRANCHE 2 ESSENTIAL EIGHT SITs · DATA EXPLORER LABELS · DLP RE-READ · DATED RETENTION LABELS COMMS COMPLIANCE E8 TEMPLATE EVIDENCE COMPLIANCE MANAGER EXPORT · STATUS · TEST DATE
Four obligations, one Compliance Manager export.

07 · Deliverables

What you keep.

  1. Configuration report: the deployed state of each control, timestamped at the time of reading.

  2. Exception register: each gap between requirement and deployment, with the affected scope and source record.

  3. Evidence index: a reference for every result, linked to its source record and its Compliance Manager control.

  4. Policy rationale: why each rule, scope and action was chosen, so the next administrator can change it safely.

  5. Configuration baseline: an export of every policy as deployed at handover, to compare against the next reading.

08 · Audience

Who it is for.

  • Compliance and risk leads who need evidence, not attestations.
  • Security architects confirming that a Purview rollout matches its design.
  • APRA-regulated entities testing CPS 234 controls, and Tranche 2 reporting entities building AML/CTF record keeping into Microsoft 365.

Questions about Microsoft Purview implementation.

Which Purview areas are in scope?

Information Protection, Data Loss Prevention, Data Security Posture Management, Insider Risk Management, Communication Compliance, Data Lifecycle Management, Records Management, Audit, eDiscovery, Compliance Manager, Data Map and Unified Catalog. Scope is agreed at the first step, so an engagement can cover one of these or all of them.

What access do you need in our tenant?

For the first reading, the Global Reader role in Microsoft Entra ID, which shows most policy configuration. Some areas need more: Data explorer needs a role such as Compliance data administrator plus the Data Explorer List viewer role group, Insider Risk Management, Communication Compliance and eDiscovery have their own role groups, and the Data Map uses data governance roles. Several of these give more than read access. Configuration uses the Purview role group for each solution in scope, for example Information Protection Admins, Records Management or eDiscovery Manager. Every role is added with an expiry date and removed at handover.

How long does it take?

Scope sets most of it, and the first step fixes the scope and the order of work. Some waits are Microsoft's and are built into the plan: an auto-labelling simulation can take 12 hours, a new adaptive scope up to five days to fill, and a DLP simulation gathers matches over up to 15 days, and the policy can be set to turn on by itself if it is not edited in that time.

Do you use our design documents?

Only to understand the requirement. Every result comes from the deployed tenant state.

What happens after exceptions are found?

Each exception has an owner and a fix. LensIQ can configure the fix and read again, or hand the register to your team or provider.

10 · Sources

Sources.

Every Microsoft fact on this page, and the APRA and OAIC requirements, with the page each comes from.

  1. Learn about Microsoft Purview Data security, data compliance and data governance
  2. Learn about data loss prevention simulation mode Simulation enforces nothing and runs up to 15 days
  3. Get started with the data loss prevention simulation mode A policy can turn itself on if not edited within 15 days
  4. Learn about data loss prevention DLP locations, from Exchange to endpoint devices
  5. Automatically apply a sensitivity label to Microsoft 365 data Auto-labelling needs a simulation first; simulations can take 12 hours
  6. Sensitive information type entity definitions The built-in Australia Tax File Number type
  7. Learn about exact data match based sensitive information types Exact Data Match tables, hashed and refreshable daily
  8. Learn about retention policies and retention labels Static scopes read a group once; adaptive scopes query daily
  9. Adaptive scopes Up to five days for a new scope to populate
  10. Disposition of content Disposition review in up to five stages
  11. Limits for retention policies and retention label policies Proof of disposition is kept after disposal
  12. Learn about auditing solutions in Microsoft Purview Audit (Standard) 180 days; Audit (Premium) one year for E5-licensed users
  13. Manage audit log retention policies Up to 10 years with the add-on; not retroactive
  14. Learn about eDiscovery Cases, holds and searches
  15. Insider Risk Management policy templates The trigger each template waits for
  16. Create and manage Insider Risk Management policies Policy health warnings
  17. Create and manage Communication Compliance policies The financial regulatory compliance template and its locations
  18. Trainable classifiers definitions The money laundering classifier: English, US rules
  19. Manage data product access policies Access to data assets is granted by their owners
  20. Learn about Microsoft Purview Unified Catalog Governance domains and data products
  21. Compliance Manager regulations list The Australian assessment templates by name
  22. Learn about regulations in Compliance Manager Premium templates and the three included with E5
  23. Learn about Data Security Posture Management The current DSPM and the classic versions it replaces
  24. Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview What the Global Reader role group can see
  25. Permissions in the Microsoft Purview portal Role groups per solution, with an expiry
  26. Microsoft Purview service description Which licences include auto-labelling, adaptive scopes, Audit (Premium) and Insider Risk Management
  27. Get started with data explorer The roles and role groups Data explorer needs
  28. Build and manage assessments in Microsoft Purview Compliance Manager Assessment exports with implementation status, test date and test results
  29. APRA, Prudential Standard CPS 234 Information Security A systematic testing program, by functionally independent specialists
  30. OAIC, APP guidelines chapter 11: security of personal information Reasonable steps include technical measures

Know what your tenant enforces.

Request a configuration review. LensIQ reads your Purview configuration, compares each control to its obligation, and returns the exception register.

Request configuration review