Is a Meta Business Accounted to run Windows App (and Windows 365 Cloud PC) on Meta Quest 3?

Hi thanks for bringing this up.  Windows App is used differently between the two scenarios that we brought to public preview:

1. Windows App to a Windows 11 AAD PC or CloudPC for true remote desktop where the mouse and keyboard are connected to the Quest3.  In this scenario, Windows App is the primary application that is being used.  Documentation for Windows App in this scenario and the requirement to have Quest For Business can be found here.  https://review.learn.microsoft.com/en-us/windows-app/get-started-connect-devices-desktops-apps?branch=main&tabs=meta-quest-avd%2Cwindows-w365%2Cwindows-devbox%2Cmacos-rds%2Cmacos-pc&pivots=azure-virtual-desktop.
2. Meta's "Remote Desktop" that allows a Quest 3 to get to a MSA Windows 11 device that is in the same room uses Windows App in a passive mode (i.e. the user should never even launch it unless they are trying to capture logs to provide to Microsoft engineering / support teams).  This is the solution that has the mouse and keyboard attached to the PC that the Quest 3 is doing more of a "remote display" and requires Mixed Reality Link installed on the Windows 11 PC.  Using Windows App passively for this scenario does not require Meta's Quest For Business license.  

Let me know if that helps address your question.

Yeah I appear to have the same issue. Went through all the rigmorale of setting up a business account but it still doesn't work. Did you find a way round it. I'd like to use it to access AVD.