Microsoft 365¶

Artific Connect · Microsoft 365 gives a key Microsoft Graph tools: mail, calendar, OneDrive and Teams channels. It installs from the Marketplace like any other bundle.

What you get¶

One toolset, microsoft, holding seven connectors — list mail, send mail, list events, create an event, search OneDrive, list Teams channels, list a channel's messages — plus a skill that tells the model what a Teams id looks like and why calendar times need their own timezone. Every call reads or writes the signed-in person's own mailbox, calendar and OneDrive, and only the Teams channels that person already belongs to.

Signing in¶

The tools act as the person the turn is for, through that person's own Microsoft work account. Two things follow:

a request must name a user; one that names nobody is told so instead of calling a tool;
each person signs in once, from the bundle's page in the console or through the link the model is given the first time it tries.

The consent screen says Artific: the application is this deployment's, registered once by its operator against Microsoft Entra as a multi-tenant application, and no organisation registers one of its own.

Before it works¶

Your administrator has to allow both hosts the bundle dials in the key's own egress policy:

graph.microsoft.com — every mail, calendar, file and Teams call;
login.microsoftonline.com — where a person signs in and where the code is exchanged for a token.

Your own Microsoft 365 tenant's admin may also need to consent once for the whole tenant before its first person can sign in, depending on how your tenant's own admin-consent policy is set for third-party multi-tenant applications; a person who is refused consent is told to ask their admin.

If the operator has not registered the Artific application at Microsoft Entra yet, the install waits: the bundle sits at needs configuration and names what it is waiting for.

The seven tools¶

Tool	Ask it for	Give it
`api__microsoft-list-mail`	recent mail	nothing required; an OData `$filter` narrows it
`api__microsoft-send-mail`	sending a mail	a recipient, a subject and a body
`api__microsoft-list-events`	upcoming calendar events	nothing required
`api__microsoft-create-event`	a new calendar event	a subject, a start and end time and a timezone
`api__microsoft-search-drive`	matching OneDrive files	a search text
`api__microsoft-list-teams-channels`	one team's channels	the team's id
`api__microsoft-list-channel-messages`	one channel's recent messages	the team's id and the channel's id

Good to know¶

Verified 2026-09-24 on learn.microsoft.com: graph.microsoft.com/v1.0 is Graph's stable surface, and the authorization code flow runs at login.microsoftonline.com/{tenant}/oauth2/v2.0/{authorize,token}; the Artific application registers with tenant organizations, so any work or school account may sign in.
Delegated scopes the application asks for: offline_access, Mail.Read, Mail.Send, Calendars.ReadWrite, Files.Read, Channel.ReadBasic.All, ChannelMessage.Read.All. A tool refused for a missing scope names it.
A calendar event's start and end are written without a UTC offset, paired with an explicit timezone name — never assume a person's timezone is UTC.
The mark: this bundle's card still uses Artific's own placeholder. Microsoft's own third-party logo usage guidance requires a licence in most cases and approval from a Microsoft business contact where none applies, neither of which this deployment has (checked 2026-09-24).