Integration · Automate and collaborate

Microsoft 365 and Meteor AI agents

Connect Microsoft 365 to a WhatsApp Met: read the calendar, mail and files of your account and book meetings through Microsoft's official MCP server.

Book a demo See every integration

How does Microsoft 365 connect to Meteor?

With the Microsoft 365 ready connector, your WhatsApp Met reaches the mail, calendar, Teams chats and OneDrive and SharePoint files of the account the admin authorizes, through Microsoft's official Work IQ server. With 12 generic tools it reads any resource by its path, computes a week's schedule, searches your documents and asks Microsoft 365 Copilot. Writes, such as creating an event or sending an email, are blocked by your organization's policy until the administrator enables them. Usage is billed to your Microsoft account, by consumption.

What it automates

What a Meteor Met does with Microsoft 365

Offer times from the real calendar

When a customer asks for a meeting, your Met reads the week's calendar view on the connected account and offers only the slots that are free in Outlook.

Leave the meeting on the calendar

If your administrator enables writes, the Met creates the event with the subject, the time and the customer's email as an attendee, and Outlook sends them the invitation.

Find a document for the customer

The Met searches OneDrive or SharePoint for the spec sheet or the quote the customer asks for and answers with what it contains, citing which file it came from.

Ask Copilot what happened with a customer

For the team, the Met can ask Microsoft 365 Copilot what was discussed with a customer in recent emails and chats, and bring the answer into the chat.

12 tools

Everything your Met can ask Microsoft 365 for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`fetch`	Reads one or more resources by path, such as /me/messages or /me/events, in parallel.
`fetch_blob`	Downloads a file's content, such as a document or an image, up to 4 MB by default.
`create_entity`	Creates a resource in a collection, such as a calendar event or a draft email.
`update_entity`	Updates an existing resource, such as an email's subject or an event's time.
`delete_entity`	Deletes a resource by its path. It is destructive and starts switched off.
`do_action`	Runs an action with side effects, such as sending an email, copying or moving an item. Starts turned off.
`call_function`	Calls a Microsoft Graph function, such as the calendar view for a date range.
`ask`	Asks Microsoft 365 Copilot or another agent a natural language question about your data.
`retrieve`	Searches your Microsoft 365 data and returns the content with its sources. It is in preview.
`list_agents`	Lists the agents available to ask, including Microsoft 365 Copilot.
`get_schema`	Returns the schema of a Microsoft Graph operation so the request is built correctly.
`search_paths`	Searches which Microsoft Graph paths are available from a prefix or a pattern.

The limits

What the Microsoft 365 integration does NOT do

We would rather say it here than have you find out during rollout.

It does not write to Microsoft 365 until your organization's policy allows it: Work IQ blocks create, update, delete and action requests by default, and an administrator enables them.
It does not ask for confirmation in the chat before writing. The admin chooses in Connections which actions stay on; delete and do_action, which sends emails, start switched off.
It is not free: Work IQ is billed by consumption in Copilot Credits, with a usage based billing plan in Copilot Studio and an Azure subscription from your organization.
It does not bring long lists: each collection returns 25 items by default and up to 100, chat messages come 10 at a time and files over 4 MB are not downloaded by default.
It does not reach every path: by default it works with /me/, /users/ and /sites/, blocks authentication and application paths, and your organization's policy can close more.
It sees no more than the authorizing account and its permissions in Microsoft 365.

Before you start

What you need to connect Microsoft 365

1

Work IQ enabled in your organization

A Microsoft 365 global administrator sets up the Work IQ service in your organization once and configures a usage based billing plan in Copilot Studio, with an Azure subscription and a resource group.
2

A Microsoft Entra app with admin consent

You register an app in Microsoft Entra with the return URL Met shows you, your administrator grants consent and you copy its application (client) ID.
3

Connect it in Met

In Met, open Connections → Microsoft 365 → Connect, paste the app ID and authorize with your Microsoft account. Then you choose which actions stay on.

Frequently asked questions

Questions about Microsoft 365 and Meteor

Work IQ uses generic tools that work on paths: the same tool reads emails, events or files depending on the path it receives. That is why the Met can first check which paths exist and their schema before asking for something.

Only if your organization enables actions in the Work IQ policy and the admin leaves the actions tool on in Met. That tool starts turned off: turn it on only if you need it.

Microsoft bills Work IQ by consumption, in Copilot Credits, with a usage based billing plan and an Azure subscription. Check with your administrator how it fits your Microsoft agreement before connecting.

Because Microsoft requires each organization to authorize the application that accesses its data. The app is yours, your administrator grants consent and can withdraw it at any time.

Step by step