Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Remote Desktop to a Microsoft Entra-joined server: "The sign-in method you're trying to use isn't allowed"

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Microsoft's page for signing in to Windows virtual machines in Azure with Microsoft Entra ID gives this message as an MFA problem: "The sign-in method you're trying to use isn't allowed. Try a different sign-in method or contact your system administrator." It appears when you start a remote desktop connection to a machine that uses Entra sign-in and the multifactor authentication demand cannot be met by the way you are signing in.

Check two things in order: the Conditional Access policy that requires MFA and the user's per-user MFA state. Microsoft's page does not link the message to a Windows "log on locally" right.

What the error means

Microsoft's page describes the feature: Microsoft Entra ID can be the authentication platform for Remote Desktop Protocol sign-in to supported Windows Server virtual machines, with Azure role-based access control and Conditional Access policies deciding who gets in. It lists the supported distributions as "Windows 11 24H2 or later installed" and "Windows Server 2022, 2025 or later installed with Desktop Experience."

Two conditions decide whether a connection can start at all. Microsoft's page says remote connection to machines joined to Entra ID "is allowed only from Windows 10 or later PCs that are either Microsoft Entra registered(minimum required build is 20H1) or Microsoft Entra joined or Microsoft Entra hybrid joined to the same directory as the VM". Users must also hold the Virtual Machine Administrator Login or Virtual Machine User Login role. Microsoft's page adds that having the Owner or Contributor role alone does not grant sign-in privileges, so a user with only those roles cannot connect this way. Microsoft's Remote Desktop troubleshooting page lists this message under "Troubleshoot sign-in issues when users RDP with Microsoft Entra credentials", next to three other Entra errors. A missing role gives a different message: "Your account is configured to prevent you from using this device. For more info, contact your system administrator."

For this message, Microsoft's page says: "If you configure a Conditional Access policy that requires MFA, you need to ensure that the device initiating the connection uses strong authentication such as Windows Hello."

Likely causes

Cause What you see How to confirm
A Conditional Access policy requires MFA and the device signs in with a password only The message appears on the connecting PC The policy applies to the VM sign-in app; the PC does not use Windows Hello
Legacy per-user MFA is Enabled or Enforced for the user The message; Microsoft's page also lists "Your credentials didn't work." as another MFA-related message Per-user MFA state for the user

Prove the cause before changing anything

All of these read only.

Microsoft's page says you can view the device and single sign-on state by running the command below; it does not name the machine, so run it on the PC that fails:

dsregcmd /status

The goal it states is "AzureAdJoined : YES" for the device state and "AzureAdPrt : YES" for the SSO state. Microsoft also says RDP sign-in through Entra accounts is captured in Event Viewer under Applications and Services Logs\Microsoft\Windows\AAD\Operational.

To read the user's per-user MFA state, sign in to the Microsoft Entra admin center as at least an Authentication Policy Administrator, browse to Identity > Users > All users, select Per-user MFA and find the user. Microsoft's page defines the states: Disabled (the default), Enabled and Enforced. It says "All users start out Disabled", that enrolling a user changes the state to Enabled, and that "When enabled users sign in and complete the registration process, their state changes to Enforced." It adds that "Administrators may move users between states, including from Enforced to Enabled or Disabled." The state you read is therefore a record of what has happened to that account, so write it down before anyone changes it. Or read it with Microsoft Graph (Beta):

GET /users/{id | userPrincipalName}/authentication/requirements

A user enrolled in per-user MFA returns a response such as "perUserMfaState": "enforced".

Example (illustrative): at contoso.com.au staff connect from laptops to rds01, an Entra-joined Azure server. After a new Conditional Access policy requires MFA for the VM sign-in application, a contractor on an older PC sees "The sign-in method you're trying to use isn't allowed". dsregcmd /status on the PC shows "AzureAdJoined : YES", so the device is joined; the PC does not use Windows Hello. The contractor's per-user MFA state is Disabled. The cause is the policy and the way the PC signs in.

Fix

Microsoft's page gives these routes. The first needs no change to tenant settings.

Use strong authentication from the device

Microsoft's page says "Support for biometric authentication with RDP was added in Windows 10 version 1809." It states the trust-model condition two ways. The troubleshooting section says Windows Hello for Business authentication during RDP "is available for deployments that use a certificate trust model or key trust model." Its requirements list says "Windows Hello for Business is supported using the certificate trust model only (not key trust model)", and its RDP section says it "is available only for deployments that use a certificate trust model and isn't available for a key trust model". Treat certificate trust as the supported case and confirm a key-trust deployment with Microsoft before relying on it. Sign in to the connecting PC with Windows Hello and retry. This changes nothing on the server.

Remove legacy per-user MFA

Microsoft's page calls "Your credentials didn't work." another MFA-related error message, described earlier on the same page. It says that if per-user Enabled/Enforced MFA is set and the error appears, you "can resolve the problem by removing the per-user MFA setting." Microsoft's per-user page says changing user states "isn't recommended unless your Microsoft Entra ID licenses don't include Conditional Access and you don't want to use security defaults."

Before you change it, record the user's current state and keep the value it returns:

GET /users/{id | userPrincipalName}/authentication/requirements

Risk: the next request sets this user's per-user MFA state to disabled. The user then stops being asked for per-user MFA at every sign-in, not only to this server. If Conditional Access or security defaults do not already cover this user, the account loses its only MFA. Microsoft's page calls this API Beta.

Microsoft's page shows the request:

PATCH https://graph.microsoft.com/beta/users/<user-id>/authentication/requirements
Content-Type: application/json

{
  "perUserMfaState": "disabled"
}

A successful call returns HTTP/1.1 204 No Content.

To undo it, send the same request with the state you recorded. Microsoft's per-user page says not to move a user to Enforced by hand unless the user is already registered, so send the recorded value, whatever it was:

PATCH https://graph.microsoft.com/beta/users/<user-id>/authentication/requirements
Content-Type: application/json

{
  "perUserMfaState": "<recorded state>"
}

Exclude the VM sign-in app in Conditional Access

Microsoft's page says: "If Windows Hello for Business isn't an option, configure a Conditional Access policy that excludes the Microsoft Azure Windows Virtual Machine Sign-in app." The page gives no portal steps for that exclusion, and an exclusion takes that application out of the policy's MFA requirement. That is a decision for the people who own the tenant's security policy. No steps are given here; record the policy's current exclusions before anyone changes it.

A missing sign-in application is a separate problem

Microsoft's page treats a missing application as its own problem, under the heading "Missing application", with its own steps. It is not given as a cause of this message, so it has no place in the fix for this error. If the message on your screen is different, read that section of Microsoft's page instead.

Confirm the fix

  • Connect again from the PC that failed. The message should not return.
  • Run dsregcmd /status on the PC and check both values still read YES.
  • Read the AAD Operational log for the sign-in.

What to watch afterwards

  • Conditional Access changes to the policies that apply to the VM sign-in application.
  • Users whose per-user MFA state was Enabled and moved to Enforced after registering.
  • New hosts, since each machine must meet the same sign-in requirements.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's page covers Windows virtual machines in Azure with Microsoft Entra sign-in. It does not say whether the message has other causes on servers outside that setup. The Graph request is a Beta API, and portal labels change. Removing MFA from an account or from a policy lowers protection until it is put back.

Sources