You can enable this functionality in your organization quite easily through a particular Group Policy.
Restriction of access to apps from only devices that meet compliance policy.ĭomain joined devices will automatically register to Azure AD and avail of the above mentioned experiences.
Microsoft Passport for Work and Windows Hello for secure and convenient access to work resources.
Users can choose from an inventory of applications pre-selected by the organization.
Access to Windows Store for Business using AD account.
Users don’t need to connect a Microsoft account (e.g. Hotmail) to see settings across devices.
Enterprise compliant roaming of user settings across joined devices.
Users enjoy SSO to Azure AD apps even when not connected to the domain network.
Users don’t see additional authentication prompts when accessing work resources (a.k.a.
None of the existing behaviors for Domain Join change in Windows 10, however new capabilities light up when Azure AD is in the picture: Users who sign-in to these computers using their AD accounts get authenticated to the domain as well. The computer participates in authorization decisions when accessing other resources in the domain. When the computer is physically in the domain network it authenticates to the domain through a domain controller (DC). The computer gets a unique identity and a channel is created so admins can reach out to the computer for settings and policy purposes (a.k.a. In this post I will talk about Domain Join and how additional capabilities are enabled in Windows 10 when Azure AD is present.ĭomain Join has been deployed by many of you since the beginning of this millennium (although Domain Join existed even before AD was born and Windows NT was around).ĭomain Join adds a computer to a particular realm, the Active Directory domain. In the previous post I talked about the three ways to set up devices for work with Azure AD.