MC174530 - Moving GCC Exempt Customers to the Outlook mobile simplified architecture

%3CLINGO-SUB%20id%3D%22lingo-sub-359792%22%20slang%3D%22en-US%22%3EMC174530%20-%20Moving%20GCC%20Exempt%20Customers%20to%20the%20Outlook%20mobile%20simplified%20architecture%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359792%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20tenant%20received%20the%20%3CEM%3E%3CSTRONG%3E%22MC174530%20-%20Moving%20GCC%20Exempt%20Customers%20to%20the%20Outlook%20mobile%20simplified%20architecture%22%3C%2FSTRONG%3E%3C%2FEM%3E%26nbsp%3Bin%20the%20Message%20Center%20last%20week.%3C%2FP%3E%3CP%3EIt%20this%20only%20a%20Tenant%20wide%20setting%3F%20It%20would%20be%20nice%20if%20we%20could%20change%20the%20GCCRestrctionsEnabled%20to%20False%20for%20a%20couple%20users%20to%20test%20out%20before%20rolling%20out%20tenant%20wide.%20Is%20that%20ability%20available%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-359792%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOutlook%20for%20Android%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20iOS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359810%22%20slang%3D%22en-US%22%3ERe%3A%20MC174530%20-%20Moving%20GCC%20Exempt%20Customers%20to%20the%20Outlook%20mobile%20simplified%20architecture%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359810%22%20slang%3D%22en-US%22%3E%3CP%3EI%20assume%20this%20is%20referring%20to%20the%20changes%20outlined%20here%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-ie%2Fexchange%2Fclients-and-mobile-in-exchange-online%2Foutlook-for-ios-and-android%2Foutlook-for-ios-and-android%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EOutlook%20for%20iOS%20and%20Android%20in%20Exchange%20Online%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20understand%20it%2C%20it's%20not%20a%20setting%20as%20such%20but%20more%20an%20architectural%20change%20that%20will%20affect%20the%20whole%20tenant%20and%20streamline%20how%20Outlook%20mobile%20apps%20communicate%20with%20Exchange%20Online.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20new%20%3CSPAN%3Enative%20Microsoft%20sync%20technology%26nbsp%3B%3C%2FSPAN%3Eimproves%20and%20simplifies%20%3CSPAN%3Edata%20synchronization%3C%2FSPAN%3E%2C%20offering%20a%20number%20of%20benefits%2C%20mostly%20improving%20performance%20and%20robustness.%20There%20is%20a%20FAQ%20here%20that%20answers%20some%20of%20the%20questions%20about%20this%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fclients-and-mobile-in-exchange-online%2Foutlook-for-ios-and-android%2Foutlook-for-ios-and-android-faq%23native-microsoft-sync-technology-migration%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ENative%20Microsoft%20sync%20technology%20migration%3C%2FA%3E%20including%20the%20answer%20to%20your%20main%20question%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EAs%20a%20tenant%20administrator%2C%20can%20I%20control%20which%20of%20my%20users%20will%20be%20migrated%20to%20the%20native%20Microsoft%20sync%20technology%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ENo%2C%20the%20migration%20to%20the%20native%20Microsoft%20sync%20technology%20will%20be%20%3CU%3Eon%20a%20tenant-by-tenant%20basis%20and%20not%20a%20per-user%20basis%3C%2FU%3E.%20While%20the%20tenant%20selection%20order%20for%20migration%20is%20random%2C%20we%20are%20being%20deliberate%20about%20migrating%20Office%20365%20mailboxes%20first.%20If%20you%20are%20a%20customer%20operating%20in%20a%20hybrid%20configuration%20where%20a%20portion%20of%20your%20mailboxes%20%3C%2FEM%3Eremain%3CEM%3E%20on-premises%2C%20the%20on-premises%20users%20leveraging%20hybrid%20modern%20authentication%20will%20be%20migrated%20to%20the%20native%20Microsoft%20sync%20technology%20at%20a%20later%20date.%20This%20means%20that%20your%20Office%20365%20users%20will%20migrate%20to%20the%20native%20Microsoft%20sync%20technology%2C%20while%20the%20on-premises%20users%20continue%20to%20use%20the%20REST%20API%20to%20connect%20to%20Exchange%20Online.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EOnce%20your%20tenant%20is%20migrated%2C%20a%20user%20will%20not%20switch%20to%20the%20native%20Microsoft%20sync%20technology%2C%20until%20after%20they%20launch%2Fresume%20Outlook%20for%20iOS%20and%20Android.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20helps!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

My tenant received the "MC174530 - Moving GCC Exempt Customers to the Outlook mobile simplified architecture" in the Message Center last week.

It this only a Tenant wide setting? It would be nice if we could change the GCCRestrctionsEnabled to False for a couple users to test out before rolling out tenant wide. Is that ability available?

1 Reply
Highlighted

I assume this is referring to the changes outlined here - Outlook for iOS and Android in Exchange Online.

 

As I understand it, it's not a setting as such but more an architectural change that will affect the whole tenant and streamline how Outlook mobile apps communicate with Exchange Online. 

 

This new native Microsoft sync technology improves and simplifies data synchronization, offering a number of benefits, mostly improving performance and robustness. There is a FAQ here that answers some of the questions about this - Native Microsoft sync technology migration including the answer to your main question:

 

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.

 

Once your tenant is migrated, a user will not switch to the native Microsoft sync technology, until after they launch/resume Outlook for iOS and Android.

 

Hope that helps!