# Microsoft Adds Script-Injection Protection to Entra ID Sign-Ins

- **Canonical URL:** https://www.probackend.com/access-management-iam-security/microsoft-tightens-entra-id-security-to-block-external-script-injection
- **Section:** Security Governance
- **Published:** 2026-11-19
- **Summary:** Microsoft will block unauthorized external scripts on Entra ID browser sign-ins starting in October 2026. See what security teams should test.

---

## Microsoft Entra ID Adds Protection Against Injected Sign-In Scripts

Microsoft will begin enforcing Content Security Policy (CSP) protections for browser sign-ins at `login.microsoftonline.com` in mid-October 2026. The rollout is expected to finish by late October. According to the report, the protection will be enabled by default, require no tenant configuration, allow trusted Microsoft-hosted scripts, and block unauthorized external scripts.

The change matters most for organizations whose browser sign-in journeys rely on extensions or other tools that inject code into sign-in pages. Administrators should identify those dependencies and test business-critical journeys before enforcement. MSAL and API-based authentication flows are not affected, according to the report.

CSP is a browser security mechanism that controls which sources may provide content such as scripts. Here, it is intended to prevent untrusted code from running in the covered sign-in experience. This is a targeted protection for browser sign-in—not a replacement for other identity and access management (IAM) controls, such as multifactor authentication, least privilege, access reviews, or account lifecycle management.

## What administrators should check

Inventory browser-based sign-in journeys that use `login.microsoftonline.com`, including employee, administrator, contractor, and application workflows. Ask browser-management, endpoint, identity, and application teams whether extensions, automation, user scripts, or other tools modify those pages. Focus on code injection into the sign-in experience, rather than the mere presence of an extension.

Test representative, business-critical journeys before the rollout. The report says Microsoft recommends checking browser developer-console output for CSP violations. In controlled tests, note any blocked scripts and the browser, application, sign-in route, and tool involved. Keep diagnostic records free of passwords, tokens, and other sensitive authentication data.

For each dependency, confirm whether it is an approved business requirement, a convenience, or an unknown risk. Contact the tool owner or vendor about supported alternatives that do not inject scripts into the authentication page. Where possible, remove or disable unsupported injection and repeat the test. If a journey changes, determine whether authentication failed or whether an extension or downstream application feature stopped working; successful sign-in alone does not confirm that every dependent workflow still behaves as intended.

Prioritize privileged and high-impact access, but include ordinary user journeys where managed browsers may carry custom tooling. Coordinate testing and any browser or endpoint changes with application owners and support teams, and give users a clear route to report problems.

## Interpreting findings and documenting results

A CSP violation can indicate a compatibility issue or a policy violation; on its own, it does not prove an attack succeeded. Investigate the source and context, and do not assume a familiar extension is safe simply because it has a legitimate purpose. Code injection on an authentication page can affect the integrity of what users see and interact with.

Record the scope and date of testing, browser and application combinations, identified tools, remediation decisions, owners, and retest results. This gives security and compliance teams a basis for follow-up and helps distinguish expected changes from unrelated sign-in incidents.

The reported scope is browser-based sign-in at `login.microsoftonline.com`. MSAL and API-based authentication flows are not affected by the CSP enforcement described in the report. Assess each application’s actual sign-in path rather than assuming all clients or Microsoft identity surfaces are affected in the same way.

## Part of a broader security effort

The report places the update within Microsoft's Secure Future Initiative (SFI), announced after Chinese hackers breached Exchange Online mailboxes belonging to dozens of organizations and hundreds of individuals in May and June 2023. BleepingComputer also cites other SFI-related measures: disabling ActiveX controls in Windows versions of Microsoft 365 and Office 2024 apps, and updating Microsoft 365 security defaults to block access to Office, SharePoint, and OneDrive files through legacy authentication protocols.

These measures address different risks. The Entra ID change concerns scripts on browser sign-in pages; ActiveX controls and legacy authentication are separate issues. Organizations should assess their own dependencies and keep the broader identity controls that protect accounts and access.

## Bottom line

The CSP protection is expected to roll out from mid-October through late October 2026, enabled by default and without tenant configuration. Identify and test business-critical browser sign-in journeys that rely on extensions or other code-injection tools, investigate CSP violations, and replace unsupported dependencies where possible. The reported change applies to browser sign-in at `login.microsoftonline.com`; MSAL and API-based flows are not affected.

Source: [BleepingComputer, “Microsoft to block Entra ID script injection attacks starting October”](https://www.bleepingcomputer.com/news/security/microsoft-to-block-entra-id-script-injection-attacks-starting-october/).

![microsoft entra id adds protection against injected sign-in](https://assets.probackend.com/a72698dd-2ff3-42c6-8ad3-67799551c594?token=ast_7b9ee8975a4b187969d396286e3f9717c42f2331)

![Abstract editorial image representing browser sign-in security and script protection](https://assets.probackend.com/193c3c41-be25-4292-a8e5-be49e594e009?token=ast_7b9ee8975a4b187969d396286e3f9717c42f2331)
