Azure Virtual Desktop Login Error Code 0x3000047

Question

Azure Virtual Desktop Login Error Code 0x3000047

Kanishka Dobhal | Redington 41

Hi

We have been facing issues with logon to Azure Virtual Desktop Windows machine for couple of users in Personal Hostpool.
Users get error when logging on using RDP Client app or the Web Client.

Error Code 0x3000047 and screenshot attached.

Other users in same hostpool can connect without any issues.
We have a hybrid AD architecture and both On-Prem and AAD are in Sync.

Any help on this would be highly appreciated.
It has been a nightmare users machines breaking during production hours with no detailed information/logs on portal.

Thanks
Kanishka

Rochelle Saclot 1 Reputation point

2022-07-26T07:21:30.007+00:00

Hi @Kanishka Dobhal | Redington am experiencing the same issue with you. what is the steps to re joining the machine in the domain? do I need to delete the device of the affected user on MEM admin center?

hoping to get response as soon as possible.
Manoj Chowdhury 0 Reputation points

2025-03-03T20:00:53.9266667+00:00

I also have the same issue from few of users in my organisation, the shared resolution here does not work so if anyone can provide the answer will be good. https://techcommunity.microsoft.com/t5/azure-virtual-desktop/error-when-connecting-to-mvd-0x3000047/m-p/1242145
Vu Hoang 5 Reputation points

2025-03-03T21:12:15.8166667+00:00

@Manoj Chowdhury
This issue was resolved for me after i found that we had to disconnect our Azure AD (Entra ID) from our old connected on-prem AD domain for authentication so it can authenticate with the proper domain for it. This was due to recent AD migrations. Hope this hint helps.

2 answers

Your answer

Rochelle Saclot 1 Reputation point

2022-07-26T07:21:30.007+00:00

Hi @Kanishka Dobhal | Redington am experiencing the same issue with you. what is the steps to re joining the machine in the domain? do I need to delete the device of the affected user on MEM admin center?

hoping to get response as soon as possible.
Manoj Chowdhury 0 Reputation points

2025-03-03T20:00:53.9266667+00:00

I also have the same issue from few of users in my organisation, the shared resolution here does not work so if anyone can provide the answer will be good. https://techcommunity.microsoft.com/t5/azure-virtual-desktop/error-when-connecting-to-mvd-0x3000047/m-p/1242145
Vu Hoang 5 Reputation points

2025-03-03T21:12:15.8166667+00:00

@Manoj Chowdhury
This issue was resolved for me after i found that we had to disconnect our Azure AD (Entra ID) from our old connected on-prem AD domain for authentication so it can authenticate with the proper domain for it. This was due to recent AD migrations. Hope this hint helps.

Answer 1

Jeff Rash 10

We get that exact error from time to time for hours on end, during which we can't connect for more than 2 seconds until the connection is dropped. And this is on two different AVD sessions in two different regions. Restarts and deallocations of the VM's don't help.

Then, miraculously, hours later or the next morning, everything is fine again for 2-3 weeks. Until it all goes to pieces again, and we have another 2-8 hours of connectivity issues. I think this can also be caused by performance issues on Microsoft's end.

We have three users from three different US time zones having the same issue at the same time each time this happens. Then all of a sudden, we can all get on again.

Vu Hoang 5 Reputation points

2023-08-14T03:32:02.7833333+00:00

Agreed. This is really a bit of a mystery occurrence. Tried various fixes suggested from Microsoft forums and from other sites, including the registry fixes that claimed to work (on top of removing it from host pool, rejoin domain, uninstalled all RDAgents software, re-register with new token, etc.) It does worked for a couple but then it does not for a few others. But then next day or so, things are ok again without any other fixes added. Would really love to know the root cause of this to better support the mass audience.
Vu Hoang 5 Reputation points

2023-08-14T03:35:09.1+00:00

.....

Answer 2

vipullag-MSFT 26,486 Moderator

@Kanishka Dobhal | Redington

Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

Based on the error screenshot, the reason is "ConnectionFailedAdTrustedRelationshipFailure". This could mostly be issue with UPN being synced to Azure or because of user system domain issue.

Below are similar issue which has troubleshooting steps and hints on resolving the issue.

https://techcommunity.microsoft.com/t5/azure-virtual-desktop/error-when-connecting-to-mvd-0x3000047/m-p/1242145
https://github.com/MicrosoftDocs/azure-docs/issues/55687

Hope this helps.

Kanishka Dobhal | Redington 41 Reputation points

2021-08-02T12:17:11.417+00:00

Thanks for the response @vipullag-MSFT . I have verified the UPNs multiple time.
The issue is with almost 20 users and none of the users have UPN mismatching on AD-DS and AAD. We end up re-joining the machine to domain in order to fix the error.
Not sure what is causing this.

In the same host pools there are users who do not face any issues, these users have the same rights as the non-working users.
In terms of the links shared, I have gone through it quite a few times.

Has anything changed recently for AVDs recently in terms of login methods? We have been using AVDs for almost 6 months now and this error has started only last month.
If there was a UPN or a sync issue that should have caused the login error from the date we deployed host pools.
vipullag-MSFT 26,486 Reputation points Moderator

2021-08-09T09:49:05.06+00:00

@Kanishka Dobhal | Redington

Thanks for responding back.
Glad to hear that the issue is resolved now.

For getting the exact root cause for the issue, support team will be able to check and share this. Would request you open a support case for getting this investigated.
Vu Hoang 5 Reputation points

2023-08-14T04:15:14.6866667+00:00

@vipullag-MSFT This is really a bit of a mystery occurrence. Tried various fixes suggested from Microsoft forums and from other sites, including the registry fixes that claimed to work (on top of removing it from host pool, rejoin domain, uninstalled all RDAgents software, re-register with new token, etc.) It does worked for a couple but then it does not for a few others. But then next day or so, things are ok again without any other fixes added. Would really love to know the root cause of this to better support the mass audience.

Share via

Azure Virtual Desktop Login Error Code 0x3000047

2 answers

Your answer