[Feature] Add an on-premises Exchange contacts connector profile #17

New Issue

2026-08-02T07:07:22+02:00

zemion commented

2026-08-02 07:07:22 +02:00

Goal

Support locally deployed Exchange contact sources without pretending that the Microsoft Graph cloud profile covers every deployment.

Parent: #8. Related shared runtime: GovOPlaN/govoplan-connectors#8.

Direction And Boundary

Start with capability probing and a read-only/import profile.
Treat the transport/API profile as explicit connector configuration and report unsupported server capabilities; do not silently fall back between protocols.
Writable synchronization is gated behind proven revision, conditional-write, deletion, and outcome-reconciliation behavior.

Scope

Endpoint/version/capability probe with TLS and authentication diagnostics using credential-envelope references.
Address-folder discovery, bounded preview, mapping, stable external IDs, revisions, pagination, and full-resync behavior.
Read-only refresh, source freshness, tombstones, timeout/backoff, and stale projection semantics.
A documented compatibility matrix backed by disposable integration fixtures for each supported server/API profile.
A separate implementation gate for remote create/update/delete after conditional-write and compensation tests pass.
No hard dependency on Mail, Calendar, Access, or IDM.

Acceptance Criteria

Operators can determine whether a deployment is supported before saving a source.
Unsupported profiles fail with actionable diagnostics and do not mutate data.
A supported read-only source previews and imports idempotently with field provenance.
Writable mode remains unavailable unless the configured profile proves the required recovery guarantees.

## Goal Support locally deployed Exchange contact sources without pretending that the Microsoft Graph cloud profile covers every deployment. Parent: #8. Related shared runtime: GovOPlaN/govoplan-connectors#8. ## Direction And Boundary - Start with capability probing and a read-only/import profile. - Treat the transport/API profile as explicit connector configuration and report unsupported server capabilities; do not silently fall back between protocols. - Writable synchronization is gated behind proven revision, conditional-write, deletion, and outcome-reconciliation behavior. ## Scope - Endpoint/version/capability probe with TLS and authentication diagnostics using credential-envelope references. - Address-folder discovery, bounded preview, mapping, stable external IDs, revisions, pagination, and full-resync behavior. - Read-only refresh, source freshness, tombstones, timeout/backoff, and stale projection semantics. - A documented compatibility matrix backed by disposable integration fixtures for each supported server/API profile. - A separate implementation gate for remote create/update/delete after conditional-write and compensation tests pass. - No hard dependency on Mail, Calendar, Access, or IDM. ## Acceptance Criteria - Operators can determine whether a deployment is supported before saving a source. - Unsupported profiles fail with actionable diagnostics and do not mutate data. - A supported read-only source previews and imports idempotently with field provenance. - Writable mode remains unavailable unless the configured profile proves the required recovery guarantees.