How to Fix SharePoint Publishing Errors When User Is Not Found
Question details
Users are unable to save or publish specific SharePoint pages due to an error referencing an invalid user address or nonexistent user.

- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Publishing or saving pages in a Microsoft 365 tenant configured with multiple UPN suffixes.
- Observed behavior
- SharePoint returns a REST error and fails to publish the page because it references a nonexistent address combining the pre-Windows 2000 logon name with the primary domain instead of the correct UPN suffix.
Confirm whether the issue affects all pages or only specific ones, and ensure you have contact information for your Microsoft 365 administrator.
Open a Microsoft 365 Support Ticket via Administrator
Since the error is rooted in backend tenant identity settings and UPN suffix configurations, an administrator must request Microsoft Support to investigate.
Forum engineers and standard users do not have access to tenant logs or domain configurations. A Microsoft 365 administrator needs to submit a ticket to resolve the underlying identity synchronization issues.
Have your M365 administrator log into the Microsoft 365 Admin Center using their administrative credentials.
Click on the 'Support' menu on the left pane and select 'Help & support'.
Provide details about the REST error, mentioning that page metadata references an invalid user address due to an incorrect UPN suffix assignment.
Submit the ticket so Microsoft engineers can analyze tenant logs, identity settings, and page metadata to apply a permanent fix.

Recreate the Problematic Page (Temporary Workaround)
If you need an immediate fix to publish content while waiting for Microsoft support, creating a brand-new page can bypass the corrupted metadata.
Looking for a Hassle-Free Office Suite? Try WPS Office
While resolving complex SharePoint and Microsoft 365 identity errors requires administrative intervention, your daily document tasks shouldn't be difficult. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for all your personal and professional productivity needs.

Frequently Asked Questions
Why is SharePoint creating an incorrect user address for page metadata?
This typically happens in Microsoft 365 tenants with multiple UPN suffixes. The system may incorrectly combine a pre-Windows 2000 logon name with the primary domain instead of using the user's actual UPN suffix, triggering a validation failure.
Can I fix the SharePoint publishing REST error without an administrator?
No, standard users cannot resolve the underlying identity and domain configuration issue. However, you can use a temporary workaround by recreating the affected page to bypass the corrupted metadata.
Will recreating the SharePoint page permanently fix the issue?
Recreating the page only acts as a temporary workaround for that specific instance by generating fresh metadata. The root cause involving tenant identity settings must still be addressed by Microsoft Support.




