Forum Discussion
PUBLIC PREVIEW: Announcing public preview of Azure AD joined VMs
- Jul 15, 2021End-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.
DavidBelanger I failed to create hostpool with Azure AD joined VM. Every time I got the message:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'AADLoginForWindows'. Error message: \"AAD Join failed.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot "}]}
I tried on 2 different Azure tenants and from different PCs and got the same result. What did I miss?
tch0704 I had the same problem. This issue was, that enabled the option to use Intune device management without having an Intune license in place. Disabling the option solved it.
- tch0704Jul 22, 2021Copper ContributorYes it works after I turn off the Intune option. However, the user accounts actually have Enterprise Mobility + E5 license. Can I enable Intune after the host pool is created?