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 collaboration across organizational boundaries, such as multiple tenants, allowing everyone to work as one extended team while staying in their own Teams environment. Teams Connect shared channels allow you to chat, call, meet, and collaborate on files while staying in the flow of work, with no tenant switching required. Simply invite stakeholders to the shared channel, which then appears alongside the user’s list of channels. From there, all the channel’s members can collaborate, regardless of their tenant.


Shared channels do not require MTO configuration, but can be leveraged in multi-tenant organization scenarios for enhanced collaboration.

 

Getting started with MTO in Teams
To enable these MTO capabilities in Teams, admins will need to configure their MTO tenant in the Microsoft 365 admin center (now in public preview), which will perform a full sync of users across the tenants in the MTO group. Teams will automatically turn on the MTO features with no additional configuration or settings required to be managed in Teams.

 

Availability

MTO capabilities are now available to commercial users on the new Teams Windows, new Teams MacOS, iOS and Android client apps. A version of the Teams web app will also be optimized for these MTO features in the future.

 

For more information about MTO, visit our admin documentation and adoption pages below:
Plan for multi-tenant organizations in Microsoft 365 (Preview) - Microsoft 365 Enterprise | Microsof...
Shared channels in Microsoft Teams
Microsoft Mechanics: Shared channels in Microsoft Teams (YouTube)
Adopting the new Microsoft Teams

Comments

Post a Comment

Popular posts from this blog

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more

How to hide users from GAL if they are AD Connect synchronized

-
Image
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
Read more