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

This is an know bug within Teams. This issue is happening on desktop and mobile version only, if you had installed the Teams app before and changed / created a new Microsoft M365 Tenant with the same user name (UPN/ SIP) Solution: Uninstall Teams App Delete all Teams references and folders Reinstall Teams App Login normally

 Teams Federation isn't working. The Get-CsTenantFederationConfiguration will show the current settings of your federation setup. Nevertheless, if you are owner of an Microsoft TRIAL tenant, federation with other tenants isn't working automatically any longer. Microsoft had introduced an new parameter: -ExternalAccessWithTrialTenants "Blocked"  Therefore, all Microsoft Tenants have the new DEFUALT setting "Blocked" defined. Your partner organization must remove "ALLOW" the federation with you. This also impacts all Microsoft MVP Tenants with only MVP assigned licenses. Note a side: The RUN TEST diagnostic will provide you with false positives here: https://aka.ms/TeamsFederationDiag IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities - Microsoft Teams | Microsoft Learn

Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams. If your organization needs to export Microsoft Teams messages, you're able to extract them using Teams Export APIs. Export content with the Microsoft Teams Export APIs - Microsoft Teams | Microsoft Learn NOTE: You might need additional API Access License.

  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