We agree 100% with the suggestion and are exploring ways to enable this. This represents a significant amount of engineering work hence we don’t have a schedule to share yet.
We’re working on the ability to share a file or folder with a specific Microsoft Account.Szymon commented
As there is a workaround to acomplish sharing with specified MS account/s only I don't know what is the big deal that MS is not able to deploy such feature?!
And the workaround are:
Scenario 1 - with sharing link only
create shareable link to a file or a folder > you may add password protect if you have got paid O365 subscription > paste the link to new email or just share it by a communicator of your choice >
recipient opens the link at his browser > clicks "Add to my Shared list" > login with his/her account if not yet logged in > confirm the account he/she want to use to access the object > now the object should be listed in "Shared" section just under sender's name
Afterwards the sender may review sharing permission of the object and will see the sharing link and named MS account of the recipient. Now the sharing link have to be removed. Named account should stay at the list.
That way sharing link is no longer valid but the recipient still has got access to the shared object.
Scenario 2 - share by email
The procedure is nearly the same as the previous one so I'm not going provide here all the details but wrap up just important things.
If you need to share the link by email you have to use any recipient's MS account alias but primary one (recipient have to create it priorly). This is because in such case sender will see at the list of people who have got access email entry instead of link. (Link sent to <recipient@email>). One the recipient adds the object to the shared list new entry is created at the object's permission list for primary alias of the recipient's MS account.
If needed or requested I may provide you more details with sceeenshots.
The only thing I don't understand is if I'm able to do so manually what's the deal with deploying such workflow automatically with small adjustments to salt the link with recipient's MS account ID for protecting the link against using it by undesirables. Detecting if the recipient email is valid MS account alias is no big deal. It's being used in other MS services.
If the object would going to be shared with more MS accounts algoritms just should just create individudal link for each recipient.
BTW - OneDrive Business has been implemented such feature.