11-06-2017 04:46 AM - edited 11-06-2017 04:47 AM
11-06-2017 04:46 AM - edited 11-06-2017 04:47 AM
Since updating my Office 2016 bits to 1709 Build 8528.2139 I am unable to attach/set permissions on a file in Outlook (Desktop) from my OneDrive for Business site. My Colleague also has the same issue with the same build. The error that I receive is in the attached screenshot and says: "An error occurred while updating permissions for 'Document.docx'. Retry | Dismiss" This worked fine before upgrading the Office bits. I tested on a VM running 1708 Build 8431.2079 and it still works as expected. It also works fine in Outlook Web. As a work around, I can click the drop down for the file and set permissions then click retry and it works. I first reported this problem to MS Premier support on 10/17/17 but have not been provided a resolution. I have since updated my Office bits to 1710 (Build 8625.2121) and the issue persists. I found someone having a similar issue here - https://stackoverflow.com/questions/46725044/outlook-spo-email-attachment-permission-error-with-acti... Is anyone else experiencing this issue?
11-06-2017 05:27 AM
Out of curiosity, if you dismiss the warning, are permissions set correctly anyway in ODfB site?
11-06-2017 07:08 AM
It sent the email, user could see the attachment listed in the email but did not apply any permissions for the user.
11-06-2017 07:11 AM
This relates to the "Direct" setting for the OneDrive for Business default sharing links. It works fine if you switch to Internal. I was told by MS PMs at Ignite that it must be set on direct for the default sharing permission to be "Recipients can edit" rather than "Organization can edit."
11-06-2017 07:54 AM
Have you verified directly on the ODfB site that no permissions were applied?
I am asking because I have seen sometimes that warning, but nevertheless the permissions were correctly applied...
11-06-2017 07:58 AM
"Direct" means that no additional permissions are applied while creating the link, hence only users that already have the correct permissions will be able to access the item.
"Internal" means that everyone in the tenant will be able to access the item using the copied link.
11-06-2017 07:59 AM
I verified that no new permissions were applied to the file on my OD4B site. There were also no anonymous links added (Which I would expect if it gave every org can edit permissions).
11-06-2017 08:05 AM - edited 11-06-2017 08:06 AM
The wording is misleading and doesn't behave as described. If I have direct selected then the default permission for modern attachments in OWA is "Recipient's can edit" and it works as expected. If I change that to Internal the default permission behavior in both OWA and Outlook is "Everyone in the org can edit." I talked with several MS PMs while in Orlando at Ignite and have been emailing them since about how to properly change the default behavior for modern attachments, Direct is the setting they had me choose. For this Outlook issue they advised opening a Premier case, I wasn't getting an answer from Premier quick enough so that is why I decided to share here.
11-07-2017 10:07 AM
Hi @Mike Tilson,
Thanks for reporting this here. You are correct that setting the default link to "direct" should cause the modern/cloud attachment to default to "Recipients can edit". Let me look into this and see if we can figure out what's going on. Thanks!
11-17-2017 09:37 AM - edited 11-17-2017 09:40 AM
This issue still exists. I have updated to v 1710 (Build 8625.2127) and now I don't even have the option in Outlook to share with the organization although that option still exists and functions correctly in OWA.
12-04-2017 01:47 PM
@Stephen Rice any updates on this? We are seeing this issue as well. Ours started showing up after we changed the default at the tenant level to be 'Specific People' instead of 'People in <company name>'.
This is making all of our users think modern attachments are broken, and they are reverting to attaching files the old way which is very much not what we want!
12-07-2017 03:15 AM
12-21-2017 01:41 PM
Our 10,000+ employee organization where everyone has either the G-3 and G-5 license is experiencing this as well. This work beautifully just last week.
12-29-2017 07:29 AM
01-11-2018 07:15 AMSolution
This issue is resolved with build 1711 8730.2175.
05-13-2018 09:21 PM
@Stephen Rice this issue has appeared for us today.
Office 365 E5 customer with Office 365 ProPlus clients installed (v 1710 - Build 8625.2139).
PowerPoint presentation was being attached to an email message using 'Attach File > Recent Items' menu in the 'Include' ribbon.
Also received failed upload errors from documents saved in SharePoint Online Office 365 groups.
05-18-2018 11:00 AM
Hi @Justin Reading,
I believe this issue is fixed but I'd suggest chatting with support to verify that your client has the fix in the update. I'm not familiar enough with the Outlook release cadence to troubleshoot here. Thanks!
Program Manager II