10-24-2017 02:08 PM
10-24-2017 02:08 PM
The always helpful and awesome @Tushar Pathak from the Microsoft Teams support team has put together a handy Guest Access Troubleshooting Guide with some of the most common Guest Access issues and solutions they see internally. All credit to him on this - I'm just the messenger on this one!
11-13-2018 12:44 AM
While this is a good guidance the - main problem I see for the moment - and being a victim of it is who is the problem owner ?
User A is a Teams User in Tenant A.
User B is a Teams User in Tenant B.
User B invite User A as a Guest in Tenant B.
User A Gets the invite and is in the Guest Loop Switching Tenant.
User A Opens a calls with helpdesk A of Tenant A. - According to helpdesk A all is ok
User A Contacts User B. User B is soooo lost …
This is so boring … LOL
05-23-2019 06:47 AM
@David Rosenthal In the trouble guide you posted, in the settings under the O365 admin center in "Settings" and "Services & add ins" then "Microsoft Teams", and the "Settings by user/license type" there is only one selection of "Business & Enterprise" and no "Guest" selection. All other parts of the trouble guide suggested settings are correct in both Azure and O365. Any ideas why I don't see "Guests" as a selection?
05-23-2019 08:47 AM
I've reached out to O365 Support, to confirm, however they just linked me back to this guide :(, but I believe this is a licensing issue. The client in question is using email, but not the licenses I believe are eligible for Guests in teams.
05-23-2019 09:05 AM
Thanks for taking the time to post. However that isn't the issue in my case. I've already verified that setting is on, and have waited a day or two to see if it was a timing issue. If you have other suggestions, I'd gladly review, as you noted things change quickly however I have followed this:
before reviewing this guide.
05-23-2019 09:09 AM
@Steven Collier Steven, thanks but as stated in my original post all other items are setup as described in the trouble shooting guide, including this "guest access" flag in the Teams setup. Very confusing. I'm wondering also if this is a licensing issue. We are only licensed for O365 Business Pro and Microsoft 365 on a few users. Not enterprise. Hopefully Microsoft will understand that SMB companies use these things too, not just the big dogs. Otherwise I still need to allow users to use insecure services like Slack... Yuck.
05-23-2019 09:31 AM
@wjfinnigan They tried to purchase Slack but failed. Instead purchased some other similar companies. Slack, I understand, is on the rocks right now due to continued funding issues which is odd considering how popular they are. I just can't get over we've verified security issues with using them.
05-23-2019 11:23 AM
So it turns out all my settings were correct. And no licenses were required.
However currently some email addresses cannot be added until after they have been added as a guest account in azure active directory:
Admin Centers > Azure Active Directory
Users > New Guest User
Not sure why the workaround is required in some situations and not in others (I'm guessing they already have a guest account on another O365 tenant, but unconfirmed).
But that is the fix and things are working for me again. I hope it is that easy on your side as well.
05-24-2019 08:05 AM
So whenever someone needs to add a guest as a member on Teams I need to add first in Azure?
I'm not sure this is something I would like to do
05-24-2019 08:08 AM
05-24-2019 08:52 AM - edited 05-24-2019 09:04 AM
@adam deltinger following the guide I managed to make it work. I had enabled Guest Access from Teams Admin Center but it didn't work straight away. It worked after I have run the PS command Set-CsTeamsClientConfiguration -AllowGuestUser $true -Identity Global
05-28-2019 05:09 AM
@ripsy85 Thanks for the info, but I'm not aware of how that PS command works. When attempting to run locally, I get the error below. Does this need to be run from the cloud? Sorry for my lack of training on this.
Set-CsTeamsClientConfiguration : The term 'Set-CsTeamsClientConfiguration' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.
At line:1 char:1
+ Set-CsTeamsClientConfiguration -AllowGuestUser $true -Identity Global
+ CategoryInfo : ObjectNotFound: (Set-CsTeamsClientConfiguration:String) , CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
You first need to connect the Microsoft Teams through PS. See below:
@Milena365 Thanks, I've been seeing that. Kind of upset that Microsoft doesn't see the need to do this type of work in a more modern fashion. We were supposed to get rid of the command line decades ago, yet it still plagues us, seems even more today. Power Shell should never be the ultimate answer, but only a work around in rare cases. Guest access is not a rare case, IMHO.