Microsoft Outlook Integration

Keep the Azure portal tab open—you'll return to add permissions and create a client secret in the next steps. Azure AD app registration is free and doesn't consume licenses.

Delegated permissions mean the app acts on behalf of the signed-in user (your agents). If you need to access mailboxes without user login (service account), use Application permissions instead, but this requires additional Exchange admin setup.

Set a calendar reminder for 23 months from now to regenerate the client secret before expiration. If it expires, all your Outlook automation workflows will break until you generate a new secret and update n8n credentials.

Use your primary work email for OAuth connection—this becomes the 'sender' for automated emails. If multiple agents need automation, each should connect their own Outlook account in separate n8n credential sets.

If send works but trigger doesn't fire, check trigger polling interval (default 1 minute). For instant triggers, use Microsoft Graph webhooks instead of polling, but this requires a publicly accessible n8n instance with HTTPS.

Shared mailboxes don't require additional licenses and don't count against your user limit. They're ideal for team@ or info@ addresses where multiple agents need visibility.

Use Outlook's built-in 'Quick Parts' feature to save email templates accessible from Outlook client. This allows agents to manually send from templates while automation uses the same templates programmatically for consistency.

For testing delays, use short intervals (5 minutes) instead of 24 hours. Once confirmed working, update to production delay values. Use n8n's 'Wait' node with 'Resume on date' option for calendar-relative delays.