Microsoft Identity
Active Directory Domain Services (AD DS) has been on the market since the year 2000. As some of you might remember, it arrived with the first release of Windows 2000 Server.
The way it works is, you join your Windows client or server devices to Active Directory (AD) to take over the management layer of it via either group policies or security settings, or you use it to chain different AD environments to each other to delegate organization permissions to resources that are stored in a different AD environment – in different forests.
Within the context of Microsoft Endpoint Manager (MEM), it's possible to connect to Windows devices that are both AD DS- and AAD-joined. Devices that are joined to AD DS and need to become available in AAD as well are known as hybrid AAD-joined (HAADJ). Before your business is ready to work natively in AAD, hybrid AAD might be the best option to use as an interim solution. Let's talk more about this in the next...