That didnt work, Issue type User not in directory - SharePoint external access error

You have granted permissions to an external user to your SharePoint site, list, document library, or document, but they receive an error stating that the account can't be found in the tenant.sharepoint.com directory.

Error User not in directory.PNG
Error User not in directory.PNG

That didn't work
We're sorry but [EXTERNAL USER ACCOUNT] can't be found in the [company.sharepoint.com] directory. Please try again later, while we try to automatically fix this for you.

The message provides some additional information -
  • Correlation ID - Which is of not much help in SharePoint Online
  • Date and Time - Time stamp of error
  • URL - SharePoint link which the external user could not access
  • User - Email account of the external user
  • Issue Type - User not in directory
The last information "Issue type" is helpful, which indicates that the user is not found in your Azure Active Directory /SharePoint User Profile or may not have permission to access the SharePoint link. All external users are added to your Azure AD in format [external-email]#EXT#@tenant.onmicrosoft.com.

Common Causes of this error

  • External account is not permitted to access the link, access is not granted.
  • (MOST COMMON) External users are using a different account to access the link, which does not have access. The account should be the same which received the email invitation.
  • External user has not accepted the invitation and directly accessing the link.

FIX - go in sequence to narrow down the problem

  • First things first, double check that external access is enabled for your Tenant and SharePoint site. There is no harm in rechecking.
  • Go to Site Settings --> Users and Permissions --> Access Requests --> EXTERNAL USER INVITATIONS / HISTORY, the status in history should show 'Accepted by USER'. If it shows pending, ask the user to click the link from the email invitation.
  • Re-assign permissions to the external account. This will send a fresh email invitation to the external user and ask them to click the invitation link received in the email.
  • Ensure that the account used is the same to which access was given and the email invitation was received.
  • Using Chrome Incognito or IE/Edge InPrivate always helps. There will be conflict when accessing 2 Office 365 accounts in the same browser window, this will even rule out cache/cookie problems. Ask the external user to open a private browser session and try accessing it.
  • Select 'Organizational Account' if the user has an Office 365 account, and select 'Microsoft Account' for any other account.
  • Remove the user (not permissions, remove the user entry completely) from SharePoint by going to 'All users' list by appending _layouts/15/people.aspx/membershipGroupId=0 to your site.
  • Remove user from Office 365 portal by going to Users --> Active Users.
You can use a similar approach for troubleshooting OneDrive external access issues.


Comments:

  • My external vendor was facing this issue. Asked her to clear their browser cache and history, did not help. Re-invited and that worked like a charm!
    anon 02 Sep 2020 14:33:47 GMT
  • Delete the external user from Azure Active Directory first, rather than SharePoint, and then from the SP site. people.aspx?MembershipGroupId=0 is the best way.
    anon 22 Oct 2020 20:18:06 GMT
  • Incognito session did the trick, the session conflicts with your organizational M365 account.
    Another TIP - if you remove the user and try to reassign permissions, it may take up to 12-24 hours until the external user is removed from the SharePoint Online site collection.
    anon 14 Oct 2020 09:10:59 GMT
  • Remove the external user using this PowerShell (SharePoint Online Management Shell) command and then re-add.

    $cred = Get-Credential
    Connect-SPOService -Url https://tenant-admin.sharepoint.com -Credential $cred
    $ExtUser = Get-SPOExternalUser -filter <account@tenant.com>
    Remove-SPOExternalUser -UniqueIDs @($ExtUser.UniqueId)

    anon 29 Sep 2020 17:54:43 GMT
  • Further comments disabled!

This is not an AI-generated article but is demonstrated by a human.

Please support independent contributors like Code2care by donating a coffee.

Buy me a coffee!

Buy Code2care a Coffee!

Comments & Discussion

Facing issues? Have questions? Post them here! We're happy to help!