Ok, so I have to admit so far I took everything that has been said here as granted, and did not actually test v116 in our environment. For testing purposes we set the recommended policy RestrictSignInToPattern to "*@ourcompany.com", plus for historic reasons we already had a few other GPO settings active which might affect our experience, such as:
- GuidedSwitchEnabled = Disabled
- BrowserGuestModeEnabled = Disabled
- NonRemovableProfileEnabled = Enabled
- forcesync = Enabled
- HideFirstRunExperience = Enabled
There are a lot of other policies, but skimming over them I think these are the most important ones which might explain the behaviour we are experiencing:
- On first run of v116, the end user gets a notification bar on top which hints towards that the is using the business version of the browser. He can close it or click the "learn more" button, which brings him to an MS Edge Marketing website.
(I would love to disable this notification bar!) - The user profile picture is on the top left. Yes, that sucks. But its not the end of the world
- Clicking on the user profile picture, the user can either
- set up an additional work profile -> he gets auto logged-in with his existing company user profile. Even if he refuses to type in his password, all company GPO settings apply. Fine with us
- set up a new personal profile (thats the new thing!!) -> he immediately gets a popup, telling him that (translated from german) "your profile does not have the permissions to login, please contact system administrator. You can continue to browse the web as a guest". There is no sign-in request or password field. This message appears as soon as he presses the "new profile" button
This leaves him at a dead end, he cannot create a personal profile/browser session. I think he cannot continue to browse as a guest, because we set the Policy BrowserGuestModeEnabled = Disabled. Fine with us.
We have a hybrid environment with Azure AD Seamless SSO set up.
While the overall experience is not great (Notification Bar, Error messages when creating a new personal profile, profile picture moved to the left side) it's not as bad as we initially thought, and we can continue to deploy v116.
Microsoft