Bits & Bytes

The BitTitan Blog for Service Providers



04/30/2020



Jaym Gates

Customers can now migrate Gmail between instances of G Suite using the Gmail API for better security and fidelity than IMAP.

Currently supported only for migrations from G Suite (Gmail API) to G Suite (Gmail API)
Customers can use their own G Suite account instead of using BitTitan service account for better throughput
- Need to create customer tenant service account and enable APIs
- Can choose to have a common service account or setup separate service accounts for Source and Destination
- Managed via uploading the account credentials JSON file during endpoint
- Refer to Set Up Google API
What is migrated?
- Calendars
- Contacts
- Mail
What new items are migrated?
- New migration support for Gmail system labels
  - Categories: Social, Updates, Forums, Promotions
  - Bin
  - Important
Enhanced handling for Snoozed and Scheduled Mails:
- Snoozed mails migrated with ‘[Gmail]/Snoozed’ label (as normal mail without snooze properties)
- Scheduled mails migrated with ‘[Gmail]/Scheduled’ label (as normal mail properties)
New migration support for Gmail custom label properties
- Label color
- Show in label list
- Show in message list

Enable via AdvancedOptions ‘UseApplicationPermission=1’

Benefits:

Customers can now perform SharePoint/OneDrive migrations securely with App Permissions instead of having to use Global Admin and/or Site Collection Admin permissions)
Refer to: https://help.bittitan.com/hc/en-us/articles/360047240093
There are now two authentication options for App ID which supports a least-permissions method to authenicate
The new App with ReadOnly permissions can be used explicitly at the Source for better security
- MigrationWiz-SharePoint-ReadOnly: https://login.microsoftonline.com/common/adminconsent?client_id=b811c97c-fabd-4219-a350-108b82a6cdd7&state=12345
  - Only to be consented for use by Global Admin at the Source tenant
  - Cannot export document permissions and cannot use AMR
  - Cannot be used at the Destination tenant
  - Permissions granted
    - SharePoint API: Sites.Read.All, User.Read.All
    - Graph API: Directory.Read.All, Files.Read.All, Group.Read.All (delegate permission)
- MigrationWiz-SharePoint-FullControl: https://login.microsoftonline.com/common/adminconsent?client_id=0173390d-c130-431b-bd6b-f096a2ccad4e&state=12345
  - Can be consented to by Global Admin at the Source/Destination tenant
  - Can export document permissions
  - Must be used at the destination tenant
  - Permissions granted
    - SharePoint API: Sites.FullControl.User.ReadWrite.All
    - Graph API: Directory.Read.All, Files.Read.All, Group.Read.All (delegate permission), User.Read (delegate permission)

Best Practice / Recommended Flow

Global Admin creates new Security Group named “MigrationWiz” (at the Office 365 Admin Portal)
Global Admin creates new user
Global Admin adds user to security group as a member
Creates MW project and fill the endpoints with the user (created above) credentials
Add the advanced option UseApplicationPermission=1

Notes specifically for OneDrive:

Notes for SharePoint:

Supported only for cloud-to-cloud migrations
- Not supported for on-prem to cloud
No longer need Site Collection Admin credentials for SharePoint
AMR or the Advanced Option UseAsynchronousMetadatRead=1 cannot be run at Source with ReadOnly App
- User will need to use FullControl at Source for AMR and permissions migration

Objective was to default the destination endpoints to v2 to:

Expected changes:

MigrationWiz will no longer support any new Box, EML, Amazon Workmail, or Open X-Change migration projects.

Box as a Source endpoint has been removed. Existing Box migrations will not be impacted
EML, Amazon Workmail, and Open X-Change endpoints have been removed. Existing migrations will not be impacted.

Teams Assessment Performance Improvement

Teams assessments will see significant speed and performance improvement now that the connection to each SharePoint site is removed during the Assessment stage.

Teams – Improved SharePoint Folder Tolerance

Previously, non-fatal SharePoint error would fail the migration
With this fix, non-fatal SharePoint errors can be skipped so that migration does not fail
This will reduce the failure rate due to SharePoint errors

Teams – Automated Folder Mapping for Renamed Channels