Forum Discussion

Mike Tilson's avatar
Mike Tilson
Iron Contributor
Nov 06, 2017
Solved

Modern Attachments - Cannot set perms

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 is...
exchange
  • Mike Tilson's avatar
    Mike Tilson
    Jan 11, 2018

    This issue is resolved with build 1711 8730.2175.

Mike Tilson's avatar
Mike Tilson
Iron Contributor
Nov 06, 2017

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.

  • StephenRice's avatar
    StephenRice
    Icon for Microsoft rankMicrosoft
    Nov 07, 2017

    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!

     

    Stephen Rice

    • sukh rehal's avatar
      sukh rehal
      Copper Contributor
      Dec 12, 2017

      StephenRice Did you get any response from Outlook team on this?

    • David Rosenthal's avatar
      David Rosenthal
      Icon for Microsoft rankMicrosoft
      Dec 04, 2017

      StephenRice 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!

      • StephenRice's avatar
        StephenRice
        Icon for Microsoft rankMicrosoft
        Dec 05, 2017

        Hi David Rosenthal,

         

        We are still investigating internally with the Outlook team. Thanks,

         

        Stephen Rice

        OneDrive Program Manager II

    • Mike Tilson's avatar
      Mike Tilson
      Iron Contributor
      Nov 17, 2017

      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.

       

       

      I took a newly imaged Surface laptop and installed Office software directly from Office 365 with version 1710 (8625.2121).  I can reproduce the error on the fresh imaged PC with that Office version on a different tenant than our production tenant.
       
      When I first installed Office on this machine it had the deferred bits and the modern attachments worked fine but broke after the update to the latest bits.

       

       

Resources