Integrations: Microsoft 365 and more

Use outside services your workspace has connected, such as Microsoft 365, with no passwords or keys in your module.

Copy page for AIUpdated November 8, 2026

Your module wants to read the support mailbox, list the company's laptops from Intune, or pick a person from the company directory. You don't build any of that. Data Visions defines each outside service once, each workspace connects it with its own account, and your module simply asks for what it needs. No passwords, no keys, nothing to keep secret in your module.

Workspace integrations, connected once

Today the workspace integration is Microsoft 365. A Workspace Admin connects it under System settings › Integrations:

  1. Enter the company's Microsoft app details. The page's How to set this up in Microsoft lists the steps.
  2. Click Test. It shows what Microsoft allowed and which services are ready.
  3. Give each service to the modules that use it, naming the mailboxes for a mailbox service.

Microsoft 365 services:

ServiceLets a module
Send mailUsed by the platform's Email. Send with Email, not directly.
MailboxRead, mark read, flag, categorize, move and reply in the mailboxes it was given. Never delete.
Intune devicesList managed devices.
Directory devicesList devices in the company directory.
Directory usersList people and their managers.

Asking for a service, and the permission that guards it

Your module declares each service it uses, with two things:

  • Why: one sentence the admin reads when deciding. "Reads the support mailbox so the agent files a work order per email."
  • Permission: one of your module's own permissions, the one a person needs to see this data through your module. The platform checks it on every read, so your code doesn't.

Make it optional when you can, so your module still works in a workspace that hasn't connected Microsoft 365. Until the admin gives your module the service, show a one-line message saying what to switch on, and where.

Lists like devices and people come back as tidy records with the same fields in every module, ready for pickers and tables.

Calling an outside API directly: the hosts you declare

For a service with no workspace integration (a payroll provider, a parts catalog), your module can call it itself:

  1. Declare every host it talks to, such as api.example.com. Workspace Admins and reviewers see this list before installing. Calling an undeclared host blocks a Marketplace listing.
  2. Keep credentials in a secret setting, typed by the Workspace Admin under Module settings. Secrets are masked for everyone, admins included.
  3. Describe the service: who runs it, which version, how it signs in.

See Outside hosts and Python packages.

Ask the Module Builder

For developers

json
"uses_integrations": [
  {"integration": "microsoft_365", "service": "mailbox", "optional": true,
   "permission": "REQUESTS.PROCESS_INBOX",
   "why": "Reads the support mailbox so the agent files a request per email."}
]

Read lists with integration_records(...), passing the signed-in person; call anything else with integration_request(...). Don't put Microsoft's hosts in your module's host list.

Good to know

  • More integrations are planned. Microsoft 365 is the one available today.
  • Your own "Sign in with…" connection isn't available to modules yet. Talk to Data Visions before planning one.
  • Need something inside the company network instead? See The Bridge.

Can't find what you need? Contact support.