@GossiTheDog@mttaggart Yeah, I didn't have a local AD ready to test. But I could definitely see a difference with authenticating RDP using a local account vs. an online account. With local accounts, the instant the password changes, the RDP client needs the new password. For online accounts, the old password still works, indefinitely.
@mttaggart I've seen no evidence that the RDP cred cache gets updated ever. Granted, I only started looking at this very recently, but the reporter seems to indicate that this is the case.
@wdormann@GossiTheDog But at any rate, with this configuration, I've confirmed that when I change my account password through account.microsoft.com or whatever, the old creds immediately cease to work for RDP access.
@wdormann@GossiTheDog Not over here. Now maybe this is because I'm using the Win11-Enterprise image, but for a clean build, you have to make sure you log in a second time with a non-Hello method (which is now basically enforced on first login).
And even then, I had to make sure enable "Use a Web account" in the RDP client settings.
@mttaggart@GossiTheDog In my case: Windows 11 Enterprise with a local account initially (via BYPASSNRO) I added a Microsoft (hotmail.com) account. I then turned on RDP. That's all. Absolutely nothing else.
If I log in via that hotmail account to RDP, it will accept the original cached password even if I change my hotmail account password.