Forum Discussion
Add-RdsAccount : One or more errors occurred.
Hi to all! I'm Testing the new Windows Virtual Desktop on Azure... I'm following this link https://docs.microsoft.com/en-us/azure/virtual-desktop/tenant-setup-azure-active-directory to create t...
Hi all,
I was observing al AAD relation between my subscriptions and this is the conclusion that solved my problem.
1. I am a Global Admin (Guest User) of a AAD where i was creating the WVD Service, like the guide says.
2. I observed that when you log-on with add-rdsaccount it takes the aadid of your account not the one that you are using to create the service, so in my case will never get that i was a Global Admin of the AAD that i was really using. I know it seems obvious but, Cause my account was member from another AAD ID.
3. So i created a new global admin user in the AAD that i used to register the WVD Service.
4. I run again the aad-rdsaccount and the command runned without problem.
So my recommendation is to see back on the aadid that you registered and verify that the account it's not only global admin so also it's should appears like a member of the AAD where you registered the WVD Enterprise Application.
Hopes it helps you Jez85
Thanks a lot! It worked!
Just ran into this issue.
The $creds for a Service Principal expire after some time, and an expired credential will throw this vague error.
You can re-generate your Service Principal's password using:
$svcPrincipalCreds = New-AzureADApplicationPasswordCredential -ObjectId "your-service-principal-id"
Use Get-AzureADApplication to find your principal's ID if you don't have it.