w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

Outlook.com: upload a saved calendar or subscribe for later updates

Choose an ICS snapshot or an online-calendar subscription in personal Outlook.com; prepare the upload destination, feed authorization and delayed-update limits without claiming import or synchronization success.

Immutable revision: d9272a099f7c04cd6a25ce04c09ff3690a72a8dc49b7b61e36e2ff9ca62b40d2. Publication and independent validation are separate; inspect metadata and provenance before use.

Outlook.com: upload a saved calendar or subscribe for later updates

Decide whether you need a saved copy or later changes from the calendar owner before choosing an add-calendar route. This preparation covers a personal Outlook.com account in a browser, using Microsoft's Personal account instructions. Work/school Outlook on the web and desktop or mobile clients need their own instructions.

Match the route to the intended result

Microsoft's guide, Personal account, uses Calendar → Add calendar after sign-in:

Input Route
Saved .ics file Upload from file → Browse → choose file → Open → choose destination calendar → Import
Calendar URL Subscribe from web → enter URL → Import

Upload supplies a snapshot without automatic owner updates. Subscription refreshes when the source owner changes events. A collapsed navigation pane can hide Add calendar; expand it.

Microsoft suggests upload if subscription is unavailable. That substitutes a copy, not updates; pause if updates are essential. Both routes end with Import; identify the route first.

Subscription updates can exceed 24 hours, despite an approximate three-hour interval mentioned here. This is no delivery deadline; do not borrow the separate work/school timing.

Prepare the account, scope and destination privately

Before any authorized action, establish which source calendar, receiving personal account and purpose are intended. Confirm permission to use the file or feed. Visibility or possession of a URL alone does not establish authority to import someone else's private schedule.

For upload, record the intended destination calendar and check it against the selected destination before importing. Do not substitute another calendar merely because the expected one is absent. For subscription, confirm that the supplied address is the intended calendar feed. Do not invent a destination selector from the upload instructions for this separate route.

Keep calendar files, event details, guest addresses and private feed URLs out of public feedback. A useful preparation note can identify the chosen route, copy date if known, destination requirement and unresolved question without disclosing the contents. The existing Google export guide [current article] covers a different source/destination workflow; its documented scope and field limits do not establish Outlook behavior.

Stop when the needed outcome is unresolved

If prompt confirmation matters, return that unresolved timing requirement rather than treating a locally absent event as evidence of the owner's decision.

This source check does not establish your feed's availability, required permissions, included events, recurrence/time-zone fidelity, guest or conferencing preservation, duplicate handling or safe retries. A completed control or visible calendar alone is insufficient to claim a complete migration. Inspect an uncertain result before repeating an operation; no cleanup or rollback guarantee is supplied here.

Microsoft's Personal account source was checked 2026-10-05T07:29:30Z; no update date or exact web runtime was displayed. Sixteen manual reader decisions were checked against this draft. No account, file, feed, import, subscription or synchronization result was accessed or tested. A distinct same-operator checker reopened the Microsoft source at 2026-10-05T07:38:28Z and completed checks of those sixteen decisions plus seven additional boundaries at 2026-10-05T07:39:20.286703Z; shared control provides no independent formal coverage. Recheck before use, after controls/source changes, or by 2026-11-05T00:00:00Z. Editorial basis: current calendar standard [current article].

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.