Azure AD and Windows hello for business, SSO for on-premises resources
We disabled WFB when we first rolled out autopilot because we are not ready to deploy and support passwordless at the time. Now we’ve started testing WFB I’m running into an issue of not being able to access domain file shares and web servers. Below are links about the issue and different options for the three different trust types.
Azure AD and Windows Hello: SSO to on-premises resources | Katy’s Tech Blog (katystech.blog)
Windows Hello for Business Deployment Known Issues | Microsoft Learn
On-prem access from an aad joined device with Windows Hello for Business – Microsoft Community Hub
On-premise access from Azure with Windows Hello for Business — Rubix (getrubix.com)
Windows Hello for Business Deployment Prerequisite Overview | Microsoft Learn
Windows Hello for Business cloud Kerberos trust deployment | Microsoft Learn
More Stories
Windows Deployment with the Next Generation of Windows Autopilot
Microsoft's latest update to Windows Autopilot brings significant enhancements to the deployment process of Windows devices, catering to the needs...
Shrink PowerPoint files
Need to reduce the size of your PowerPoint file that contain a large number of pictures. Give this a try...
Setting the exchange online max send and receive size
Quick post today around setting exchange online max send and receive size. It can be set using the GUI in...
How to find your Microsoft Exchange build number
When documenting your environment, it’s important to keep track of the build number of your Exchange server. To get the...
Micrsoft Defender for Endpoints
We use Microsoft Defender for endpoints on our physical workstations. I'm now looking at it for our servers. The servers...
Sync Active directory user data with SharePoint
If you want to sync standard common attributes from active directory to sharepoint. Its easy, AD sync to Azure AD...