- last edited on
We’re continuing to make progress on converging the Azure AD and Microsoft account identity systems. One of the big steps on this journey is to redesign the sign-in UI so both systems look consistent. We're happy to announce that this updated design is in public preview!
Read more about it in the Enterprise Mobility & Security blog.
08-07-2017 09:08 AM - edited 08-07-2017 09:19 AM
Can I revert back to the old signin? This morning my Office desktop apps do not recognize my Office 365 credentials. I want to revert back to see if the issue is the new signin.
My device is Azure AD JOINed, running Click-to-Run office 365 ProPlus, 1707 8326.2070.
08-07-2017 01:52 PM
According to the comments section on this blog, https://practical365.com/blog/surprise-new-office-365-sign-experience-end-users/, clearing out your IE cache and staying with the old sign in fixes the office desktop apps issue.
Best of luck.
08-07-2017 03:55 PM
Also, there's a opt-out link at the bottom right in the new UX where you can go back to the old experience if you need it in the future.
08-10-2017 07:14 AM
08-10-2017 07:14 AM
Hi @Eric Starker, is there a way to force the new experience and remove the option to go back to the old one?
My team and I are launching our new SPO-based intranet at the end of the month and we don't need the added confusion of "which way do we log in?" popping into our change management plan.
I'd also rather they learn and know the new system as opposed to training on the old one then announcing the new one when it's the only option soon after our intranet launch.
Anything to simplify our process is appreciated.
08-10-2017 10:04 AM
08-10-2017 10:04 AM
Hi Matt, I'm a Program Manager working on the new UI. I'll reach out to you via PM to discuss your request.
08-22-2017 03:13 AM
09-04-2017 12:17 AM - edited 09-04-2017 12:38 AM
@Eric Starker and @Kelvin Xia, I have the same question as @Paul Spurrell. We enabled auto-acceleration for SharePoint Online which worked fine with the old sign-in experience but doesn't seem to work with the new one.
Kelvin mentioned in a comment on another conversation that it may be related to another change pushed out by O365 around the same time: https://techcommunity.microsoft.com/t5/Office-365/New-sign-in-experience-for-Office-365-what-s-it-ab...
Any status on that?
09-05-2017 05:52 PM
09-05-2017 05:53 PM
09-05-2017 11:55 PM
I can verify that it doesn't seem related to the new sign-in experience as I'm prompted for login even with the old one.
I'm basically back to where we were before enabling auto-acceleration, i.e. when I enter the URL of one of our SPO sites I get redirected to login.microsoftonline.com to sign in.
This happens in both Chrome and IE11.
09-06-2017 06:03 AM
I just tried again this morning, and Seamless SSO, via Azure AD Connect, when combined with SharePoint Online auto-acceleration automatically logs me in to our SPO site, via the old sign-in experience. However, when accessing our SPO site, via the new sign-in experience, it still requires clicking on my username.
09-06-2017 06:11 AM
I can confirm it still doesn't work!
I even raised a premier support call for this and they told me monday 5th September its not resolved yet .
Transcript from call
- At the moment, for new experience the KMSI option is only available for cloud users.
- I have already validated internally and the back end team is aware of this issue and currently working on implementing a better experience for the KMSI.
- There is no available ETA, however this is treated as high priority as multiple customers are having the same issue
- The new expected behavior will be available before the “New sign-in experience” will be enabled as default
09-07-2017 11:26 PM - edited 09-07-2017 11:27 PM
Fired up IE this morning and tried to visit our site and this time it correctly redirected via the various MSFT login urls and our ADFS and finally logged me in without interaction. It also works fine when in Chrome now.
Perhaps the mentioned update reached our tenant/AAD or whereever the bug was?
09-08-2017 03:57 AM - edited 09-08-2017 04:02 AM
I can confirm the issue is still there when accessing a site collection.
Auto-acceleration works fine for the default site collection, [companyname].sharepoint.com.