Skip to main content

Scheduled Service Change: Run Full Sync for O365

Last Updated:
2013-01-17 00:00:00
Event:
2013-01-18 00:00:00
Status:
Closed
Brief Description:
User Impact:
• Changes to the User’s Display Name that are submitted On Friday Jan 18th 2013 will not be propagated to Office 365 until Monday Jan 21st. This will only affect the display name when viewed by User’s who have already been migrated to Office 365. Users of the On Premises Exchange Environment will see their changes on the Normal Daily Schedule.\n• Changes to the User’s preferred email address that are submitted On Friday Jan 18th will not be propagated to Office 365 until Monday Jan 21st. This will only affect the preferred email address for users who have already been migrated to Office 365. User of the On Premises Exchange Environment will see their changes on the Normal Hourly Schedule.\n• Changes to the User’s Email routing and EGA routing that are submitted On Friday Jan 18th will not be propagated to Office 365 until Monday Jan 21st. This only affects senders who have been migrated to Office 365 who are sending to Users who have also been migrated to Office 365 where the Recipient makes a change to their routing.\n
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
Run a "full sync" on DirSync server to include users who are not synced with O365. (users designated as "Inactive" in AD)