We're excited to announce that the general availability rollout of the new Azure AD sign-in and “Keep me signed in” experiences has started! These experiences should reach all users globally by the end of the week. Users who go to our sign-in page will start to see the new experiences by default, but a link allowing users to go back to the old experiences will be available until early December to give you some extra time to make the transition. We'd like to take this opportunity to acknowledge the delays we have had with these features and thank you all for your patience. When we released these experiences in preview, we received a lot of great feedback from you and it was pretty clear we needed to take a little extra time to ensure the new experiences worked well with all the scenarios Azure AD sign-in is used for. Read about it in the Enterprise Mobility & Security blog.

We are also experiencing this issue where the KMSI dialog is being displayed for all of our internal ADFS sign ins when previously it was automatic. For now, we have disabled the feature. If there is a fix for this, please let me know. Thank you.

Yes, that might have been caused by Chrome SSO. Everything we do in the new sign in experience and stay signed in experience are cookie-based, and cookies are not shared across regular and in-private sessions.Regarding the other two issues you reported:1. Translation issue - thanks for reporting this. I'll work with our localization team to get that fixed.2. Checkbox - the checkbox is essentially a no-op when you say Yes since saying Yes means that you won't have to interactively sign in again in the future. It only applies when you say No so we don't nag you.

@Kelvin I see your point, but if we had proper documentation on what's supported and not and how the different flow works, I'm sure that would decrease the number of escalations :) Smart links are still required for true, seamless SSO experience in some cases, and there is definitely demand for such from the enterprise customers. If you can publish some guidelines and recommendations, I think it will benefit all sides. Anyway, I'll stop with the offtopic :)

Hi, Many of our users have set a site, library or folder as favorites in File Explorer which connects through webdav(?) to SharePoint. As we are using SSO, users don't get the option 'keep me signed in' anymore. This causes a permission denied when opening the folder or library in file explorer -> no cookie is saved. Is there a workaround to have the cookie or 'Keep me signed in' back? Thanks Bernd

Hi Kelvin Xia, I did some additional tests on the SSO experience. When I delete my cookies and open a mapped sharepoint webdav connection I cannot load it which is expected (cookie is removed). When I open the sharepoint tenant url I get logged in through SSO and most of the time the magical cookie is created. When the cookie is created I'm able to open the webdav connection. For other users (same permission etc) they get a sign in screen where they need to enter there username. then they are redirected to the homepage but they are not able to open the webdav connection. Eddy Verbeemen please correct me if I'm wrong :-) VasilMichev few years ago we used the smartlinks to enforce the 'keep me signed in'. At a certain moment this was not longer working and we went back to the default login where we could choose to 'keep me signed in'.It seems that there is a different between SSO where a prompt is shown for a username and no prompt is shown...CheersBernd

The new Azure AD sign-in and “Keep me signed in” experiences rolling out now!

Michael Kostuch
Copper Contributor
Nov 17, 2017
We are using Power BI with a Web app and this web app is embedded reports in Salesforce. As soon as this was implemented, we started getting these dialog boxes, so the reports would not come through. HOw can we turn these off so they have a smoother experience. Currently Salesforce won't allow that dialog at all, so they get blank pages as a result of this. If they go through the web app directly in a url, and answer the dialog, the dashboard reports render fine. But this dialog caused our field to lose a week's worth of work so far. I finally found this so I am hoping someone can tell me how to turn it off...for good? We have a critical case open with MSFT right now as a result.
dialog.docx1.9 MB
Ed Sparks
Iron Contributor
Nov 28, 2017

We are seeing unexpected behavior when we choose "don't show me this again" and click No.

Every time we login again it gives the prompt again.

Shouldn't "don't show me..." respect a yes or no answer and go away?
- Kelvin Xia
  Microsoft
  Dec 03, 2017
  Sorry about that. We pushed out a fix for that mid-last week. It should work now.
  - Srikanth Komirishetty
    Brass Contributor
    Dec 03, 2017
    Hi Kelvin, thank you for quick response. Its still the issue for us. Should we perform any steps to speed up the change to our tenant?
Srikanth Komirishetty
Brass Contributor
Dec 02, 2017
Does anyone has issues with "Stay Signed-in" prompt that shows after successful authentication with ADFS? Our tenant is not presenting the prompt (as described here https://cloudblogs.microsoft.com/enterprisemobility/2017/09/19/fewer-login-prompts-the-new-keep-me-signed-in-experience-for-azure-ad-is-in-preview/ )as it did couple of weeks ago. The option to keep the user signed in has been enabled in our Company Branding settings. Any thoughts?
- Kelvin Xia
  Microsoft
  Dec 03, 2017
  Is your ADFS set up to send the PSSO claim, or do you have Windows SSO set up? If it is, we're automatically dropping the persistent auth cookie (which the "Stay signed-in" prompt does when the user selects "Yes"). We have a few bugs a few weeks ago when we did not do that, which could explain the difference in behavior you're seeing now vs then.
Joe Johannes
Copper Contributor
Dec 28, 2017
Hi, MS admin for years, new here. Just saw this, perhaps it can help us. Our call to Microsoft (before this change) had no immediate fix. Our 8k+ users to o365/SPO need access to SP sites. We would like to use this ..."Keep me singed in" for most users. Others with Generic IDs which would only prompt for a password to get to secure content on SPO sites. Is this possible to do both? Details would be golden!!! Thanks, Joe
- Kelvin Xia
  Microsoft
  Jan 02, 2018
  Hi Joe,
  
  can you please clarify what you're trying to achieve? Is this an issue that has occurred with the new sign-in experience or is this just new functionality you want enabled?
Daniel1582
Copper Contributor
Jun 19, 2020

I get this after clicking Yes to the KMSI:
Whoops!
Something went wrong
We cannot sign you in to E-WorkBook Cloud. Wait a moment
and try again. If the problem persists you will need to contact
your system administrator.
Event log shows this:
Status
Interrupted
Sign-in error code
50140
Failure reason
This occurred due to 'Keep me signed in' interrupt when the user was signing in.

I opened a support case. Just wanted to share my experience.

Forum Discussion

The new Azure AD sign-in and “Keep me signed in” experiences rolling out now!

Share

Resources