What is Hybrid Azure AD Join ?
Let’s just start with the official definition from the Microsoft documentation:
Hybrid Azure AD Join: Joined to on-premises AD and Azure AD requiring organizational account to sign in to the device.
This means that after the device is Hybrid Azure AD joined, it behaves the same as any other computer connected to Active Directory.
Sign in with an Active Directory account is required.
User credentials are verified against an Active Directory domain controller.
Group Policy objects for users & computers read from the domain controller are applied automatically.
After the Active Directory connection process is complete, additional steps are performed asynchronously in the background to register the device in Azure AD as well.
Continue reading “Why a Windows Server 2019 VDI should be Hybrid Azure AD joined”
In the past months, I have had to deploy Microsoft Teams and OneDrive from the Office365 portfolio in Citrix environments, in addition to the standard office applications in numerous projects.
The standard installation, that the user can perform through the Office365 portal, is a user-based installation. In a Citrix environment, this is only recommended for desktop operating systems (pooled or personal desktop).
A user-based installation can be detected very quickly in the User Profile, since data is then located under AppData\Local\Microsoft\Teams.
This type of installation in a worker with server operating system has many disadvantages:
Continue reading “Install Teams & OneDrive in Citrix (Machine-Based)”
- No control over the installed version
- Several different versions possible on the same worker
- Complete data (~1 GB) is stored in the user profile