Skip to main content
Microsoft Outlook Logo

Microsoft Outlook

Email and calendar management

✅ Ready📖 Documentation Available

Configuration Guide

Overview

The Microsoft Outlook connector provides access to organizational email data through Microsoft Graph API. It syncs users, emails, attachments, and mail folders across your Microsoft 365 organization.

Authentication

The Outlook connector uses OAuth 2.0 via Microsoft Graph API with Application Permissions. This allows background access to organizational mailboxes without requiring individual user sign-ins.

How to configure and enable the Outlook Connector

Step 1: Register Application in Azure Portal

  1. Sign in to Azure Portal:
    Navigate to portal.azure.com and sign in with your Microsoft 365 administrator account.
  2. Access App Registrations:
    • Search for “App registrations” in the top search bar
    • Or navigate to Microsoft Entra IDApp registrations
  3. Create New Registration:
    • Click “New registration”
    Register Application
    • Enter application details:
      • Name: Enter a meaningful name (e.g., “PipesHub Outlook Connector”)
      • Supported account types: Select “Accounts in this organizational directory only (Single tenant)”
      • Select a platform: Web
      • Redirect URI: (Get the redirect uri from pipeshub configure outlook dialog in connector settings)
    Register Application
    • Click “Register”
    Register Application
Single-tenant configuration ensures the application only works within your organization for better security.

Step 2: Copy Application Credentials

  1. After registration, you’ll see the Overview page
  2. Copy the following values (you’ll need these later):
    • Application (client) ID: Found under “Essentials” section
    • Directory (tenant) ID: Found under “Essentials” section
Application Overview
Copy the “Application (client) ID” NOT the “Object ID”. These are different values.

Step 3: Create Client Secret

  1. In the left sidebar, click “Certificates & secrets”
  2. Click “New client secret”
  3. Configure the secret:
    • Description: Enter a description (e.g., “PipesHub Connector Secret”)
    • Expires: Choose expiration period (recommended: 24 months)
  4. Click “Add”
  5. Immediately copy the secret value from the “Value” column
Create Client Secret
The client secret value is only displayed once! If you navigate away, you cannot retrieve it again and must create a new secret.

Step 4: Configure API Permissions

  1. In the left sidebar, click “API permissions”
  2. Click “Add a permission”“Microsoft Graph”
  3. Choose “Application permissions” (not Delegated permissions)
  4. Add the following permissions:
    • User.Read.All
    • Mail.Read
    • MailboxSettings.Read
  5. Click “Add permissions”
Configure API Permissions
Application permissions allow the connector to access data across your organization without requiring individual user sign-ins.
  1. On the API permissions page, click “Grant admin consent for [Your Organization]”
  2. Confirm by clicking “Yes”
  3. Wait for the status to show green checkmarks
Grant Admin Consent
Admin consent is required for application permissions. Only Global Administrators or Application Administrators can grant this consent.

Step 6: Configure Connector in PipesHub

  1. Navigate to SettingsConnectors in PipesHub
  2. Find the Outlook connector and click “Configure”
  3. Enter the following details:
    • Application (Client) ID: From Step 2
    • Client Secret: From Step 3
    • Directory (Tenant) ID: From Step 2
    • Redirect URI: Pre-filled (verify it matches your environment)
  4. Check the “Has Admin Consent” checkbox
  5. Click “Next” or “Save”
Configure Connector in PipesHub

Step 7: Configure Filters (Optional)

Filters allow you to control what emails and calendar events are synced and indexed from Outlook.
Outlook Filters Configuration

Sync Filters

Sync filters determine which emails and calendar events are downloaded from Outlook. Data excluded by sync filters is never downloaded.Available Sync Filters:
  1. Received Date - Filter emails by received date
    • Operators: Is After, Is Before, or Is Between
    • Use cases:
      • Sync only recent emails (e.g., last 6 months)
      • Focus on specific time period
    • Example: Operator: Is After, Date: 2024-01-01 → Only syncs emails from 2024 onwards
  2. Mail Folders - Filter by specific Outlook folders
    • Operator: In (include only) or Not In (exclude)
    • Value: Enter one or more folder names (e.g., Inbox, Sent Items, Important)
    • Note: Folder names are case-sensitive
    How to identify Mail Folders: The connector syncs from standard Outlook folders and any custom folders you’ve created:
    • Standard folders: Inbox, Sent Items, Drafts, Deleted Items, Junk Email, Archive
    • Custom folders: Any folders you’ve created in Outlook
    Outlook Folder Structure
    Example Configurations:
    • Sync only Inbox and Sent Items: Operator: In, Values: Inbox, Sent Items
    • Exclude Junk and Deleted folders: Operator: Not In, Values: Junk Email, Deleted Items

Indexing Filters

Indexing filters control what synced data gets processed for AI search. All data is synced, but only enabled content types are indexed.Available Indexing Filters:
  • Email Section:
    • Index Emails (default: enabled)
    • Index Email Attachments (default: enabled)
  • Calendar Section:
    • Index Calendar Events (default: enabled)
Example Configurations:
  • Sync last year’s emails: Received Date → Operator: Is After, Date: 2024-01-01
  • Sync specific project period: Received Date → Operator: Is Between, Start: 2024-03-01, End: 2024-06-30
  • Sync future events only: Start Date → Operator: Is After, Date: 2024-12-09
  • Index emails but not attachments: Disable “Index Email Attachments” toggle
Filters help optimize performance and storage by limiting the scope of synced data. You can adjust filters at any time, and changes will apply on the next sync.

Step 8: Enable the Connector

  1. After saving the configuration, toggle the connector to “Enable”
  2. The connector will verify credentials and begin initial sync
  3. Wait for the status to show “Connected” or “Syncing”
Unlike user-facing OAuth flows, there’s no login screen because the connector uses application permissions with client credentials.

Supported Features

The Outlook connector syncs the following data:
  • Users: User profiles and mailbox information
  • Emails: All messages from organizational mailboxes
  • Attachments: Files attached to emails
  • Mail Folders: Folder structure (Inbox, Sent, Drafts, custom folders)

Data Sync Behavior

Initial Sync

  • Processes all existing emails and folders from all user mailboxes
  • Duration depends on mailbox sizes
  • Runs in the background without affecting mailbox performance

Incremental Sync

  • Polling-based: Checks for new/updated emails at regular intervals
  • Uses Microsoft Graph delta queries for efficient updates
  • Only syncs new or modified emails after initial sync

Troubleshooting

Common Issues

Invalid client credentials error:
  • Verify Client ID, Client Secret, and Tenant ID are correct
  • Ensure Client Secret hasn’t expired
  • Create new Client Secret if needed
Insufficient privileges error:
  • Check all three API permissions are added: User.Read.All, Mail.Read, MailboxSettings.Read
  • Grant admin consent if status shows “Not granted”
  • Wait 5-10 minutes for permissions to propagate
Tenant ID not found error:
  • This connector only works with Work or School accounts (Microsoft 365)
  • Personal accounts (outlook.com, hotmail.com) are not supported
Client Secret expired:
  • Create new Client Secret in Azure Portal
  • Update configuration in PipesHub
  • Set reminders to rotate secrets before expiration
For personal Microsoft accounts, this connector is not supported as they lack Tenant IDs required for authentication.

Ready to Get Started?

The Outlook connector is fully operational and ready for use. Follow the configuration guide above, or reach out to our support team if you need assistance.