Forum Discussion
External users can't open documents in desktop application
Hi all,
This behavior is expected (external users not getting the "Open in Office" option) whenever the external user is authenticating via the new one time passcode (OTP) method. You can see a better overview here: Documentation
There are two states an external user can be in today: If they are authenticating via OTP, then they do not have a real AAD account and thus cannot open in clients. This occurs when you share a file or folder with an external user who is not in your directory (i.e. they have never been shared to before).
Inviting a user to a site or a group or using the Azure B2B platform will create an account in AAD for the guest user. These users must have an MSA or AAD account to sign-in with to accept the invitation. They can use Office apps.
This is definitely something we're looking to improve and I definitely suggest you check out the "What's new in External Sharing & Collaboration with OneDrive & SharePoint" talk at Ignite next week ;)
Bottom line is, the users must authenticate using a MSA/Work account into your tenant and be listed as a guest in azuread in order to use the client, if they do not have to login by using anon link / specific people with code option, they will not be able to use the client.
I think what is happening is your tenants have been updated awhile back so the specific people option now uses the codes and you just now have invited people that haven't been invited to your tenant yet and seeing the side effect of that change?
Anyway, hopefully Microsoft has a fix to just allow client no matter what soon!
MicrosoftHi all,
This behavior is expected (external users not getting the "Open in Office" option) whenever the external user is authenticating via the new one time passcode (OTP) method. You can see a better overview here: Documentation
There are two states an external user can be in today: If they are authenticating via OTP, then they do not have a real AAD account and thus cannot open in clients. This occurs when you share a file or folder with an external user who is not in your directory (i.e. they have never been shared to before).
Inviting a user to a site or a group or using the Azure B2B platform will create an account in AAD for the guest user. These users must have an MSA or AAD account to sign-in with to accept the invitation. They can use Office apps.
This is definitely something we're looking to improve and I definitely suggest you check out the "What's new in External Sharing & Collaboration with OneDrive & SharePoint" talk at Ignite next week ;)