The Teams Windows and MacOS desktop clients will soon allow users to add a personal account to the set of Office 365 tenants they connect to. A great deal of excitement ensued after people saw Microsoft 365 roadmap item 68845 and assumed this meant that Teams would support connections with multiple work accounts. The ability to add more than one work account to your Teams profile isn’t available now as the update is to support connectivity to Teams at home (personal), but support for multiple work accounts is coming in the future.
Over time, you might join several Office 365 tenants as a guest. Some of those Azure AD guest accounts probably won’t be needed forever and you want to clean them up. This is easy for individuals to do through their MyAccount page, which might just be a page that they never knew existed.
Office 365 makes extensive use of Azure Active Directory guest accounts. Implementing a risky sign-in policy is a good idea, but it can have the unfortunate side-effect of suddenly blocking guest accounts that could previously access tenant resources. If blocks happen, they can only be lifted through administrative intervention in the guest account’s home tenant.
Microsoft has launched email one-time passcodes (OTP) into preview for Azure Active Directory guest accounts. It’s all to do with better collaboration. OTP doesn’t support Teams, Planner, or Office 365 Groups yet, but it can be used to share documents from SharePoint Online or OneDrive for Business.
Now that we know all about the different email addresses used by Office 365 Groups and Teams, the question arises of how to include a team channel as a member of a distribution group. As it turns out, there’s a simple way and a more complicated way.