Microsoft Edge not passing through "Domain Joined" on terminal server.

Question

Hi all,

I have a CA policy only granting access if EITHER the device is compliant or hybrid joined it doesn't have to be both.

Works fine on all windows 10/11 devices, but on any of the servers it's not working, it stopped monday the 24th of july.

All other apps work on the servers when the CA policy is applied including Outlook. But as soon as you open Edge even being signed into the "work" profile it gives me the error 53000, i have also tried a new CA policy making it hybrid joined only option and gives me the error "this device is not domain joined" dsregcmd clearly states that it is domain joined and Outlook app works. Even excluding the device ID doesnt work in the CA policy.

After doing more digging i've found that it seems Microsoft Edge isnt pushing through the details of the "joined type".

Has anyone else seen this issue? i know Microsoft have changed the servers to be listed as servers now intune as per link. https://techcommunity.microsoft.com/t5/intune-customer-success/windows-server-devices-now-recognized-as-a-new-os-in-intune/ba-p/3767773

Not sure if this has anything to do with it, but my OS still just says "Windows".

MS support have been lacking. Will update when i have more.

Thanks!

UPDATE

I have confirmed it is Microsoft Edge not pushing throught the information about being domain joined, no fix yet, i have tried multiple versions and still no luck including the beta version.

Certainly looking for a fix as everything else looks correct.

Answer 1

Can confirm, that Azure hybrid joined state not passed on Terminal server with Windows 2016, with MS Edge version 144.0.3719.82

Perhaps the same happens on Windows 10 LTSB 2016, with MS Edge version 144.0.3719.82

Answer 2

Hi @Kent Trigwell ,

What edge version are you using? Has your edge been updated recently?

After upgrading to Edge 115, only in Windows Server 2016 platforms, a PRT is not sent to login.microsoftonline.com as expected, breaking SSO and/or blocking access to resources protected with Conditional Access policies.

Downgrading to Edge 114 allows the issue to be resolved.

In the meantime, the Edge product team has completed their investigation and has identified this issue in Edge 115, that will be fixed soon.

Regards,

Wenying Lu

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.