Microsoft 365
PlannedPer-tenant connection is planned; no live connection is available on this website.
Integrations
Every provider connection is labelled by current state. This website does not imply a live accounting, email, device or mobile integration.
Status register
Per-tenant connection is planned; no live connection is available on this website.
Per-tenant connection is planned; no live connection is available on this website.
A provider and authorised production credentials have not been selected.
Capture depends on licensed SDK access and real-device validation.
Native applications are a separate delivery stream and are not available here.
Readiness dossier
For fictional NQC-014, a buyer should ask whether a provider can import a selected job reference, export its current record, or neither; which account authorises it; and what users see if the provider is unavailable. No provider connection is active on this website. Use the browser-local exports and resource sheets until a SaaS connection is verified.
Each live integration needs an authorised account, least-privilege scopes, tenant-bound credential storage, webhook verification where applicable, bounded retries, observable failures, revocation and audit evidence. Credentials and provider data belong to the SaaS application—not the public website.
Acceptance evidence
| Evidence | Required demonstration |
|---|---|
| Authorisation | Correct account, scopes, consent and revocation |
| Data boundary | Tenant-isolated reads, writes and denied cross-tenant access |
| Reliability | Retry, duplicate, timeout and provider-outage behaviour |
| Audit | Who initiated the action, what changed and the provider response |
| Exit | Disconnect, credential deletion and export consequences |
Until these checks exist for a named provider, its status remains planned or access-dependent.