How to Fix PrimarySmtpAddress Update Delays in Microsoft 365 Groups
Question details
Administrators experience delays or errors when updating the PrimarySmtpAddress for a Microsoft 365 Group, as changes do not immediately reflect in Microsoft Graph.

- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- Modifying the primary email address of a Microsoft 365 Group using the Set-UnifiedGroup PowerShell command.
- Observed behavior
- The Set-UnifiedGroup command executes successfully (HTTP 200), but Microsoft Graph and other Microsoft 365 services do not immediately display the updated PrimarySmtpAddress due to asynchronous synchronization.
Ensure you are connected to Exchange Online PowerShell using an account with Exchange Administrator or Global Administrator privileges before attempting to modify group attributes.
Verify Changes with Get-UnifiedGroup and Allow Propagation Time
Use this method to confirm that the address change was accepted by Exchange Online, even if it hasn't populated to Microsoft Graph yet.
Because Microsoft 365 services synchronize asynchronously, a successful command in PowerShell might not instantly update across the entire tenant. Exchange Online processes the change first, followed by a delayed sync to Microsoft Graph.
Open PowerShell as an administrator and connect to your Exchange Online environment using your admin credentials.
Ensure that the new primary SMTP address you want to assign is not currently in use by another mailbox, alias, or distribution group.
Execute 'Get-UnifiedGroup -Identity "YourGroupName"' to check if the PrimarySmtpAddress property has successfully updated on the Exchange side.
Allow sufficient time (up to 24 hours in some cases) for the backend asynchronous synchronization to propagate the changes to Microsoft Graph and other services.

Escalate Persistent Issues to Microsoft Support
If the address fails to update after 24 hours or you encounter explicit update errors, escalate the issue via a support ticket.
Create and Manage IT Documentation Seamlessly with WPS Office
While you troubleshoot Microsoft 365 backend services, you can rely on WPS Office for all your everyday document and reporting needs. It is a free, lightweight, and highly compatible alternative to Microsoft Office.
- 1. Download WPS Office: Visit the official WPS website and download the free installer.
- 2. Install the application: Run the installer and follow the quick setup wizard to install the software.
- 3. Open and edit your files: Launch WPS Office and directly open your existing Microsoft Office documents.

Frequently Asked Questions
Why doesn't Microsoft Graph show the new PrimarySmtpAddress immediately?
Microsoft 365 services synchronize asynchronously. While Exchange Online accepts the address change instantly, propagating this update to Microsoft Graph and Azure AD can take several hours depending on backend server loads.
How can I check if the PrimarySmtpAddress change was successful?
You can verify the success of the update by running the Get-UnifiedGroup cmdlet in Exchange Online PowerShell. If the correct address is displayed there, it has been accepted and will eventually sync to other services.
What permissions do I need to run Set-UnifiedGroup?
You must be assigned the appropriate administrator roles, such as Exchange Administrator or Global Administrator, and your PowerShell session must be authenticated with those credentials.
Can I force the synchronization process between Exchange and Microsoft Graph?
No, backend synchronization across Microsoft 365 services happens automatically and asynchronously. If changes do not appear after a 24-hour wait period, you should contact Microsoft support.




