Share via

Windows App on Android not allowing sign in to Azure virtal desktops on personal profile

Joshua Roles 20 Reputation points
2026-05-08T09:59:18.82+00:00

We’re seeing an issue with Azure Virtual Desktop on Android and ChromeOS where users get a 0x1151 error when launching a session. Users can connect fine from Windows, MacOS and from a work profile if the device is enrolled with Intune, but they're unable to connect from a personal Android profile or ChromeOS.

There's no Conditional Access policies blocking sign in, but we do have screen capture protection enabled, and I've found similar posts stating it's a handshake error between the client and server because of this, but I can't see how that's the case if it's working on the work profile on the same device.

we're also have another issue on the personal profile when we have an app protection policy applied to the windows app where when the user tries to connect they get a MAM message stating that they've been signed out of a managed account and the remove the account and add it again, doing this just results in the same message so the user's not able to get far enough to run into the other issue.

The virtual desktops are running Windows 11 25h2 and are fully updated, and the android phone we're testing on is on Android 15 and the windows app is up to date.

Azure Virtual Desktop
Azure Virtual Desktop

A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.

0 comments

Answer accepted by question author

Himanshu Shekhar 6,145 Reputation points Microsoft External Staff Moderator
2026-05-08T11:40:09.87+00:00

Joshua Roles - The issue is due to Screen Capture Protection (SCP) compatibility limitations.

Microsoft states that Screen Capture Protection is client-dependent and requires supported clients - https://learn.microsoft.com/en-us/azure/virtual-desktop/screen-capture-protection?tabs=intune

Current guidance indicates SCP is supported on Windows and macOS Remote Desktop clients, and not supported on mobile or browser-based clients (e.g., Android, ChromeOS)

When a user connects from an unsupported client, the session may:

  1. fail to launch, or return connection-related errors (such as 0x1151)

Why behavior differs between profiles

Work profile (Intune-managed):

  1. Device/app is managed and compliant
  2. Policies and supported configurations are enforced → connection succeeds

Personal profile (unmanaged):

  1. Treated as an unsupported client scenario when SCP is enabled
  2. Results in connection failure due to SCP restrictions - MAM/App Protection issue (second symptom) - App Protection (MAM) on Android requires proper app registration and supporting components (e.g., Company Portal) . If the app is not correctly enrolled or policy state is inconsistent:

Users may see repeated prompts such as:

  1. “Signed out of managed account”
  2. “Remove and re-add account”

This behavior is typically seen in:

  1. Unmanaged (personal) profiles
  2. Improper or incomplete MAM enrollment state

Recommended actions we can suggest -

  1. Validate SCP impact
  2. Temporarily disable SCP and test Android/ChromeOS access

Platform decision

Either: Allow only supported clients (Windows/macOS) or disable SCP for cross-platform access

Fix MAM issue

Ensure:

  1. Company Portal installed
  2. Proper MAM enrollment completed
  3. Reinstall Windows App and re-register the account if needed

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.