Overview
The Flows360 connector for Microsoft 365 lets you build reliable, bidirectional integrations between Microsoft 365 and the other tools your teams rely on every day. Move records, trigger downstream workflows, and keep data consistent across CRMs, ERPs, data warehouses, support desks, and internal apps — without writing or maintaining glue code.
Use this connector to eliminate manual data entry, reduce swivel-chair work between systems, and give every team a complete, real-time view of customers, operations, and pipeline. Flows360 handles authentication, pagination, retries, rate-limit backoff, and schema drift so your integrations stay healthy as Microsoft 365 evolves.
Capability summary
Authentication
Auth method: OAuth 2.0
Required scopes
read
write
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| No | No | ||
| No | No | ||
| No | No |
Supported actions
| Action | Description |
|---|---|
Setup steps
1. Sign in to Microsoft 365
Log in to your Microsoft 365 account with an administrator user that can create or manage API credentials.
2. Create credentials for Flows360
In the Microsoft 365 admin area, create a new API key, service account, or OAuth application dedicated to Flows360. Grant it the minimum scopes required to read and write the objects you plan to sync.
3. Copy the credentials
Copy the generated client ID, client secret, API token, or service account key. Treat these values as secrets — they grant access to your Microsoft 365 data.
4. Connect from Flows360
In Flows360, open Connectors → Microsoft 365 → Connect. Paste the credentials into the matching fields and (for OAuth) complete the authorization redirect.
5. Test the connection
Run the built-in test in Flows360. A successful test confirms credentials, network access, and the required scopes. You can now use Microsoft 365 as a source or destination in any flow.
Limitations
- Throughput is bounded by the Microsoft 365 API's published rate limits; Flows360 automatically retries with exponential backoff.
- Computed, derived, or read-only fields in Microsoft 365 cannot be written to from Flows360.
- Real-time triggers depend on Microsoft 365 supporting webhooks; otherwise Flows360 falls back to polling on the schedule you configure.
- Large historical backfills should be run during off-peak windows to avoid hitting daily API quotas.
Troubleshooting
My Microsoft 365 connection fails with an authentication error.
Double-check that the credentials were copied without extra whitespace, that the credential has not been revoked or expired in Microsoft 365, and that you connected to the correct environment (sandbox vs production). Re-issue the credential in Microsoft 365 and reconnect from Flows360 if the problem persists.
Flows are being throttled or returning 429 errors.
You are hitting Microsoft 365's API rate limit. Reduce the frequency of polling triggers, batch updates where possible, and narrow filters so flows only fetch the records they need. Flows360 retries automatically, but sustained high volume may require redesigning the workflow.
Some records or fields are missing from Flows360.
This is almost always a permissions or scope issue. Confirm the credential used by Flows360 has read/write access to the specific objects, records, and fields you expect, then reconnect. Some Microsoft 365 fields are derived or admin-only and cannot be exposed via API.