# Microsoft 365 integration consultant: Outlook, Teams, Excel and SharePoint, connected.

> SBD builds Microsoft 365 integrations on Microsoft Graph that turn Outlook mail into records, post useful alerts to Teams, keep Excel reports filled and file documents to SharePoint, with app access scoped to the mailboxes and sites it needs, for teams of 1 to 1,000 people. Workflow automation builds start at $1,000, with the fixed price set after a $500 Automation Audit that is credited to the build.

- Canonical: https://smallbaydigital.com/integrations/tools/microsoft-365/
- Publisher: SmallBay Digital

## What a Microsoft 365 integration from SBD does

Established companies tend to run on Microsoft 365: Outlook for mail, Teams for conversation, Excel for numbers and SharePoint or OneDrive for files. The automation opportunities look like those in Google Workspace, but the access model, limits and tooling are different, and an IT team usually has a say.

We build four kinds of thing. Mail intake: invoices, orders and enquiries arriving in Outlook mailboxes read, classified and turned into records in accounting, CRM or ticketing, with the original linked. Teams alerts: messages to a channel or chat when something needs a person, with the context to act and no noise. Excel reporting: workbooks on SharePoint filled from your systems on a schedule. SharePoint filing: documents saved to the right site, library and folder by client and type, with metadata set.

We have not published a case study built on Microsoft 365, so we will not point you to one.

## Power Automate, connectors or a Graph integration

Power Automate, Microsoft's own automation tool, is often the right choice for simple flows inside the Microsoft estate. Make, Zapier and n8n also have Microsoft 365 modules. We build directly on Microsoft Graph, usually from n8n or a small service, when:

- The workflow spans Microsoft 365 and several systems outside it, and needs one place for logs, retries and alerts.
- An app must read many mailboxes, and IT wants access limited to named ones.
- Volume or concurrency would hit Graph throttling without careful pacing.
- Documents need extraction or AI classification with a person approving the result.

## App permissions scoped to the right mailboxes

An app that reads mail without a signed-in user needs application permissions such as Mail.Read. Granted in Microsoft Entra ID, those apply to every mailbox in the tenant, which is rarely what IT wants. Microsoft's answer is RBAC for Applications in Exchange Online, which assigns the permission to the app with a resource scope, such as a management scope or an administrative unit, so it can reach only the mailboxes in that scope. Microsoft's documentation states it replaces Application Access Policies.

There is a trap in it. Microsoft notes that permissions from Entra ID and from Exchange RBAC are added together, so if the app still holds an unscoped Mail.Read in Entra ID, the Exchange scope achieves nothing. We remove the tenant-wide grant, assign the scoped role, and prove it with Microsoft's test cmdlet before go-live. Microsoft also notes that permission changes can take between 30 minutes and 2 hours to apply, which we plan into the change window.

## Graph throttling, change notifications and SharePoint limits

Microsoft Graph throttles per service. From Microsoft's throttling page in October 2026: Outlook allows 10,000 requests per 10 minutes and four concurrent requests per app per mailbox, and 150 MB of uploads per 5 minutes. Posting a Teams channel message is limited to 50 requests a second per app per tenant, and one a second per channel and per user. Excel workbook calls are limited to 1,500 per 10 seconds per app per tenant. SharePoint counts resource units: in a tenant with up to 1,000 licences, an app gets 1,250 a minute and 1,200,000 a day, where a single read costs 1, a multi-item query or write 2, and a permissions call 5. SharePoint asks callers to honour Retry-After and to identify themselves in the User-Agent header, and says well-identified traffic is prioritised.

Change notifications replace polling, with limits of their own. A subscription to Outlook messages lasts at most 10,080 minutes, just under seven days, or 1,440 minutes with resource data included; a OneDrive or SharePoint list subscription lasts up to 42,300 minutes, and a Teams chat message subscription up to 4,320. Microsoft lists the maximum notification latency for drive items and lists as 6 hours. So we renew subscriptions before expiry, handle lifecycle notifications, and pair every subscription with a delta query sweep so a late or missed notification does not mean missed work.

## Excel and SharePoint details that decide reliability

Excel automation through Graph works best against Excel tables. Loose ranges break when rows are added. A workflow that appends rows to a named table keeps working when someone adds a column or sorts the sheet; one that writes to fixed cell addresses breaks. We convert report sheets to tables before connecting them, and keep calculated columns and charts on separate sheets from the data the workflow writes.

