Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant Migration Specialist)

 Faster Search with new Slash commands in Teams (Tips & Tricks)

  Handling Call Queues and Auto Attendant during Cross-Tenant Migration   Note: Call queues can’t be externally chatted with. This is an important information and is the main problem you will have to deal with. Nevertheless, there is a feature, where a call is assigned to a Teams Channel. This allows at least the functionality of Guest User Access. Steps for handling Call Queues: Identify all Call Queues and Groups/ Channel(Teams) Identify all User assigned to Call Queues Identify Users assigned to multiple Call Queues Identify the purpose of the each Call Queue Identify Call Queue used internal, external (phone), internal and external, channel used For all Call Queues used internally, discuss and consider changing them to a Channel based Call queue and build a solution for revers Guest Access. Meaning, make sure you have a process included where migrated users, using the call queue have access via Guess Access from Target to Source. It is advised, that users in a Call Q

  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 3 rd 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 Exc

How to fix Exchange Hybrid Wizard Error 1603 This issue is related to TLS 1.2 Some links for you: Microsoft Entra Connect: TLS 1.2 enforcement for Microsoft Entra Connect - Microsoft Entra ID | Microsoft Learn The following scripts, you need to copy and same as CheckTls.ps1 and EnableTls.ps1 Frist if you run any of the following scripts, make sure UAC is disable :) Start with checking TLS Settings: FunctionGet-ADSyncToolsTls12RegValue {[CmdletBinding()]Param(# Registry Path[Parameter(Mandatory=$true,                    Position=0)][string]$RegPath,# Registry Name[Parameter(Mandatory=$true,                    Position=1)][string]$RegName)$regItem= Get-ItemProperty-Path $RegPath-Name $RegName-ErrorAction Ignore     $output= ""|selectPath,Name,Value     $output.Path = $RegPath$output.Name = $RegNameIf($regItem-eq$null){$output.Value = "Not Found"}Else{$output.Value = $regItem.$RegName}$output}$regSettings= @()$regKey= 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFrame

 You have Exchange Hybrid in place. Now you wonder about an address with you see on-premises with all users. This address has the following format: x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOxxxxxx)/cn=Recipients/cn=234xxxx This address is now found in the Exchange proxyAddresses in On-Premises as well as in Entra ID. Additionally you will see them in msExchShadowProxyAddresses The ExchangeLabs is Microsoft internal Exchange Online Organization and therefore needed. This x500 address is created in Exchange Online and sync'ed via Azure AD Connect (Entra ID Connect) back on-premises. If you delete this address on-premises, the connection between will sync this Cloud leading attribute back to on-premisses. If you have multiple Domains and Active Directories connected to your Tenant, this x500 address from your tenant will be added to ALL users. Also to users which are from an local AD without Exchange / Exchange Hybrid. As long AAD Connect/ Entra ID Connect will have