Failed to Login to Sharepoint

Question

Failed to Login to Sharepoint

Abdelrahim GAMMAR 20

[Moderator note: Personally Identifiable Information removed] does not exist in tenant '[Moderator note: Personally Identifiable Information removed]' and cannot access the application '[Moderator note: Personally Identifiable Information removed]'(Office 365 SharePoint Online) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account.

0 comments

Answer accepted by question author

Alexis-NG 18,070 Microsoft External Staff Moderator

Hi Abdelrahim GAMMAR,

The error message indicates that the account currently in use is not recognized within the tenant and, as a result, does not have access to SharePoint Online resources hosted in that environment. This typically occurs when the account either does not belong to the tenant or has not been properly granted access as an external user.

To address this, please first ensure that you are signing in with the correct organizational account. Alternatively, if you are accessing the resource as an external user, it is necessary for your account to be explicitly added as a guest (external) user within the tenant and granted the appropriate permissions to the SharePoint site.

In addition, to rule out any authentication or session-related inconsistencies, it is recommended to sign out of all Office applications, clear your browser cache, and then sign back in using the correct account.

You can do that by pressing Ctrl + Shift + Del to bring up Delete browsing data tab.

For further validation, you may also attempt access using an incognito or private browsing session, as this helps ensure a clean sign-in without cached credentials interfering.

Should the issue persist after these steps, please reach out to your administrator or the SharePoint site owner. They can verify whether your account has been properly added to their tenant as an external user and confirm that the necessary access permissions have been assigned.

I hope this provides enough clarity and helps you stay inform with your current situation.

Thank you for your patience and your understanding. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.

Note: Follow the steps in this documentation to enable email notifications if you want to receive email notifications related to this topic.

0 comments

1 additional answer

Your answer

Answer 1

The error indicates that the account being used to sign in does not exist as a guest or member in the UNSSC tenant, so it cannot access SharePoint Online for that tenant.

Use these steps to resolve it:

Confirm the correct account and tenant
- Make sure the user is using the account that was actually invited to the UNSSC tenant (same email address/identity provider).
- If the user might be signed in with another Microsoft or organizational account, have them:
  - Sign out of all Microsoft accounts in the browser.
  - Open a new InPrivate/Incognito browser window.
  - Try accessing the SharePoint link again and sign in with the intended account.
Ensure the user is invited/added to the tenant
- The error message explicitly states the account needs to be added as an external user.
- A UNSSC tenant administrator should:
  - Add the guest user to the directory following the steps in “Add the guest user to your directory” so the account exists in Microsoft Entra ID for that tenant.
  - Alternatively, if the resource is a SharePoint site/list/library shared directly, ensure the guest user is properly provisioned by either:
    - Enabling SharePoint integration with Microsoft Entra B2B, or
    - Manually adding the guest user to the directory first, then sharing the resource.
Re-share the SharePoint resource if needed
- After the guest user is added to the directory, re-share the SharePoint site/list/library with that guest account via the SharePoint Permissions page, then have the user accept the invitation and sign in again.

If the user still gets a similar error after being added as a guest, verify that the correct sign-in URL/tenant is being targeted and that the user is not accidentally signing into a different tenant or account session.

References: