Microsoft 365

Neudash has first-class Microsoft 365 coverage for the Office and Graph workflows that commonly drive automations:

  • Outlook Mail
  • Outlook Calendar
  • OneDrive
  • Microsoft Excel

What Neudash supports

OAuth

Neudash provides a managed Microsoft OAuth client for standard setup. That means you can usually connect Microsoft 365 without creating your own Azure app first.

If you need a bring-your-own client for policy or tenant reasons, Neudash also supports custom OAuth clients.

Trigger and event coverage

Microsoft 365 support includes dedicated event handling for:

  • Outlook Mail — mailbox-driven automations
  • Outlook Calendar — calendar event create, update, and delete
  • OneDrive — file-level change detection
  • Microsoft Excel — row-level add, update, and delete events

The Excel support is the one most worth calling out: Neudash does not treat Excel as just “a file changed.” It can work at the row level when the workbook and sheet are configured accordingly.

Why the Excel integration matters

For many operators, Excel is really a lightweight workflow database. The useful signal is:

  • a row was added
  • a row changed
  • a row was deleted

not merely that a workbook changed.

That is the level Neudash aims to support so Office automations can be built around business records instead of raw file churn.

When to use Microsoft 365 in Neudash

Use Microsoft 365 support when:

  • Outlook is part of the process entry point
  • calendar changes should trigger follow-up work
  • OneDrive documents need downstream handling
  • Excel is used as an operational table for business workflows

Office guidance

If you are deciding between Excel and OneDrive:

  • use Excel when row-level business changes matter
  • use OneDrive when the workflow is file/document centric

That distinction keeps the process model clean.

Recommended pattern

For most Microsoft 365 automations:

  1. Create or reuse a Microsoft OAuth connection
  2. Choose the right trigger source:
    • Outlook Mail
    • Outlook Calendar
    • OneDrive
    • Microsoft Excel
  3. Connect it to the stream or process that owns the business logic
  4. Keep the process focused on the business decision, not Graph plumbing

Related docs