11-15-2017 01:23 PM
11-15-2017 01:23 PM
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.
11-15-2017 01:38 PM
@Eric Starker Do you have any information on the ADFS web theme to allow on-premises ADFS look and feel to match the new sign in experience? We saw some information during the original preview announcement that this would be coming but are unable to find any info. We have our TAM also checking for information but thought I'd check here as well.
11-15-2017 02:55 PM
11-15-2017 11:05 PM
@Kelvin Xia two minor issues still remain:
1) When using federated account, I have to press the Next button in order to be taken to the AD FS login page. In the previous experience this was automatic, simply pressing Tab for example did the trick.
2) Why am I being prompted for the KMSI experience when using Private sessions? Maybe you should implement a check for this?
11-16-2017 12:18 AM
Hi, we are using a Federated domain With local ADFS. Before this change, single signon worked without any questions when we are logged into the local domain.
Now, after this New "experience", Our users must click on a Choice on the keep me logged in or not page. This is an anucence for Our users. We use Azure AD for authentication to Our intranet in the cloud.
Is there a setting on an Application or Azure AD Directory, or a URL parameter or similar that can be used to disable this?
11-16-2017 03:20 AM
Microsoft support answered it for me. Turn it off in Company branding:
11-16-2017 09:30 AM
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.
11-16-2017 09:51 AM
11-16-2017 12:09 PM
Kelvin, correct me if I'm wrong, but most of the complaint about the auto-redirect with just filling in the UPN were because it didn't allow users to select the KSMI checkbox. Now that that's a separate step, this issue no longer applies?
On the Private session thingy, does KMSI even work with Private sessions? It writes a cookie, no? Which is *not* saved if/when I'm using a Private session. So displaying the KMSI step is pointless?
And one other thing comes to mind after seeing the comments made by other folks here - are you guys respecting the "LoginOptions" parameter for federated logins/smart links? The idea being that it automatically ticked the KMSI checkbox in the old experience...
11-16-2017 01:51 PM
11-16-2017 11:47 PM
Three remarks on the new experience:
1. Spelling mistake (in Dutch translation, a period in the middle of a sentence)
2. The checkbox in the KMSI dialog is confusing (don't show this again). Does it make me stay logged in even longer when I select Yes and thick the checbox?
3. When I choose "Yes" in my regular browser session, open a private session, enter a different account in the private session. I get logged in with the account of the regular session anyway, no matter the account I filled in. Is this by design?
11-16-2017 11:56 PM
What browser are using Bart? What you are describing in scenario 3 shouldn't be happening, unless maybe in federated environment with WIA autologin. Kelvin can correct me here.
11-17-2017 12:17 AM
@Kelvin, I'm not a programmer so I will trust you on the Private session thingy, although I've seen some JS samples that supposedly to just that. In all fairness, the previous experience wasn't detecting private sessions either. It's just that the KMSI is a separate step now, thus more visible, and can be a bit irritating :)
And on a related topic, can you folks please publish an official statement on what's supported in terms of smartlinks now? Just the other day you published an article mentioning 46% of all auths are AD FS, and I'm certain many of these do take advantage of smart links. Yet, there is zero documentation on them from Microsoft.
11-17-2017 06:56 AM
@Vasil Michev I tried Chrome, we are federated and are using WIA indeed.
We have now removed SSO for Chrome in our ADFS. It is probably not related to the new sign-in, Chrome was added as SSO browser to our ADFS a few days ago.
11-17-2017 09:37 AM
11-17-2017 09:52 AM
11-17-2017 10:02 AM
Okay, but what if that is entirely undesirable behavior in half of your use cases? When my users are on their personal computers, this is a good thing. When they are using one of our many shared workstations, the last thing I want is for them to be encouraged to "Stay signed in".
How do I prevent it from being offered on office computers without preventing it on their personal devices? Most, though not all, of our offices are AD joined, so if there's a GPO I can push out please indicate that in some way.
If the classic login screen can be permanently forced per-domain (per tenant may not work for our parent company), that would also be acceptable.
Because as it stands, this is a horrible idea. I'm going to have realtors reading each other's emails after we told them we were setting them up with MFA to keep anyone else from getting into their email.
11-17-2017 10:16 AM
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.
11-17-2017 10:47 AM
11-17-2017 11:10 AM
11-17-2017 11:29 AM
That makes me feel better.
May I suggest stating that in more places? Like the announcements, relevant blog posts, or other places that admins will see before they start to flip out?
11-19-2017 11:24 AM
@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 :)
11-21-2017 06:00 AM
while I do see some benefit on the KMSI feature for regular users, I would prefer to have privileged admin accounts be prompted for MFA Login in their browser profiles every time.
How can I achieve this without turning the feature off for everyone?
11-21-2017 06:12 AM
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?
11-21-2017 07:56 AM - edited 11-21-2017 07:59 AM
We had Microsoft turn ours off at the tenant level until a better plan could be put in place. The problem with Company branding is: 1.) It's a global setting 2.) It can affect Sharepoint Online users and Office 2010 users (and we had just moved over 30K sharepoint sites to Sharepoint Online, so I didn't want to interrupt their experience for my experience with Power BI to work, 3.) Even as a global admin, we could not delete the company branding. The delete button would not highlight and we verified our permissions. We could turn it on or off for KMSI, but we could not delete company branding 4.) We found the KMSI box "Don't ask me again doesn't work" either. It only stays for the session, so to the user they think they should never have to see it again. 5.) We were told we could add a parameter to the Web app to turn this off in the code, so we are pursuing this now as our permanent solution, but for now our customers can function again with KMSI.
11-21-2017 10:22 AM
11-21-2017 10:22 AM
@Bernd Verhofstadt Just curious, are you using smart links and passing the LoginOptions parameter?
@Kelvin, that's one of the use cases I warned you about - mapped drives rely on this functionality, and the LoginOptions parameter was a nice and easy way to handle this in federated setups.
11-21-2017 10:36 AM
11-21-2017 01:38 PM
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 :)
@Vasil Michev 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...
11-25-2017 09:17 AM
Am I the only one not seeing the KMSI at all now? Cloud account, no federation. I tried deleting cookies, private sessions and different browsers, I don't ever see KMSI now. I thought the changes are supposed to only effect federated scenarios?
11-28-2017 01:12 PM
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?
12-02-2017 12:16 PM
12-02-2017 06:20 PM
12-02-2017 06:22 PM
12-02-2017 06:25 PM
12-02-2017 06:26 PM
12-02-2017 06:28 PM
12-03-2017 10:30 AM
Thanks for that detail Kelvin. But I need to request yet another documentation update here - the only place I've seen the PSSO claim detailed so far is the claims rules added by AAD Connect. As some organizations might not be using AAD Connect (or at least not managing the AD FS farm with it), can you please post a detailed article on how the claim should look like and so on?
12-04-2017 01:08 PM
We are seeing this issue as well when we try to map a users onedrive. Have you found a fix yet?
12-14-2017 07:15 AM
We don't use ADFS but we have AD Connect, is there any reason why we are not seeing the new KMSI experience? It is very hard to keep users informed IF we rely on the roll out dates suggested by Microsoft.
12-14-2017 10:53 AM
12-14-2017 10:54 AM
12-18-2017 07:48 AM
We have SSO set up and based on your statement, Microsoft has added logic not to show the prompt.
Is there a way we can show this prompt with SSO enabled? To your previous question, we have not set up ADFS to pass PSSO Claim for SharePoint.
Appreciate your help.
12-18-2017 10:14 AM
12-18-2017 10:15 AM
@Kelvin Xia what exactly does the "shared machine" logic cover? I stopped receiving the KMSI prompt on my personal PC, which is pretty much the most secure machine I use (even added as trusted IP), and since I'm not using any form of SSO for said account, that only leaves the "shared machine" scenario? On the same machine, another user from the same tenant is getting the KMSI prompt...
12-18-2017 02:58 PM - edited 12-18-2017 02:59 PM
The reason I ask is, we get this window every single time when we close the browser. I need not enter my password but I have to click on my account (I have to pick every single time I close the browser). If I switch to old sign in experience, I can check the box to keep me signed in and it will never ask me to pick the account. As the old sign in page is going away, we need to provide our users a way to avoid picking account each and every time the re-open the browser. The only, I saw is with the prompt and that is why, I'm reaching you to see if we can enable that prompt on SSO.
12-19-2017 12:34 AM
@Srikanth Komirishetty do you happen to be using Smart links? Even with the old experience, without smart links configured you have to enter/select the UPN before federation happens. But you can construct "smart links" (basically an URL with added parameter for the domain) to bypass this process and have you log in automatically. Perhaps those are not working with the new experience?
12-20-2017 02:11 AM - edited 12-20-2017 03:50 AM
Current set up
We have SharePoint Online site with auto acceleration enabled. Our Azure AD is federated with on-premise ADFS. We have seamless SSO working in IE where user does not need to type any username password.
By default, when the user logins in thru IE, only Session cookie is generated, so when the user closes the browser and reopens the user is authenticated again. Also, the new KMSI (Keep me signed In) screen is not displayed to the user during the login experience in IE, so there is no way for user to generate persistent cookie which works across multiple sessions. In chrome, user can see the KMSI screen and hence persistent cookies can be generated.
Is there a way by which global admin can configure such that all users by default gets persistent cookies instead of session cookie, so that they don’t even need to click “yes” in KMSI screen?
I saw below blog where it says to create custom claim rule in ADFS to issue Persistent SSO claim. But again, the last line of the blog says “As of right now, AAD does not support SAML based use of the Persistent Single Sign On Claim / SAML attribute.” So, is this blog relevant now?
by Eric Starker on November 15, 2017
by Alex Simons (AZURE) on February 26, 2020
by Alex Simons (AZURE) on July 10, 2019
by Alex Simons (AZURE) on September 07, 2018