I cannot connect to our VM from my Mac

The first thing I did during our first VM install attempt was to authenticate with my Azure AD credentials, but that didn't work. Then I tried to log in with the local account and add a work account using my AzureAD credentials, and that works for connecting from my Parallels VM but not from my Mac.

Assume I'm a customer with only Macs and want to install a Windows Server VM -- I hope Microsoft's answer isn't "sorry we can't support you." Does Microsoft have prescriptive guidance to address this need? At this point, I've screwed around enough trying to get this working that I'm ready to try a third rebuild of the VM based on the 'I only have Macs' user scenario.

Microsoft does support Mac‑only customers connecting to Windows Server VMs, but the key is enabling Azure AD login correctly and using the right client setup. The Windows App for Mac works, but it requires the VM to be provisioned with the Azure AD login extension and policies aligned otherwise you’ll hit the “login method not allowed” error.

Guidance for Mac‑Only Users

VM Edition Requirement

Use Windows Server 2019/2022 Datacenter or Windows 10/11 Pro/Enterprise. Azure AD login is only supported on these editions.

Enable Azure AD Login at Creation

When creating the VM in the Azure portal, select “Login with Azure AD credentials” in the Management blade. This automatically enables a system‑assigned managed identity and installs the Azure AD login extension.

If VM Already Exists

You can still enable Azure AD login afterward by:

Assigning a system‑managed identity to the VM.

Installing the AAD login extension via PowerShell or Azure CLI.

Ensuring outbound connectivity to Microsoft’s public endpoints for authentication.

Client Setup on Mac

Install the latest Windows App for Mac (11.3.5 or newer).

Add the VM using its public IP or DNS name.

Use the AzureAD\UPN format (AzureAD\jim@psaskincare.group) or just the UPN (jim@psaskincare.group) depending on the app build.

Clear cached credentials if you’ve tried multiple formats.

Network & Policy Checks

Ensure TCP 3389 is open in the VM’s NSG inbound rules.

Confirm Network Level Authentication (NLA) is enabled.

Verify the Azure AD account is added to the Remote Desktop Users group or granted access via RBAC

This issue is most likely related to the new Windows app for macOS client configuration or compatibility, rather than the target VM itself, since RDP works correctly from a Windows-based environment (Parallels VM).

The Windows app for Mac uses a different connection stack compared to traditional Microsoft Remote Desktop, and it may be affected by:

• Incorrect workspace or feed configuration in the Windows app
• Credential or authentication method mismatch (e.g., saved credentials vs manual login)
• Network/security settings on macOS blocking specific app components
• Version-related limitations or bugs in the new Windows app for macOS

Recommended actions:

• Verify the workspace is correctly added and refreshed in the Windows app
• Remove and re-add the connection to clear cached configuration
• Ensure the latest version of the Windows app for macOS is installed
• Test with manual RDP settings if supported, to isolate workspace-related issues

Since connectivity works via Parallels RDP, the VM and network path are confirmed as healthy, and the issue is isolated to the Mac Windows app client layer.This issue is most likely related to the new Windows app for macOS client configuration or compatibility, rather than the target VM itself, since RDP works correctly from a Windows-based environment (Parallels VM).

The Windows app for Mac uses a different connection stack compared to traditional Microsoft Remote Desktop, and it may be affected by:

• Incorrect workspace or feed configuration in the Windows app
• Credential or authentication method mismatch (e.g., saved credentials vs manual login)
• Network/security settings on macOS blocking specific app components
• Version-related limitations or bugs in the new Windows app for macOS

Recommended actions:

• Verify the workspace is correctly added and refreshed in the Windows app
• Remove and re-add the connection to clear cached configuration
• Ensure the latest version of the Windows app for macOS is installed
• Test with manual RDP settings if supported, to isolate workspace-related issues

Since connectivity works via Parallels RDP, the VM and network path are confirmed as healthy, and the issue is isolated to the Mac Windows app client layer.