I cannot connect to our VM from my Mac

Hi Jim Perkins

Thanks for the extra detail . The key difference here is how the new Windows App for Mac handles Azure AD credentials compared to the classic RDP client inside Parallels. The “Other user” prompt you’re seeing usually means the app isn’t parsing the AzureAD format correctly. The trick is to use the full UPN with the AzureAD\ prefix, but it has to be typed exactly as AzureAD\yourUPN (so in your case: AzureAD\jim@[Removed PII]..group). If that still fails, try just the UPN (jim@[Removed PII]..group) without the prefix some builds of the app accept one format but not the other

Another thing worth checking is whether the VM has the Azure AD login extension enabled; without that, the Windows App can choke on cloud identities even if RDP works fine. Also, make sure your Mac keychain isn’t caching old creds clearing saved credentials and re‑adding the workspace often fixes this. If you’re still hitting the same error, let me know the exact wording

Additional information -- I have installed the Mac Windows app (11.3.5, which appears to be the latest build) and connected to the VM using a local machine account, but I am unable to do so using my AzureAD account. When trying, I get to a login prompt for Other user and an error message "The user name or password is incorrect." I have tried using AzureAD\jim@[Removed PII].group and jim@[Removed PII].group, and neither works.

However, I have no problem connecting from my Parallels VM via RDP using both the local machine account and the Azure AD account. Further, I can see that jim@*[Removed PII].*group is identified as an Administrator, so this account is authenticated on our VM.

Good day Jim Perkins

I think you can connect via RDP inside Parallels but not through the new Windows App for Mac tells me the VM itself is fine the hiccup is more likely on the client side. A couple of things to check: make sure you’re running the latest version of the Windows App (they’ve been pushing frequent updates), and double‑check that the AIMS1 VM is added using the correct workspace or subscription context. Sometimes the app caches old credentials, so signing out and back in can clear that up

Also, confirm that the Mac firewall or any VPN you’re running isn’t blocking the connection the Windows App uses slightly different ports than the classic RDP client. If all else fails, try removing the VM entry from the app and re‑adding it fresh; that usually resets the handshake. If you’re still stuck after that, let me know the exact error message you’re seeing and we can dig deeper.

If everything is okay, don't forget to share your experience with the issue by "Accept answer". If you need more information, feel free to leave a message. We are happy to help!