GEO Mailboxes migration switch error. "ExchangeImpersonation SOAP header must not exist for this type of OAuth token." (4303097)

GEO Mailboxes migration switch error.  "ExchangeImpersonation SOAP header must not exist for this type of OAuth token."

Multinational companies that have offices around the world often have needs to store their employee data at-rest in specific regions to meet their data residency requirements. 

For this issue there is the Multi-Geo Capabilities in Office 365, a new feature that helps multinational customers address their regional, industry specific or organizational data residency requirements in Office 365.

Multi-Geo enables a single Office 365 tenant to span across multiple Office 365 datacenter geographies (geos), and gives customers the ability to store their Exchange and OneDrive data, at-rest, on a per-user basis, in their chosen geos. 

Switching a Geo mailbox may fail even while mailbox syncing works. A soap error: "System.Web.Services.Protocols.SoapException: ExchangeImpersonation SOAP header must not exist for this type of OAuth token" may be generated. 

INFORMATIONAL...

Note:  This may not be the only solution but one possible recommendation. 

At one customer site the resolution was to have the service account/mailbox in the GEO location so that it could complete the switch process.

Move the service account / mailbox to the proper multi-geo location for the mailboxes to be switched and try again.