For more information about hybrid provisioning options like Autojoin, you can view Microsoft’s documentation here. They rely on the traditional on-premises Active Directory Domain Services (AD DS) for Identity and Access management (IAM) and are also registered with Azure AD (see figure 2).Ĭhances are if you already have Azure AD Connect (AADC) installed and are synchronizing your on-premises AD DS to Azure, you most likely already have hybrid Azure-AD-joined devices in your environment because they were auto-provisioned with the Windows Autojoin feature. These devices are simply AD-joined Windows endpoints that have been synchronized from on-premises Active Directory to Azure AD. Let’s begin with a very common use case, hybrid Azure AD joined. In this blog, we’ll work on untangling this web of new trust types for binding end-user devices to Azure AD, help clarify the benefits and differences between each, and examine how they compare to traditional on-premises domain joins.

If you don’t yet have a solid understanding of these new trust types, then you might be hesitant to start adopting and investing in these newer technologies, including deciding when to convert from traditional AD-joined devices to Azure-AD-joined devices.

IOS, Android, and macOS Windows 10 or newer, 8.1 via Workplace JoinīYODs, mobile devices, and corporate-owned non-domain-joined devicesĪll Windows 11 and Windows 10 devices except home editions Windows Server 2019 VM’s in AzureĬorporate-owned non-AD domain-joined devices

Macos azure ad login