question

IainJackson-2787 avatar image
0 Votes"
IainJackson-2787 asked ChrisWilson-0216 answered

Can't remove old classic WVD feed from appearing

One of my predecessors set up a WVD environment back when it was powershell only - a classic deployment. I was added to the app pool at the time as an end user only. The subscription has since been deleted and the WVD admin Azure AD account no longer exists. Fast forward to today and I have created an ARM based WVD deployment which works great, only I can still see the old classic feed in the Remote Desktop App which obviously doesn't work, but I have no way of getting rid of it. I have tried powershell using my Azure Admin account but Get-RdsTenant and Get-AzWvdWorkspace both return blank. Get-RdsHostPool returns a not found error also. Is there any way to unpublish/remove this classic feed?

azure-virtual-desktop
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We have the same situation where we do not know the name of the WVD tenant but I believe the subscription is still around. Adding the TenantCreator role did not immediately resolve the problem as we still could not query the tenant name using Get-RdsTenant. Maybe we have to wait for it to be synced to Microsoft end of things?

0 Votes 0 ·
vipullag-MSFT avatar image
0 Votes"
vipullag-MSFT answered IainJackson-2787 commented

@IainJackson-2787

Apologies in delayed response.

You need to assign Tenant creator role to your user following this guide and then remove all the classic artifacts using the old RDS powershell cmdlets.

Hope this helps.

Please 'Accept as answer' if the provided information is helpful, so that it can help others in the community looking for help on similar topics.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the reply. I have the Tenant Creator role assigned but to no avail:
Get-RdsTenant -Name "Default Tenant Group"
Get-RdsTenant : User is not authorized to query the management service.

Also I don't know the original subscription ID as I believe it has already been removed or expired. Can you think of anything else that might help?

0 Votes 0 ·
ChrisWilson-0216 avatar image
0 Votes"
ChrisWilson-0216 answered

@IainJackson-2787/@tommihovi - We just went through a similar situation here and found that the old tenant was set up using a Service Principal.

Check Azure Active Directory > App Registrations > All applications to see if there are any Service Principals that were used to create your Classic deployment.

If there is, create a new secret and connect in this manner:

 $aadtenant = "Directory (tenant) ID"
 $appid = "Application (client) ID"
 $secret = "Client Secret (value)"
    
 $creds = New-Object System.Management.Automation.PSCredential($appid, (ConvertTo-SecureString $secret -AsPlainText -Force))
 Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com" -Credential $creds -ServicePrincipal -AadTenantId $aadtenant
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.