Microsoft introduced Microsoft Teams a while ago, scaring Slack having a potential competing product in a way that Slack printed a page size advertisement in the New York times and online on Slacks blog:
The community was extremely enthusiastic around the release … until they found out that only team members could be added from their own tenants. Another thing was that Microsoft Teams is only available for paying Office 365 (so called business accounts) and EDU accounts (free for education).
Especially the limited team member scope was reason for the community to compose a UserVoice request:
Well, Microsoft heard it and promised to solve it in June, delayed it twice but (partially) delivered today:
It is a first step, you now should be able to invite guests from other tenants. I just tried and still not possible hear, but I’m sure it will be soon. The delivery method on Office 365 often is trickled down in segments so I’m apparently not in the first batch.
Next in line will be guest access for MSA (Microsoft Account) types of guests. Another improvement, who doesn’t have an MSA (especially if you want to use Microsoft Teams ).
Interesting part of all of this is that the UserVoice specifically requested NOT to limit guest access to MSA accounts:
“Finally, making external parties sign up for a Microsoft account (such as Hotmail) to authenticate against any collaboration service does not work, and better approach is required and needed.”
In other words, the request was to open Teams up for all types, not only Microsoft based accounts. From a business point of view, there is something to say for limitation to Azure AD accounts (and eventually MS accounts) to be able to at least getting some user context en improving security to where potential critical business information can be shared.
From a developer’s perspective I guess we can expect interfaces to automate team member management and extended APIs. For now let’s wait for the next step, adding MSA guest access first.