SOLVED

Inviting guests was working - now it's not

%3CLINGO-SUB%20id%3D%22lingo-sub-197045%22%20slang%3D%22en-US%22%3EInviting%20guests%20was%20working%20-%20now%20it's%20not%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197045%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20enabled%20Teams%20guest%20access%20in%20April%2C%20tested%20it%2C%20and%20rolled%20it%20out%20to%26nbsp%3Bteam%20owners.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ELast%20week%20we%20discovered%20we%20could%20no%20longer%20invite%20guests.%3C%2FSTRONG%3E%20The%20Add%20Members%20dialog%20box%20shows%20the%26nbsp%3Bpre-guest-access%26nbsp%3B%22We%20didn't%20find%20any%20matches%22%20message%20when%20an%20external%20email%20is%20entered.%20%3CSTRONG%3EWe%20also%20can't%20add%20an%20existing%20guest%20to%20another%20team%3C%2FSTRONG%3E%20-%20the%20error%20messages%20%22%3CEM%3EWe%20couldn't%20add%20member...We%20ran%20into%20an%20issue.%20Please%20try%20again%20later%3C%2FEM%3E%22%20show.%20Similar%20results%20for%20public%20or%20private%20teams%20in%20Windows%2C%20Mac%2C%20web%2C%20iOS%20and%20Android.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EAny%20clues%3F%3C%2FSTRONG%3E%20We%20checked%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fguest-access-checklist%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eall%20the%20settings%3C%2FA%3E.%20None%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FGuest-Access-Troubleshooting-Guide%2Fm-p%2F119797%23M8423%22%20target%3D%22_blank%22%3Eguest%20access%20troubleshooting%20guide%3C%2FA%3E's%20scenarios%20were%20relevant.%20We're%20a%20nonprofit%20enterprise%20tenant.%20Everything%20else%20seems%20to%20be%20working...as%20well%20as%20ever.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-197045%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGuest%20Access%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-199017%22%20slang%3D%22en-US%22%3ERe%3A%20Inviting%20guests%20was%20working%20-%20now%20it's%20not%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-199017%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20know%20if%20we%20have%20access%20to%20the%20new%20Admin%20Center%20yet%2C%20but%20the%20solution%20was%20to%20turn%20guest%20access%20off%20temporarily%20and%20then%20re-enable%20it.%20Maybe%20something%20got%20lost%20in%20the%20transition%20to%20the%20new%20Admin%20Center%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197057%22%20slang%3D%22en-US%22%3ERe%3A%20Inviting%20guests%20was%20working%20-%20now%20it's%20not%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197057%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F875%22%20target%3D%22_blank%22%3E%40Christopher%20Webb%3C%2FA%3E.%20I'm%20checking%20with%20my%20admin%20teammate%20who%20has%20access%20to%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20see%20a%20similar%20issue%20began%20mid-month%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FAdding-external-users-to-teams%2Fm-p%2F194348%2Fhighlight%2Ftrue%22%20target%3D%22_blank%22%3Eanother%20thread%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197053%22%20slang%3D%22en-US%22%3ERe%3A%20Inviting%20guests%20was%20working%20-%20now%20it's%20not%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197053%22%20slang%3D%22en-US%22%3EHave%20you%20checked%20to%20make%20sure%20you%20may%20have%20received%20the%20new%20Teams%20Admin%20center%3F%20Might%20need%20to%20check%20the%20policies%20there%20something%20could%20have%20been%20overwrote%20possibly!%20It%20should%20be%20accessible%20here%20if%20you%20have%20it%20pushed%20to%20your%20tenant%3A%20%3CA%20href%3D%22https%3A%2F%2Fadmin.teams.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fadmin.teams.microsoft.com%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-712586%22%20slang%3D%22en-US%22%3ERe%3A%20Inviting%20guests%20was%20working%20-%20now%20it's%20not%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-712586%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4032%22%20target%3D%22_blank%22%3E%40John%20Egleston%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20got%20the%26nbsp%3Bexternal%20guest%20error%20%22we%20ran%20into%20an%20issue%22%20when%20adding%20a%20person%20to%20Microsoft%20Teams.%3C%2FP%3E%3CP%3EWe%20found%20a%20different%20solution%20that%20may%20be%20useful%20to%20other%20readers%20of%20this%20post.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ESituation%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3A%20Had%20a%20project%20using%20a%20Microsoft%20Team%2C%20external%20consultants%20were%20added%20to%20the%20project%20using%20their%20email%20addresses%20e.g.%20bob.McLastname%40bobconsulting.com%3C%2FP%3E%3CP%3ESome%20months%20later%20a%20new%20project%20was%20started%20with%20the%20same%20real%20people%20but%20the%20consulting%20company%20had%20been%20bought%20out%20so%20now%20Bob's%20email%20address%20became%20e.g.%20bob.McLastname%40reallybigconsultingfirm.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETrying%20to%20add%20bob.McLastname%40reallybigconsultingfirm.com%20to%20the%20new%20project%20Teams%20site%20gave%20the%20%22we%20ran%20into%20an%20issue%22%20adding%20a%20guest%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Azure%20AD%20we%20searched%20for%20Bob%20McLastname%20and%20found%3C%2FP%3E%3CP%3E-%26nbsp%3Bbob.McLastname%40bobconsulting.com%3C%2FP%3E%3CP%3EWhen%20we%20deleted%20bob.McLastname%40bobconsulting.com%20from%20Azure%20AD%20we%20were%20then%20able%20to%20add%20him%20to%20the%20new%20project%20team%20without%20error%20using%26nbsp%3Bbob.McLastname%40reallybigconsultingfirm.com%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

We enabled Teams guest access in April, tested it, and rolled it out to team owners.

 

Last week we discovered we could no longer invite guests. The Add Members dialog box shows the pre-guest-access "We didn't find any matches" message when an external email is entered. We also can't add an existing guest to another team - the error messages "We couldn't add member...We ran into an issue. Please try again later" show. Similar results for public or private teams in Windows, Mac, web, iOS and Android.

 

Any clues? We checked all the settings. None of the guest access troubleshooting guide's scenarios were relevant. We're a nonprofit enterprise tenant. Everything else seems to be working...as well as ever.

4 Replies
Highlighted
Have you checked to make sure you may have received the new Teams Admin center? Might need to check the policies there something could have been overwrote possibly! It should be accessible here if you have it pushed to your tenant: https://admin.teams.microsoft.com
Highlighted

Thanks, @Deleted. I'm checking with my admin teammate who has access to that.

 

I see a similar issue began mid-month in another thread.

Highlighted
Best Response confirmed by John Egleston (Contributor)
Solution

I don't know if we have access to the new Admin Center yet, but the solution was to turn guest access off temporarily and then re-enable it. Maybe something got lost in the transition to the new Admin Center?

Highlighted

@John Egleston 

We also got the external guest error "we ran into an issue" when adding a person to Microsoft Teams.

We found a different solution that may be useful to other readers of this post.

 

Situation : Had a project using a Microsoft Team, external consultants were added to the project using their email addresses e.g. bob.McLastname@bobconsulting.com

Some months later a new project was started with the same real people but the consulting company had been bought out so now Bob's email address became e.g. bob.McLastname@reallybigconsultingfirm.com

 

Trying to add bob.McLastname@reallybigconsultingfirm.com to the new project Teams site gave the "we ran into an issue" adding a guest error.

 

In Azure AD we searched for Bob McLastname and found

- bob.McLastname@bobconsulting.com

When we deleted bob.McLastname@bobconsulting.com from Azure AD we were then able to add him to the new project team without error using bob.McLastname@reallybigconsultingfirm.com