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

  If you want to do in deep Teams Client analysis, you need to download WebLogs from the active Teams client. This you can do by pressing the key phrase of CTRL (STRG on German Keyboard) + ALT + SHIFT + 1 The log files will be stored in your download folder. Happy analyzing ;)

 Teams Shared Channel without Tenant Switching An new feature to Microsoft Teams was introduced and makes cross-tenant collaboration much easier. The need of switching a tenant, gaining access to Shared Channel, were you are member of with your Guest Account is now obsolete. With B2B relationships between 2 tenants, the B2B Guest Account can be used within your own organization. This eliminates the tenant switching for efficient collaboration. This feature is available bi-directional. NOTE: with this shared channels, NO B2B Guest Account is needed . The trust relationship between those tenants involved, for Teams only (M365 Group with Teams enabled) accessing the SHARED CHANNEL ONLY in TEAMS based on the invite. Opponent users are found and identified based on the their UPN and Tenant ID Trust. The "embedded" Team Channel is marked with to identifiers: - @Contoso : this indicated, the Teams and its Channels are located outside of your organization and is naming the partner te

Cross-Tenant Access Settings - Unable to find Tenant It might be happen that the name.onmmicrosoft.com or FQDN of the partner tenant isn't working. In this case you must use the ENTRA TENANT ID: Not Found: Found with ENTRA ID TENANT ID

Connecting with PowerShell to the Teams module. Often I'm asked: How to connect to Teams Module with PowerShell. If it fails with the message below, this is in Windows 10/11 the issues with Set-ExecutionPolicy. Set-ExecutionPolicy Unrestricted Required: PowerShell 5.1, .NET Framework 4.7.2 Install-Module -Name PowerShellGet -Force -AllowClobber Install-Module -Name MicrosoftTeams -Force -AllowClobber (or if installed: Import-Module PowerShellGet, Import-Module MirosoftTeams) Connect-MicrosoftTeam s

 If you need to build templates or compare tenant settings. e.g. if you need to identify discrepancies for a cross-tenant migration.  The PowerShell cmdlet  Export-M365DSCConfiguration   allows you to compare settings. Introduction - Microsoft365DSC - Your Cloud Configuration Microsoft365DSC - Configuration-as-Code for the Cloud # Generated by Microsoft365DSC from https://export.microsoft365dsc.com on 04/03/2024, 17:44:22 # Visit https://microsoft365dsc.com for more information # Getting client credential $Credential = Get-Credential # Exporting resources using credentials Export-M365DSCConfiguration -Components @("AADAdministrativeUnit", ......l

 NOTE: the core (during setup) language is set, defined and "burned-in" during your tenant setup. You CANNOT change the M365 Core language (the language the tenant was setup in). This impacts all users in your tenant. They will ALLWAYS receive notification in the language defined during SETUP. Meaning: If you have set FRENCH during setup and change to e.g. English or whatever else. System Messages like SharePoint Storage limit is reached will be in the setup default language. In this case here French! The Organizational Information setting below will not change the default language to users or admins. ! Be ware of the difference of "PREFERRED LANGUAGE" and the "CORE" language chosen during tenant setup! -> NOTE: always document the language during setup of a tenant ! You will are not able to see the core language. But in case of tool based cross-tenant migrations, e.g. with SharePoint, the library folder in a target tenant will appear in the source tena