Skip to main content
Use the @bijection/connectors/exchange-ews entrypoint to declare Exchange Server (EWS) resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Mailbox

incremental: incremental

The following example matches configuration standard.

Configuration: standard

Case: exchange-ews/mailbox/incremental/standard. Connection and resource configuration are declared by this exact case. Credential kind: mailbox. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: contents
Collection: memberships
Collection: messages
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Reads an Exchange Server (on-premises) mailbox through Exchange Web Services into the same messages, contents and memberships tables as the IMAP mailbox. Bind the connection’s ews endpoint (host, port, security: "implicit_tls"; EWS is HTTPS only) and folders: a distinguished folder id (inbox, calendar, sentitems, …) optionally followed by /-separated display names below it (inbox/Projects), at most eight. The private mailbox credential (exchangeEws.credential) holds auth:
  • { kind: "ntlm", username, password, domain? }: NTLMv2 bound to the TLS channel and to HTTP/<host>, as Extended Protection requires.
  • { kind: "basic", username, password }.
  • { kind: "kerberos", principal, keytab, kdc, service? }: a keytab ticket to HTTP/<host> (or service), checked for mutual authentication.
and optionally trusted_certificate, a private authority (PEM) the server is verified against. A network route (relay or private endpoint) carries the EWS connection; a Kerberos installation’s KDCs are reached directly. Each folder is read with SyncFolderItems: the first pass is a baseline that states the folder’s members, later passes state each creation, update, deletion and read-state change. A deletion withdraws membership, never the message. A refused sync state or a folder that was replaced restarts as continuity loss. Bodies are GetItem MIME; a calendar item’s carries its iCalendar. The connector reads only: no sending, no notifications, no impersonation and no Autodiscover. No real Exchange server has been reached by these checks.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.