In SharePoint, structure is metadata as much as folders. Filed documents get columns for client, document type and period, so libraries can be filtered and retention policies applied by type. For reading large libraries, SharePoint's own guidance favours delta queries with a token, which it prices at one resource unit, so our syncs track changes rather than rescanning everything.

Teams messages posted by a workflow carry a link to the record and a clear next step, and are posted to a channel owned by the team that acts on them. If nobody acts on a type of alert for a month, we remove it.

Where a workflow writes to a workbook that people also open in the desktop app, we schedule writes outside working hours or write to a separate data workbook that the report links to, so nobody's open session collides with an automated update.

## How a Microsoft 365 engagement with SBD works

Every engagement starts with an [Automation Audit](https://smallbaydigital.com/services/audit/) at $500, credited in full to your build. We map the mailboxes, Teams channels, workbooks and sites involved, and agree the permission model with your IT team before anything is registered.

Workflow automation builds start at $1,000, internal tools at $3,000 and multi-module systems at $5,000. Work runs in two-week sprints with sixty days of hypercare, and care plans start at $50 a month, which covers subscription renewal and alerting. See the [pricing page](https://smallbaydigital.com/pricing/). Your Microsoft licences stay between you and Microsoft.

## What you own when we finish

The Entra app registration, its credentials, the Exchange role assignments and the workflow platform are in your tenant. You receive a permission document listing every Graph permission, its scope and the reason for it, a list of subscriptions and their renewal schedule, and a runbook for throttling, expired credentials and failed notifications. Certificates and secrets have expiry dates, and the runbook says who renews them and when.

## At enterprise scale

Microsoft 365 is the office stack for most established companies, from professional services firms to manufacturers and public bodies. Integrations are usually approved by an IT or security team that owns Entra ID and Exchange, while finance, operations and sales own the processes being automated.

- **Scoped app permissions** We use RBAC for Applications in Exchange Online to limit mail access to named mailboxes, remove any tenant-wide grant in Entra ID, and prove the scope with Microsoft's test cmdlet.
- **IT review** Before registration we give IT a permission document with every Graph permission, its scope and the reason. Nothing is consented without their sign-off.
- **Throttling-safe design** Clients respect per-mailbox concurrency, honour Retry-After, batch where Graph allows it and identify themselves to SharePoint, so integrations stay within limits.
- **Durable notifications** Subscriptions are renewed before expiry, lifecycle notifications handled, and delta queries run on a schedule so late or missed notifications never mean missed work.
- **Credential lifecycle** Certificates or secrets are stored in your vault with expiry dates on the runbook and reminders set, so an expired credential never stops a process silently.
- **Audit trail** Every item processed is logged with its source, the action taken and who approved it, kept in your tenant or your own database.

### Engagements

- **Already on Microsoft 365, invoices in an Outlook mailbox.** We read the accounts payable mailbox only, extract each invoice, draft the bill in accounting for approval and file the PDF to SharePoint by supplier and month.
- **Already on Microsoft 365, Teams full of noise.** We replace scattered alerts with a few channels that post only what needs a person, with the record linked and the next step stated.
- **Already on Microsoft 365, IT blocked a broad app.** A previous integration asked for tenant-wide mail access and was refused. We rebuild it with scoped Exchange roles and a written permission model IT can approve.

## Related

- [Power Apps consultant](https://smallbaydigital.com/integrations/tools/power-apps/)
- [Gmail automation](https://smallbaydigital.com/integrations/tools/gmail/)
- [Invoice processing](https://smallbaydigital.com/solutions/use-case/invoice-processing/)
- [For CIOs](https://smallbaydigital.com/solutions/role/cio/)
- [IT teams](https://smallbaydigital.com/solutions/function/it/)
- [Security at SBD](https://smallbaydigital.com/trust/security/)

## Sources

- Microsoft Learn: Microsoft Graph service-specific throttling limits (Outlook, Teams, Excel), checked 29 October 2026 <https://learn.microsoft.com/en-us/graph/throttling-limits>
- Microsoft Learn: Change notifications overview (subscription lifetimes, latency), checked 29 October 2026 <https://learn.microsoft.com/en-us/graph/change-notifications-overview>
- Microsoft Learn: Avoid getting throttled or blocked in SharePoint Online (resource units, Retry-After, traffic decoration), checked 29 October 2026 <https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online>
- Microsoft Learn: Role Based Access Control for Applications in Exchange Online, checked 29 October 2026 <https://learn.microsoft.com/en-us/exchange/permissions-exo/application-rbac>
