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 – Introduction

Posted on August 7, 2019
Hello, everyone. In the previous post, we talked about Azure policies and how they can help ensure adherence to standards and rules defined by the company. As promised in the last post about Azure Identity, today we’ll talk about Microsoft Entra ID, what it’s for, and the differences compared to conventional Active Directory based on Windows Server. What is Microsoft Entra ID? Microsoft Entra ID is a Microsoft cloud-based identity and access management service. With Microsoft Entra ID it’s possible to manage access to services hosted in the cloud, for example, Office 365, virtual machines hosted in Azure, configure single sign-on (SSO) for applications developed by the company, enable multi-factor authentication (MFA), etc. Microsoft Entra ID has some licensing options that enable services, tools, and provide differentiated support, as illustrated below: Microsoft Entra ID Free – This is the basic tier enabled when you activate a Microsoft 365 subscription. With this subscription, it’s possible to manage users, groups, and use Single Sign On (SSO) for up to 10 applications per user and manage up to 500 thousand objects in the directory. It’s also possible to perform cloud password resets for users created in Azure through the Self-service password change service, and also sync objects from Windows AD to Microsoft Entra ID using the Microsoft Entra Connect tool, which we’ll cover in upcoming posts. Office 365 – Offers the Microsoft Entra ID Free options, but with unlimited objects and also MFA Multi-factor Authentication. Microsoft Entra ID Basic – With Microsoft Entra ID Basic, you can use all the Microsoft Entra ID Free options, but with unlimited objects, B2B collaboration (allows assigning guests), group-management-based access and provisioning, logo inclusion on pages, and an SLA. Microsoft Entra ID Premium P1 – With Entra ID Premium P1, you can use the features of Microsoft Entra ID Basic, but with this license, the applications assigned to each user are unlimited. This plan offers advanced reports, dynamic groups, group naming policy, on-premises write back for password reset, unlock, and change using the self-service portal. With this plan, synchronization between Microsoft Entra ID and on-premises AD is possible. It’s also possible to use MFA Multi-factor Authentication, Cloud App Discovery, Connect Health, location-based conditional access, the ability to integrate with identity governance partners, and integration with cloud security applications. Microsoft Entra ID Premium P2 – This plan offers all the options of Entra ID Premium P1, plus the tools, identity protection, access reviews, and privileged identity management. What are the differences between on-premises AD and Microsoft Entra ID? In the table below, you can see some differences between Microsoft Entra ID and AD DS.
Windows Server Active Directory

Microsoft Entra ID

LDAP

REST API’s

NTLM/Kerberos

OAuth/SAML/OpenID/WS-Federation

Uses GPO

Does not use GPOs

X.500 structured directory

Flat structure

Access control with granular customizations

Predefined roles

Domain/forest

Tenant

Trust Relationship

Guests

Summary In today’s article, we talked about Microsoft Entra ID concepts, its licensing options, and the difference between Microsoft Entra ID and on-premises AD. In the next post, we’ll get into access management using RBAC, how to configure custom roles and assign them to users in the Azure portal and with PowerShell. I hope this content has helped enrich your knowledge of Azure. Did you like the content? Like it 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}