Forum Discussion
Solved
Native Microsoft Sync Technology Migration
Back in the end of last year, Microsoft announced that they are moving Outlook for iOS and Android from the REST API protocol to the Microsoft native sync technology, starting with Office 365 customers and then Outllook.com users.
Six months later, I have checked up on this (as the message centre post has disappeared) and my Office 365 users are still using the REST API but my personal Outlook.com account is using the native sync.
Could anyone else please confirm that they are also still waiting?
Thank you.
Link for details:
It seems we have now been converted today, as it now shows 'Microsoft sync technology' in the account info and the 'Teams Meeting' option shows up in Outlook mobile.
Running the PowerShell command shows that not all users are using it yet, but I have noticed that my device is showing twice. One for 'REST' and one for 'Outlook'.
Finally...
Also notice that Outlook mobile on iOS got updated to version 3.24.1 overnight. Coincidence?
Anthony Russell - we're in the same boat and have a case open.
It seems we have now been converted today, as it now shows 'Microsoft sync technology' in the account info and the 'Teams Meeting' option shows up in Outlook mobile.
Running the PowerShell command shows that not all users are using it yet, but I have noticed that my device is showing twice. One for 'REST' and one for 'Outlook'.
Finally...
Also notice that Outlook mobile on iOS got updated to version 3.24.1 overnight. Coincidence?
- Ross Smith IV
Microsoft
We've now migrated all O365 tenants to the native Microsoft sync technology.
It's currently available for outlook.com accounts, and it's the other way around - first outlook.com, then O365 will follow.
Q: As a tenant administrator, can I control which of my users will be migrated to the native Microsoft sync technology?
No, the migration to the native Microsoft sync technology will be on a tenant-by-tenant basis and not a per-user basis. While the tenant selection order for migration is random, we are being deliberate about migrating Office 365 mailboxes first. If you are a customer operating in a hybrid configuration where a portion of your mailboxes remain on-premises, the on-premises users leveraging hybrid modern authentication will be migrated to the native Microsoft sync technology at a later date. This means that your Office 365 users will migrate to the native Microsoft sync technology, while the on-premises users continue to use the REST API to connect to Exchange Online.- Ross Smith IV
For Outlook mobile, major feature deployment operates with a staggered rollout where we begin with consumer accounts (if applicable) and then deploy to commercial accounts like Office 365. Our primary focus for commercial accounts was moving Government Community Cloud. Now that's complete, we'll be focusing on the remaining O365 tenants.
As to the text you highlighted, you're taking it out of context from the rest of the paragraph as we're migrating O365 accounts to the Microsoft sync technology before we migrate on-premises Exchange accounts leveraging hybrid modern auth.
- I’m sure that said Office 365 accounts first, because they are the accounts that benefit from it the most.
MC165218Wording on the message center posts is not always the best. If you have an outlook.com account added to the application, you should already see it using the native sync technology (go on the account settings screen, look at the bottom).
