Jan 13 2017 12:18 PM - edited Jan 13 2017 01:54 PM
Within the last month we have started to notice more and more external users having issues accepting sharing invites sent from SharePoint online.
I believe this has to do with recent changes to the creation of Microsoft accounts. In this current example, we have invited an external user who tries to create a microsoft account, but are told they cannot create a new account with a company email address - this would typically indicate the external user's company is using Office 365 / AAD, and we could instruct them to sign in with the organizational account option. However when they attempt to log in with with the Org account option, they are told the account doesn't exist. See attachments for.
I'm stuck. Any thoughts on why the system believes they have an Org account, but are unable to log in with it?
Jan 14 2017 12:40 AM
Jan 14 2017 01:10 AM
Yeah @Juan Carlos González Martín you are right but they changed this to use Azure B2B and thought you do no longer need a ms account
Jan 14 2017 01:34 AM
Jan 14 2017 02:11 AM
Hi @Juan Carlos González Martín.
If I understand well, you are saying that it is not possible anymore to create an MSA using an email address in a domain that is already in Office365. Am I correct?
Can someone point to an official statement by Microsoft about that?
Jan 14 2017 02:20 AM
Jan 14 2017 02:22 AM
it is still possible but prefered to use B2b if possible. as far as i know it is not necessary to create a live account anymore.. but not 100% sure
Jan 14 2017 02:25 AM
Jan 14 2017 04:02 AM
Thank you very much @Juan Carlos González Martín !
Precious post, as usual!
Jan 14 2017 04:43 AM
Jan 14 2017 09:17 AM
@Deleted
Consumer email addresses (such as outlook.com or gmail.com) are not supported by B2B. Hence an external user with a consumer email address must sign in with an MSA.
Jan 14 2017 10:10 PM
@Salvatore Biscari @Juan Carlos González Martín thanks for explaining and adding the direct links :)
Jan 16 2017 07:55 AM
I understand Live IDs with Org accounts are no longer supported when the org account is associated with an AAD account.
However the issue with a few users is that they are unable to create a Live ID account AND they are getting an error that their Organizational account doesn't exist.
Leaving them with no way to accept a sharepoint invite or log in with their business account.
Feb 02 2017 07:02 AM
I'm still not sure of all the details around this but it appears that this change is having consequences and forces people to register with a non work account. I think this is how it manifests itself...
An invite was sent to an individuals work account xx@yy.com, but their organisation is O365 enabled and the individual has not been assigned O365 licence. Our set up is such that the invited user has to use the invited email address, so we know what organisation they belong to. However because they aren't on O365 user & they are now unable to create an account with work email ID we are now stuck in limbo.
Is this expected behaviour or unintended consequence or we have missed some configuration setting somewhere ?
Only solution I have at the moment is to get user created within AD or to invite under personal email account. Neither of which we want
Anyone else experiencing this ?
Feb 03 2017 09:36 AM
Also another scenerio I just encountered this week - working with adding users from a company who doesn't use Office 365 but does use Azure AD - but only for migrating their users between companies. So the user we were inviting couldn't create an MSA with their work account and couldn't accept an invite with their Org account, because the email address associated with the user is not the same as their AAD entry.