Free & Busy Sync during Cross-Tenant Migration (Exchange Online)

-

 

Free & Busy Sync during Cross-Tenant Migration

You have two options “migrating” mailboxes cross-tenant:

-          Microsoft Cross-Tenant Migration
this will move, reconnect a user’s mailbox in target and removes the source mailbox entirely

-          Using a 3rd party tool, copying the mailbox content and syncing calendars
this will leave the source mailbox intact and can confuse users in the source environment, which user is now active (see the user adoption story)

 

Organization relationship in Exchange Online

If you migrate the User Mailbox entirely, meaning, nothing is left behind in the source, you can use Organizational Free/Busy Lookup:

This feature is named: Organization relationship in Exchange Online

 

This allows:

-          Set up an organization relationship to share calendar information with an external business partner.

-          Set up an organization relationship with another Microsoft 365 or Office 365 organization or with an Exchange on-premises organization.

But is not a free/busy synchronization, rather this is a normal EWS based calendar share and query feature. Users which are migrated, do not have a mailbox in the source tenant and there for a free/busy query against the target, with the new target email address can be initiated

There are three levels of access that you can specify:

·        No access.

·        Access to availability (free/busy) time only.

·        Access to free/busy, including time, subject, and location.

 

Follow this Microsoft article for setup:
Create an organization relationship in Exchange Online

 

NOTE:

It can be used while source mailbox are intact, but there must be a solution, e.g. Out of Office notification, stating other that a user has been migrated and is working actively on the target side !

 


Free/Busy sync cross-tenant with  Exchange Online

 

If you have used the copying mailbox content and permission option, e.g. with 3rd party tool. Mostly the source mailbox will stay as is. It might be required for accessing Share or Group mailboxes during the migration. If this is the case users still active in the source tenant need to know if a user is active where (source or target) if you use the Organization Relationship.

Another technology option comes into place, Calendar + Free/Busy Sync! It is always a 3rd party solution.

Free/Busy sync is established between the source and target tenant. Keeping users calendar in-sync. This applies to both possible directions from source to target and from target to source. If a calendar is in sync.

 

Free/Busy is part of a EWS calendar sharing feature and can be enabled e.g. in Quest on Demand cloud migration suite.

 



Comments

Post a Comment

Popular posts from this blog

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

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