Esc

↑↓ move↵ openIndex · Pagefind
← All integrations

Productivity

Microsoft 365

Planned

Planned: file Outlook inbox messages that name a project number as project correspondence, after review.

Planned. This connection is not available in os.construction yet. This page describes the intended scope; it is not a release date.

Coverage by service or edition

Mail filing from Connections (planned). Each service needs its own permissions and acceptance checks.

  • OneDrive

    Planned

    Drive/item identity and resource-specific delta.

  • SharePoint

    Planned

    Site/list/item identity and explicit resource grants.

  • Outlook Mail

    Planned

    Planned: inbox messages whose subject names a project number are offered for review and filed as project correspondence. Other messages are skipped and never stored. Read only; incremental with Graph delta links.

  • Outlook Calendar

    Planned

    Recurrence and timezone mapping; no invitations.

  • Teams

    Planned

    Channel messages and separately paginated replies.

  • Excel

    Planned

    Workbook/table and stable business keys.

  • Entra, Planner, OneNote & adjacent products

    Planned

    Separate contracts required; no implied Dynamics, Power BI, Business Central or Project support.

Prepare for a scoped walkthrough

Use this checklist to agree the scope. These are preparation steps, not instructions for an available authorization or sync screen.

  • Select tenant, delegated/application access and resource grants; consent alone is insufficient for Selected permissions.
  • Confirm the destination company/project and the reviewer responsible for approving imported records.
  1. Confirm the scope

    Select tenant, delegated/application access and resource grants; consent alone is insufficient for Selected permissions.

  2. Agree the mapping

    Drive/item IDs → document; site/list/item IDs → list record; mailbox/message ID → correspondence.

  3. Preview and reconcile

    Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.

  4. Review before applying

    An authorized reviewer must confirm destination scope, unresolved records and control totals. A successful extraction is not proof that data has been applied.

  5. Check recovery and access

    Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.

Mapping and synchronization

Record mapping

Drive/item IDs → document; site/list/item IDs → list record; mailbox/message ID → correspondence.

Sync boundary
Opaque next/delta links per resource. Mail moves, drive deletes and Teams replies have different lifecycles.
Source ownership
The provider remains authoritative for its source records. Local project placement, access and workflow decisions need explicit destination ownership. Match by scoped IDs, not names alone.
Outbound policy
No provider business writes are offered here. Sending, posting, inviting, deleting and permission changes require separately approved capabilities.

Conflicts and recovery

When records disagree

Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.

When a run stops

Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.

Limits to plan around

  • No family-wide access implied. Personal accounts, sovereign clouds and adjacent Microsoft products require separate review.
  • Not available in os.construction yet. Provider documentation describes the upstream API, not an os.construction connection.

No provider connection is initiated from this page. For the reviewed accounting import workflow available today, see the accounting import guide.

Documentation and source dates

Provider documentation establishes upstream capabilities, not os.construction availability. Confirm the current edition and API contract before planning setup.

Back to integration directory
Open file