'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix SharePoint iOS Error AADSTS50020 Caused by Wrong Tenant
Question details
The user is unable to access the SharePoint iOS app due to error AADSTS50020, which occurs because the app is attempting to authenticate against the wrong organization's Microsoft Entra tenant.
- Product
- Microsoft SharePoint iOS App
- Device & OS
- iOS
- Scenario
- Attempting to sign into a work account on the SharePoint iOS app after previously accessing a shared file as a guest in another organization's environment.
- Observed behavior
- The SharePoint iOS app returns error code AADSTS50020 and blocks access. Clearing only the SharePoint app data fails to remove the saved guest sign-in state.
Ensure you have the correct login credentials for your primary work account and save any pending work in other Microsoft 365 iOS apps before clearing account data.
Clear Account Settings and Microsoft Edge Internals
Perform a comprehensive reset of saved sign-in data across both SharePoint and Microsoft Edge to force the app to authenticate with the correct home tenant.
Because iOS shares authentication states between Microsoft 365 applications, clearing SharePoint's data alone is often insufficient. The wrong tenant might remain selected because Microsoft Edge on iOS has saved a previous guest or B2B sign-in token.
Swipe up from the bottom of your iPhone or iPad screen and swipe away all running Microsoft 365 applications, including SharePoint and Edge, to close them completely.
Open the iOS 'Settings' app, scroll down to find 'SharePoint', tap it, and toggle on the 'Clear Account Settings' option.
Open the Microsoft Edge app, sign out of your profile, type 'edge://signin-internals' into the address bar, and tap 'RemoveAllAccounts'.
Restart your iOS device. Once restarted, open the SharePoint app and sign in again using the correct work account credentials.
Clear OneDrive Account Settings
If you are experiencing similar tenant routing issues across multiple Microsoft apps, clearing OneDrive's account settings can help flush conflicting cached credentials.
Looking for a Seamless Office Alternative? Try WPS Office
If complex tenant authentication issues and login errors in Microsoft 365 are slowing down your mobile workflow, WPS Office offers a straightforward, lightweight alternative. You can view, edit, and manage your documents effortlessly without restrictive account routing issues.
- 1. Download the App: Install WPS Office from the Apple App Store on your iPhone or iPad.
- 2. Open Your Files: Launch WPS Office and directly browse your local device files or connect your preferred third-party cloud storage.
- 3. Edit Without Hassle: Start editing your Word, Excel, or PowerPoint documents immediately without dealing with complex organizational account restrictions.
Frequently Asked Questions
What does error code AADSTS50020 mean?
This error means that the Microsoft Entra identity provider successfully authenticated your account, but you are not authorized to access the requested resource. This typically happens when the app tries to log you into a tenant where you do not exist or lack guest permissions.
Why doesn't clearing the SharePoint app cache fix the tenant error immediately?
On iOS devices, authentication tokens and guest sign-in states are often shared across various Microsoft apps via Microsoft Edge or the Microsoft Authenticator app. Clearing only SharePoint data leaves the cached Business-to-Business (B2B) guest tokens intact in these shared locations.
Can this wrong tenant issue affect other Microsoft 365 apps on iOS?
Yes, other applications like OneDrive and Teams can experience similar tenant routing issues if they latch onto a cached guest account. Clearing account settings for those specific apps in the iOS Settings menu usually resolves the conflict.
