Access Control
Block Legacy Authentication Safely
Find older password-only sign-ins in Microsoft 365, check which devices and apps still depend on them, and plan how to block them without losing access.
Content review: 2026-09-22 · Estimated effort: Medium
Priority and effort are suggestions, not risk scores or deadlines. Check business impact, vendor instructions, licenses and obligations before making changes. Test before wider rollout.
Before you start
Before starting: identify the tenant administrator, change approver, recovery route, and affected service owners. Record current settings and test protected emergency access. Never remove your only working administrator access.
Put it into practice
- In Microsoft Entra, open Monitoring & health > Sign-in logs. Review both interactive and non-interactive user sign-ins, filtering Client app for legacy authentication. Inventory older mail clients, scanners, scheduled jobs, and applications; ask owners about infrequent jobs that the available logs may miss.
- Move dependencies to vendor-supported modern authentication or a documented alternative. A protocol name alone is not proof of Basic authentication: some mail protocols support OAuth. Test sending, receiving, and scheduled workflows before retiring the old path; do not use app passwords as an MFA replacement.
- Choose the available enforcement route. Security defaults includes legacy-auth blocking at no additional cost, but is a tenant-wide package without per-user exceptions or report-only rollout. Review all its effects and prepare all users before enabling it under Entra ID > Overview > Properties > Manage security defaults. Do not disable existing protections merely to follow this guide.
- If licensed for Conditional Access, use Microsoft's linked legacy-auth blocking policy instructions. Start in Report-only, inspect the impact, then enforce for a pilot and expand. Report-only does not block anything. Follow the emergency-access guidance, document any necessary exclusions with an owner and expiry, and separately review workload identities not covered by user policies.
- Verify: confirm the intended policy is enforcing, supported clients still work, and relevant legacy attempts are denied for the expected reason. Use only an authorized test account if a live test is needed; never re-enable a retired protocol to test it. No observed legacy sign-ins alone is not proof of a block. Record scope, date, exceptions, and evidence without credentials.
- If disruption occurs: use the tested recovery route and diagnose the specific dependency. Prefer a supported replacement; any temporary policy exception needs approval, compensating protection, an owner, and a removal date. Do not switch off MFA tenant-wide to restore one device.
Use what you have
Tools and templates
“Included” tools require an eligible product or subscription. Options reviewed 2026-09-22; check current vendor terms.
Start without another software subscription
Review Entra security defaults, which does not require a premium license, and inventory dependencies with the free change worksheet.
What to account for: Security defaults is tenant-wide. Selective policy customization may need Conditional Access licensing; a different authenticator cannot make an old application support modern authentication.
Allow for equipment, storage and staff time. Eligibility details are linked below.
Microsoft Entra security defaults
No additional premium license; requires a Microsoft Entra tenant
In Entra ID > Overview > Properties, review Manage security defaults. Inventory dependencies and protect emergency access before changing enforcement.
Limits: An on/off tenant-wide package, not a per-user pilot policy. Conditional Access customization requires at least Entra ID P1; do not disable existing protections to use this option.
Your information: Your existing Microsoft tenant processes identities, sign-ins and policy information. Never upload tenant exports to this website.
Official instructions: Microsoft Entra security defaults ↗Download a working template
Open the Excel or Word file using your existing Microsoft Office license. Replace fictional entries, fill in the blanks and save your own copy. These manual worksheets have no macros, scoring or automatic verification.
- Security change and verification record (Excel (.xlsx)) ↓
Plan one scoped change per row, including prerequisites, recovery, test expectations and actual results. An untested change is not a verified success.
Fictional worksheet preview: Security change and verification record Change ID Proposed change Actual test results EXAMPLE-CHANGE-01 Test an approved MFA policy in a limited scope Not tested Three columns shown. The full worksheet also records prerequisites, expected behavior and recovery steps. Confirm permissions and recovery access before making changes.
Fictional worked example
Use these invented entries as a guide when filling in your worksheet. They are not a customer story or lab result. Record what you observe in your own checks.
A team discovers an older scanner that sends invoices through business email.
Use the Security change and verification record template.
What to enter before testing
- Change ID
- EXAMPLE-LEGACY-01
- Service and scoped recipients
- Invoice scanner and its sending service
- Prerequisites and recovery access checked
- Pending: confirm supported authentication and recovery owner
- Actual test results
- Not tested
How to verify
Inventory the scanner dependency with its owner and follow current provider instructions for a supported sending method. Use a harmless authorized test message and inspect available sign-in or mail evidence before changing enforcement. Verify legitimate sending and the intended block separately.
If the result is unexpected
If invoices stop sending, use the pre-agreed business fallback and investigate the dependency. Pause broader rollout; avoid restoring legacy authentication across the tenant. Record any approved temporary exception with an owner and expiry.
Keep completed worksheets private. Leave out passwords, recovery keys and confidential messages. This site does not receive your edits, but a cloud editor or synced folder may send them to its provider.
Sources and review approach
These guides use selected NIST CSF 2.0 alignments. They are not official crosswalks or complete framework implementations. We have not tested these steps in your environment.
- NIST CSF 2.0: PR.AA-03: strengthening authentication paths
- https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20 ↗
- https://learn.microsoft.com/en-us/entra/identity/conditional-access/policy-block-legacy-authentication ↗
- https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults ↗