Problem mapping a drive while signed into created azure user

Question

Problem mapping a drive while signed into created azure user

Nuno Gomes 0

I've been trying to map a drive for a file storage using the provided script in the connect section. I believe the problem lies within the kerberos system. I've setup everything correctly (i assume), logged into the created user in windows (which has all the right permission) but when i run the script i get the error "New-PSDrive : The specified network password is not correct".
Since i was able to sign into the microsoft account and into the azure portal using the credentials, i assume those are correct.
Can anyone help?

Im using windows 10 in the lastest update.

Vinodh247-1375 44,716 Reputation points Volunteer Moderator

2026-07-11T16:02:46.4133333+00:00
Please confirm if you had a chance to try any of the suggestions provided for your question.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful.

If in case you have any resolution please share the same here with the community as it can be helpful to others. Else, please respond with more details and we will try to see if we can help further.

1 answer

Your answer

Vinodh247-1375 44,716 Reputation points Volunteer Moderator

2026-07-11T16:02:46.4133333+00:00

Please confirm if you had a chance to try any of the suggestions provided for your question.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful.

If in case you have any resolution please share the same here with the community as it can be helpful to others. Else, please respond with more details and we will try to see if we can help further.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

This is almost always not a wrong password issue but an identity mismatch with Kerberos. When mapping Azure file shares using AD or AAD DS, the credentials used for SMB auth must be the domain identity (for example, DOMAIN\username or ******@domain.com tied to AD), not the Microsoft account login used for the Azure portal. If you are using Azure Files with AD integration, ensure the storage account is domain-joined, your VM or machine is also domain-joined, and you are logged in with that domain user. Also verify SPN and Kerberos ticket using klist. If you are using AAD Kerberos (preview scenarios), make sure the device is Azure AD joined and you are using the correct UPN format. In short: portal login working does not mean SMB/Kerberos auth will work; align the identity type and domain join properly.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.