Fix Windows 10 AAD Join not allowing user to share local resources
When a machine is only joined to AAD then these credentials are not allowed to be exposed to sharing local resources on workstations.
For example, if one machine wants to access a share on another machine we need to be able to use the AAD credentials between the machines as an authenticator.. however, these credentials do not present themselves to the local machines.
Somehow, we need to be able to take a local share, assign it to an AAD Group then be allowed to add/remove AAD users to and from that group so that local resources can be authenticated with the AAD user.
AAD joined machines are meant to work in a primarily cloud environment where all sharing happens through cloud collaboration tools – OneDrive, Sharepoint and Teams, or for large storage – Azure Files
Sharing local resources on workstations is a legacy on-premises concept when devices were connected on a common network, and required to share resources. In a cloud-first world, there are more capable tools to enable this functionality.. We recommend using them for collaboration so that the access is not dependent on the device being online and active to access those resources.
If there are specific use cases where the above does not work, we’d like to hear those
Jonathan Nguyen commented
Is there still no solution for this?