CSOM for SharePointOnline user fields no longer returning Email
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint CSOM
Developer environment
Windows
What browser(s) / client(s) have you tested
- [ ] 💥 Internet Explorer
- [x] 💥 Microsoft Edge
- [x] 💥 Google Chrome
- [ ] 💥 FireFox
- [ ] 💥 Safari
- [ ] mobile (iOS/iPadOS)
- [ ] mobile (Android)
- [ ] not applicable
- [ ] other (enter in the "Additional environment details" area below)
Additional environment details
Describe the bug / error
CSOM for SharePointOnline user fields no longer returning Email (null/empty). Code snippet attached
Steps to reproduce
- Read SharePoint online list item with User field using SharePoint CSOM.
- User field value does not return Email and only return LookupId and LookupValue
Expected behavior
- User field value should return Email aparf from LookupId and LookupValue
Hello @HarminderSethi,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.
I have also have this issue since 10th December 2025 on our tenant. Microsoft Graph no longer returns email address in MicrosoftGraphFieldValueSet from SharePoint list item, only LookupId and LookupValue. I have tested with Graph Explorer and can see that the Email value is null. I have logged a service request with Microsoft.
thx @dcowleyrm also on flagging this and on opening a ticket with Microsoft. Good to have this tracked here for everyone, but let's also open direct tickets to Microsoft support where possible for faster resolution. Seems that this is impacted in both CSOM and in Microsoft Graph API surface.
Temporary fix is in your SP List create another column that references the persons e-mail you can then leverage this in your code.
Possible fix from Microsoft. "User spUser = context.Web.SiteUsers.GetById(user.LookupId); context.Load(spUser); context.ExecuteQuery();" And there is a Service Health alert for this issue https://admin.microsoft.com/adminportal/home#/servicehealth/:/alerts/SP1196502
Any update on this?
Doing any workaround such as 'loading' user fields explicitly would require lots of changes in many places (where email string comparisons are being done)
I have had the following reply to my Microsoft Service Request.
Microsoft Product Group has recently completed preliminary testing on the proposed fix, and the results indicated that the issue was resolved, where the queries are now correctly returning the Author or Email field. The team is planning to roll out the fix to a larger testing environment and will continue to monitor the behavior of the updated code to ensure stability and expected performance. If no issues are observed, a production rollout will be initiated December 17th, and the full deployment may take up to 48 hours to complete.
Narf. Took an hour of head scratching to find this issue. Glad to hear it'll be resolved soon.
Any one able to see the email id with regards to this issue fix
Not yet showing for our tenant.
Negative for our tentant as well
Is there a Microsoft blog that mentions when this will be available in production?
Microsoft has shared the following update via the service ticket / Service Health notification:
We've completed our validations and testing of our newly developed code fix and are preparing its deployment to all impacted environments. Additionally, we anticipate that the deployment will have taken place prior to our next scheduled update, at which point we’re aiming to gather a remediation timeline to be provided by our next scheduled communication update.
Further updates can be tracked through the Microsoft 365 Admin Center (Service Health) under alert SP1196502: https://admin.microsoft.com/adminportal/home#/servicehealth/:/alerts/SP1196502
Is there a Microsoft blog that mentions when this will be available in production?
https://admin.cloud.microsoft/?#/servicehealth/:/alerts/SP1196502
We don't have an access for the given link. Could you please provide the snapshot?
I've just verified on my tenant and the Email property is now correctly populated again in CSOM user fields 🎉
CSOM returns emails on our tenant as well
@HarminderSethi Since the issue has been resolved and verified on multiple tenants, can we go ahead and close this issue?