This was a nice feel good story but for organizations with dependencies on services for DNS, DHCP and legacy applications as well as having computers joined to AD this story only proves that the journey is that much harder for complex and legacy organizations. It does give a lot to look forward to if you can get past some of the major humps.
In the part about 'User Accounts & Groups: The Shift to Cloud-Only Identities' the process they used is to disable the account on premise and then reenable it in the cloud.
Is this a supported way of doing this?
As I know, the only supported way is to disable Sync and then enable it again for users that should still be hybrid.
I found some posts about private preview from 2022 that will support Individual user object converting from synced to cloud only. Has this feature ever evolved?
This was a nice feel good story but for organizations with dependencies on services for DNS, DHCP and legacy applications as well as having computers joined to AD this story only proves that the journey is that much harder for complex and legacy organizations. It does give a lot to look forward to if you can get past some of the major humps.
Hi
In the part about 'User Accounts & Groups: The Shift to Cloud-Only Identities' the process they used is to disable the account on premise and then reenable it in the cloud.
Is this a supported way of doing this?
As I know, the only supported way is to disable Sync and then enable it again for users that should still be hybrid.
I found some posts about private preview from 2022 that will support Individual user object converting from synced to cloud only. Has this feature ever evolved?
Regards Georg