Forum Discussion
MicrosoftPUBLIC PREVIEW: Announcing public preview of Azure AD joined VMs
- End-to-end single sign-on is definitely something we are working on but isn't available in the first release due to the protocol we are using. We know how important that feature it.
Hello everyone,
A question, does this solution need to have local domain control?
my structure is 100% Azure
MicrosoftHi, David
I'm creating an environment through the azure portal following local steps, but putting the user's permission on the app when I try to access the remote desktop tool whenever I get error 0x30000047
Attached is the print of the permissions on the host and on the application
I don't know if there would be any other configuration to be done after deployment. what I
noticed is that whenever the deployment ends the host's status becomes Unavailable
NOTE: I don't have Azure AD DS enabled in my environment, only Azure Active Directory and Intune
- DavidBelangerJust to make sure, are you following the steps at: https://docs.microsoft.com/azure/virtual-desktop/deploy-azure-ad-joined-vm
Need to ensure the Host Pool is set to the validation environment and that you set the right RBAC role on the Resource Group or VM itself.I managed to create two different Host Pools, each with its VM and application publishing, working 100%.
but now i'm trying to create again and the VMs are only with the status Unavailable, with this error it is not possible to work with access via RDP publishing.
I've already performed both procedures
https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-agent#error-vms-are-stuck-in-unavailable-or-upgrading-statehttps://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-agent#step-1-uninstall-all-agent-boot-loader-and-stack-component-programs
but without success, any other procedure to perform and try to fix this error?
