Network password incorrect using Azure AD DS Identity

SF 1 Reputation point

Receiving the following error when using an identity connection to a smb file storage from a domain laptop. "New-PSDrive : The specified network password is not correct" The connection to the smb share works fine using the storage account and key. New-PSDrive command is a follows. New-PSDrive -Name Z -PSProvider FileSystem -Root "\\myshare" -Persist -Credential $credGetCredentials Here's what has been reviewed and verified. - Port 445 communication is working. - Azure AD DS says it's healthy. - On premise AD DS is synchronizing passwords to Azure AD. - SMB share permissions have been added for the users. - NTFS permissions have been set for users. (This was done while using the storage account to connect the share) - Passed credentials to New-PSDrive using UPN but still receive the error. What are we missing? What log can we look at in Azure to see a connection failure?

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,200 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,094 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Alex Harvey 21 Reputation points

    Had the same thing recently and it was due to the Synchronization setting on the AAD DS. It has to be set to ALL not Scoped.

    It's mentioned in the first note on this article.

    Hope this is somewhat useful and good luck!

    2 people found this answer helpful.
    0 comments No comments

  2. DA Brian Kinsley 6 Reputation points

    @Alex Harvey , where do you change the setting?

    1 person found this answer helpful.
    0 comments No comments

  3. Alex Harvey 21 Reputation points

    It's under the Synchronization settings menu for Azure AD Domain Services. You can then change the scope from 'Scoped' to 'All'.

    One other thing I have found that gives the same experience is that you need to allow the RC4 cypher. If you have deployed CIS benchmarks Level 1 for AD in the domain it will disable RC4 and cause this issue too. It is noted here

  4. SF 1 Reputation point

    @Alex Harvey , In working with Microsoft the computer mounting the smb file share had to be a member of the AAD DS. We were trying to connect to a computer connected to our internal hybrid domain. If we missed something, let me know. Thanks.