Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know

Posted on March 17, 2026

Starting February 2026, Microsoft Authenticator will introduce jailbreak/root detection for work or school accounts. Microsoft states this change is intended to prevent work or school accounts in Authenticator from functioning on jailbroken or rooted devices.

Microsoft also states that this feature does not require any IT admin configuration or control, and that personal accounts are unaffected.

What “jailbroken” or “rooted” means in Authenticator

Microsoft explains that if a mobile device’s operating system has been jailbroken (iOS) or rooted (Android), or otherwise tampered with Microsoft Authenticator may no longer work for work or school accounts.

What happens when Authenticator detects a jailbroken/rooted device

Microsoft states that if Authenticator detects the device is jailbroken or rooted, users will see an error during any interactive operation that involves a work or school account in Microsoft Authenticator.

Microsoft also states that, to protect the organization, all existing work or school accounts will be wiped/removed from Authenticator on a jailbroken/rooted device.

Rollout approach (three phases)

Microsoft states the rollout will occur in three phases and is expected to complete in July 2026:

  1. Warning mode: Users on jailbroken/rooted devices will see a warning indicating their device is jailbroken/rooted and that they’ll eventually be unable to add or use work or school accounts.
  2. Blocking mode: Users on jailbroken/rooted devices will see a warning indicating they can no longer add or use a work or school account.
  3. Wipe mode: Users will see a warning indicating their work or school accounts have been removed from the app.

Scope: what’s affected vs. not affected

Microsoft states this change applies to work or school accounts in Microsoft Authenticator, and that personal accounts are unaffected.

Microsoft also states this feature does not require IT admin configuration or control.

What Microsoft advises users to do

Microsoft directs users who need help removing jailbreak/root modifications or who need help ensuring continued sign-in to contact their organization’s support team.

For more details about this topic, please check the official Microsoft reference: Jailbreak/root detection in Microsoft Authenticator | Microsoft Support

Conclusion

Microsoft Authenticator will begin enforcing jailbreak and root detection for work or school accounts starting in February 2026. This change is automatic, requires no administrator configuration, and is designed to prevent Microsoft Entra ID credentials from being used on jailbroken or rooted devices. Organizations and users should be aware of the phased rollout and ensure work or school authentication occurs only on supported, uncompromised devices.

Did you find this article helpful? Consider showing your appreciation by liking and sharing it. 🙂

Disclaimer:  The views expressed in this post are personal and do not represent the opinions of my organization. The provided solution is offered “AS IS” without warranties or guarantees and should be validated in a test environment before deployment in production.

Your suggestions and feedback are invaluable; feel free to leave a comment.

[ ]’s Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra multifactor authentication topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024
  • Troubleshooting Error Code ‘0x000005e’ in WHfB: PIN Authentication Woes February 11, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}