Reference · built on requestConnectorMessaging & notifications

Microsoft Outlook

Exchange Online and Outlook mailboxes: messages, folders, send, rules, and change notifications through the Microsoft Graph mail API.

Request accessPricing ↗

About

Microsoft Graph exposes Outlook mail for personal and organisational accounts, covering primary and shared mailboxes on Exchange Online and on-premises Exchange in a hybrid deployment. A message lives in a mailFolder; well-known folders such as Inbox, Drafts, SentItems, and DeletedItems can be addressed by name. Graph also carries attachments, messageRule inbox rules, mailSearchFolder, outlookCategory, mailboxSettings, and mailTips. In-place archive mailboxes are not reachable.

Through Fibric, an operator watches the folders you choose in the mailboxes you scope, and proposes a reply draft, a send, a move, or a flag for a person to approve in Outlook.

This is a reference listing. It documents what Fibric would read from Microsoft Outlook and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Messages in a folder through GET /me/mailFolders('Inbox')/messages or /users/{id}/messages, with $select for subject, from, receivedDateTime, isRead, and conversationId
  • Change notifications from a subscription on /users/{id}/mailFolders('inbox')/messages for created, updated, and deleted messages
  • Incremental changes per folder through GET /me/mailFolders/{id}/messages/delta and its @odata.deltaLink
  • Attachments through the message's attachments relationship, and internetMessageHeaders when requested with $select
  • Inbox rules through messageRule and automatic-reply settings through mailboxSettings
  • Out-of-office status of recipients through mailTips

Proposed actions

  • Target capability: propose a reply by creating a draft with createReply or createReplyAll, updating its body, then send once approved
  • Target capability: propose a new message through POST /me/sendMail or /users/{id}/sendMail with Mail.Send
  • Target capability: propose moving a message to a folder with the move action
  • Target capability: propose marking a message read, setting categories, or setting a follow-up flag through Update message
  • Target capability: propose forwarding a message with the forward action

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • First reply from a shared mailbox

    A change notification fires on the shared inbox. The operator reads the message, drafts a reply with createReply, and proposes it. A person approves in Outlook and the draft is sent to Sent Items.

    With First Response

  • Escalation packet from a thread

    Messages sharing a conversationId are gathered with their attachments and internetMessageHeaders into one packet. The operator proposes forwarding it to the escalation owner with a summary on top.

    With Escalation Packet

  • Quote follow-up flagged for the seller

    When a quote thread has had no reply for the interval you set, the operator proposes a follow-up draft and a follow-up flag with a due date, so it appears in the seller's Outlook.

    With Quote Follow-up

Requirements

  • A Microsoft 365 or Exchange Online organisation and an app registration with a client secret, certificate, or federated identity credential
  • Admin consent for the Mail permissions used, or a signed-in user's consent under delegated access
  • To limit app-only access to some mailboxes: an Exchange Online RBAC for Applications role such as Application Mail.Read, scoped, with no unscoped Entra grant
  • An HTTPS notificationUrl Fibric operates for change notifications, renewed before each subscription expires
Authentication
An OAuth 2.0 access token from the Microsoft identity platform, presented as Authorization: Bearer, for an app registered in the Microsoft Entra admin center with delegated permissions (a signed-in user) or application permissions (no user) such as Mail.Read, Mail.ReadWrite, and Mail.Send.

Limits

  • A message subscription lasts at most 10,080 minutes (under seven days), or 1,440 minutes with resource data; a mailbox allows 1,000 active subscriptions in total
  • Delta query tracks one folder at a time; with a $filter it returns at most 5,000 messages, and $search is not supported
  • Message and folder ids can change on copy or move unless the Prefer: IdType="ImmutableId" header is used
  • Throttled calls return 429 with a Retry-After header in seconds; sendMail answers 202 Accepted before delivery, and a message may address at most 500 recipients

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Microsoft Outlook ↗

Questions and answers

Can the app be limited to certain mailboxes?
Yes, for app-only access. Exchange Online RBAC for Applications assigns roles such as Application Mail.Read or Application Mail.Send to the service principal with a management scope or administrative unit. The unscoped permission must be removed in Microsoft Entra ID, and changes take 30 minutes to 2 hours to apply.
How does Fibric learn about new messages?
A subscription on /users/{id}/mailFolders('inbox')/messages posts change notifications to an HTTPS notificationUrl, with latency under a minute on average and 3 minutes at most. It must be renewed within 10,080 minutes. Delta query on the same folder fills any gap after an outage.
Does sendMail confirm delivery?
No. sendMail returns 202 Accepted, which means the request was accepted, not delivered; delivery is subject to Exchange Online limits and throttling. The message is saved to Sent Items unless saveToSentItems is false. A message from an Exchange Online mailbox may have at most 500 recipients.
Ask about Microsoft Outlook

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Microsoft Outlook through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy