How to Fix Specific People Link Breaks After User Rename

When a user in your organization changes their display name or email address, existing “Specific People” links in SharePoint may stop working. These links are used to grant access to a specific person or group on a site, list, or library. The cause is that SharePoint stores the user’s identity as a claim that references the old account, and the link does not automatically update after the rename. This article explains why the break happens and provides step-by-step methods to fix the broken links using SharePoint admin tools and PowerShell.

Why a User Rename Breaks Specific People Links

SharePoint uses a claim-based identity system. When you grant access to a “Specific People” link, SharePoint stores the user’s unique identifier, which is tied to their Azure Active Directory account. When a user’s display name or user principal name changes, the claim stored in the SharePoint permission entry still points to the old value. This mismatch causes the link to break — the user sees an error or a blank page when trying to access the resource.

The rename itself can happen through Azure AD, Microsoft 365 admin center, or an on-premises directory sync. The key factor is that SharePoint does not automatically refresh permission entries after a rename. The link remains tied to the old account claim until someone manually updates it.

What Happens to the Link

When you share a file or folder using a “Specific People” link, SharePoint creates a permission entry for that user. After a rename, the user’s new identity exists in Azure AD, but the permission entry still references the old one. The user may still see the item if they have other permissions, but the specific link itself fails. In some cases, the link may appear to work for a short time because of cached credentials, but it eventually breaks.

How to Confirm the Link Is Broken

To check if a link is broken, open the shared item and click the “Shared with” button. If the renamed user does not appear in the list, or if their name shows as “User Not Found,” the link is broken. You may also see a “403 Forbidden” error when the renamed user tries to access the link.

Steps to Fix Broken Specific People Links

There are two main methods to fix broken links: using the SharePoint admin center for individual sites, or using PowerShell for bulk repairs. Both methods require the renamed user’s new identity to be fully synced to SharePoint.

Method 1: Fix Links Using the SharePoint Admin Center

1. Open SharePoint admin center
   Go to https://admin.microsoft.com and select SharePoint from the left navigation. Alternatively, go directly to https://admin.microsoft.com/SharePoint.
2. Navigate to Active sites
   In the left menu, click Active sites. Find the site that contains the broken link. You may need to search by site name or URL.
3. Open site permissions
   Click the site name to open its details panel. In the panel, click the Permissions tab. This shows all users and groups with access to the site.
4. Remove the old user entry
   Find the renamed user’s old identity. It may appear with the old display name or as “User Not Found.” Click the check box next to the entry, then click Delete user permissions. Confirm the deletion.
5. Add the renamed user
   Click Add people. Type the renamed user’s new display name or email address. Select the appropriate permission level (for example, Read or Contribute). Click Add.
6. Re-create the Specific People link
   Navigate to the item that had the broken link. Use the Share button to create a new “Specific People” link for the renamed user. Test the link by opening it in a private browser window.

Method 2: Fix Links Using SharePoint Online Management Shell

If you have many broken links across multiple sites, use PowerShell to fix them in bulk. You need the SharePoint Online Management Shell and the renamed user’s old and new user principal names.

1. Install and connect to SharePoint Online Management Shell
   Open Windows PowerShell as an administrator. Run Install-Module -Name Microsoft.Online.SharePoint.PowerShell if not already installed. Then run Connect-SPOService -Url https://-admin.sharepoint.com and sign in with a global admin or SharePoint admin account.
2. Get the site collection where the broken link exists
   Use Get-SPOSite to list all site collections. Note the URL of the site that contains the broken link.
3. Remove the old user permissions
   Run Remove-SPOUser -Site -LoginName . Replace with the site URL and with the user’s old user principal name (for example, oldname@contoso.com). This removes all permission entries for the old identity.
4. Add the renamed user
   Run Add-SPOUser -Site -LoginName -Group to add the user to the appropriate SharePoint group. If the link was granted directly to the user (not via a group), use Set-SPOUser -Site -LoginName -IsSiteCollectionAdmin $true or assign a permission level using Add-SPOUser with the -PermissionLevel parameter.
5. Repeat for each site
   Run the same commands for every site collection that had a broken link. You can script this by reading a CSV file of site URLs and user names.

If Specific People Links Still Have Issues After the Main Fix

SharePoint Link Still Shows “User Not Found”

If the link still shows the old user after you have added the renamed user, the SharePoint permission cache may not have refreshed. Wait 15–30 minutes and check again. If the problem persists, verify that the rename has synced to SharePoint by checking the user’s profile in the SharePoint admin center under User profiles. If the profile still shows the old name, force a profile sync using PowerShell with Set-SPOUser -Site -LoginName again.

PowerShell Command Fails with “User Not Found”

This error usually means the old user principal name is incorrect or the user was deleted instead of renamed. Check the user’s current UPN in Azure AD. If the user was deleted and recreated, you cannot fix the link — you must create a new link for the new user account. If the user still exists but the UPN changed, use the new UPN for both the remove and add commands.

Broken Links in Multiple Libraries Across One Site

When a user has been granted access to many items via “Specific People” links, the permission entries are stored at the item level. The methods above fix site-level permissions, but item-level links may remain broken. To fix item-level links, use the Share button on each item to remove the old user and add the new one. For bulk item-level fixes, use PnP PowerShell with Get-PnPListItem and Set-PnPListItemPermission to iterate through items and update permissions.

Site-Level vs Item-Level Permission Fix: Comparison

Item	Site-Level Fix	Item-Level Fix
Scope	Removes and re-adds user at the site collection level	Updates permissions on individual files or folders
Tools	SharePoint admin center or SharePoint Online Management Shell	SharePoint UI or PnP PowerShell
Time required	Minutes per site	Minutes per item; hours for bulk
When to use	User had site-level permissions and the link was granted via a group	User had direct “Specific People” links on many items

The best approach is to first fix site-level permissions, then use PnP PowerShell to fix item-level links. This ensures the renamed user has access to the site and can see the items, even if the old links are still broken.

After completing the fix, you can now restore access for renamed users without losing the work that was shared with them. Next, review your organization’s user rename process and consider automating permission updates using Azure AD Connect and SharePoint PnP provisioning. One advanced tip is to run a scheduled PowerShell script that checks for permission entries with old user principal names after each rename, preventing link breaks before users report them.