Can't map Azure File Share on an Azure AD Joined Windows 10 Device

Question

Hi,

I have a Windows 10 device which is Azure AD joined and can be managed via Intune. I am using my Azure AD credentials to login my laptop device.
Now next step further, i have setup a Storage account in Azure under which i set up the Azure File Shares. I have allowed my user in that specific file share Access Control (IAM) list.
But the problem is i am trying to map this File Share as a network drive in my Azure AD joined windows 10 Device using my Azure AD credentials which is not working. Again and again it is throwing me an error "The specified network password is not correct" even i am entering the correct password.

Can someone help me about this problem or facing the same scenario.

@Jason Sandys @AmanpreetSingh-MSFT

Thanks in Advance

Regards

Dan

Answer 1

You can't mount a drive to Azure Files with just an Azure AD identity. You can either connect via a storage account key (why provides you with no file/folder level permissions) or else via domain services such as Active Directory or Azure Active Directory Domain Services which requires the device to be domain joined.

https://learn.microsoft.com/en-us/azure/storage/files/storage-files-active-directory-overview

https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows

Answer 2

i have achieved my first target, but i am stuck in the 2nd part, i hope if someone can help me out.

i am stuck in a scenario that i have on-boarded my Windows 10 devices on Microsoft In-tune via Azure AD joined process (Connect with work or school account), now i want to access the Azure file share which i already have mounted as a network drive in my Azure AD DS joined Azure VM.

Is There any way i can access my Azure file Share from Azure AD joined machine directly from azure cloud or via Azure AD DS joined Azure VM network drive.

Thanks
Dan

Answer 3

I've been stumbling around trying to figure out how my Azure AD joined users can access Azure Files. We have Azure AD DS, but of course the laptops are not domain joined. The comment above may be out of date, as I found this Learn article that provided the crucial piece. You have to be connected to Azure so that the laptop can access the Azure AD DS. I tested it successfully with Azure VPN. The trick is to specify the username with the full FQDN of the AD DS domain. I thought when they said this that they meant the UPN, but no they want the full domain name. In my case, we had named the Azure AD DS as "aadds.company.com", so we have to supply the username as "username@aadds.company.com" even though in Azure AD DS the UPN is listed as "username@company.com".

https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-active-directory-domain-service-enable?tabs=azure-portal#mount-the-file-share-from-a-non-domain-joined-vm

In case it matters, we do have the Azure AD DS and the Azure Files private link in the same vNet.

I hope this helps someone like me who finds this page way before the other one.