How to run and read Microsoft's Zero Trust Assessment
In short
Microsoft's Zero Trust Assessment is a free, open-source PowerShell module that tests your tenant's security configuration against Zero Trust and Secure Future Initiative guidance. Install ZeroTrustAssessment, run Connect-ZtAssessment and Invoke-ZtAssessment, and you get a local HTML report showing each test's risk, status and fix. Start with failed high-risk identity tests.
Microsoft publishes detailed guidance on how to configure Microsoft Entra ID, Microsoft Intune, Azure networks and Microsoft Purview securely. Checking a tenant against all of it by hand is slow and error-prone. The Zero Trust Assessment does the checking for you.
What is Microsoft's Zero Trust Assessment?
Zero Trust is a security approach built on three principles: verify explicitly, use least privilege access, and assume breach (Microsoft's Zero Trust overview). The Zero Trust Assessment is a free PowerShell module from Microsoft, named ZeroTrustAssessment. It reads your tenant's configuration and tests it against hundreds of security settings aligned with the Zero Trust pillars and Microsoft's Secure Future Initiative (SFI). It produces an HTML report with a result and remediation guidance for each test.
According to Microsoft's overview, the tests draw on NIST, CISA and CIS standards, Microsoft's internal security baselines and customer deployments. The code is open source, so your team can read what each test does before you run it.
Microsoft describes it as read-only, and it stores everything it collects on the machine that runs it. By default it also sends your tenant ID to Microsoft as telemetry, which -DisableTelemetry on Invoke-ZtAssessment turns off.
What does the Zero Trust Assessment check?
It tests your tenant's configuration across seven pillars: identity, devices, network, infrastructure, data, security operations (SecOps) and AI. As of September 2026 (version 2.6.0), the report opens on an Overview tab, then shows a tab for each pillar that returns results.
| Pillar | What it looks at | Where the checks are documented |
|---|---|---|
| Identity | App credentials and consent, privileged roles, MFA and phishing-resistant methods, guest access, legacy authentication, risky sign-ins | Configure Microsoft Entra for increased security |
| Devices | Intune compliance policies, enrollment, disk encryption, local admin passwords, antivirus and update policies | Configure Microsoft Intune for increased security |
| Network | Named locations, tenant restrictions, Microsoft Entra Internet Access and Private Access, Azure Firewall, web application firewall and DDoS Protection | Protect networks in the Entra guidance, and Azure network security recommendations |
| Infrastructure | Microsoft Defender for Cloud recommendations, only for Azure subscriptions you tag ZeroTrustAssessment:Infrastructure |
Microsoft Defender for Cloud |
| Data | Sensitivity labels, auto-labeling, data loss prevention, audit logging and retention | Configure Microsoft Purview for increased security |
| SecOps | Microsoft Defender XDR incidents and alerts, Microsoft Sentinel rules, Defender for Identity sensors and email protection policies | Microsoft Learn pages linked from each test |
| AI | Agent identity owners and sponsors, Conditional Access for agents, and Sentinel connectors for Microsoft 365 Copilot and AI services | AI in the Entra guidance (agent identity checks) |
Microsoft says it adds controls over time, so check these pages for the current list. The Entra and Intune pages list the minimum license for each check, and the Purview page points to the Microsoft Purview service description.
Check licenses before you plan work: a check that needs Microsoft Entra ID P2, such as making privileged role assignments just in time with Privileged Identity Management (PIM), is a purchasing decision, not a quick fix.
How do you run the Zero Trust Assessment?
You install the module in PowerShell 7, connect with Connect-ZtAssessment, and start the run with Invoke-ZtAssessment.
Before you start
- PowerShell 7. Microsoft notes that Windows on ARM64 isn't supported yet, and that a new Windows install may need the Microsoft Visual C++ Redistributable (x64).
- A Global Administrator for the first run, to consent to read-only permissions.
- For later runs, an account with Global Reader, Security Reader, Exchange Administrator and SharePoint Administrator, per Microsoft's prerequisites. The last two aren't read-only, so if you use PIM, activate them for the run and check the activation lasts long enough: the maximum is 24 hours, and a large tenant can take longer.
- A trusted, managed workstation, because the report lands on its disk.
Steps to run Invoke-ZtAssessment
- Open a new PowerShell 7 window. If you've run an older version, remove it with
Uninstall-Module ZeroTrustAssessment -Force -AllVersionsand restart PowerShell. - Install the module with
Install-Module ZeroTrustAssessment -Scope CurrentUser. - Run
Connect-ZtAssessment. On Windows, you'll get a sign-in prompt for each service it reads: Microsoft Graph, Azure, Exchange Online, Security & Compliance, SharePoint and Azure Information Protection. On the first run, sign in as a Global Administrator and accept the Microsoft Graph permissions. - Run
Invoke-ZtAssessmentwith-Pathpointing to a dated folder, so each run stays separate. - Leave it running. Microsoft warns that large tenants can take more than 24 hours, and says not to stop the run even if it logs warnings or errors. Progress logs sit in the
zt-export/logsfolder inside the assessment folder.
Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-ZtAssessment
Invoke-ZtAssessment -Path C:\ZTA\2026-09-22
When it finishes, ZeroTrustAssessmentReport.html opens in your default browser.
What the consent grants
The Graph permissions are all read permissions, such as Directory.Read.All, Policy.Read.All and AuditLog.Read.All. They're granted to the Microsoft Graph PowerShell app, listed in your tenant as Microsoft Graph Command Line Tools, and they stay after the run. Record the grant in your change log, and review it under Entra ID > Enterprise apps in the Microsoft Entra admin center.
The Azure sign-in feeds every test that reads Azure, including Entra log export, Azure Firewall, web application firewall, DDoS Protection, Defender for Cloud and Microsoft Sentinel checks. If you don't use Azure, close that window, and the report marks those tests as skipped.
How should you handle the report?
Treat the report as sensitive: keep it in a restricted location with named access, not in email or a Teams chat, and delete the local export folder once you've saved it. Microsoft warns that the report and export folder contain tenant information attackers could use, so share them only with authorized people.
How do you read and prioritize the results?
Start with failed tests rated High risk in the Identity tab, because identity controls protect everything else. Then work through high-risk device and data items, and only then the medium and low ones.
Each test shows a Risk level and a Status. Select a test to see what was tested and how to fix it. Microsoft's glossary defines High risk as potential for environment-wide exposure, Medium as moderate exposure, and Low as defense in depth or an operational improvement.
The guidance also rates User Impact (whether nonprivileged users must act or be told about a change) and Implementation Cost (a targeted action, a project or an ongoing program). Use all three to order the work:
- High risk, low user impact, low cost. Admin-only changes users won't notice. Do these first.
- High risk, higher user impact. For example, requiring phishing-resistant sign-in methods. Plan communications and pilot first.
- High risk, needs a license. Raise the license case with the finding attached.
- Medium risk. Backlog each item with an owner and a target date.
- Low risk. Schedule it as hardening work.
If a recommendation doesn't fit your environment, record the decision and the reason.
Many identity failures trace back to sprawl: guests and accounts nobody uses, admins who no longer sign in, and app registrations nobody owns. The identity sprawl field guide walks through finding and removing them, and our Microsoft 365 permissions audit covers admin roles, app consent and nested groups. Sprawlsight's free snapshot checks some of the same basics, such as ENTRA-002 ("MFA is required for all users on all cloud apps") and ENTRA-030 ("Users can't consent to applications on their own").
How does the Zero Trust Workshop relate to the assessment?
The Zero Trust Workshop is for planning, and the assessment is for testing. The Microsoft Zero Trust Workshop pairs written guidance with a workshop tool. It helps you record progress and build a roadmap across Identity, Devices, Data, Networking, Infrastructure, Security Operations and AI.
Microsoft calls the assessment the Workshop's technical backbone, so roadmaps rest on real tenant data. For a small team: run the assessment, fix the clear high-risk items, then use the Workshop to plan bigger projects.
How is it different from Secure Score and security baselines?
The Zero Trust Assessment is a deep, on-demand test against Microsoft's Zero Trust guidance. Microsoft Secure Score is a continuously updated score in the Microsoft Defender portal. CISA's Secure Cloud Business Applications (SCuBA) baselines and the Center for Internet Security's CIS Microsoft 365 Foundations Benchmark are external standards you measure against when you need evidence for auditors or customers.
| Zero Trust Assessment | Microsoft Secure Score | CISA SCuBA (ScubaGear) | CIS Microsoft 365 Foundations Benchmark | |
|---|---|---|---|---|
| What it measures | Configuration against Zero Trust and SFI guidance across identity, devices, network, infrastructure, data, security operations and AI | Recommended security actions completed, scored in points | Conformance with CISA's secure configuration baselines | Conformance with consensus configuration recommendations |
| How it runs | PowerShell 7 module on your machine | Built into the Microsoft Defender portal | ScubaGear PowerShell tool | A published benchmark you check by hand or with tooling |
| Output | Local HTML report with risk, status and remediation per test | Score, recommended actions, history and comparison with similar organizations | HTML, JSON and CSV reports | Recommendations with audit and remediation steps |
The tools overlap but won't agree line for line, because each has its own scope and scoring. Microsoft also notes that Secure Score shows how far you use the available controls, not how likely a breach is. A sensible split: watch Secure Score week to week, run the Zero Trust Assessment for depth, and use SCuBA or CIS when someone asks which standard you meet.
Our guide to Microsoft 365 security baselines compares the public baselines in more detail. Copilot policy gaps covers the Conditional Access, data loss prevention and labeling gaps that matter most once Microsoft 365 Copilot is in use.
How do you make the assessment routine?
Re-run it quarterly and after major changes, such as a new Conditional Access policy. Keep each run in a dated folder, and track high-risk failures until they're fixed.
- Track high-risk failures in a simple list: test, owner, date fixed, date confirmed.
- Update before each run. Remove old versions and install the latest.
- Clean up. Delete the export folder, and remove the module if you won't run it again soon.
If you'd rather not run it by hand, Sprawlsight's full assessment also runs Microsoft's Zero Trust Assessment, alongside the CISA SCuBA and Maester benchmark suites. It adds weekly scans with a record of what changed between them, and maps results to Zero Trust, the Microsoft cloud security benchmark (MCSB) and the NIST Cybersecurity Framework (CSF) 2.0.
Frequently asked questions
Is Microsoft's Zero Trust Assessment free?
Yes. It's a free, open-source PowerShell module from Microsoft, installed from the PowerShell Gallery. The module costs nothing, but many of its tests check features that need licenses, such as Microsoft Entra ID P1 or P2 and Microsoft Intune Plan 1. Microsoft's Entra and Intune guidance lists the minimum license for each check, and the Purview guidance points to the Microsoft Purview service description.
Does the Zero Trust Assessment change anything in my tenant?
No. Microsoft describes it as read-only, and it stores everything it collects on the machine that runs it. By default it does send your tenant ID to Microsoft as telemetry, which the -DisableTelemetry switch turns off. The first run needs a Global Administrator to consent to read-only Microsoft Graph permissions, and that consent stays in place until you remove it.
How long does the Zero Trust Assessment take to run?
It depends on the size of the tenant. Microsoft notes that large tenants can take more than 24 hours. Don't stop the run even if it logs warnings or errors, and check the logs folder inside the assessment folder to follow progress.
What roles does Invoke-ZtAssessment need after the first run?
After a Global Administrator consents on the first run, Microsoft's prerequisites list Global Reader, Security Reader, Exchange Administrator and SharePoint Administrator for later runs. Exchange Administrator and SharePoint Administrator aren't read-only roles, so activate them just in time if you use Privileged Identity Management.
Is the Zero Trust Assessment the same as Microsoft Secure Score?
No. Secure Score is a continuously updated score in the Microsoft Defender portal, based on recommended actions you've completed. The Zero Trust Assessment is a deeper, on-demand test you run locally, and it returns risk-rated results with remediation steps for each test. Most teams use both.