Microsoft Teams Connect shared channels is rolling out to public preview

Following on from above ... here is a screenshot with the ability to write and read posts in shared channel even though there is a prompt for the 2nd factor for the shared channel.

Setup in tenants were.

• Conditional Access MFA enabled in 'gbbtest.xyz' tenant, for access to Office 365 apps (which includes Teams of course)
• Conditional Access MFA Disabled in 'm365x71532238.onmicrosoft.com' tenant - so not enforcing MFA for user 'garyb2338@m365x71532238.onmicrosoft.com' (this is the issue the tenant 'gbbtest.xyz' is trying to avoid, ie risk they want to eliminate)
• B2B Direct Connect setup on both side for the respective tenants (ie not using Default settings. Default is actually set to Block all inbound and outbound)

'garyb2338@m365x71532238.onmicrosoft.com' logs into home tenant, and can get access to his channels, as well as access to a Shared Channel in the gbbtest.xyz tenant, that 'adelev@gbbtest.xyz' has shared with him.

... And has the ability to write and read posts in shared channel even though he didn't do MFA, and he is getting prompted for the 2nd factor by 'gbbtest.xyz' tenant