Delegate Permissions in EXO- Private Items

%3CLINGO-SUB%20id%3D%22lingo-sub-1486668%22%20slang%3D%22en-US%22%3EDelegate%20Permissions%20in%20EXO-%20Private%20Items%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1486668%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20found%20a%20unique%20scenario%20that%20we%20are%20not%20sure%20if%20it's%20%22functioning%20as%20expected%22%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20found%20that%20when%20we%20delegate%20full%20access%20permissions%20in%20EXO%2C%20the%20person%20receiving%20the%20permission%20can%20see%20private%20calendar%20items%20of%20the%20person%20they%20gained%20access%20too%20in%20Outlook%20Web.%20Outlook%20thick%20client%20itself%20still%20maintains%20private%20items%20as%20private%20and%20the%20delegate%20cannot%20see%20those.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20tried%20using%20the%20outlook%20thick%20client%20to%20have%20the%20user%20do%20the%20delegate%20access%20themselves%20with%20the%20%22private%20items%22%20radio%20button%20off.%20(user%20should%20not%20be%20able%20to%20see).%20Same%20results-%20in%20Outlook%20on%20the%20Web%20the%20delegate%20could%20still%20see%20private%20items%2C%20while%20the%20Outlook%20thick%20client%20could%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20has%20been%20working%20as%20expected%20in%20Exchange%202013%2C%20but%20after%20migrating%20to%20Exchange%20Online%20users%20were%20finding%20this%20new%20behavior.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20the%20expected%20behavior%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1486668%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1488277%22%20slang%3D%22en-US%22%3ERe%3A%20Delegate%20Permissions%20in%20EXO-%20Private%20Items%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1488277%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F567017%22%20target%3D%22_blank%22%3E%40mattyounggren%3C%2FA%3E%26nbsp%3BHello%2C%20I'm%20not%20sure%20this%20is%20the%20correct%20answer%20but%20the%20behavior%20you're%20describing%20is%20identical%20with%20a%20delegates%20Full%20Access%20permissions%20and%20protected%20content%20(encryption).%20Meaning%2C%20the%20delegate%20with%20Full%20Access%20can%20see%20encrypted%20content%20in%20Outlook%20on%20the%20web%20but%20not%20when%20using%20the%20desktop%20client.%20As%20far%20as%20I%20understand%20from%20reading%20about%20it's%20expected%20behavior.%20If%20anyone%20else%20is%20reading%20this%20and%20know%20more%20about%20it%2C%20please%20reply%20and%20update%20the%20conversation.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We found a unique scenario that we are not sure if it's "functioning as expected" or not.

 

We found that when we delegate full access permissions in EXO, the person receiving the permission can see private calendar items of the person they gained access too in Outlook Web. Outlook thick client itself still maintains private items as private and the delegate cannot see those. 

 

We also tried using the outlook thick client to have the user do the delegate access themselves with the "private items" radio button off. (user should not be able to see). Same results- in Outlook on the Web the delegate could still see private items, while the Outlook thick client could not.

 

This has been working as expected in Exchange 2013, but after migrating to Exchange Online users were finding this new behavior.

 

Is this the expected behavior? 

 

 

1 Reply

@mattyounggren Hello, I'm not sure this is the correct answer but the behavior you're describing is identical with a delegates Full Access permissions and protected content (encryption). Meaning, the delegate with Full Access can see encrypted content in Outlook on the web but not when using the desktop client. As far as I understand from reading about it's expected behavior. If anyone else is reading this and know more about it, please reply and update the conversation.