Prepare replies in Outlook
An incoming question is read and a draft answer is ready in Outlook. You review and send it yourself.
Microsoft 365 integration
About this source
Gen8
Source: Microsoft 365 integration
Managed AI service for SMEs. We set up, connect and manage; you stay in control.
© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft
Integration · route: native
Outlook, SharePoint and OneDrive directly — Teams through another route
Microsoft 365 is a collection, not one integration. Gen8 has its own integrations for Outlook mail, Outlook calendar, SharePoint and OneDrive. Not for Microsoft Teams: what a workflow does with Teams is custom development configured per environment. We state that distinction first because it determines what to expect from each component.
- Permissions stay in force
- EU hosting
- Visible approval
At a glance
Route: native
Components: Outlook (mail and calendar), SharePoint, OneDrive; Microsoft Teams through custom development
Capabilities
What the integration can do
Outlook mail. Search the mailbox, read messages, manage mail and prepare drafts. Sending is disabled by default in our setup.
Outlook calendar. Read calendars and appointments and propose or create an appointment.
SharePoint. Read sites, lists and document libraries — and prepare documents or list items in your designated location with its existing metadata.
OneDrive. Read files from designated folders as answer sources or input for the next step.
Microsoft Teams. It has no own Gen8 integration. Channel notifications or picking up Teams messages require custom development: the route is selected and built per environment within administrative permissions.
Inspiration
What you can automate with this
A few examples of work you can hand over through this integration. We work out what fits your organisation together during scoping.
Organize the inbox
Messages in your designated folder are searched, read and organized according to your agreements, so work reaches the right step.
Propose a follow-up appointment
If an email calls for a meeting, an appointment is prepared as an Outlook calendar proposal. Nothing is silently inserted.
Record an email decision
A decision made by email becomes a SharePoint document or list item, in your designated location with its existing metadata.
Answer using a file as source
The workflow searches your designated OneDrive folders and uses the file as an answer source or input for the next step.
A notification in Teams (custom development)
A channel notification when something is ready for review. There is no own integration: we build the route per environment within what your administrators permit.
Permissions and data
What access is needed
An administrator configures each Gen8 connection with only the permissions the selected actions need. A workflow using SharePoint as knowledge does not request mailbox access; a workflow writing drafts does not request send permissions.
Scope is especially important in a Microsoft environment, where permissions are often broader than necessary. A designated folder, list or library differs from tenant-wide access. We configure access as narrowly as the integration allows, and your administrator should choose deliberately rather than click through. Processing within Gen8 takes place in the EU; Microsoft processes data in your tenant under your agreements.
Control
Where approval is required
Reading happens without intervention. Writing starts as a proposal: a draft email is ready in Outlook, a document or list item is visible before reaching SharePoint, and a calendar appointment is proposed rather than silently inserted.
Small, reversible actions can run automatically with logging after a settling-in period. Sending email is not one of them. For everything on the custom Teams route, we deliberately retain approval longer: a route built per environment deserves more visibility than an integration proven repeatedly.
Evidence
What we can demonstrate
Outlook mail, Outlook calendar, SharePoint and OneDrive each have their own Gen8 integration with their own tools — hence the native route. Microsoft Teams does not, and we do not soften that detail: a Teams workflow requires custom development and an agreement on building and maintenance; see MCP, API and custom development. For environments partly using Google, see Google Workspace and the comparison in Google Workspace or Microsoft 365. Individual components: SharePoint.
Record an email decision in SharePoint
Plan01Components selected: read Outlook mail, record in SharePoint
Action02Message read in designated folder
Action03Existing file searched for in designated library
Action04Document prepared with existing metadata
Reflect05Teams notification needs custom development: excluded from this run
Proposal ready · a person approves the document
Can we receive notifications in Teams?
Yes, but not through a ready-made integration. It is a custom route selected and built per environment.
Does a workflow send email on our behalf?
Not in our setup. Preparing an Outlook draft is the starting point; sending remains a human action.
Does the integration get access to the entire tenant?
That is exactly what we want to avoid. We configure designated mailboxes, sites, libraries and folders, and your administrator should make that choice deliberately.
What if we partly use Google?
Mixed environments are the rule rather than the exception. Gmail, Drive and Calendar have their own integrations; see Google Workspace.