Microsoft has recently updated its Microsoft Authenticator app requirements, meaning it now requires iOS 17 or later to function properly. For organisations still relying on older Apple devices, such as iPads restricted to iOS 15.8.8, this change effectively means those devices can no longer support new authentication setups.
The Microsoft Authenticator app is a critical tool used daily by many businesses. It plays a key role in multi-factor authentication (MFA), enabling secure login approvals and identity verification for Microsoft 365 and other services.
As a result of this update, devices must now run iOS 17 or later. Older devices, such as iPads capped at iOS 15, are no longer able to add new accounts. While existing setups may continue to work for a limited time, functionality is expected to degrade over time as updates and support progress.
Devices that support iOS 17 include iPhone XS (including XS Max and XR), iPhone SE (2nd, 3rd and 4th generations), and the iPhone 11 series and newer.
This shift reflects Microsoft’s ongoing investment in modern security features, many of which depend on newer operating system capabilities.
What Businesses Should Be Aware Of
Increased security risk from legacy devices: Older devices that cannot be upgraded will no longer receive critical security updates. As a result, they become more vulnerable to cyber threats and attacks. For organisations working towards standards such as Cyber Essentials, this can also lead to potential compliance issues.
Impact on user access and productivity: If employees are unable to add new accounts, reconfigure MFA or regain access when needed, it can quickly lead to login disruption. This not only affects productivity but also leads to increased reliance on IT support.
Growing compatibility gaps: As more software providers introduce similar requirements, legacy devices are likely to lose compatibility across multiple business applications. Over time, this can lead to inconsistencies across teams and a more fragmented technology environment.
Recommended Actions
- Start by reviewing your current devices – Identify any iPads or iPhones running below iOS 17, especially where Microsoft Authenticator is being used. It’s also worth understanding where authentication is business‑critical, so you can prioritise the right users and devices.
- Plan ahead for device upgrades where needed – If devices cannot be updated to a supported version, they will need to be replaced or phased out. In some cases, it may be more practical to move authentication to newer, supported devices already in use within your team.
- Take the opportunity to review your authentication approach – This could include allowing the use of Microsoft Authenticator on personal devices under a secure BYOD policy, or exploring alternatives such as hardware security keys or conditional access policies within Microsoft Entra.
- Finally, make sure these changes are clearly communicated – Users should understand why this is happening, what it means for them, and what steps they need to take. Clear communication early on can help prevent confusion and reduce the risk of access issues.
How Hobb Can Help
We support businesses in adapting to changes like this everyday, from assessing current devices to implementing secure authentication solutions. Where upgrades are needed, we can also supply modern hardware and offer competitive pricing through our partner network.
If your organisation is affected, we can help you transition smoothly while maintaining secure and reliable access. To get in touch, email us at hello@hobb.co.uk or call 01782 566888.
