Microsoft Outlook connector

Use your Microsoft Outlook data for reporting, automation and AI.

Data Panda brings your Outlook mailbox metadata together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your sales, support and IT teams use every day.

About Microsoft Outlook

The email backbone of almost every Microsoft 365 enterprise.

Microsoft Outlook shipped as Outlook 97 in January 1997, replacing Exchange Client and Schedule+ and folding mail, calendar, contacts, tasks and notes into one personal information manager. Today it sits inside Microsoft 365 across desktop, web and mobile, with the user's mailbox living on Exchange Online and the rest of the M365 stack (Teams, OneDrive, SharePoint, Copilot) plugged in around it. Outlook on the web, the new Outlook for Windows and the mobile clients all read from the same Exchange Online mailbox, which is the object that matters for reporting.

For most M365 shops Outlook is no longer just personal mail. It is where customer threads start before a CRM ever sees them, where shared mailboxes (sales@, support@, billing@) catch the work before a helpdesk takes it over, where distribution lists fan out announcements that nobody re-confirms, and where Inbox rules and mailbox-forwarding configurations quietly redirect mail to outside addresses long after the person who set them up has left. The Microsoft Graph Outlook surface exposes messages, mailFolders, attachments, events, calendars, contacts, mailboxSettings and messageRules through one API. That is enough surface to answer the operational questions IT, security and revenue ops only ask after something already went wrong, but it also reaches the most sensitive store of text the company has, so what gets pulled and what stays inside Exchange is a deliberate scope decision.

What your Microsoft Outlook data is for

What you get once Microsoft Outlook is connected.

Mailbox and response reporting

Volume, response time and shared-mailbox load per inbox in one place, instead of an Exchange admin export someone runs by hand.

Median and tail response time per inbox owner and per recipient domain
Shared-mailbox queue depth and unanswered-thread count over time
Active versus dormant mailboxes per business unit, with last-login age

Inbox-driven automation

Let Outlook message events trigger work in the systems where the answer needs to land.

Customer threads from named domains create or update the matching CRM contact and activity
Inbox-rule and mailbox-forwarding changes get logged for the next security review
Distribution-list audits run on a schedule, not after someone leaves the company

AI workflows

Put mailbox topology behind AI that helps route, summarise and triage, on the metadata layer rather than message bodies by default.

Thread classification by topic and customer for sales@ and support@ inboxes
Auto-prioritisation of messages from strategic accounts based on CRM tier
Long-thread summaries dropped into the right reviewer's task list, with explicit scope

Custom apps on your data

Small internal tools on Outlook metadata for IT, security and revenue teams.

IT dashboard of mailbox forwarding rules and Inbox rules per user
Sales dashboard of inbound conversations per account, joined to the CRM
Compliance app showing distribution-list membership per mailbox and per external domain

Use cases

Use cases we deliver with Microsoft Outlook data.

A list of concrete reports, automations and AI features we have built on Microsoft Outlook data. Pick the one that matches your situation.

Response time by tierMedian and tail reply time split by customer tier, supplier and internal recipient.

Shared-mailbox loadVolume and unanswered-thread count per sales@, support@ and billing@ inbox over time.

Dormant-mailbox auditMailboxes with no read or send activity in N days, joined to HR offboarding.

Inbox-rule inventoryInbox rules per user, with the actions and target folders or addresses they touch.

Mailbox forwarding auditPer-mailbox forwarding configuration, with destination domain and last-changed date.

Distribution-list sprawlDistribution lists per business unit, with active versus dormant lists and external members.

External-domain mail flowInbound and outbound mail volume per external domain, ranked over a rolling window.

CRM-coverage gapCustomer-domain threads in Outlook that never made it onto a Salesforce or HubSpot record.

Attachment-volume hotspotsMailboxes carrying the largest attachment footprint, by file type and sender.

Calendar-load overlapMeeting hours per role, with the share that overlaps Teams calls and the share with no agenda.

Real business questions

Answers you will finally get.

How long does it take our shared mailboxes to reply, per customer tier?

Median and tail response time per shared mailbox (sales@, support@, billing@) and per inbox owner, joined to your CRM tiering on the recipient domain. Sales and support leadership see whether strategic accounts get the response time the contract promises, and which queues drift on which segment. The number lives next to the rest of the warehouse, so it does not need a manual Outlook search the week before a QBR.

Which Inbox rules and mailbox-forwarding settings are quietly redirecting our mail?

