RecoveryTools
DVR

SharePoint User Information List Not Updating: 5 Causes and Fixes

Jamie Kaler
· 5 minute read
Quick Answer

SharePoint user information list not updating has 5 causes. Every site collection holds its own copy of user data. Only users active in that site get synced values. Microsoft says changes flow from Entra ID in batches. Microsoft gives no fixed time for the profile sync. Microsoft's 2017 blog gives up to 24 hours for site copies. Alerts or shared items make a user active again. Disabled or unlicensed users do not sync.

You fixed a job title in Entra ID and SharePoint still shows the old one.

You get 5 causes and the fix for every one. I also flag what Microsoft pages leave out.

Why Does the User Information List Show Old Details?

Microsoft's 2017 support blog says every site collection stores a copy of user data in a hidden list. You can open it at /_catalogs/users/simple.aspx after your site address.

Microsoft's user profile sync page shows the path. Changes move from Entra ID to the directory store and the User Profile Application and then to sites. Microsoft batches them at regular intervals.

What are the 5 Causes and Fixes?

CauseSignFix
Inactive in the siteOld values on one siteAdd an alert or share an item
Sync delayEntra ID shows the new valueWait for the batch
Blocked or unlicensedAccount not processedEnable and license the user
Custom propertyValue never arrivesBulk update API or custom code
Search schemaSearch shows old valuesSet PeopleIdx and update profiles

Microsoft says default properties follow Entra ID and custom properties need a bulk update API or custom development.

How do You Fix Old User Details in a Site?

Who it suits. Site owners and admins with access to the site. Extra application. None needed.

  1. Check Entra ID. Confirm the new value exists in Microsoft Entra ID for that user.
  2. Check the account. Microsoft says blocked or disabled accounts are not processed. The user must be enabled and licensed.
  3. Open the hidden list. Add /_catalogs/users/simple.aspx to your site address and look at the stored value.
  4. Make the user active. Create an alert for the user on the site or share an item with the user.
  5. Wait up to 24 hours. Microsoft's 2017 blog gives that window for site copies.

Sharing an item also touches access. Our guide on SharePoint permission levels shows what every level allows.

Who it suits. SharePoint admins who edited the search schema. Extra application. None needed.

  1. Open the search schema. Select Manage Search Schema in the SharePoint admin center.
  2. Set the index. Open the managed property and go to Advanced Searchable Settings. Set Full text index to PeopleIdx.
  3. Use the organization level. Make the schema change there and not in one site collection. Then update the user profiles.

Microsoft says the schema fix applies only after you update a profile. Our guide on SharePoint search not working after a move covers wider search faults.

Which Limits Apply to These Fixes?

  • Old source. The hidden list steps come from a 2017 Microsoft blog that names no SharePoint version. Test on one site first.
  • No cmdlets. I found no current Microsoft page on PowerShell commands for this list so this post gives none.
  • No sync time. Microsoft gives no number for the profile sync. The 24 hour window comes from the 2017 blog.
  • All profiles. Microsoft says to contact Microsoft 365 technical support to apply a schema fix to all profiles.

My Verdict on Old User Details

Fix SharePoint user information list not updating by checking Entra ID first and the site second. Most stale values trace back to an inactive user or a missing sync.

Make the user active in the site before you open a ticket.

Key Takeaways

  • Every site collection stores its own copy of user data.
  • Only active users in a site get synced values.
  • Blocked or unlicensed accounts are not processed.
  • Search values need the PeopleIdx setting and a profile update.

Next Read

Frequently Asked Questions

Does Every Site Collection Have Its Own User List?

Yes. Microsoft's 2017 blog says every site collection stores user data of its own. The hidden list sits at /_catalogs/users/simple.aspx.

Do Inactive Users Get Fresh Values?

No. Microsoft's 2017 blog says only active users sync in a site collection. Alerts and shared items make a user active.

Can Blocked Accounts Fail to Sync?

Yes. Microsoft says blocked or disabled accounts are not processed. The user must be enabled and licensed.

Does Microsoft Give a Fixed Sync Time?

No. Microsoft says sync times vary by workload. The 2017 blog gives up to 24 hours for site copies.

Can an Alert Make a User Active Again?

Yes. Microsoft's 2017 blog lists an alert for the user as one fix. Sharing an item with the user works too.

Do Custom Profile Properties Sync by Default?

No. Microsoft says custom properties need a bulk update API or custom development. Default properties follow Entra ID.

Can a Schema Change Leave Old People Search Values?

Yes. Microsoft says the fix applies only after you update a user profile. A schema change made at site collection level is one cause.

Jamie Kaler
Jamie Kaler Marketing Head and Content Strategist, RecoveryTools

Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.

Published 11 November 2026. Sync facts come from the Microsoft Learn page on user profile synchronization. The hidden list steps come from a 2017 Microsoft support blog on profile updates in a site collection. Search steps come from the Microsoft troubleshooting page on people property search results. Check the pages again before you edit anything because Microsoft updates them.