Trascritto
Microsoft Entra Domain Services - Simply Explained
14 ago 2026 ·
17 min. 16 sec.
Scarica e ascolta ovunque
Scarica i tuoi episodi preferiti e goditi l'ascolto, ovunque tu sia! Iscriviti o accedi ora per ascoltare offline.
Microsoft Entra Domain Services - Simply Explained
Descrizione
Moving an old Windows app to an Azure VM does not remove its need for a classic domain with LDAP, Kerberos and Group Policy. This Knowledge Nugget shows IT admins...
mostra di più
Moving an old Windows app to an Azure VM does not remove its need for a classic domain with LDAP, Kerberos and Group Policy. This Knowledge Nugget shows IT admins and cloud architects where Microsoft Entra Domain Services fits next to Entra ID and Active Directory, and which limits to check before choosing it.
In this episode
Key takeaways
Worth quoting
“The main identity record stays in Entra ID. Users and groups from Entra ID copy into the managed domain so the older app can see and use them in the form it understands.” – Mirko Peters (05:16)
“For cloud-only users, that often means the user needs to change their password after domain services is enabled. That password change creates the protected form needed for the managed domain.” – Mirko Peters (06:18)
Explore more on M365.FM
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
mostra meno
In this episode
- 00:00 – The cloud app that still expects a Windows domain
- 00:45 – Why Entra ID alone cannot run every legacy app
- 03:28 – What Microsoft Entra Domain Services actually is
- 07:20 – Entra ID, Active Directory and Domain Services: different jobs
- 10:40 – When Domain Services fits and when it does not
- 13:53 – The managed-service trade-offs
- 15:35 – A simple Azure migration story
Key takeaways
- Microsoft Entra Domain Services provides a managed Windows domain inside an Azure virtual network for legacy apps that still need LDAP, Kerberos, NTLM, domain join or Group Policy, without you running domain controllers.
- Identity data flows one way, from on-premises Active Directory or Entra ID into the managed domain, so users and groups must be managed in the source directory, and cloud-only users may need a password change before they can use it.
- New cloud apps should sign in directly through Entra ID; Domain Services does not fit apps that need LDAP write access, schema changes or full domain admin control.
Worth quoting
“The main identity record stays in Entra ID. Users and groups from Entra ID copy into the managed domain so the older app can see and use them in the form it understands.” – Mirko Peters (05:16)
“For cloud-only users, that often means the user needs to change their password after domain services is enabled. That password change creates the protected form needed for the managed domain.” – Mirko Peters (06:18)
Explore more on M365.FM
- Episode page: the full Knowledge Nugget with chapters, key quotes and FAQ
- Microsoft Entra Domain Services – the managed Windows domain in an Azure virtual network for apps that need LDAP or Kerberos
- Microsoft Entra ID – the source of cloud identities, which copy one way into the managed domain
- Active Directory – the self-run domain for hybrid companies and the better choice when full domain control is needed
- Related episode: Group Policy - Simply Explained
- Related episode: Microsoft Entra Cloud Sync - Simply Explained
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
Informazioni
| Autore | Mirko Peters M365, Azure & AI |
| Organizzazione | m365 FM |
| Sito | www.m365.fm |
| Tag |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Commenti