Apr 09 2019 11:31 PM - edited Apr 09 2019 11:31 PM
May 29 2019 01:12 PM
You can setup the management UI using the following instructions. This is not integrated into the Azure portal but a standalone AppService-based UI:
To start, go to this GitHub URL.
If you're deploying in an Enterprise subscription, scroll down and select Deploy to Azure, then skip ahead fill out the parameters.
If you're deploying in a Cloud Solution Provider subscription, follow these steps to deploy to Azure:
Here is the guidance on the parameters you should enter:
To launch the UI, click on appservice with name you provided in the template (e.g. Apr3UX) and navigate to the URL associated with it (e.g. https://rdmimgmtweb-210520190304.azurewebsites.net)
Sign in using the Your Windows Virtual Desktop credentials.
Apr 06 2020 08:21 AM
There has not been any activity on this in a while. Did the portal get released and I missed it? Any update would be great.
Sep 09 2020 05:18 AM
Sep 15 2020 05:24 AM
Hi @Pavithra Thiruvengadam, We are already using portal.azure.com. But all the Host Pools and WVDs created earlier (via PowerShell) are not visible in the portal.
For example in Azure FreeTrial mode we created entire WVD stack. Post expiry we moved to PayAsYouGo mode. Now the subscription ID is changed. However we managed to clear most of the earlier parameters and created WVDs and a Win2019 server as DNS. We are stuck in one step of "New-RdsRolesAssignment". Get-RdsRolesAssignment has earlier Subscription's App ID. Now the Subscription ID and App ID is different. There is no way we can change or remove that. We hit a dead end and cannot use the created WVD.
We don't have access to the data where MS manages RdsRolesAssignment, RdsTenant etc.
When you can't see any of the previously created Host Pools or associate a TenantName with HostPool using PowerShell/ISE or Portal is there any solution at all?
Sep 15 2020 10:32 AM
I believe all this info has been documented in various places - you cannot manage Classic resources using Azure portal. You will need to create new ARM resources or migrate the existing Classic ones to manage using the portal. Migration can be manual if you have a small WVD env but for larger env, we request you to wait for our automation tool - No ETA. @RajVenkat
I think you also have different problem - did you move a subscription from 1 AAD tenant to another?