{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Enabled by default.
- Authentication: OAuth 2.0.
- Connection: A user authorizes the connection in the provider's consent screen.
- Scopes:
Mail.Read,Mail.Send,Mail.ReadWrite,Mail.Read.Shared,Mail.ReadWrite.Shared,Calendars.Read,Calendars.ReadWrite,offline_access.
Credentials
Set these per environment. See Connect an integration.
These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.
Cloud access modes
Hosted Cloud tools support both user-delegated OAuth 2.0 authorization code access and application/service access using the OAuth 2.0 client credentials grant. These are separate credential configurations. The local Code runtime has its own supported authentication methods.
Set every application variable below in the target project environment. Delegated OAuth app variables above do not activate application access.
Configure application access describes provider setup, identity selection, project tool policy and supported-operation restrictions.
Setup
- Choose who owns the Microsoft OAuth app: On hosted Veryfront, Outlook uses the Veryfront-managed Microsoft OAuth app: connect Outlook from the project's integrations and approve the Microsoft consent screen, no environment variables needed. Set MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET only to use your own Microsoft OAuth app, which is required for local and self-hosted runs.
- Register an app in Microsoft Entra: In the Microsoft Entra admin center, open App registrations and register a new application. For Supported account types, choose accounts in any organizational directory and personal Microsoft accounts, because the connector signs in through the common endpoint.
- Add the redirect URIs: Under Authentication, add a Web platform. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/outlook for hosted Veryfront, or your app origin followed by /api/auth/outlook/callback for a local or self-hosted app.
- Add Microsoft Graph permissions: Under API permissions, add these delegated Microsoft Graph permissions: Mail.Read, Mail.Send, Mail.ReadWrite, Mail.Read.Shared, Mail.ReadWrite.Shared, Calendars.Read, Calendars.ReadWrite, offline_access. If your tenant does not let users consent to apps, an administrator must grant consent for the organization.
- Create a client secret: Under Certificates & secrets, create a client secret. Set MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET from the app's credentials. Client secrets expire, so rotate MICROSOFT_CLIENT_SECRET before the expiry date you choose.
- Verify access: Run List Emails (read-only). It returns message summaries from the connected mailbox without changing it.
Provider notes
- The connection requests Mail.Read, Mail.Send, Mail.ReadWrite, Mail.Read.Shared, Mail.ReadWrite.Shared, Calendars.Read, Calendars.ReadWrite and offline_access. offline_access lets the connection refresh its access token. Mail.Read.Shared lets the tools read mailboxes shared with the user. Mail.ReadWrite.Shared lets Move Shared Mailbox Email move messages in those mailboxes.
- The shared mailbox tools address the mailbox you name in the mailbox argument and never fall back to the signed-in user's mailbox. This connector signs in with delegated OAuth only, so the signed-in user must have access to that mailbox in Exchange. Application (app-only) permissions are not used by this connector.
- Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.
Tools
Verify the connection
Call a read tool such as outlook__list_emails with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.