Fix Teams File Opens Read-Only after a SharePoint Site Rename

When you rename a SharePoint site, files that you open in Teams may suddenly appear as read-only. This happens because Teams caches the old site URL and the file’s permissions get tied to that stale address. In this article, you will learn why the rename breaks file access and how to clear the cache, update permissions, and re-add the file to Teams so you can edit it again.

The fix involves three actions: clearing the Teams cache, resetting SharePoint permissions, and re-syncing the file. You can do all of these without contacting your administrator, unless your organization blocks cache clearing. Follow the steps below in order to avoid losing any unsaved changes.

Why a SharePoint Site Rename Makes Teams Files Read-Only

When you rename a SharePoint site, the site’s URL changes. For example, the site https://contoso.sharepoint.com/sites/ProjectX becomes https://contoso.sharepoint.com/sites/ProjectAlpha. Teams stores the original URL in its local cache to speed up file access. After the rename, Teams may still try to open files using the old URL, and SharePoint responds with a permission error because the old URL no longer exists.

SharePoint treats the renamed site as a new location for permission checks. If your user account was granted access through a group that was linked to the old site URL, that group may not automatically apply to the new URL. As a result, SharePoint grants you read-only access to the file, even though you had full edit rights before the rename.

How the Teams Cache Stores Site URLs

The Teams desktop app caches file metadata, including the full SharePoint URL, in a local folder. Every time you open a file from the Files tab, Teams reads this cache first. If the cache contains a URL that no longer matches the renamed site, Teams cannot obtain write permission. Clearing the cache forces Teams to fetch the new URL from SharePoint.

How SharePoint Permissions React to a Rename

SharePoint does not automatically update permission inheritance when a site is renamed. If your access was granted via a security group that references the old site path, that group might not be recognized on the renamed site. The result is that you can view the file, but you cannot edit it. Checking your effective permissions on the new site URL is the second step in the fix.

Steps to Clear the Teams Cache and Restore Edit Access

Follow these steps in order. If you are using the Teams web app, skip the cache-clearing step and start at step 2.

1. Close Teams completely
   Right-click the Teams icon in the system tray and select Exit. Confirm that no Teams process is running by pressing Ctrl+Shift+Escape to open Task Manager. Look for any process named Teams or ms-teams and end them.
2. Clear the Teams cache folder
   Press Win+R, type %appdata%\Microsoft\Teams, and press Enter. In the folder that opens, delete the subfolders named Cache, Code Cache, GPUCache, and blob_storage. Do not delete the whole Teams folder. If you see a message that a file is in use, close Teams again and retry.
3. Restart Teams and open the file
   Start Teams from the Start menu or desktop shortcut. Go to the channel where the file is located and open the file from the Files tab. If the file now opens in edit mode, you are done. If it still opens read-only, continue to the next step.
4. Check your SharePoint permissions on the renamed site
   Open a browser and go to the new site URL. Select Settings (gear icon) > Site permissions > Advanced permissions settings. In the ribbon, select Check Permissions. Enter your user name and select Check Now. Verify that you have at least Edit or Contribute permission. If you see only Read, ask your site owner or administrator to grant you edit rights.
5. Re-add the file to Teams
   If permissions are correct but the file still opens read-only, remove the file from the channel and upload it again. Select the file in the Files tab, choose More options (three dots), and select Delete. Then select Upload and choose the file from your local drive. This creates a new file link that references the renamed site URL.
6. Use the Sync button to refresh the library
   In the Files tab, select Sync in the toolbar. This forces Teams to re-enumerate the file library and update all cached URLs. If you do not see a Sync button, select More options (three dots) and choose Sync from the menu. Wait for the sync to complete, then try opening the file again.

If Teams Still Has Issues After the Main Fix

Teams Shows a Blank Window After Clearing the Cache

Clearing the cache can sometimes cause Teams to display a blank white window on the next launch. This happens because the cache also stores UI resources. To fix this, close Teams, delete the Cache folder again, and restart Teams. If the problem persists, sign out of Teams and sign back in.

The File Opens Read-Only Only on One Device

If the file opens in edit mode on another device but not on your current one, the local cache on that device is stale. Repeat the cache-clearing steps on that specific device. Also check whether the file is open in another application, such as Word or Excel, which can lock the file and force read-only mode.

SharePoint Site Permissions Say You Have Edit, but Teams Still Shows Read-Only

This usually means Teams is still using the old URL. Go to the Files tab, select More options (three dots) on the file, and select Open in SharePoint. If the URL in the browser does not match the new site name, the file link is outdated. Delete the file from the channel and re-upload it, as described in step 5 above.

New Teams Desktop vs Teams on the Web: Key Differences

Item	New Teams Desktop	Teams on the Web
Cache location	Local folder in %appdata%\Microsoft\Teams	Browser cache and cookies
Cache clearing method	Delete cache folders manually	Clear browser cache via browser settings
URL refresh behavior	May require restart after cache clear	Refreshes automatically when you reload the page
File opening behavior	Opens in desktop Office apps by default	Opens in Office for the web
Best for this issue	Good if you prefer desktop apps	Faster fix if you cannot clear desktop cache

If you use Teams on the web, the cache-clearing step is different. Clear your browser’s cache and cookies for the SharePoint domain, then reload the Teams page. The web version does not store site URLs as persistently, so this often resolves the read-only issue faster.

After you regain edit access, consider asking your administrator to update any links that point to the old site URL. Old links will continue to fail for other users. You can also create a new link by selecting Copy link from the file’s more options menu and sharing that with your team.

You can now clear the Teams cache, verify SharePoint permissions, and re-add the file to restore edit access. Start with the cache clear because it is the most common fix. If that does not work, check your permissions on the renamed site. Use the Sync button as a final refresh before you re-upload the file. For future renames, remember that clearing the cache is the first step to try on every affected device.