
No-Faffing Managed IT Support & Cyber Security Support. Made in Yorkshire, built for the UK.
Jonathan Edwards' recent YouTube video explains why iCloud passkeys are making passwordless access to Microsoft 365 far more practical for everyday users. He demonstrates how a single passkey can now work across a user’s Mac and iPad using Face ID or Touch ID, even when an iPhone is missing or unavailable. Consequently, this change removes a common friction point in passwordless rollouts and aligns authentication with how people actually work today. As a result, IT teams must consider both the user benefits and the administrative work involved.
Edwards walks viewers through live demos that show creating a passkey on a Mac and signing in on an iPad, which helps non-technical audiences see the flow. He also highlights the technical update from Apple that allows synced passkeys to be used across multiple Apple devices without re-registration. These demonstrations clarify how biometric prompts replace passwords, and why that reduces the risks of phishing and credential theft. Therefore, organizations can better judge the user experience before adopting new policies.
Furthermore, Edwards points out the scenarios that used to block access, such as a flat or forgotten phone, and shows how synced passkeys solve those problems. He explains the distinction between device-bound passkeys, which never leave a single device, and synced passkeys that store encrypted private keys in a cloud provider like iCloud. Accordingly, viewers get a practical sense of how security models differ and what they mean for daily operations. This clarity helps decision-makers weigh tradeoffs more confidently.
The video dives into the Microsoft Entra configuration required to enable passkeys, and Edwards warns about the common missteps that can silently break registration. For example, choosing an Authenticator-only option or misconfiguring Conditional Access rules can prevent users from registering passkeys without obvious errors. Thus, he stresses carefully checking the passkey option and testing Conditional Access policies before broad rollout. Consequently, admins should pilot changes with a small user group to catch configuration gaps early.
Edwards also covers the new passkeyType property and how it interacts with attestation settings, noting that enforced attestation currently restricts organizations to device-bound passkeys. He recommends using the newer passkey profiles approach to create tailored policies for different groups, which helps balance convenience and compliance needs. This way, security-sensitive teams can keep device-bound policies while flexible teams use synced passkeys for better productivity. Therefore, administrators gain finer control without sacrificing governance.
While synced passkeys offer clear convenience, Edwards openly discusses the tradeoffs between convenience and absolute security. On one hand, device-bound passkeys offer the strongest protection because the private key never leaves the hardware. On the other hand, synced passkeys improve resilience and reduce help-desk calls when users switch devices or lose hardware, which matters for modern hybrid work patterns.
Moreover, Edwards notes that trusting a cloud provider for key sync introduces different risks, such as the need to trust end-to-end encryption implementations and account recovery flows. Therefore, organizations must decide whether the operational benefits outweigh those added considerations. In practice, many will choose mixed strategies that combine device-bound enforcement for high-risk roles and synced passkeys for general staff.
Edwards emphasizes several adoption challenges, including compatibility requirements like iOS 17+ and Android 14+ (with Android 15 recommended) and the need for administrators to update back-end settings. Additionally, Conditional Access policies flagged as “Require MFA” may inadvertantly block passkey registration unless adjusted. Consequently, IT teams must update documentation, train help-desk staff, and run phased pilots to reduce disruption.
He also highlights that automatic tenant changes are scheduled following the public rollout, meaning admins should plan for the change instead of being surprised. Training end users remains critical because biometric prompts and passkey workflows differ from traditional password resets. Thus, good communication and a staged rollout can prevent a spike in support requests while improving security overall. For these reasons, careful planning matters as much as technical configuration.
According to the video, Microsoft expanded passkey profiles to public preview in November 2025 and plans General Availability in March 2026, with automatic tenant enablement following soon after. Edwards advises administrators to use the preview period to validate Conditional Access rules, confirm platform requirements, and test both synced and device-bound scenarios. This proactive testing reduces the chance that users will face silent registration failures when the settings change at scale.
In closing, the video offers a practical playbook: pilot with a small group, avoid the Authenticator-only trap, adjust Conditional Access to permit registration, and consider mixed passkey profiles to balance risk and productivity. With these steps, organizations can move toward true passwordless authentication while keeping user experience smooth. Hence, Edwards’ walkthrough serves as a useful guide for IT teams planning the transition.
iCloud Passkeys Microsoft 365, Microsoft 365 passkey support, iCloud passkeys passwordless sign-in, passwordless authentication Microsoft 365, Apple passkeys for Microsoft 365, enterprise passkeys Microsoft 365, secure sign-in iCloud passkeys, Microsoft 365 security iCloud passkeys