01-04-2019 10:45 AM
To be clear every time I follow the link in the Teams Guest Invitation I get routed through to the Free Teams account I was forced to create, and didn't want in the first place.
I'm stunned that our Guests users (who are generally inexperienced IT users have been able to access the system at all). This is a support/ User Interface nightmare.
01-04-2019 10:54 AM
01-04-2019 11:10 AM
01-04-2019 12:42 PM
Also, you could look more deeply in AzureAD for guest account and you can use PowerShell to check the state of a guest user :
could you tell us what you have in you side ?
01-04-2019 01:14 PM
Could I ask a question? We're in the process of doing some pilots and I was confused how this worked for you - in our testing it seemed to work differently.
When I invite a guest and they get the email, it asks them to log in, and they use the invite email name and the password attached to their email account - they don't have to enter any special MS account.... doesn't it work that way for you?
I've tested it with someone who has never been in Teams, and someone who already has used it before and it works the same way. But this isn't the first time I've been confused by Teams....
Again, just a curiosity question so I can update my training materials.
01-04-2019 01:18 PM - edited 01-04-2019 01:18 PM
Both ways asks for a login, the e-mail template is always the same. Just sometimes it's easier if you have and use the same e-mail and login already on your machine it's usually cached so it goes right in. The issue usually happens most when you have either a user that has a work account with the same e-mail as a Microsoft account, or they get invited to a different address then what they are logged in with already, and that can be problematic sometimes.
As for the UI. Last I checked, you enter your e-mail, then right after you click next it offers to create one, or it was on the first box, it's been awhile but I know it was def. there on the first box, or right after you input one. (It's a small link and hard to notice... probably should be larger)