Forum Discussion
SharePoint Designer 2013 Stuck at the Windows Security Window
I FINALLY found a solution!! And it was SO simple.
At the Office 365 sign-in page select "Keep me signed in" then enter your user name and, if needed, password. (see attached)
The new sign-in experience does not provide the checkbox.
If this does not work for you then you may want to review the entire discussion to see other possible solutions.
David Cox post notes that he was able to get it resolved via a Office 365 support ticket. I believe only SharePoint Administrators can submit the ticket, e.g. I cannot as a Site Collection Administrator.
The "Keep me signed in" solution no longer works!
When I enter my user name in the old and new experience I am now directed to an organization page to log on. A
"Stay signed in?" window pops up. I select Yes and still have the problem.
David Cox seems to have had luck with a support ticket via Office 365. I am not an admin, so I do not have that option.
So, once again I am stick at the credentials window when I try to use SharePoint Designer. I will update if a solution is found.
Hi CatherineB, Did you manage to solve this? I am having the same issue and have tried everything with no success so far. Regards, Debbie
Hi Debbie Hilton - Last fix which seems to have worked the longest is mapping a drive to the site.
I believe that the authentication problem has to do with Designer not fully supporting Multi-factor Authentication. Web searches turn up some people saying it should, and others saying it doesn't. It seems to work sometimes and not others, and seems to throw this error most often when using the "new sign-in experience" that O365 has been trying to roll out for months.
If you're reading this and you know that your organization has MFA enabled for your user account, then you could try creating an App Password for SharePoint Designer 2013. Or if you're really good friends with the Global Admins, you could ask them to disable MFA on your account at least temporarily to prove to them and Microsoft that it's an MFA issue. (warning - if you do have mfa disabled temporarily, you'll have to re-enroll your verification stuff when it's re-enabled)
Here's an article that explains how and why to create an App Password in O365. In our environment using the App Passwork method seems to have been successful but we don't have that many people using SPD2013.
https://docs.microsoft.com/en-us/azure/multi-factor-authentication/end-user/multi-factor-authentication-end-user-app-passwords
I hope the app password trick works for you!
