Easiest way to get back to this is go to azuread and delete the guest account then delete it from deleted users and resend invite. If this doesn’t work you’ll need to see if it’s the same bug we’ve been dealing with where the account is a work account and they don’t have a Teams license or teams enabled on their end (sometimes those users don’t even know their account is in azuread somehow) and they might have to just setup a new outlook.com account to use.
Easiest way to get back to this is go to azuread and delete the guest account then delete it from deleted users and resend invite
Nice :thumbs_up:. Thanks for the workaround. We've gotten the user registered under a different account so we're good now. I would love to know if that fixed it though. I suspect so.
I hope you guys "trap" this error better in the future. It is very confusing in that the app doesn't tell the user anything. I had to hand hold the user to dig into the console window looking for errors.
We have just been looking at the issue where 'GuestUserNotRedeemed' was being returned for a Guest account. Turns out the guest user had previously had SharePoint shared before to their work account which wasn't at the time in Office 365. So they had used another account for authentication (@outlook.com) but now when we shared a site from Teams it was returning an error and getting confused. Reason being since then they had migrated to Office 365 with their work account.
So we removed all trace of the guest user from our Office 365 and shared the Team out again. This resolved the issue.