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 Entra ID – Enabling SMS-based authentication

Posted on June 11, 2020

Hello everyone. In today’s article we’ll show how to enable the option for accessing applications hosted or integrated with Microsoft Entra ID using SMS-based authentication.

What is SMS-based authentication?

SMS-based authentication, currently in preview, allows users to access applications integrated with Microsoft Entra ID without needing to know their username and password, which are replaced by their registered phone number and confirmation of possession of it through the code received during sign-in via SMS.

Enabling SMS-based authentication

The first step is to enable the feature in the Authentication Methods portal of Microsoft Entra ID. To access this portal directly, click this link.

Let’s select the Text message option.

Let’s follow the steps below to select the users we want to allow access via SMS for:
1 – Enable the feature by clicking YES on the ENABLE option.
2 – In the TARGET option, you can select all users, but if you want to roll out the feature in a controlled way, use the Select users option.
3 – By clicking Add users and groups you can select the groups or users for whom we want to enable this option.

For our demonstration, let’s select the user chrystal@ulyneves.com.

Click Select.

Click Save after you have at least one user selected.

Let’s add the phone number to be used during sign-in in the Authentication methods option. If the user already has a registered contact, this step can be skipped.

Activating SMS sign-in on the user portal

Let’s activate SMS authentication through the user’s profile security settings.

Let’s go to the URL https://mysignins.microsoft.com/security-info

In the Security Info menu, if the user has a registered phone number and SMS Sign-in enabled, you’ll be able to see the following message: You can enable your phone number (+ X XXXXXXX) to be used as a username for sign in. Click Enable.

You will receive a message asking you to confirm the number. Confirm the number and click Enable.

If everything is correct with the activation, you will receive a confirmation message. Click Done.

If you receive a message stating that the number is being used by another user in the tenant, check whether this number is not registered to another user. If it is, remove it and try again.

Accessing the Office 365 portal using SMS

Let’s now access the Office 365 portal through the URL https://portal.office.com/.

Instead of using the UPN or username, we’ll use the phone number in the format +1 4251234567 and click Next.

You will receive an SMS code that should be used on the screen below.

Click Sign in.

With the SMS code correctly verified, access is granted to the Office portal without needing to use a username and password.

Note: If access requires second-factor verification, before granting access, the user will be prompted to complete the second verification just as it would work if they had used their username and password in the first stage.

Summary

In today’s article, we showed how to enable authentication using SMS. This is one more option for allowing users to access their resources in Azure without using a username and password.

I hope this content has contributed to enriching your knowledge of Microsoft Entra ID.

Did you like the post? Like and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

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

Leave a Reply Cancel reply

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

Recent Posts

  • Conditional Access report-only: why a successful sign-in can show a policy failure October 9, 2026
  • Microsoft Entra SMS and Voice Retirement: An Admin Preparation Checklist September 24, 2026
  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • 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

Archives

  • October 2026
  • 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}