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 – Controlling Access to Azure Through Terms of Use

Posted on February 11, 2020

Hello, everyone. In today’s article, we’ll explain how to force device registration in Azure using terms of use. This control applies to scenarios where administrators want to identify the devices used by users to access applications hosted in Azure.

For this demonstration, we’ll create a term of use, a conditional access policy so the term of use is applied to users, and show how to verify whether the device is registered in the Azure portal and on the user’s device.

Configuring the Term of Use in Azure

Access the terms menu in the conditional access policy via the path Azure AD > Security > Conditional Access Policy > Terms of use, or click this link.

Click New terms.

Let’s configure the term of use following the steps below:
1 – Enter the name of the term of use for tracking in the Azure portal.
2 – Enter the name of the term that will appear to users.
3 – Select the user’s preferred language.
4 – Upload the file with the terms of use policy.

Select the terms of use file in PDF format and click open.

Let’s enable the option that requires the term to be accepted on every device the user uses to access the application. This option requires the user to register their device before receiving the term of use. For more information, visit this link.

1 – Enable the Require users to consent on every device option.
2 – Check the Create conditional access policy later option.
3 – Click Create.

Creating the Conditional Access Policy

Let’s now create the conditional access policy to make the term of use available to users.

Access the Conditional Access Policies menu in Azure, or click this link.

Click New Policy.

For this demonstration, we’ll apply the policy only to user chrystal@ulyneves.com through the steps below:
1 – Enter the policy name in the Name field.
2 – Click Users and groups.
3 – Check the Select users and groups option.
4 – Click Select.
5 – Select the user or group you want to apply the policy to.
6 – Click Select.
7 – Click Done.

Let’s now configure which application will request the term of use. You can apply the same term to all applications hosted in Azure. For this demonstration, we’ll use the Azure management portal.
1 – Click Cloud apps or actions.
2 – Select the Select apps option.
3 – Click Select.
4 – Search for and select the Microsoft Azure Management app.
5 – Click Select.
6 – Click Done.

Let’s now define the control this policy will perform if access matches the scope defined in the previous steps.
1 – In the Access controls menu, select the Grant option.
2 – Select the Grant access option.
3 – Select the term of use created earlier.
4 – Click Select.

Let’s now enable the policy by selecting the ON option in the Enable policy menu.
Click Create.

Accessing the Azure Portal

Let’s test whether the policy is working by accessing the Azure management portal with user chrystal@ulyneves.com.

We can see in the image below that the created policy doesn’t allow the user to access the portal before registering their device in Azure. Let’s click More details.

As shown in the image below, the user’s device is not registered and therefore needs to be registered before accessing the portal. This option to force registration is necessary because we enabled the Require users to consent on every device option when creating the term of use.

Registering the Device in Azure

Let’s register the user’s device in Azure to gain access to the term of use and get access to the Azure management portal.

Click Settings > Accounts > Access work or school.

The configuration window for registering the device in Azure will open.

Click + Connect.

Sign in with the user you want to grant access to the portal. In our demonstration, Chrystal.

Click Next.

We can see in the image above that the device is registered in Azure.

With the device registered in Azure, when accessing the Azure portal again, the term of use is presented to the user.

Click Aceitar.

With the term of use accepted by the user, access to the Azure portal is granted.

Validating the Device Registration

To confirm whether the device was registered in Azure correctly, go to the Azure AD > Devices menu, or click this link.

On the device, open the Windows command prompt and run the following command:

dsregcmd /status

We can see that the device has the Workplacejoined status.

Monitoring the Term of Use

Azure allows you to monitor the terms made available to users. To identify how many users accepted or rejected the term, access the terms of use menu through this link.

Click the number corresponding to the term status column, as shown below:

As shown in the image below, you can see the users and devices used to accept the term of use.

Summary

In today’s article, we showed how to control device registration in Azure using terms of use. We explained how to create a term and apply it using a conditional access policy.

I hope this content has contributed to expanding your knowledge of Azure AD.

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 Microsoft Entra Conditional Access 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}