Microsoft and Google mailbox providers

MailGen resolves the provider from the stored mailbox connection. Microsoft and Google accounts can appear in the same application. Supported operations still depend on the provider.

Prepare Microsoft Graph access or Google Cloud access for the selected provider. App login and mailbox authorization are separate connections.

Select the intended connected mailbox before an action. Switching accounts after acceptance does not move that operation to the new mailbox.

Backend callers use standardized middleware operations and data. Provider adapters own API paths, paging, credentials, and provider-specific errors. An unsupported capability returns an unavailable state or error. Permission for one provider does not authorize another.

Write-path differences

In m365local, low-level folder create/update/delete and updateEmailLabels update the local projection. That alone does not prove an Outlook folder or category change. The m365Ent label adapter calls Graph category updates, but it is a different provider path.

The current manual move command uses a dedicated Microsoft move operation with owned-message checks and provider evidence. Passive sorting emits ordered move and conversation-category operations. These paths differ from the low-level local projection helpers. Draft save/send and native Outlook scheduling also have provider-specific write implementations.

Use the operation's actual result and confirmation state. Do not infer provider support from a local database change or the presence of a UI control.