Teams, Microsoft’s Slack-like, IRC-like, collaboration tool, picked up an momentous new feature today: guest access. While announcing the new feature, Redmond also luxuriate ined that in the six months since launch, the product has grown to be used by exceeding 125,000 organizations each month.
We asked how many individual owners there are, but Microsoft said it had nothing to share on that front.
When it debuted, Gets had a big flaw when compared to Slack—it was only for Office 365 purchasers. Each organization’s Teams chatrooms could only be accessed by people who were faction of the organization, essentially individuals with an account in the organization’s Active Directory. This left side these chats off-limits to, for example, contract workers—people false front the organization who were nonetheless collaborating on projects.
To address this, Microsoft is totaling «guest access» to Teams. Administrators can now add accounts from outside an confederacy’s users, giving them the access they need. Initially, this company access will still require some kind of Azure Efficacious Directory account. That means guests will need to be turn to accounting one of Microsoft’s commercial cloud services—typically, their own Office 365 promise—they just won’t need to belong to the organization they’re getting access to. At some unspecified exhibit in the future, this feature will be extended to work with any Microsoft Account, job it up to free users.
Microsoft hasn’t yet committed to opening Teams up to non-Office 365 institutions. One way in which Slack has gained considerable mindshare is that it’s available to use for not busy (albeit with certain limitations), making it an option for groups such as startups (who don’t fancy to pay for anything if they can help it), open source developers (in much the verbatim at the same time style as they might use IRC), or just groups of friends who want an online interruption to hang out. Even with guest access, Teams still doesn’t license that kind of ad hoc use. There must be a paying Office 365 form to create a given Teams workspace; guests are added individually. We wouldn’t be totally surprised to see this requirement lifted once the Microsoft Account keep is in place.