Forum Discussion
camha
Nov 13, 2021Copper Contributor
Sharepoint Error: This username may be incorrect for Guest User
Hi all, I am a Sharepoint and O365 admin (not super admin) for my organization. For all our sites the current External sharing setting is: "New and existing guests - Guests must use sign in or prov...
camha
Nov 15, 2021Copper Contributor
Hi, is this something for the partner's domain (p.com) or ours ?
Nov 15, 2021
Your org. settings.
- camhaNov 20, 2021Copper Contributor
ChristianJBergstrom this is from my org setting:
Am I correct to infer that the problem is not from our side?
I want to clarify the re-invitation issue:
- The user from p.com did receive an email invite, prompted to sign up for MS account
- They also get a verification code
- Once clicked Finish, they received:
the blurred out names are p.com (partner's domain)
- Nov 20, 2021
camha Hello again, I've actually never worked with Set-MsolCompanySettings as I've haven't stumbled across a scenario that required that config. But let me add some parts that might explain it further.
-AllowEmailVerifiedUsers
Indicates whether users can join the tenant by email validation. To join, the user must have an email address in a domain which matches one of the verified domains in the tenant. This setting is applied company-wide for all domains in the tenant.Set-MsolCompanySettings (MSOnline) | Microsoft Docs
AllowEmailVerifiedUsers controls whether users can join the tenant by email validation. To join, the user must have an email address in a domain which matches one of the verified domains in the tenant. This setting is applied company-wide for all domains in the tenant. If you set that parameter to $false, no email-verified user can join the tenant.
AllowAdHocSubscriptions controls the ability for users to perform self-service sign-up. If you set that parameter to $false, no user can perform self-service sign-up.
AllowEmailVerifiedUsers and AllowAdHocSubscriptions are tenant-wide settings that can be applied to a managed or unmanaged tenant.Here's an example where:
You administer a tenant with a verified domain such as contoso.com
You use B2B collaboration from a different tenant to invite a user that does not already exist (userdoesnotexist@contoso.com) in the home tenant of contoso.com
The home tenant has the AllowEmailVerifiedUsers turned on
If the preceding conditions are true, then a member user is created in the home tenant, and a B2B guest user is created in the inviting tenant.As the message indicates that the other org. has this disabled this you should probably reach out to them and either have them create an account or toggle this setting to true.
Let me know how it goes, I like learning new stuff!