Cross-Tenant Comparison (Tenant to Tenant)
The main head word in T2T comparison is the “Technology Harmonization”. Beside this, users will experience a different M365 feature usability, this is the other side to be identified and leads to the Change & Adoption approach.
Several topics are included in this topic, not limited to technology only but overlap with user experience too.
Commonly we start with
the licensing comparison. This might mainly restrict the usage of services or
limit the services towards migrated users. From here you analyze each service
step-by-step. Not only data / storage limitation could apply. Like in personal
OneDrive, where the target could have lower storage limits than in source.
Areas like Guest User
Access, Domain restrictions, Teams federation and other B2B configurations
might lead to data migration/ usage limitations. It is advised to work with
both side equally and see how the target environment is leading and if changes
must apply, how this governance can be achieved.
Users can work quite
freely in a M365 tenant, like they can create new services attached to M365
groups. This is could be different in the target tenant. Not only this is a
technical restriction, but also impact the user experience intensely.
The most complex task
for comparison is the AIP, labeling, policies and encryption. Matching both
sides is a project in itself. Encryption is another hassle, as the AIP
encryption keys must be accessible from the target and must be migrated while
you migrated the DNS domains. IF DNS domains aren’t migrated, it must be
considered another project in a project, decrypting source data and
re-encryption during migration.
experience from source to target is completely depending on the possibilities
and feature sets in the target environment. As an experience isn’t technical,
rather than it is behavioral.
Work and human culture
in the target environment might also differ from source. Only a holistic
approach will make users feel comfortable after the migration.
Compare the technical
feature set per service and list the difference between source and target. Go
on with conducting interviews with the IT departments and users across the
You should involve two skills, the technical expertise and a good adoption specialist. Both need working hand in hand with the client.
The result will
directly define the areas where the change & adoption team will work on.