Productivity platform

Microsoft 365 request forms for MSP workflows

Build Microsoft 365 onboarding, offboarding, mailbox, permissions, and license request forms with live tenant data and workflow handoff.

Build this workflowSee related setup
Direct answer

FormNode turns Microsoft 365 requests into structured workflows by collecting tenant-specific data, validating user inputs, routing approvals, and sending clean payloads to provisioning automation.

Dynamic Microsoft 365 user/license fieldsMicrosoft 365 workflows stay structured, tenant-aware, and automation-ready.
Approval decision tablesMicrosoft 365 workflows stay structured, tenant-aware, and automation-ready.
Portal forms per clientMicrosoft 365 workflows stay structured, tenant-aware, and automation-ready.
Workflow fit

Use FormNode when the request needs more than a static form.

  • New user onboarding
  • User offboarding
  • Mailbox permission requests
  • License changes
  • Password reset and unlock requests
Example workflow

A manager submits a new-user request, FormNode validates the username against tenant data, collects approval, and posts the approved payload to an automation workflow.

Useful fieldsTarget user, Manager, License, Mailbox, Permission type, Start date
Why FormNode fitsDynamic Microsoft 365 user/license fields, Approval decision tables, Portal forms per client, Webhook payloads for provisioning systems
Common questions

Can FormNode provision Microsoft 365 users by itself?

FormNode collects and validates the request, then sends it to your automation workflow. The workflow handles provisioning through CIPP, Graph, PowerShell, or another system.

Can Microsoft 365 fields be tenant-specific?

Yes. Dynamic fields can call tenant-aware webhooks so users, licenses, mailboxes, and departments are specific to the selected customer.

Related FormNode pages