logo
search
Permission & Access Issues

How to Fix Excel Permission Errors When Opening Files Shared by One User

Maira MehtabMaira Mehtab Sep 27, 2026 870 views

Question details

A user is unable to open Excel files shared by a specific manager due to a permission error, which started occurring after the user's account was migrated to a different email domain.

Product
Microsoft Excel / Microsoft 365
Device & OS
not provided
Scenario
Accessing a shared Excel spreadsheet from a specific colleague after the recipient's email domain (UPN) was recently changed.
Observed behavior
Files shared by most users open normally, and the affected account works in private browsing and on other devices. However, files shared by one specific manager consistently display permission errors.
Before you start

Verify that you are fully signed out of your old domain account on all Microsoft services, and ensure you are logged into OneDrive and Office strictly using your new email address.

Solution 1Recommended

Perform a Clean Sharing Test with a New File

This isolates whether the error is tied to old file links generated before your domain migration, or if it is a persistent sharing block between your new account and the manager.

When an account undergoes a domain change, previously generated sharing links often retain the old User Principal Name (UPN). Generating a brand new file forces the system to look up your current directory details.

1
Create a new test file

Ask the specific manager to create a completely blank Excel workbook in their OneDrive or SharePoint.

2
Share with the new email address

Have the manager share this new file directly to your newly updated email domain address, avoiding any old contact group lists.

3
Open in a private window

Copy the new sharing link, open an Edge InPrivate or Chrome Incognito window, sign in with your new domain credentials, and attempt to open the file.

Interpreting the Test: If the new file opens successfully, the manager simply needs to re-share their older files. If the new file still throws a permission error, the issue lies in the tenant backend.
Free Microsoft Office alternative

Avoid Complex Permission Sync Issues with WPS Office

If backend tenant permission errors and domain migration bugs in Microsoft 365 are disrupting your workflow, consider switching to WPS Office. It provides a lightweight, highly compatible, and frustration-free environment for creating, editing, and sharing your spreadsheets.

  1. 1. Download WPS Office: Visit the official WPS website to download and install the free software suite.
  2. 2. Open your files: Launch WPS Spreadsheet and easily open your existing .xlsx files directly from your local drive or cloud storage.
  3. 3. Share seamlessly: Use simple link sharing or email attachments to collaborate with your team without worrying about domain credential mismatches.
Fully compatible with Microsoft Excel formats (.xlsx, .xls, .csv)Simple file sharing without complex tenant-level backend restrictionsLightweight installation that runs smoothly on older or lower-spec devicesFamiliar interface ensures a zero-learning-curve migration
microsoft office alternative - wps office

Frequently Asked Questions

Why do files shared by other users work, but not this specific manager?

The manager's sharing history or local Microsoft cache might still be mapping your identity to your old email domain (UPN). When you try to authenticate with your new domain, the Microsoft backend detects a mismatch and denies access.

Will clearing my browser cache resolve domain migration permission errors?

Clearing browser cache or using an Incognito window helps resolve local caching issues. However, if the credential mismatch is deeply rooted in the Microsoft 365 backend tenant, browser troubleshooting will not be enough, and admin support is required.

How do I know if my new domain account is working properly for Excel sharing?

Ask a colleague who has never shared a file with you before to send a test Excel link. If that file opens without an error, your base account and domain migration are functioning properly, and the issue is strictly isolated to the previous manager's sharing cache.