Hello @christopher townsend
Mapping a network drive with Azure AD credentials often fails because SMB authentication doesn’t automatically interpret Azure AD UPNs correctly without the right prefix or configuration. By explicitly specifying your username in the format AzureAD\john
(or AzureAD\******@contoso.com
) when prompted, or by using the net use
command with the correctly formatted user string, you can typically work around the issue. If problems persist, double-check local security settings and consider a local account or hybrid join configuration as alternatives.
What You Can Try
Use the Correct Username Format: When mapping the drive or entering credentials manually, try one of these formats:
Prefix with “AzureAD\”: For example, if your AzureAD account is ******@contoso.com
, try entering the username as:
AzureAD\john
**Use the Full UPN with the Prefix:** Alternatively, try:
```sql
AzureAD\******@contoso.com
```
Sometimes one format works better than the other depending on your exact environment and how the profile is set up on the remote PC.
- Map the Drive via Command Prompt: Use the
net use
command from a Command Prompt (opened as administrator) to force the credentials in the proper format. For example: cmd
Then, enter your password when prompted. This method can sometimes bypass issues that the GUI mapper encounters.net use Z: \\RemotePC\C$ /user:AzureAD\******@contoso.com
😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!