(replace hobo.cloud with your Windows Virtual Desktop tenant name)Run the following command to add the RDS Owner role to the Service Principal. For the next steps you need to go back to the Configure the virtual machines, in my case I will create two D4s v3 VM’s. Set Now that the Service Principle is working for the “When looking in the management console, you see that the old two VM’s are removed from the Hostpool, and the four new ones are added.Great article – I have also struggled with this. After troubleshooting without success, I decided to open a In this blog I will show you step-by-step how you can create a Service Principal that you can use to provision a new Windows Virtual Desktop Host pool via the “Windows Virtual Desktop – Provision a host pool” wizard within the Microsoft Azure Portal, AND the ARM Template to Update an existing Windows Virtual Desktop hostpool. To install the module, run PowerShell as an administrator and run the following cmdlet:Follow all instructions in this article in the same PowerShell session. To solve this navigate to App Registration > “WVD Service Principal > Overview and on the right hand side you will see the heading “Managed application in” and it will say “Create Service Principal” click this and it will complete the creation of the Service Principal into “Enterprise Applications” and can be used to redeploy and add into RBAC roles in required groups and subs. A role assignment has three components: security principal, role definition, and scope. This then works with RDS broker for powershell login but I couldn’t use it for redeployment as Azure login does not recognize it. I will do this in the following steps:Give this application a name, in this case I will give it the name Give the client secret a name, in this case I will use Run the following command and login with a Windows Virtual Desktop RDS Owner roleRun the following command. Deploy WVD through marketplace. It's free and you can unsubscribe at any moment. The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. To learn more about host pools, continue to the tutorial for creating a host pool in Windows Virtual Desktop. Click Configure the Image source (for now I will keep it with a Gallery image) and fill all the other requested information in. It’s the only virtual desktop infrastructure (VDI) that delivers simplified management, multi-session Windows 10, optimizations for Microsoft 365 Apps for enterprise, and support for Remote Desktop Services (RDS) environments. Make sure to sign in with an account that has permissions to create role assignments.Run the following PowerShell cmdlets to connect to Windows Virtual Desktop and display your tenants.When you find the tenant name for the tenant you want to create a role assignment for, use that name in the following cmdlet:After you create a role assignment for the service principal, make sure the service principal can sign in to Windows Virtual Desktop by running the following cmdlet:After you've signed in, make sure everything works by testing a few Windows Virtual Desktop PowerShell cmdlets with the service principal.After you've created the service principal and assigned it a role in your Windows Virtual Desktop tenant, you can use it to create a host pool. Prerequisites. Now select Service principal as Windows Virtual Desktop tenant RDS Owner and fill in the Application ID, Credentials, and your Azure AD tenant ID. Some time ago, I wrote a blog about How to provision a Windows Virtual Desktop (WVD) Host Pool with Service Principal in the case that MFA is enabled for (every) user/admin in the Azure environment and you cannot provision a Windows Virtual Desktop hostpool. Windows Virtual Desktop is a comprehensive desktop and app virtualization service running in the cloud. I followed the MS WVD deployment documents to create a service principal using “New-AzureADApplication”, this creates the App Registration and then you add the credential (secret). Click Fill in the Windows Virtual Desktop information. This enables me not only to give independent advice, but also to carry out the implementations. The password is especially important because you won't be able to retrieve it after you close this PowerShell session.Here are the three credentials you should write down and the cmdlets you need to run to get them:Next, you need to create a role assignment so the service principal can sign in to Windows Virtual Desktop. Next step is to follow this Microsoft doc: The Windows Virtual Desktop delegated access model is based on the Azure RBAC model. Click Next : Review + create Click Create The deployment of the Windows Virtual Desktop Host Pool is now underway. It is the only virtual desktop infrastructure (VDI) that delivers simplified management, multi-session Windows 10, optimisations for Microsoft 365 Apps for enterprise and support for Remote Desktop Services (RDS) environments.
Create your own key and save the value During the next step, deploying Windows Virtual Desktop from the marketplace, in step 3 of that template you need this password. By continuing to use the site, you agree to the use of cookies. Sign in to Windows Virtual Desktop by using the service principal.
