This message was deleted.

well, they tried to eliminate it all together as configurable with Pre-HF1. Then HF1 after the uproar they at least put it back to where we can configure it. But then of course they are still leaning towards disabling it. honest answer; I think they are really trying to get customers to Azure hybrid or Azure join and get away from this. So yea, just enable it if you need it then (assuming you don't already have Azure AD Seamless SSO doing that where it would negate having to need to roam that around)

Ho okay, thanks for the info I guess I will have to stop blocking the aad join in the future. I don't really like it, I only had problems with it

its really up to you on that. This setting was just something MS changed and then gave us control back where they are 'encouraging' that hybrid join situation, but the roam identity works just fine right now again with that set if you need it. Who is to say though they might go and take it out again just to frustrate us in the next few releases. 😐

So... RoamIdentity was sort of enabled by default before MS decided to stick their nose into it?

Yea