Private Items
⚡ ALL INFORMATION CLICK HERE 👈🏻👈🏻👈🏻
Private Items
Tags
Development
Enterprise Content Management
Modern Workspace Tips and Tricks Insights
IT Strategy and Planning Product Reviews Insights
Infrastructure Security and Compliance Virtualization Insights
Services
Managed IT Services
Security and Compliance
Enterprise Content Management
Enterprise Messaging and IT Infrastracture
Managed Desktop
Escalation Support
IT Strategy and Planning
Project Management
Industries
Law Firms
Corporations
Financial Firms
Legal Departments
Non-Profit Organizations
Use Cases
Data Security
Systems Management
Strategic Consulting
Cloud Collaboration
24/7 Tech Support
Learn
Events
Company
Careers
Resources
Blog
We use cookies to improve your experience on our site and enable certain core website functionalities. For more information, visit our Privacy Policy page.
May 3, 2010
2 min read
A common situation in organizations is to make calendars public, so that employees can see other employee’s availability, and collaborate better. Users may also delegate rights to other users to view their messages, tasks, and contacts. In these situations, people may rely on marking sensitive items private to hide them from other users. In Outlook or OWA, other users will see a placeholder for the private items, but won’t be able to view any of the details. However, you should keep in mind that this privacy is only a feature of the client application–Outlook or OWA–and is not inherent to Exchange. Exchange itself does not support any kind of item-level security or privacy, and only has a field called “sensitivity” which is used by Outlook and OWA. The client applications look at that field to determine whether to display the item.
This architecture is common to all versions of Outlook and Exchange, through 2010, and is not really a bug, so much as an architectural decision by Microsoft to keep item-level permissions in the client-tier. The end result is that people should realize that just because they mark an appointment or other item private in Outlook, it doesn’t mean that no one else will be able to see it. Items that are extrememly sensitive should probably not be stored in Exchange in the first place, or you should take off all delegate / view rights to your mailbox. People who you give delegate rights to should also be people who you trust.
Developers should note that when writing custom applications with WebDAV, Exchange Web Services, or any other method, all items will be returned including private items. The custom application should look at the sensitivity setting of each message before displaying it. If the sensitivity is private, then the mesage should not be displayed. We, at Kraft Kennedy, have run into this issue several times when creating custom applications with WebDAV that pull back appointments from the Exchange calendar.
Microsoft has details about allowing other users to manage your mail and calendar here:
Note, the last paragraph of the article:
Sign up for our monthly digest of tech updates and happenings.
Copyright 2022 Kraft Kennedy. All rights reserved
Products (68) Special Topics (42) Video Hub (876)
Sharing best practices for building any app with .NET.
Best practices and the latest news on Microsoft FastTrack
The employee experience platform to help people thrive at work
Expand your Azure partner-to-partner network
Bringing IT Pros together through In-Person & Virtual events
Find out more about the Microsoft MVP Award Program.
Show only
|
Search instead for
Show only
|
Search instead for
Home
Exchange
Exchange Conversations
Private Items in a Shared Mailbox (Exchange Online)
Subscribe to RSS Feed
Mark Discussion as New
Mark Discussion as Read
Pin this Discussion for Current User
Bookmark
Subscribe
Printer Friendly Page
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
All Discussions
Previous Discussion
Next Discussion
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
Is there a super simple 1 liner that does this for a shared mailbox automatically? :) I've got a script coming together that queries the users of a shared mailbox, then sets the delegation settings for each user individually But it seems like we'll just have to periodically re-run if membership changes, unless I'm missing something.
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Email to a Friend
Report Inappropriate Content
What's new
Surface Pro X
Surface Laptop 3
Surface Pro 7
Windows 10 Apps
Office apps
Microsoft Store
Account profile
Download Center
Microsoft Store support
Returns
Order tracking
Store locations
Buy online, pick up in store
In-store events
Education
Microsoft in education
Office for students
Office for schools
Deals for students and parents
Microsoft Azure in education
Enterprise
Azure
AppSource
Automotive
Government
Healthcare
Manufacturing
Financial Services
Retail
Developer
Naked Body Videos
Great Outdoor
Lingerie Porn Tube