Rethink Guest Access
Switching 'tenants" is impractical for most business uses. Your average CEO, or hourly employee, is not going to remember to switch accounts to see negotiations. The fact that you can't see notifications seemlessly from one account is why you need to rethink the guest access layout.
It would better to see all notifications AND ANSWER THEM from your 'main' account. Not after you switch to your guest account. Efficient communication is thrown to the wayside with the current guest access setup. To me, guest access is useless.
This is the main reason I will not use teams. ALL of my collaboration is external to my agency and Teams seemed the way to go. But Now I see each person I want on the team has multiple isses with getting into the team, then different issues with staying in the team. Many of these folks are not computer savvy...please make this a priority!
Partners want to be notified when guests access.
If you promote in-house Teams, the teams with Microsoft may not be notified, so contact may be delayed.
David McKnight commented
Having to change tenants to use the features of Teams is the primary reason we have been slow to deploy to our clients. They are not going to think to switch to our tenant to check to see if there is anything worth looking at -- they need to be proactively notified to look (and the little number above the tenant switch is not it). They need to get a banner that says a message has come in, or an @mention is there -- or there is other activity in a channel they are following. Without this, the collaboration promise falls way short.
I totally agree on this one.
Guests getting alerts and not having to switch are two must have features.
See also: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31421677-eliminate-context-switching-from-guest-feature
Wholeheartedly agree on this.
Use Case: I was at Ignite this week and a part of an Ignite Teams group. Switching the context to the other org (ex. Contoso), I get the notifications and ease of use for Contoso, but not my business Teams. I lose complete visibility to it unless I switch back to it.
Ian Caldwell commented
Guest access in Teams has become a nightmare for our company. We are project-based and work extensively with external partners - and we have no idea what system they use, so when they already have Exchange online and nothing else, Teams will not work. Guest access for Teams either must work with almost any invited user, or be turned off completely. This half-way, might or might-not work Teams guest access is killing adoption among our 250+ employees.
gravescj2018 commented from docs.microsoft.com
Step 3 says "The guest receives a welcome email from the team owner, with information about the team and what to expect now that they're a member. Guest users who have an email address that belongs to an Azure Active Directory or Office 365 work or school account can accept the invitation directly."
There is a serious problem when the organisation has only part adopted Office 365. This is happening with some UK universities where students have an Office 365 email account and ID but staff have an "on premise" exchange email account.
Trying to add these staff members as guests to a "Teams" set-up at another institution which has fully adopted Office 365 - is very difficult. Currently the advice from Microsoft Partners seems to be go and create a Gmail account - use that as your guest access method and get the gmail account to forward all your email from teams to your institutional account. Current GDPR ethos makes using a consumer account problematic in various instances.
Microsoft needs to find a way round disenfranchising potential guests that operate in an environment which is completely Microsoft licensed but which blocks them from being a guest because their exchange email address is blocked from becoming a "Microsoft account"
Graham McKendry commented
Sounds similar to https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31421677-eliminate-context-switching-from-guest-feature - Possibly an opportunity to merge the UserVoice requests...