Open tonyrosas opened 4 years ago
we have the same issue here
Does anyone have any suggestions?
We fixed 2 things:
First was silly one, as we had never logged with the new account
Second was to add the user a right to create AAD applications. "Application developer" -role.
After these changes the deployment was successful
@rseppala thank you very much for the suggestion. The Azure admin user principal name I put into the template was my own and I am a global admin and have deployed several other AAD applications. I will try giving myself the Application developer role just to make sure and try again.
When you tried again did you use the redeploy option or delete what was created and started over?
We had already deleted, so no experience if redeploy would do. Did you get it up'n running?
@rseppala I did not, I deleted the entire resource group for now and we will be holding off for the official Microsoft Management tool for now. It was just released on Friday with the migration utility coming soon.
I followed the Microsoft documentation. https://docs.microsoft.com/en-us/azure/virtual-desktop/delegated-access-virtual-desktop
It deployed several automation accounts, 12 of them, then on the 13th one, it sat there for 2 hours and 12 seconds then timed out. The operation name is "Create an Azure Automation job". I am a global admin as well and do not use MFA.
"error": { "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": "RequestTimeout", "message": "{\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource provision operation did not complete within the allowed timeout period.\"\r\n }\r\n}"