Simplify external user authentication
We have started using SharePoint Online as a file sharing and collaboration solution with external partners, but the pitfalls in the external user authentication process are causing us a log of problems. If the external users don't read our instructions, it is difficult for them to understand whether to use Microsoft account and when the Organizational account, and even if they manage through that, they might have another Microsoft account open or passwords stored in the browser cache, and end up with getting error messages and fail to access our site. On top of that, because we are sharing only document libraries, there is a bug which only grants the external users Limited access on the first invite, so we have to go and grant the permissions again to each user to get them the correct access to the document library. We might need to turn to another file sharing solution altogether, since we are getting frustrated and even angry feedback from our external partners on this.
Please, do whatever you can to simplify the SharePoint Online external user authentication process!
In order to create a Microsoft Account, I also need to put in my phone number for an SMS code. IT IS TIME for Microsoft to allow non-Microsoft accounts for external users to authenticate with. Stop the war with Gmail, you will not win.
The minute Google starts to invest in better data security and agrees to stop mining data, corporations are going to abandon Microsoft and all its proprietary garbage, and just finally allow users to do what they've been doing for years: store **** in Google Drive.
Couldn't agree more.. Signup is a really confusing process for 3rd parties, we have issues with every new attempt to share externally..
Peter England commented
Agree. Also have the issue where we cannot apply MFA to external accounts, and we don't know if an external account is on another O36 tenant.
As a result of all of these issues we have been setting external users up in our O365 tenant, but this leaves us with the (cached) login issue if an external user is part of their own O365 tenant.
I SECOND THAT!