Allow to see private emails in shared mailboxes in outlook (in OWA you can see them)
On shared mailboxes in office 365 emails that are flagged by the sender as private are hidden. In OWA they are visible.
Users having full access to the shared mailbox do not see emails sent with a private flag - and they do not get informed about it. The emails are just silently hidden by outlook without any further notice. Quite stupid, for a shared mailbox (e.g. incoming orders!)
We discovered that by coincidence: Our users were concerned because the number of unread emails was increasing - although there were no unread emails visible for them.
If they open the same mailbox in OWA, they can actually SEE the private email!
Get consistent behavior between OWA and Outlook.
Let an administrator configure right to see the private messages on shared mailboxes.
Ross Curtis commented
Seriously Microsoft, why would you remove a feature that has been available for previous versions of Exchange? Makes me want to migrate everything back On-Prem!
I´m having the same issue with a user, I tested everything but it doesn´t work.
We have this issue as well - any new updates?
Hello, we've just 'discovered' this as well. This could have had a potentially serious impact to the organisation as our shared mailboxes are only normally accessed by Outlook and emails were not being picked up.
It needs to be a grantable permission/tick box in O365 that will apply to shared mailboxes.
Same problem here, there is a workaround by converting the mailbox to a normal mailbox with a license, assigning permissions and converting it back to a shared mailbox, but thats too time consuming.
Ran into this issue this week. Due to the nature of our business we use a lot of shared mailboxes. Workarounds just not acceptable and extremely bad practice. How do we get this changed? make placards and march on MSO365 Ivory Tower?
This needs to happen ASAP, I work in the Healthcare, and have shared mailboxes set up for a couple of departments, because of HIPPA we must send and receive encrypted emails, which some like mimcast automatically mark as private as well, this is a huge pain point and something MS should work on quickly.
I need the same thing
Liam Bowers commented
Getting this issue also, it's so inconsistent and causing issues!
Just ran into this issue the other day. Users and managers are very upset at potential lead loss due to this issue...
I've just had to explain this quirk to my manager. It's baffling that there isn't the check box option available to admins.
Bump. Agree with all comments below. Users are very upset about missing orders and other critical messages.
Richard Aylin commented
This is now getting to be a significant issue. Because of new GDPR regulations, senders are being more paranoid about security and sending increased volumes of "private" emails to shared mailboxes. This is causing us massive headaches. Please can we get a solution rather than laborious workarounds??
We can't have users looking for unread items in Outlook and OWA on the off chance there is an item marked as Private. This is just daft behaviour. We need the option to disable the Private flag in a shared mailbox - the default is unworkable - the workaround of converting to a User mailbox and then giving Delegate Access the ability to see Private items is no good when you have 9000 shared mailboxes. There should be a Powershell cmdlet "Set-Mailbox -IgnorePrivate $true"
Tim Stark commented
Why isn't this added yet, it is a huge deal to HR departments.
+1 on the urgency for this!
I suggest everyone bumps this up.
Mark Byrne commented
As a workaround you can create a Transport rule to change the Sensitivity value to Normal whenever a mail with the sensitivity set to private comes into the shared mailbox.
It's not ideal and I'm sure some users have a valid reason for sending the mails with the private flag so ideally the issue needs fixing by Microsoft allowing an easier way of having delegates of a shared mailbox view mails marked as private.
Dan Van Fleet commented
Bump again, the work around isn't workable at all. Changing a user requires a crazy amount of work and potential points of error / failure / data loss. Is there not a PowerShell method to set this flag. Please Please. I totally agree with Chris Henderson. This error just made a POP-3 mailbox look good to a client.
Chris Henderson commented
Bump. This is very infuriating and the 'work-around' is not even a viable work-around. There should be a method to either achieve this easily via PowerShell, or better yet, the ability to disable Private flags on shared mailboxes / enable the ability for all delegates to view private emails. A single flag added to the 365 settings to achieve either of the latter two.
The current operating procedure is not time feasible in the slightest.
Yes please fix this peculiar and troublesome behaviour. The workaround posted below is very cumbersome and inelegant.
Martin Meraner commented
This is truly inconsistent behavior. I have a hard time explaining that to our users, because it is ridiculous.
I will leverage the issue by adding delegate access via powershell, but seriously, this is not the way to do it.