Onboarding commands and events

Kafka carries the durable request and progress of Microsoft onboarding. Prepare Graph access and the runtime infrastructure first.

The worker consumes app.onboarding.commands.v1. App-user and connected-account values identify the onboarding request. After identity resolution, msintegrationv2.users.user_id identifies mailbox queue ownership. Do not substitute an email address or login ID for a queue key.

The worker saves durable import checkpoints. For lifecycle progress, it first publishes through the Kafka producer, then records a successful outbox mirror and checkpoint. This publish-then-mirror sequence is not an atomic outbox-first delivery guarantee. Producer correlation and causation let the interface follow one run. Browser progress delivery and durable import completion remain separate observations.

The final initialization command follows a different path. It persists an authorized completion outbox entry before publishing the queued command. Its delivery state then moves through dispatch and publication. Partition assignment and the initialization barrier control release of waiting mailbox work.

mailbox.onboarding.initializingDone is the final queued mailbox operation. A command accepted by Kafka does not mean import completion. Inspect durable progress and the final operation before opening dependent work. See the current sequence.