Inbox rules per user with their conditions and actions, plus the per-mailbox forwarding configuration, joined to HR offboarding dates and to an internal allow-list of destination domains. Security sees which rules forward customer threads to gmail.com or to an ex-employee's personal address, which is the silent failure mode after a departure that nobody catches without a list.

How much of our distribution-list footprint is still alive?

Distribution lists per business unit with member count, last-message date and external membership. The works council, IT and procurement see which all-staff and all-supplier lists are still being used, which ones quietly hold ex-employees or partners that should no longer receive internal news, and which ones can be retired before the next phishing campaign uses one as a relay.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Microsoft 365 mailbox seats lined up against actual mailbox activity. Dormant or near-dormant accounts that still carry a full Exchange Online plan become a list rather than a hunch, so the next renewal conversation runs on real numbers rather than reseller defaults.

For sales leaders

Inbound and outbound thread counts per account, joined to the CRM. Sales leadership sees which strategic customers get answered on time on the shared sales@ mailbox, and where the gap between Outlook activity and CRM activity hides revenue work nobody logged.

For operations

Shared-mailbox load, Inbox-rule inventory, mailbox-forwarding audit and distribution-list sprawl in one view. IT runs the quarterly mailbox cleanup with a real list per team owner instead of asking everyone to do their own audit.

Ideas

What you can automate with Microsoft Outlook.

Pair with Salesforce

Log Outlook customer threads to the right Salesforce account

Inbound and outbound Outlook threads from named customer domains land as activities on the matching Salesforce account, contact and opportunity, with subject, sender, timestamp and Internet message id attached. Account execs see the conversation history without forwarding mails to a logging address, and the deal record stops missing the supplier replies that moved the close date.

Pair with HubSpot

Track HubSpot sequence replies and bounces against the Outlook mailbox

HubSpot sales sequences send through Outlook and the engagement loop closes on the same mailbox: replies, opens and bounces post back to the HubSpot deal and contact with the originating thread linked. Sales managers see which sequences land in the actual customer thread and which ones get filtered or bounced by the recipient, instead of trusting a generic open-rate number from outside the inbox.

Pair with Microsoft Teams

Surface Outlook threads in the right Microsoft Teams channel

Long customer or supplier threads in Outlook post a compact summary in the matching account or support channel in Microsoft Teams, with sender domain, last reply timestamp and a deep link back to the thread. Account teams pick up the context in the channel they already watch, and shared-mailbox owners stop forwarding mails by hand to keep everyone in the loop.

Pair with Zendesk

Convert Outlook support threads into Zendesk tickets

Inbound Outlook threads to a support alias open or update the matching Zendesk ticket with sender, subject, body excerpt and attachment list, with the original Outlook conversation id kept on the ticket for traceability. Support stops losing the conversations that begin in personal mailboxes before reaching the helpdesk, and the SLA clock starts on the original send timestamp rather than on the moment an agent forwarded the mail in.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Microsoft Outlook data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Microsoft Outlook to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Microsoft Outlook connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Does the connector pull message bodies, or only metadata?

The default pull through the Microsoft Graph Outlook surface stays at message and conversation metadata: message id, conversation id, subject, from, to, cc, timestamps, folder ids, attachment metadata, plus mailbox-level signals like Inbox rules, mailbox forwarding and shared-mailbox delegation. Message body content is not part of the standard scope, which keeps the warehouse focused on inbox topology and response analytics rather than on what people wrote to each other. Body access needs a separate conversation about scope, retention and the Graph permissions involved, and is not how we recommend most customers start.

How does the connector handle shared mailboxes and delegation?

Shared mailboxes (sales@, support@, billing@) are first-class objects on Exchange Online, and Microsoft Graph supports reading from a user's primary mailbox and from shared mailboxes the calling identity has been granted access to. The connector pulls the underlying mailboxes plus the delegation grants, so reports on shared-inbox load join the right messages to the right team rather than treating every mailbox as a single user. In-place archive mailboxes are explicitly out of scope on the Graph API.

Where does this connector stop and the Outlook Calendar connector pick up?

Both surfaces sit on the same Exchange Online mailbox, but we keep them as separate connectors so the scope is explicit. This Outlook connector covers mail: messages, mailFolders, conversation threads, attachments, mailboxSettings and messageRules. The Outlook Calendar connector covers events, calendars, calendarGroups and free/busy. If you want both, you wire both, and the warehouse joins them on the user identity and the conversation id where applicable.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Microsoft Outlook setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors