Dear @Sean Smith,
Thank you for posting your question in the Microsoft Q&A forum.
I understand how inconvenient it must be to be unable to access Outlook due to error 500: TenantAccessBlockedException. This error indicates that access to Outlook on the web has been blocked for your account or organization. It usually occurs when certain policies or restrictions have been applied at the tenant level.
Please see the following workarounds that will help you verify the issue:
Option 1: Clear browser cache and cookies then use private mode
Clear your browser cache to remove outdated or corrupted files:
- For Google Chrome:
Go to Settings > Privacy and security > Delete browsing data.
Select All time, check both Cookies and other site data and Cached images and files, then click Delete from this device.
- For Microsoft Edge:
Go to Settings > Privacy, search, and services > Delete browsing data.
Select All time, check both Cookies and other site data and Cached images and files, then click Clear now to proceed.
Once you've completed these steps, please sign in to your account via office.com and navigate to the Apps section, and select Outlook to confirm that you can access it.
After clearing the cache, please open a private or incognito window in your browser to continue:
- For Google Chrome:
Click on the vertical three-dot menu and select New Incognito Window.
- For Microsoft Edge:
Click the horizontal three-dot menu and choose New InPrivate Window.
After opening a private window, please return to the Outlook web page.
If you’ve been using a different browser, such as Google Chrome, please try downloading Microsoft Edge and visit office.com to see if the issue persists.
- Option 2: Contact your IT administrator
Method 1: Unassign and reassign the user license
Sign in to the Microsoft 365 Admin Center > Users > Active users > Locate and click the user account.
Under Licenses and Apps, uncheck the current license assigned to the user, then click Save changes.
After saving, select the appropriate license for the user again and click Save changes.
This article provides further guidance on the topic: Assign or unassign licenses for users in the Microsoft 365 admin center - Microsoft 365 admin | Mic…
Method 2: Contact Microsoft Support
If the issue continues after these steps, your IT administrator may consider reaching out to Microsoft Support for further assistance.
A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis. For that reason, the most efficient solution would be to contact Microsoft’s support team directly.
- I recommend creating a support ticket via Microsoft Admin Center > Support > Help & Support for further investigation.
- Microsoft provides customer service phone numbers based on your region. You can find the appropriate contact number here: Customer service phone numbers - Microsoft Support
As community moderators, we kindly ask for your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into performing deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.
I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.
Thank you for your patience and 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.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.