Urgent.News

One page, thousands of outlets. See who else covered it.

Editions

Tech

Microsoft shifts Entra ID towards passkey-first authentication

Microsoft is preparing a major change to enterprise identity security, making passkeys the default authentication experience in Entra ID from September 1, 2026, before ending its own SMS and voice authentication delivery services on February 1, 2027. The shift will affect organisations whose employees still rely on text messages or telephone calls for multifactor authentication. As Microsoft’s…

Microsoft is set to make passkeys the default authentication method in Entra ID from September 1, 2026, before phasing out SMS and voice authentication by February 1, 2027. This shift impacts organizations whose employees still use text messages or phone calls for multi-factor authentication (MFA). When Microsoft's rollout reaches individual organizations, users with existing SMS or voice authentication options will automatically become eligible for passkeys and be prompted to register one during their next MFA challenge.

However, Microsoft will no longer provide native telecom delivery for SMS and voice authentication after February 1, 2027. Organizations retaining these methods due to operational, regulatory, or accessibility reasons will need to use customer-managed telecom providers available through the Microsoft Security Store. Microsoft's migration plan includes providing further details on customer-managed telecommunications options in September 18, giving administrators ample time to identify affected accounts, evaluate alternatives, and revise authentication policies before the native service is withdrawn.

Passkeys employ public-key cryptography, offering enhanced security against phishing compared to traditional passwords or MFA methods. While SMS and voice authentication are safer than passwords, attackers have developed increasingly effective techniques to defeat them, including SIM swapping, social engineering, interception of messages, and AI-assisted phishing campaigns.

Microsoft has observed higher interaction rates for AI-assisted phishing compared to conventional campaigns, emphasizing the need for authentication mechanisms that do not rely on user recognition of fraudulent prompts or websites. The Entra ID change is part of a broader industry trend towards passwordless authentication, with Apple, Google, and Microsoft promoting passkeys through FIDO2 and WebAuthn standards.

Microsoft has already been expanding passkey deployment across its consumer and enterprise products, with new Microsoft consumer accounts becoming passwordless by default in 2025, and Entra administrators gaining additional tools to encourage workforce users to register passkeys. However, migrating to passkeys requires more than just enabling a new authentication button; administrators must identify users dependent on SMS and voice, ensure compatible devices are available, establish account-recovery procedures, and address situations involving shared devices, contractors, or employees who cannot use biometric authentication.

Passkeys do not transmit biometric information to Microsoft; instead, fingerprint or facial recognition occurs locally on the user’s device, unlocking the cryptographic credential. Organizations can also continue using Windows Hello for Business and FIDO2-compatible hardware security keys alongside passkeys, tailoring authentication policies based on workforce and security requirements.

Written by urgent.news from Arabian Post's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at thearabianpost.com →

More in Tech

Why I stopped pasting production JWTs into random websites (and built an offline tool suite instead)

Be honest: how many times this week have you pasted a bearer token, a customer payload, or an .env config snippet into an online formatter just to quickly see what went wrong?

  • Created offline tool suite called Omnikite to avoid pasting JWTs into random websites
  • Omnikite runs entirely in browser memory, never uploads data to external servers
  • Suite includes cryptography, developer essentials, and browser-based file processing tools

AWS IAM Least Privilege Without Losing Your Mind

Least privilege is the IAM principle everyone agrees with and few actually implement, because doing it by hand is tedious and "Action": "*" always works.

  • Begin with deny-all policy, add only needed permissions
  • Scope resources instead of actions (e.g., specific ARN)
  • Utilize conditions to further tighten policies

I audited every post on my 200-post blog. Here's what was quietly broken.

I've been running a technical blog for years. Posts accumulate — but so does everything around them: theme edits, editor migrations, hand-written HTML from 2018, mobile layouts nobody re-checked after…

  • Heading structure issue fixed by modifying theme template and inspecting posts
  • Visually hidden class problem resolved with proper CSS clipping technique
  • Version control implemented with separate updates and SHA-256 identifiers

More from Sunday 16 August →