Microsoft Verification Code Issues

Question

Some of our external users appear to be having issues when trying to access folders or files shared with them as follows:

"Access to portal was a little strange as the first time I clicked link – I got sent a SharePoint Verification code (valid for 15 min) the next time I logged in I got a request for email and password.

As I had not set up a password I then clicked – retrieve new password – and the system would not let me reset as I did not have permissions."

Not sure if anyone else is experiencing this or knows why it may be happening?

Answer 1

Hi Tim_73,

I go through the post carefully, based on the description, I think you may select “Specific People” shared option when share files with external users. User will get One-time passcode to get access for the files. Please check the link for more information on user’s experience: External or guest sharing in OneDrive, SharePoint, and Lists (microsoft.com).

As you can see from the link, One-time passcode(Verification code)  is sent when user don’t have Microsoft account registered for his email address, and in some scenario, user may need to provide passcode even they have Microsoft account. Like there is no other methods to verify users access to the folder. As for the issue. here are some suggestions:

1. If the user has Microsoft account, then you may suggest user to sign in with his account email and password and check the result.
2. To check if the issue caused by cookies in users browser, suggest user to open the shared link in email from InPrivate Window in browser and check the result
3. Try stop sharing the files/folders(For more information: Stop sharing OneDrive or SharePoint files or folders, or change permissions), reshare it to the user and check the result.

For more information on One-time passcode: One-time passcode authentication for B2B guest users - Azure AD | Microsoft Docs

Best Regards,

Clark

Answer 2

Hi Tim_73,

Have you checked information above? Welcome to post back if there are any updates on the issue.

Regards,

Clark