Documentation Index
Fetch the complete documentation index at: https://docs.pipeshub.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The Microsoft Outlook connector provides access to organizational email data through Microsoft Graph. It syncs users, messages, attachments, and mail folders across your Microsoft 365 organization for search and retrieval in PipesHub.What gets synced
| Entity | Description |
|---|---|
| Users | User profiles and mailbox context used for permissions and scope |
| Emails | Messages from organizational mailboxes (subject to sync filters) |
| Attachments | Files attached to email messages (when indexing is enabled) |
| Mail folders | Standard and custom folder structure (Inbox, Sent, Archive, etc.) |
| Group mail | Microsoft 365 group conversations (when enabled for indexing) |
Authentication
The connector uses OAuth 2.0 with Microsoft Graph application permissions (client credentials plus admin consent). It runs as a background integration—no per-user interactive sign-in inside PipesHub for this connector.Configuration Guide
Follow the steps below: first register an app in Azure and grant permissions, then add the Outlook connector under Workspace Settings in PipesHub.How to configure and enable the Outlook connector
Step 1: Register an application in Azure Portal
-
Sign in to Azure Portal:
Navigate to portal.azure.com and sign in with your Microsoft 365 administrator account. -
Access App Registrations:
- Search for App registrations in the top search bar
- Or go to Microsoft Entra ID → App registrations
-
Create a new registration:
- Click New registration

- Enter application details:
- Name — A meaningful name (e.g.
PipesHub Outlook Connector) - Supported account types — Accounts in this organizational directory only (Single tenant)
- Name — A meaningful name (e.g.
- You do not need a Redirect URI for this connector; it uses application credentials and admin consent, not an interactive redirect flow in PipesHub.
- Click Register

Single-tenant registration limits the app to your directory, which is the typical setup for an internal connector.
Step 2: Copy application credentials
- After registration, open the app Overview page.
- Copy (you will paste these into PipesHub later):
- Application (client) ID — in Essentials
- Directory (tenant) ID — in Essentials

Step 3: Create a client secret
- In the left sidebar, open Certificates & secrets.
- Click New client secret.
- Set Description (e.g.
PipesHub Connector Secret) and Expires (24 months is a common choice). - Click Add, then copy the secret Value immediately from the table (not the Secret ID).

Step 4: Configure API permissions
- Open API permissions → Add a permission → Microsoft Graph.
- Choose Application permissions (not Delegated).
- Add:
User.Read.AllMail.ReadMailboxSettings.Read
- Click Add permissions.

Application permissions let the connector access org mail data without each user signing in interactively.
Step 5: Grant admin consent
- On API permissions, click Grant admin consent for [your organization] and confirm Yes.
- Wait until each permission shows Granted for [organization] with a green state.

Step 6: Open Connectors and start Outlook setup
- In the main app, open your user profile menu at the bottom of the left sidebar → Workspace Settings.
- Under Workspace, select Connectors.
- Find Outlook and start setup (+ Setup on the card), or open an existing instance to edit.


Step 7: Authenticate the Outlook instance
- In Outlook Configuration, open the Authenticate Instance tab.
- Set Instance name (e.g.
Outlook connector). - Under OAuth (Admin Consent) Credentials, enter:
- Application (Client) ID — from Step 2
- Client Secret — from Step 3
- Directory (Tenant) ID — from Step 2
- Enable Has Admin Consent if consent was granted in Azure (Step 5).
- Click Next →. Use the in-product Setup Documentation links if you want Azure steps side-by-side.

Step 8: Configure records (sync strategy and filters)
On Configure Records, you control sync cadence and scope. Indexing filters always apply; sync filters are optional—add only the constraints you need (each filter uses an operator and value where applicable).
- Sync Strategy — e.g. Scheduled or Manual (exact options depend on your workspace).
- Sync Interval — When scheduled, set the refresh interval (e.g. 1 Hour).

- Index Emails — Message bodies and metadata for search.
- Index Attachments — Attachment content where supported.
- Index Group Conversations — Microsoft 365 group mail threads.
- Recent mail only — Received Date with an operator such as Is After and your cutoff date.
- Specific mailboxes — Users with operator In and selected users (leave empty for all).
- Fewer attachments in search — Turn off Index Attachments, keep Index Emails on.

You can change filters later; effects apply on subsequent syncs per connector behavior.
Step 9: Enable sync and monitor
After saving, you may see Instance is configured and ready to sync — choose Start Syncing Now or I’ll do it later.

There is no separate interactive “Sign in to Microsoft” step inside PipesHub for this connector after admin consent—access is via application permissions and client credentials.
Supported Features
The Outlook connector syncs the following data:- Users — User profiles and mailbox context used for the integration
- Emails — Messages from organizational mailboxes (within sync filter scope)
- Attachments — Files attached to messages (when attachment indexing is enabled)
- Mail folders — Standard and custom folder hierarchy
- Group conversations — When Index Group Conversations is enabled
Useful Links
- Azure Portal: portal.azure.com
- Register an app (Microsoft Entra): Quickstart: Register an app
- Application permissions: Microsoft Graph permissions reference
- Admin consent: Grant tenant-wide admin consent
Troubleshooting
Troubleshooting
Troubleshooting
Common issues
Invalid client credentials- Verify Application (Client) ID, Client Secret, and Directory (Tenant) ID with no extra spaces.
- Confirm the secret has not expired; create a new secret in Azure and update PipesHub if needed.
- Ensure
User.Read.All,Mail.Read, andMailboxSettings.Readare added as application permissions. - Confirm admin consent shows as granted; allow several minutes for propagation.
- The connector targets Microsoft 365 (work or school) tenants with a Directory (Tenant) ID.
- Consumer-only mailboxes without a tenant suitable for app-only Graph access are not supported.
- Create a new client secret in Azure → Certificates & secrets, then update the Authenticate Instance tab in PipesHub.
Personal Microsoft accounts (e.g. outlook.com as a consumer identity without the right tenant model for this flow) are not a supported target for this enterprise connector pattern.
Data sync behavior
Synchronization process
Synchronization process
Initial sync
- Processes existing mail and folder scope according to your filters
- Duration depends on mailbox volume and API throttling
- Runs in the background
Incremental sync
- Polling-based — Refreshes on your Sync Interval when using a scheduled strategy
- Uses Microsoft Graph change tracking / delta patterns where applicable so only new or changed items are fetched after the initial pass
FAQ
Queries not returning results. What could be wrong?
Queries not returning results. What could be wrong?
There are three common causes:
-
Email mismatch — The email used during connector authentication does not match your PipesHub account email. That causes permission issues and can hide synced data.
- Fix: Reconfigure the connector and complete the flow using the same email as your PipesHub account (see the warning in Step 9).
-
Records show in “All Records” but not in search — Documents appear in All Records but not in search results.
- Fix: Verify sync filters and indexing toggles on Configure Records, and ensure indexing has finished for those items.
-
Data not yet indexed — The connector is still syncing or has not finished initial indexing.
- Fix: Open Workspace Settings → Connectors, select Outlook, check the instance Overview and sync status, and wait for indexing to complete.
Ready to get started?
The Outlook connector is ready for production use. Follow the configuration guide above, or contact support if you need help.
























