Access on-premises resources from an Azure AD-joined device in Microsoft 365 Business Premium
This article applies to Microsoft 365 Business Premium.
Any Windows 10 device that is Azure Active Directory joined has access to all cloud-based resources, such as your Microsoft 365 apps, and can be protected by Microsoft 365 Business Premium. You can also allow access to on-premises resources like line of business (LOB) apps, file shares, and printers. To allow access, use Azure AD Connect to synchronize your on-premises Active Directory with Azure Active Directory.
To learn more, see Introduction to device management in Azure Active Directory. The steps are also summarized in the following sections.
This procedure is only applicable to OAuth and NTLM. Kerberos is not supported.
Run Azure AD Connect
Complete the following steps to enable your organization's Azure AD joined devices to access on-premises resources.
To synchronize your users, groups, and contacts from local Active Directory into Azure Active Directory, run the Directory synchronization wizard and Azure AD Connect as described in Set up directory synchronization for Office 365.
After the directory synchronization is complete, make sure your organization's Windows 10 devices are Azure AD joined. This step is done individually on each Windows 10 device. See Set up Windows devices for Microsoft 365 Business Premium users for details.
Once the Windows 10 devices are Azure AD joined, each user must reboot their devices and sign in with their Microsoft 365 Business Premium credentials. All devices now have access to on-premises resources as well.
No additional steps are required to get access to on-premises resources for Azure AD joined devices. This functionality is built into Windows 10.
If you have plans to login to the AADJ device other than password method Like PIN/Bio-metric via WHFB credential login and then access on-premise resources (shares,printers..etc), please follow https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-base
If your organization isn't ready to deploy in the Azure AD joined device configuration described above, consider setting up Hybrid Azure AD Joined device configuration.
Considerations when you join Windows devices to Azure AD
If the Windows device that you Azure-AD joined was previously domain-joined or in a workgroup, consider the following limitations:
When a device Azure AD joins, it creates a new user without referencing an existing profile. Profiles must be manually migrated. A user profile contains information like favorites, local files, browser settings, and Start menu settings. A best approach is to find a third-party tool to map existing files and settings to the new profile.
Users won't be able to authenticate to applications that depend on Active Directory authentication. Evaluate the legacy app and consider updating to an app that uses modern Auth, if possible.
Active Directory printer discovery won't work. You can provide direct printer paths for all users or use Hybrid Cloud Print.