Mar 23 2017 05:21 AM
Interesting behavior I have found Today at my corporate tenant: I created a new Group in tenant and invite some external users to the tenant...one of the external users invited reported that he was able to accept the invitation using his personal account in the form user@contoso.com...and here is where things become interesting: my intention was not to invite the user through his personal account, but use his professional account that is also user@contoso.com. So since it seems this user logged into our Office 365 tenant using his personal account, it seems he is not going to be able to use his professional accounts....have you seen also this?
Mar 23 2017 05:41 AM
Those duplicate accounts are a real burden. I believe you have to remove the user from your AAD (and/or SharePoint user profiles) and send out a new invite.
We recommend to ask the person who receives the invite to open a private/incogito browser session and paste the link.
Mar 23 2017 06:33 AM
Out of curiosity, what is your "RequireAcceptingAccountMatchInvitedAccount" setting at? From https://technet.microsoft.com/en-us/library/fp161390.aspx or in the UI here: https://support.office.com/en-us/article/Manage-external-sharing-for-your-SharePoint-Online-environm...
Mar 23 2017 07:24 AM
Yes, I have seen this many times...
The account (MSA or O365) used to accept the invite is the one that needs to be used in the future.
As @bart_vermeersch said, if you want to change it, you have to send out a new invite.
BTW, it is not possible anymore to create a new MSA using an O365 email address (see https://blogs.technet.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-micro...).
Also, it is very easy to change the primary email address for an MSA , hence effectively removing the work email address from the MSA (see https://www.howtogeek.com/277170/how-to-change-the-primary-email-address-for-your-microsoft-account/).
Mar 23 2017 07:52 AM
Mar 23 2017 07:59 AM
Yes, now I remember that you already referenced the MS announcement... 🙂
Anyway that info could be useful to someone other reading this thread.
About the choice between the personal account and the professional one when receiving an invite, AFAIK it is already so! 😉
Mar 23 2017 08:02 AM
Mar 23 2017 08:04 AM
Ah... OK!
Mar 23 2017 11:32 AM
So glad they finally put end to this *#$&*#. And I'm not sure RequireAcceptingAccountMatchInvitedAccount would make a difference in this scenario.
Mar 23 2017 12:53 PM
Sort of what I was trying to highlight, especially with @Sahil Arora on the thread now 😉 That property should be used for Groups, not just SharePoint sharing. Otherwise people can just pass around your invitation link and join in from any Microsoft account or AAD account they want. That is most definitely not the intention of guest access in my mind. I invite a person, I want that person at that address. Not their personal account, not their friend or coworker. That person alone, usually from their org account.
Mar 23 2017 03:54 PM
Are you sure that RequireAcceptingAccountMatchInvitedAccount is not actually valid also for Groups external members?
Mar 23 2017 04:50 PM
I don't actually know to be honest. My guess based on other behavior I see around Office 365 Groups is that it will apply to the Modern Team Site that comes with the Group, but not other parts like Guest Access in the Group itself.
Mar 24 2017 03:51 AM
I don't actually know too, but I would expect it to work...
@Sahil Arora can shed some light, hopefully.