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.

 

Technology – what is different between source and target

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.

 

User Experience – what changes imply for users

 

Migrating user 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 company.
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.

For more and detailed information read the chapter “User Adoption Process”

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more