Delegated User or Enterprise App
MSPintegrations connects to Microsoft 365 for Remote Mailboxes in two ways: signing in as a Microsoft user, or connecting an Enterprise App with a tenant ID, application ID, and client secret. Both connection types poll Microsoft 365 mailboxes. Use this page to decide which one fits your setup, then follow the matching guide.
Comparison
| Sign in with Microsoft user | Enterprise App | |
|---|---|---|
| Authentication | A Microsoft user signs in and consents | Tenant ID, application ID, and client secret |
| Licensed mailbox user required | Yes | No |
| Interactive sign-in required | Yes, at setup and when reconnecting | No |
| Mailbox selection | Defaults to the signed-in user's mailbox | You choose a mailbox for every Remote Mailbox |
| Sending email through Microsoft Graph | Supported with the delegated Mail.Send permission | Supported with the Mail.Send application permission and an explicit sender mailbox |
| Maintenance | Reconnect when consent breaks | Rotate the client secret before it expires |
When to Sign In with a Microsoft User
Choose a delegated Microsoft user when:
- You already have, or can license, a dedicated Microsoft 365 user for MSPintegrations
- You want the connection to poll that user's own mailbox by default
- You want a default sending identity that workflows can use without selecting a connection and sender mailbox
Continue with Connect to Microsoft 365.
When to Use an Enterprise App
Choose an Enterprise App when:
- You do not want to buy a mailbox license for a dedicated service user
- You want unattended authentication that no user password change can break
- You are polling many mailboxes and want a credential type that never needs an interactive reconnect
- You want workflows to send through Microsoft Graph without relying on a licensed service user
Continue with Connect with an Enterprise App.