Showing posts from 2024

How to configure Teams Shared Channel without Tenant Switching

 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. 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 tenant. - (External) : further identification of a Channel, not located in your home Teams, is the word External. With those indicators, users are easily aware of the data boundaries where they are working in. Configuration on Microsoft 365 Tenant Level Teams Admin Portal The first step are to be accomplished in Team

Cross-Tenant Access Settings - Unable to find Tenant

Cross-Tenant Access Settings - Unable to find Tenant It might be happen that the 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

Connect PowerShell to Microsoft Teams

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

Export all your M365 Tenant Settings (DSC)

 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 on 04/03/2024, 17:44:22 # Visit for more information # Getting client credential $Credential = Get-Credential # Exporting resources using credentials Export-M365DSCConfiguration -Components @("AADAdministrativeUnit", ......l

Change Microsoft 365 Tenant Default Language

 NOTE: the default language is set, defined and "burned-in" during your tenant setup. You CANNOT change the default language. 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. !

Surface Slim 2 Pen not writing on Surface PRO

 It is an nightmare to solve this issue, put with a lot of patience you can solve it. Uninstall and reinstall everything on driver and firmware related to PEN and TOUCH . Procedue: 1. Surface Pen is paired on your Surface Pro open Device Manager 2. Click View on top and check Show hidden devices. 3. Expand Human Interface Devices category. Right click drivers and select Uninstall.  HID-compliant pen > Uninstall device Surface pen settings > Uninstall device Surface pen integration > Uninstall device HID-Compliant touch screen > Uninstall device Intel (R) Precise Touch Device > Uninstall device Surface Touch Pen Processor > Uninstall device Some have different names, but AGIAN uninstall EVERYTHING with PEN and TOUCH ! Note: If prompted with a checkbox stating, "Delete the driver software for this device", leave it uncheck then hit Uninstall. 4. Expand Firmware > Surface touch > Uninstall device Note: If prompted with a checkbox stating, "Delete the

Cross-Tenant Migration Legal-Hold or Encrypted Mail or File Data

 This is a quick note and IMPORTNANT : Within a Cross-Tenant Migration project, you can experience data encryption. Note the following statement and plan accordingly. Legal-Hold: There is no possibility to migrate data (EXO, SPO, OneDrive) if the source is set on legal-hold Encrypted Data: It depends on the encryption method. Either AIP or user based. If it user based, the migration can work and with the resignment of the the encryption/decryption might work again. But while the DNS domain is with the source tenant, encrypted mails become unusable. With AIP, the only way is to decrypt in source, than migrate and encrypt in target again. Migrating a tenant AIP key is NOT possible

Teams new and MTO (Multi Tenant Organization)

Microsoft is moving towards a new optimized collaboration and administration for organizations operating multiple M365 tenants. New Teams client is supporting this feature. Nevertheless, there are (today in public preview) limitations to MTO, which might be removed over time. Self-service of multitenant organization functionality is limited to a maximum of five tenants and 100,000 internal users per tenant. To request a raise in these limits, submit a Microsoft Entra ID or Microsoft 365 admin center support request. Further to me, it is NOT a real multi-tenant organization, as we know from earlier days in AD, where we had "SubDomains", it is based on automated B2B identities, which are provisioned as B2B users automatically. This is the sync feature in MTO. Below the extract from Microsoft blog release: Using shared channels for seamless cross-tenant collaboration and communication In a  recent blog , we shared how Microsoft Teams Connect enables seamless and secure collabora