Microsoft integration contracts

Local administration: zix microsoft --help. Inspect intent, prerequisites and related tools before a remote request: operation guidance.

Owner-approved Microsoft Graph user/organization/mail operations; separate Rust planning and mail presentation components. It also maintains a display-only mailbox descriptor and a separately installable browser mail client. The host application owns account selection, consent, token custody and activation.

Artifact	Purpose	Distribution
zixcel-microsoft	Validate bounded acquisition requests and produce read-only plans	GitHub source; Cargo registry publishing disabled
@zixcel/microsoft-mail-presentation	Present configuration fields and missing prerequisites	npm
@zixcel/microsoft-mail-web	Read delegated Graph mail changes and perform explicitly consented actions	npm

Display a connection plan

npm install @zixcel/microsoft-mail-presentation

import { mailPresentation } from '@zixcel/microsoft-mail-presentation'
console.log(mailPresentation.label, mailPresentation.state)
for (const prerequisite of mailPresentation.requirements) {
  console.log(prerequisite.label, prerequisite.detail)
}

The descriptor has PlanningOnly status. It contains no credentials, performs no network operations and does not validate or authorize a user's account. Its schema is data for a host-owned form. Installing this package does not activate a service.

Plan bounded read-only acquisition in Rust

cargo run --locked --offline -- mail-schema
cargo run --locked --offline -- mail-plan examples/mail-request.json

Supply opaque account and authorization references. Never put tokens, passwords or client secrets in a request. Metadata requires delegated Mail.ReadBasic; bodies separately require Mail.Read. Read-only plans do not request Mail.ReadWrite or Mail.Send. Pages are bounded to 1–100 messages and responses to 1 MiB. Folder IDs must be encoded as one path segment and requests use immutable message IDs.

Graph bodies are untrusted input. Acquisition, rendering, semantic interpretation and authority to modify mail remain separate responsibilities. The planning crate performs no networking, login, sending, moving or read-state changes. A successful OIDC login does not establish Graph mail permission.

Develop and verify

pnpm install --frozen-lockfile --ignore-scripts
pnpm test
pnpm typecheck
pnpm build
pnpm --filter @zixcel/microsoft-mail-web test
pnpm --filter @zixcel/microsoft-mail-web typecheck

Tests use reserved example addresses, a never-issued registration identifier and a stub token. They do not access an account. Live Entra registration, account consent and end-to-end host activation require separate integration verification.

Browser client · Interface reference · Security · License · Notices

Local administrator runtime

See the separate Node provider package for account-bound read/write operations and isolated fake-HTTP tests. The existing Rust planning API remains independently scoped.

Isolated public API playground and owner operation boundaries · 日本語

OSS responsibility and source completion defines the supported package boundary and required acceptance. It does not declare unexecuted source, distribution or production checks complete.

Node administrator baseline

The runtime implementation is in packages/provider-microsoft. Its README defines the reviewed operation catalog, account/credential scope, permission and billing coverage, source additions, examples and isolated test commands. Rust planning-only packages and presentation packages retain their own scopes; a planning fixture is not proof of an external API effect.

Run the Node runtime package's frozen install and tests from that directory. Source additions are reviewed separately from the currently published immutable version and from live-account acceptance. No provider connection or account change occurs during source tests.

Dependency updates: repository policy. Registry releases: version tags and GitHub OIDC.

Native Zix provider

Reviewed Rust adapter adds scoped read commands through the common zix protocol. Source/development tests and native distribution are separate; no real credentials or cloud operations are used by CI.

Tenant discovery and Exchange administration

The Microsoft administration guide describes the Rust admin library and native CLI. These are separate from this root planning-only crate. They provide bounded Graph reads and typed, operator-approved Exchange recipient changes; no authentication, real changes or new runtime installation is enabled by the source update.

Local mail enablement documents native 0.3.1 auth, Crowsi custody, reviewed tenant changes, DKIM, probes and official runtime setup.

Operation requirements and related-tool handoffs: LLM guidance.