Passwordless Authentication for UAE Businesses: The Passkey Shift
Table of Content
- Two different "OTP phase-outs"
- What Microsoft Announced
- Why OTPs Are Failing
- Passkeys and FIDO2 in Plain English
- The Passkey Types You Will Meet In Microsoft 365
- MFA vs Passwordless: How To Choose
- How To Roll Out Passkeys In Microsoft 365
- Do You Need To Pay For An SMS Provider?
- Making Users Actually Adopt It
- Common Pitfalls
- A Simple 90-Day Plan
- How Americana Can Help
- Frequently Asked Questions
If you manage IT for a UAE company, you have probably noticed two stories about one-time passwords (OTPs). Your bank has stopped texting you codes. And Microsoft has announced that it is stepping away from SMS and voice sign-in codes in Microsoft Entra ID.
They are connected, but they are not the same story, and mixing them up is the most common mistake in the headlines. This guide separates them, explains passkeys in plain English, helps you choose between MFA and passwordless for different staff, and walks through a rollout in Microsoft 365 that your users will not hate.
Two different "OTP phase-outs"
The Central Bank directive is not a general ban on OTPs for UAE companies. It targets financial-sector customer authentication. For most non-financial businesses, the change that actually lands on your IT desk is Microsoft's. The banking news matters mainly because it shows regulators and customers now treat SMS codes as outdated, and your clients' security questionnaires will start to reflect that.
What Microsoft Announced
According to Microsoft's announcement, starting on 1 September 2026, passkeys became the default authentication experience in Entra ID. As the rollout reaches each organisation, users who are enabled for SMS or voice will automatically be enabled for passkeys and will be prompted to register one the next time they complete multifactor authentication.
Then the harder deadline arrives:
Anyone who truly needs SMS or voice after that date will contract a third-party provider and pay its telecom charges. For most SMEs, moving to passkeys is the cheaper, simpler path, and passkeys are included at no extra licence cost.
The practical implication: you have until early February 2027 to make this a planned project rather than a help-desk emergency. Because the rollout reaches tenants progressively, your users may already be seeing prompts.
Why OTPs Are Failing
OTPs were a big improvement over passwords alone. The problem is that attackers adapted.
• They can be phished. A fake sign-in page collects your password and your code, then replays both in real time to the real service. This is called adversary-in-the-middle phishing, and it works against anything the user can type or approve.
• SMS can be intercepted or hijacked. SIM swapping, weaknesses in telecom signalling and social engineering of mobile carriers all undermine text-message codes.
• Prompt fatigue works. Attackers who already have a password spam approval requests until a tired employee taps "yes".
• AI makes phishing better. Microsoft's threat intelligence reports AI-enabled phishing campaigns achieving click-through rates as high as 54%, against roughly 12% for traditional campaigns.
The pattern is the same everywhere: any second factor that a human can be tricked into handing over can eventually be stolen. The fix is to remove the human's ability to hand it over.
Passkeys and FIDO2 in Plain English
A passkey is a login credential that replaces your password. Instead of a secret that you know and type, your device holds a cryptographic key pair:
• A private key that never leaves your device (or your credential manager) and is unlocked with your face, fingerprint, or device PIN.
• A public key stored by the service, which can verify you but cannot be used to impersonate you.
FIDO2 and WebAuthn are the open standards that make this work across browsers, operating systems and services.
Two properties matter for businesses:
• Phishing resistance. The passkey is bound to the genuine website address. A lookalike page cannot trigger it, so there is no code or password to give away.
• Passwordless convenience. Sign-in becomes "touch to approve" rather than "type password, wait for a code, type code".
Technically, a passkey with a biometric or PIN covers both "something you have" and "something you are or know", so it is a strong form of multifactor authentication on its own, just without the weak codes.
The Passkey Types You Will Meet In Microsoft 365
• Windows Hello for Business and Entra passkeys on Windows: device-bound credentials tied to the PC's secure hardware. Microsoft began rolling out Entra passkeys on Windows as generally available from April 2026, including for scenarios where the device is not managed. Best for corporate Windows laptops.
• Microsoft Authenticator passkeys: device-bound passkeys held in the Authenticator app. Authenticator supports one passkey per account, and these passkeys do not sync to a new phone, so a lost phone means re-registering.
• FIDO2 security keys: physical USB or NFC keys. Strong, portable and good for shared devices, though they cost money and can be lost.
• Synced passkeys: stored in platform credential managers such as iCloud Keychain or Google Password Manager and available across a person's devices. Entra supports them as generally available. They are very convenient, but Microsoft advises treating them as phishing-resistant with the same security posture as other unattested authenticators, which matters for sensitive accounts.
MFA vs Passwordless: How To Choose
The question is rarely "MFA or passwordless?" It is "which method for which person?" This table shows the trade-offs.
Rule of thumb for an SME:
• Administrators and finance approvers: device-bound passkeys or hardware keys, ideally attested.
• General office staff: Windows Hello plus a synced or Authenticator passkey as backup.
• Frontline, shared-device and contractor users: security keys or tightly scoped Conditional Access.
• Everyone: a documented recovery route that does not rely on SMS.
How To Roll Out Passkeys In Microsoft 365
Allow four to eight weeks for an SME of a few hundred users. Start before February 2027, and before any holiday freeze that would leave your help desk thin.
1. Audit what you have today.In the Entra admin center, review the Authentication methods policy and registration reports. Identify who is registered for SMS or voice, who has no strong method at all, and which accounts are privileged. Microsoft's own guidance puts this first. Also list service accounts and legacy apps that cannot use modern authentication, because they will need separate handling.
2. Decide your passkey policy before Microsoft's default reaches you.Because users enabled for SMS or voice are auto-enabled for passkeys as the rollout reaches your tenant, review your passkey settings now rather than inheriting defaults. In Entra ID, go to Authentication methods and configure Passkey (FIDO2). Use passkey profiles to apply different rules to different groups: for example, device-bound and attested passkeys only for admins, and synced passkeys allowed for general staff.
3. Pilot with IT and friendly users.Start with your IT team and 10 to 20 volunteers across different roles and devices, including Mac, iPhone and Android users. Note every snag: older operating systems, browsers, mobile device management conflicts, and shared workstations.
4. Provide a safe way to onboard and recover.Use a Temporary Access Pass for first-time registration and for recovery, so no one has to fall back on SMS. Write a help-desk procedure that verifies identity before issuing one. If recovery is weak, attackers will target it.
5. Launch a registration campaign.Entra's registration campaign feature prompts users to register a passkey during sign-in. Roll out in waves by department, and give each wave a short, scheduled window with help-desk cover.
6. Enforce phishing-resistant authentication where it matters.Create a Conditional Access policy using authentication strengths to require phishing-resistant methods. Start with administrators, then finance and HR, then executives, then everyone. Microsoft recommends phishing-resistant MFA for all administrator roles. Keep a break-glass emergency account with a strong, separately stored method and monitor its use.
7. Remove the weak methods.Once a user has a passkey, disable SMS, voice and email codes for that user or group. Monitor sign-in logs for failures and for users who are still falling back to weaker methods. If your SIEM is Microsoft Sentinel, add alerts for new authentication method registrations, since attackers who compromise an account often add their own method.
8. Only then consider reducing passwords.Passwordless sign-in is a destination, not a switch. Some legacy apps, VPNs and service accounts will still use passwords for a while. Our guide to moving from VPN to Zero Trust covers how to handle those applications.
Do You Need To Pay For An SMS Provider?
Probably not. The extra step of selecting a telecom provider through the Microsoft Security Store is intended for organisations with a regulatory, technical or business reason to keep SMS or voice. Document who those users are, and test with a pilot group before relying on it. If the answer is "a few people with no smartphone", a security key is usually cheaper and safer.
Making Users Actually Adopt It
Most failed rollouts fail on people, not technology.
• Lead with "no more codes". Employees do not care about FIDO2. They care that sign-in will be faster. Sell the benefit, then briefly explain the security.
• Go first. Have the leadership team register first. When the General Manager uses a fingerprint instead of a code, resistance drops.
• Use champions. One enthusiastic person per department who helps colleagues beats a company-wide email.
• Keep instructions short and visual. A one-page guide with screenshots in English and Arabic, and a two-minute video, will outperform a long policy document.
• Address privacy concerns directly. Staff often worry that "biometrics" means the company stores their fingerprint. Explain that the fingerprint or face data stays on the device, and the company never sees it. Be especially clear about personal phones.
• Plan for the awkward cases. Staff on long-haul travel, people with dual SIMs or roaming issues, shared devices in retail or site offices, and contractors all need a defined option.
• Set a deadline with support attached. A clear date and drop-in help sessions work better than open-ended encouragement.
• Measure and share progress. Track the percentage registered, SMS usage and help-desk calls, and publish them weekly. Visible progress creates momentum.
Common Pitfalls
• Assuming "passwordless" means "phishing-proof" in every form. A push approval or code is not the same as a passkey.
• Leaving weak recovery paths. If a helpdesk can reset a user's method after a phone call, attackers will make that call.
• Allowing synced passkeys for privileged accounts by default. Decide this deliberately using passkey profiles.
• Ignoring shared and legacy devices. These cause the most day-two support tickets.
• Starting in January. February 2027 is close. Begin now.
• Treating it as an IT-only project. HR, communications and department heads all affect the outcome.
A Simple 90-Day Plan
Pair this with the basics in our Microsoft 365 email security guide, because phishing-resistant sign-in is only one layer, and with the baseline controls in our SME cybersecurity guide.
How Americana Can Help
Americana helps UAE organisations plan and deliver identity projects like this: authentication audits, Entra passkey policy design, pilot and registration campaigns, Conditional Access, and staff communications in English and Arabic. If you want to be passkey-ready well before February, book an identity readiness assessment.
Frequently Asked Questions
1. What is a passkey?
A passkey uses public-key cryptography to authenticate a user. The user unlocks it with an appropriate device method, such as a biometric check or PIN, rather than entering a shared password.
2. Is passwordless authentication the same as MFA?
Passwordless describes a sign-in experience without a password; MFA describes the use of multiple authentication factors. An implementation can meet both descriptions depending on its design.
3. Does a banking OTP change automatically apply to every company's staff logins?
Financial-sector customer authentication requirements and workplace identity-provider changes are different scopes. Confirm which rules and product changes actually apply to your organisation.
4. How should businesses roll out passkeys?
Audit current methods, define device and recovery policies, pilot with a small group, train users, expand in waves and monitor registration and support issues.
Tehreem Fazal is a creative strategist, content marketer, and freelance writer with over six years of experience crafting impactful stories for local and international brands. She specializes in content strategy, brand storytelling, and SEO-driven writing across industries like fashion, real estate, food, digital marketing, lifestyle, and automotive etc. Her words have shaped the voice of leading names including Master Group, LUMS, Metropolitan Properties UAE, and more. With a background in English Literature, Tehreem blends creativity with strategy to make every piece of content resonate and convert. When she's not writing, she's exploring new ideas, brands, and narratives that inspire.

IT Procurement & Licensing in the UAE: Lead Times, Renewals and Cost Traps
A practical IT procurement playbook for UAE businesses: realistic lead times, genuine vs grey-market hardware, warranty checks, a licence renewal calendar for Microsoft and Meraki, common overpayment traps and a TCO checklist.
Read More
Smart Boardroom Solutions for UAE Offices: Beyond the Traditional Meeting Room
A practical buyer's guide to smart meeting rooms in the UAE: wireless vs cabled sharing, interactive panels, Microsoft Teams Rooms, acoustics, network prerequisites and a room-size matrix with budget bands.
Read More
