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

Azure VM – Integrating Windows Server 2019 Access with Microsoft Entra ID Authentication

Posted on February 18, 2020

Hello everyone. In today’s article, we’ll show you how to configure an Azure credential to access Windows Server 2019 Datacenter edition or Windows 10 version 1809 or later virtual machines. This functionality is possible because the virtual machine is joined to Microsoft Entra ID during the creation process.

Benefits of using an Azure credential

Using Azure credentials for access to VMs brings several benefits to the organization:

  • Use the same credentials from a federated or managed domain to allow access to the operating system.
  • There’s no longer a need for local users.
  • Control access to the operating system using Azure RBAC.
  • Ability to use Microsoft Entra Conditional Access policies to require MFA or evaluate access risk.

Note: When you enable the option to use Microsoft Entra ID credentials to access the VM, the virtual machine is joined to Microsoft Entra ID and can no longer belong to an on-premises domain or Azure AD DS. For more information, check out this link.

We’ll walk through step by step how to create a virtual machine in Azure and grant administrator access to a Microsoft Entra ID user. This feature is currently only available for machines hosted in Azure.

Creating a server in Azure

Let’s start by creating a server in Azure. To do this, access the Virtual Machines menu in your Azure portal or click this link.

Let’s click + Add to add a new virtual machine.

On the first menu (Basics), select the subscription and the resource group available in your subscription.

Enter the VM settings as shown below:
1 – Fill in the Virtual machine name field with your VM’s name.
2 – We’ll select the Windows Server 2019 Datacenter operating system for this illustration.

Enter the credentials that will have local access to the server:
1 – Enter the username.
2 – Enter the password.
3 – Confirm the password.

Configure the ports that will be opened for communication with your server. For this illustration, we’ll keep the default, which is remote access through port 3389.

Click Next: Disks >.

On the (Disks) tab, we’ll keep the default and click Next: Networking >.

On the (Networking) tab, if you don’t have a specific network, keep the settings and click Next: Management >.

Enabling authentication with Microsoft Entra ID

The (Management) menu is the most important one for us in this article. In it, we enable the integration between the operating system and Microsoft Entra ID.

To enable the access integration, change the Login with AAD credentials (Preview) option to On.

Click Review + Create.

Next, Azure validates the minimum settings required to create the VM and displays the message “Validation passed”.

Click Create.

Configuring permissions in Azure

With the VM created, let’s now define who will have access privileges to it.

Click the virtual machine you created.

Follow the steps below:
1 – Click Access control (IAM).
2 – Click + Add.
3 – Click Add role assignment.

In the Add role assignment menu, select the Virtual Machine Administrator Login role so we can populate the group that grants administrator access to virtual machines in Azure.

In the select field, search for the Microsoft Entra ID user you want to grant administrative access to on the VM.

Select the user and click Save.

Accessing the VM with the Azure credential

Let’s now access the virtual machine by following these steps:
1 – With the virtual machine selected, click Overview.
2 – Click Connect.
3 – Click Download RDP File.

Note: To access the VM via RDP, you need to use a Windows 10 device that is Microsoft Entra joined or Microsoft Entra hybrid joined and belongs to the same domain as the VM you created. For more information, check out this link.

Run the .rdp file and sign in with the Azure credential that was granted access in the previous step.

Verifying permissions on the VM

With access successfully completed, let’s now validate whether the administrator permission was granted correctly.

In the Windows Windows Settings menu, select the Accounts option.

We can see that the selected Microsoft Entra ID user appears with the Administrator role.

Validating server status

Let’s confirm whether the server was correctly joined to the Microsoft Entra ID domain by running the command below in the Windows prompt:

dsregcmd /status

You can see in the AzureAdJoined field that the server is joined to Microsoft Entra ID.

Summary

In today’s article, we showed how to create a VM in Azure while enabling access through a Microsoft Entra ID sign-in. We defined this user’s permission level and confirmed that the VM we created was joined to Microsoft Entra ID.

I hope this content has helped enrich 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 Microsoft Entra ID topic archive.

Leave a Reply Cancel reply

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

Recent Posts

  • 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
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 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}