MorningAI brings Outlook and client files into one agent task

A sponsor’s revised brief is in an attachment, the old numbers are in an email thread, and the next call is somewhere in your calendar. MorningAI’s October 19 Microsoft 365 connector puts those sources within reach of its Agent. The useful change is less copying between windows; approval still needs a clear place in the workflow. Dated product update.

A draft is a useful stopping point

The connector can search Outlook threads and attachments, consult calendars, and find files in OneDrive and SharePoint. Each teammate connects their own account; a company may require IT approval first. MorningAI’s example leaves an approved reply in Outlook for the user to send, then books a proposed meeting after approval. These are app capabilities, not a new Microsoft model release.

For a creator, a sensible first task would be to compare a sponsor’s latest brief with the deliverables in the email thread and prepare a reply listing any mismatch. This is a proposed exercise, not a workflow we ran. Ask for the source document and relevant passage beside each changed deliverable. Then inspect the actual draft’s recipients and attachments in Outlook. If the evidence is incomplete, keep the question in the reply rather than letting a confident summary become a commitment.

Put a spending boundary around the task

The same release adds per-task credit visibility and monthly limits. Administrators can set monthly limits that pause work when reached. Auto-reload can purchase more credits and resume paused work. A usage display alone therefore does not establish a spending cap if automatic purchases remain enabled. Credit-control sections.

The announcement does not give an exact connector price or universal plan entitlement. Check those in your account before connecting. Start with one brief and one draft; compare the result with the source yourself. Our guide to models, apps and agents explains why a connected app’s permissions matter as much as its selected model.