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

 How to structure Teams with Groups   With Teams Client 2.1 there are new, helpful features released. Often we see, that we are part of TOO MANY TEAMS. This is primarily, if Teams is used as a Information and Community board too. This is ok, but it has disadvantages in the form of Teams becomes not over seeable any longer. The well-known setting option allows you to "hide" or "show" Teams. But this isn't all. Might want Teams which are more frequently used in your upper sort order. OR Teams which are less frequent used or not that important, further to the end of your list.

 Hi all, this is part 7 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 6 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 5 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 4 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

 Hi all, this is part 3 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

Hi all, this is part 2 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

Hi all, this is part 1 of  7 videos we streamed about the cross-tenant migration during Merger and Acquisitions. After watching this series, you are able to manage and setup a cross-tenant migration project. Knowing whats important, where to have more intense focus on and what possible to migrate and what's not. Part 1: General Overview Part 2: Personal Data Migration (Mailbox, OneDrive, ..) Part 3: Collaboration Data Migration (SharePoint, Groups, ..) Part 4: Collaboration Services (Telephony, Teams, ...) Part 5: Legal and Compliance (Migration and what to consider) Part 6: Device Migration (Azure, Intune, SCCM, ...) Part 7: Change & Adoption

  Cross-Tenant Synchronization for seamless application access is now generally available! - Microsoft Community Hub Cross-tenant access settings for secure collaboration now generally available! - Microsoft Community Hub More learning can be found here: What is a cross-tenant synchronization in Azure Active Directory? - Microsoft Entra | Microsoft Learn

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

During the last month, Microsoft updated the Teams experience. The important feature turning off incoming video has moved to a new position. Click " VIEW " and than " MORE OPTIONS " -> " Turn off incoming video "

 It is important for users informing other about their status or migration. Therefore, Exchange Online offers good solution, the Out Of Office Message. User might even receive a new DNS domain in some cases. For good user experience, internal and external persons could be informed. Out of Office messages are also visible in Microsoft Teams. User the cmdlet  Set-MailboxAutoReplyConfiguration Example: Set-MailboxAutoReplyConfiguration -Identity user@contoso.com -AutoReplyState Enabled -InternalMessage "I'm migrated to TARGET." -ExternalMessage "Due to our company merger, I'm migrated to COMPANY, you will be able contacting me at user@target.com." -ExternalAudience All 

 

  Cross Tenant User Adoption Process   Change & Adoption is the most critical task in any tenant-2-tenant migration. Not only users who are migrated are impacted heavily by the migration. Users in the target tenant too. Especially in the target tenant they will experience constant changes. New users and groups are appearing, but not “life”, not actively working in the tenant. Further, new services related content will sequentially appear, like SPO sites, Teams Channel, Yammer or others. Since data is flying in slowly, there must be a communication and identification in place, that user are enabled identifying data source in migration. Same applies, for user in the source environment. Content/ data migrated will be in read-only. Content could become unavailable due to accomplished migration to the target. All depends on the migration process, procedures and planning. This needs to be communicated to all users in proper manner. Talking about external users, there is even a m

If you want to test the new amazing (but not jet feature rich) Teams client. Really awesome is the speed and I can't await that all features are available Here it comes and how to enable. You have to navigate into Team Admin Center.

 In this cross-tenant/ tenant-2-tenant migration book, I guide you through the holistic approach, which in deep exercise of Team Voice. I’m working as an Enterprise Solution Architect for Cross-Tenant migration, leading teams with more than 40 persons involved. Technically there are many more aspects, like 3rd party tools vs. Microsoft own solutions and scripts to be written. This book provides you an inside but not providing scripts and detailed configuration. Scripts and configurations are very much an individual approach for each cross-tenant migration. Two very special chapters will be released in 2023, handling and working with Guest User Access and Change & Adoption approach. Both are not only technically important but require a deeper look into their dependencies. Working on an end-2-end overview, technical considerations and understandable working template, this Migration book, it was work consolidated during the last 1 ½ years. DOWNLOAD HERE:  https://www.slideshare.net/th

Dedicated White Paper to Microsoft TEAMS CROSS-TENANT Migration. The guide includes Teams Team/Channels, private/ personal chat and Enterprise Voice  (Direct Routing) migration explanation and recommendations. It is written for decision maker, project manager and solution architects. Download @ SlideShare  https://www.slideshare.net/thomaspoett/cross-tenant-migration-microsoft-teams

  Cross-tenant Shared DNS Space (Native Cross-Tenant Domain Sharing for Exchange Online)   Upcoming new features, describe and change migration approach, (private preview) Reference: Supporting Mergers, Acquisitions, and Divestitures in Microsoft 365 - Microsoft Community Hub   Microsoft has announced publicly a new expected solution architecture and some of the configuration and management tasks you must perform when utilizing native cross-tenant domain sharing functionality. Below, the step-by-step description to enable cross-tenant domain sharing for a single SMTP domain. (valid as long no major changes are introduced by MS) The domain will be Authoritative in the Tenant where you perform the primary domain management. Up on enablement for domain for cross-tenant domain sharing, you will be able to add the domain as an Internal Relay in additional tenants. An internal Relays is like in Exchange On-Premises relay configuration.     Cross-Tenant Domain Sharing Conf