Start by naming what you actually shared
After a collaboration ends, the first mistake is treating “calendar access” as one thing. On a personal Outlook.com account, there are two separate sharing models, and they are removed in different places:
- A named person with delegated or shared access. You granted a specific account permission to view or edit your calendar. Removal happens in Sharing and permissions.
- A published calendar. Outlook generates a link (HTML for browser viewing, ICS for import or subscription) that anyone holding it can use. Removal happens through Unpublish.
Before you change anything, make a short written inventory: who was named, which calendar (default or secondary), whether you ever opened the publish settings, and where you sent any link. This matters because the two removal paths do not affect each other. Removing a person does not unpublish a link, and unpublishing does not remove a named person’s permission.
Step 1: Review and remove a named person’s access
Open the calendar sharing settings for the specific calendar you shared. In the list of people with access, identify the collaborator’s account as it was entered. Remove that entry.
What that removal does and does not mean:
- It stops the sync. The removed person’s copy no longer syncs or receives updates.
Outlook.com calendar Sharing and permissions can change or remove a person’s access; a removed copy no longer syncs or receives updates. Source
- It does not reach copies already exported. If the person downloaded an ICS file or took screenshots, removal cannot recall those. Do not tell yourself the event data is gone everywhere; tell yourself the live feed is closed.
- It does not touch published links. If you also published the calendar, that link remains live until you unpublish it.
If you are unsure whether a person had direct access or merely a link, check both places. The sharing list shows named accounts; the publish settings show link state. A person who only ever received a link will not appear in the sharing list at all.
Step 2: Understand the two published link types before you remove them
Outlook.com can expose a calendar in two link formats, and they behave differently for the recipient.
- HTML link. The recipient views the calendar in a browser. There is no local copy to update; the page reflects what the publisher exposes.
Published calendar HTML links allow viewing in a browser; ICS can be imported as a snapshot or used to subscribe for updates. Source
- ICS link. The recipient can either import the file once — creating a frozen snapshot — or subscribe to the URL so their calendar app polls for updates. An imported snapshot will not change when you edit your calendar. A subscription may continue to reflect changes until the link is unpublished or the subscriber removes it.
This distinction is the heart of the audit. If you sent an ICS link and the recipient imported it, unpublishing stops future updates but does not erase the snapshot already in their calendar. If they subscribed, unpublishing is the control that ends the live relationship.
| What you shared | Where removal happens | Effect on the other person | Limit you cannot fix |
|---|---|---|---|
| Named person with access | Sharing and permissions | Their copy stops syncing and receiving updates | Copies they exported or screenshotted remain |
| Published HTML link | Unpublish in calendar settings | Browser viewing of that link ends | Cached pages or saved screenshots may persist |
| Published ICS link, imported | Unpublish in calendar settings | No further updates flow to the snapshot | The imported snapshot stays in their calendar |
| Published ICS link, subscribed | Unpublish in calendar settings | The subscription can no longer refresh from your calendar | Their app may keep old events until they remove the subscription |
Step 3: Unpublish the old calendar link
If you published a calendar, remove the publication rather than merely changing its details. In Outlook.com, the path is Settings, then Calendar, then Shared calendars, where a published calendar offers Unpublish.
Settings, then Calendar, then Shared calendars provides Unpublish for a published calendar. Source
After unpublishing, open the same settings page again and confirm the publish option is no longer active for that calendar. Then test from a browser where you are not signed in, using the old link if you still have it. You are checking whether the link still renders your calendar; you are not trying to recover or “delete” the link from the internet.
Do not assume that unpublishing deletes old copies. It removes your publication, which is the control you own. A recipient’s imported ICS file, a downloaded HTML page, or a screenshot is outside your account and outside your reach.
Step 4: Decide what to do about a shared calendar you no longer need
Sometimes the cleanest audit result is to stop sharing the calendar itself. If the calendar existed only for the collaboration, consider whether you still need it at all. Deleting or renaming a calendar is a separate action from removing a person or unpublishing a link, and this guide does not assume any particular menu path beyond the reviewed settings above. If you are unsure, remove access and unpublish first, then decide about the calendar.
Common mistakes
- Removing the person and stopping there. The published link is a separate exposure. Check both.
- Unpublishing and assuming the collaborator’s copy vanished. An imported ICS snapshot is a local copy; unpublishing stops updates, not the copy.
- Treating a subscription as an import. A subscriber may keep receiving changes until you unpublish; an importer will not.
- Sending a fresh link “just to check.” Every new link is a new exposure. If you must test, use a link you are about to unpublish.
- Confusing a personal Outlook.com account with a work Exchange account. Business tenants are administered by an organization, and their roles and removal flows are not the personal-account flow described here. If your calendar is on a work account, stop and ask your administrator.
- Assuming an edited profile or empty calendar proves deletion. Changing what a calendar displays does not establish that stored data or previously shared copies are gone.
Owner-side review checklist
Use this before you close the collaboration file:
- List every calendar you shared and the account names you granted access to.
- Remove each named person who no longer needs access in Sharing and permissions.
- Check whether any calendar was published; note HTML versus ICS.
- Unpublish each published calendar under Settings, Calendar, Shared calendars.
- Re-open the settings to confirm the publication is gone.
- Test the old link in a signed-out browser session.
- Record what you cannot control: exported ICS files, screenshots, forwarded links.
- If the calendar was work-managed, route the request to your administrator instead of using this flow.
Limits: what this audit cannot do
This process closes the live channels you control on a personal Outlook.com calendar. It does not recall copies already in someone else’s calendar app, and it does not prove that a recipient deleted anything. It also does not cover business Exchange permissions, which are organization-managed. And it is not an account inventory: a calendar audit tells you about calendar sharing, not about every other place your username or profile appears.
If you want a separate, optional check of your own known public handles, TraceSeek is a username lookup app that checks 3,000+ platforms and offers a free first scan, with a stated scan time of 20-30 seconds. It reports public matches as leads, not proof of identity, and it does not change your Outlook privacy settings or access private calendar content. For a broader cleanup, see our guide to finding forgotten online accounts at /guides/find-forgotten-online-accounts/, and for a related visibility check, see /faq/check-whether-your-google-calendar-is-publicly-visible/.
Protecting your own footprint going forward
- Share by name, not by link, when you can. A named permission is easier to revoke and easier to audit than a link that can be forwarded.
- Set a review date. When a collaboration starts, note when you will revisit sharing. Calendar links tend to outlive the project that justified them.
- Prefer the least durable format. If a recipient only needs a one-time view, understand that an ICS import creates a snapshot you cannot update or withdraw.
- Keep a recovery method you control until closure is complete. Do not delete the account or recovery path you rely on before you have finished removing access and unpublishing links.
- Treat public matches as leads. A username match on another platform is a starting point for your own review, not evidence that a particular person owns an account.
Key facts
Outlook.com calendar Sharing and permissions can change or remove a person’s access; a removed copy no longer syncs or receives updates.
Published calendar HTML links allow viewing in a browser; ICS can be imported as a snapshot or used to subscribe for updates.
Settings, then Calendar, then Shared calendars provides Unpublish for a published calendar.
TraceSeek checks 3,000+ platforms for public username matches and offers a free first scan, with a stated scan time of 20-30 seconds.