Can My Boss See My Private Outlook Calendar Events?

Usually your boss cannot see the details of a private Outlook event. That is the whole difference between private and not private in Outlook: a normal event shows its title and location to anyone who can read your calendar, and a private one shows only Private appointment and the time. Microsoft's help page "Make an appointment or meeting private" says that if you give someone Read access to your calendar, "they will not be able to see the details of your private appointments". They see a block labelled Private appointment, its time, and a lock icon. The exceptions matter, though. A delegate you gave "access to view private items" sees everything; the people invited to the meeting see the full invite; anyone with full access to your mailbox can see private items in new Outlook or Outlook on the web; and a compliance admin with eDiscovery can search the whole mailbox. Private also never hides the time: your boss still sees that you are busy from 2 to 3.

By default, coworkers in your organization see only whether you are free or busy, not titles. Private matters when someone has more access than that.

Calendars feed your status in chat apps too: an event marked Busy turns Teams to In a meeting, private or not. Calendar sync can also change a Slack status.

Who can see a private event, and what they see

The Full Access row comes from Microsoft's troubleshooting article "Private items aren't displayed in a shared mailbox in Outlook" (updated 11 August 2026): in classic Outlook, private items stay hidden unless the delegate has explicit permission, but "access granted through Full Mailbox Access can result in private items being visible" in Outlook on the web, new Outlook for Windows and Outlook Mobile.

When your boss can see the details

You made them a delegate with private access. Managers and assistants often share calendars both ways. In classic Outlook, File > Account Settings > Delegate Access lists your delegates, and the Delegate can see my private items box is off by default. An admin can also set it with PowerShell, using the CanViewPrivateItems flag.

They are invited. Marking a meeting private hides it on your calendar view. Everyone on the invite still receives the full details.

They or IT have full access to your mailbox. Admins can grant full mailbox access, usually for an assistant or after someone leaves. With that access, private items can show in the web and new Outlook.

Your company searches the mailbox. Calendar items live in your Exchange mailbox, next to your email and Teams chats, and compliance admins search all of it with Microsoft Purview eDiscovery. What that covers is in can my employer read my Teams chats.

Microsoft's older Outlook help put it plainly: do not rely on Private to keep people out; if someone has Read permission to your calendar, other email programs or scripts can show them private items. Treat Private as a courtesy screen, not a lock.

How to make an Outlook event private

• • New Outlook for Windows and Outlook on the web: open the event, select Private on the Event tab, then save or send the update.
• • Classic Outlook: select the event, and in the Tags group select Private, then Save & Close.

A lock symbol appears on the event in your calendar. Only the organizer can mark a meeting private.

Private hides the title, not the time. Also choose Show as on purpose. Busy blocks the slot for scheduling and sets your Teams status to In a meeting; Free leaves the slot open. Changing a status with Outlook is covered in how to change your status in Outlook, and a Busy event that keeps Teams red is in Teams status stuck on Busy.

Check who can see your calendar

In new Outlook or Outlook on the web, right-click your calendar and choose Sharing and permissions. Each person is listed with their level, such as "Can view when I'm busy", "Can view titles and locations", "Can view all details", "Can edit" or "Delegate". For a delegate, look for Can view private events, and turn it off if you do not want them to see private items.

An Exchange admin sees the same list in PowerShell:

# what access each person has to your calendar (admin, Exchange Online PowerShell)
Get-MailboxFolderPermission -Identity you@contoso.com:\Calendar

That cmdlet needs an admin sign-in, so we did not run it. The same sharing levels are written into Microsoft Graph, the API that new Outlook and Outlook on the web use. We read Graph's public API description on 27 October 2026, with no sign-in:

# graph_calendar_check.py: read Microsoft Graph's public API description (no sign-in) and print
# the event privacy values and the calendar sharing roles Outlook uses.
import re, urllib.request, datetime
def get(u): return urllib.request.urlopen(urllib.request.Request(u, headers={"User-Agent": "curl/8"}), timeout=120).read().decode()
meta = get("https://graph.microsoft.com/v1.0/$metadata")
print("Graph v1.0 $metadata read", datetime.date.today())
def enum(name):
    m = re.search(r'<EnumType Name="' + name + r'"[^>]*>(.*?)</EnumType>', meta, re.S)
    return re.findall(r'<Member Name="(\w+)"', m.group(1))
print("event sensitivity values:", enum("sensitivity"))
print("calendar sharing roles:", enum("calendarRoleType"))
pres = re.search(r'<EntityType Name="presence"[^>]*>(.*?)</EntityType>', meta, re.S).group(1)
print("presence fields:", re.findall(r'<Property Name="(\w+)"', pres))

Graph v1.0 $metadata read 2026-10-27
event sensitivity values: ['normal', 'personal', 'private', 'confidential']
calendar sharing roles: ['none', 'freeBusyRead', 'limitedRead', 'read', 'write', 'delegateWithoutPrivateEventAccess', 'delegateWithPrivateEventAccess', 'custom']
presence fields: ['activity', 'availability', 'outOfOfficeSettings', 'sequenceNumber', 'statusMessage', 'workLocation']

Two of the eight sharing roles are delegates, and they differ only in private events: delegateWithoutPrivateEventAccess and delegateWithPrivateEventAccess. With the sharing roles freeBusyRead, limitedRead, read and write, Private hides the details, as Microsoft's help page above says for Read. An event's privacy is stored in its sensitivity field, which has four values.