Overview
Outlook tools let your agents work with your Microsoft 365 mailbox and calendar. Agents can read messages and their full body, browse the folder hierarchy, download attachments, create and delete drafts, send mail, move messages into folders, manage contacts, and create or update calendar events. This document covers the available tools, setup, authentication, and the scopes Dust requests.This tool uses personal credentials. Each user authenticates with their
own Microsoft account, so an agent only ever sees what that user can see.
Outlook Mail can also be installed with workspace credentials for
platform-level automations; Outlook Calendar is personal-credentials only.
Admin: Setup in Dust
The setup process requires a Microsoft Entra ID admin (‘privileged role administrator’ or ‘application administrator’) who is also a Dust admin. This ensures full access to the necessary permissions.- Under Spaces → Tools, select
Add Tools, then selectOutlook. - Review the permissions. Each tool action can be set to one of four stake levels: high (always ask for confirmation), medium (let users save a confirmation for a specific input), low (users can disable confirmations entirely), or never ask (runs automatically) from the “Available tools” settings.
- On the first connection, tick Consent on behalf of your organization.
Usage
After admin setup, the Outlook tool can be added to an agent by selecting it from the agent builder. They require no additional configuration.Available Tools
Outlook Mail
Outlook Calendar
Permissions needed
Dust requests delegated permissions, so a user can never do more through Dust than they can do in Outlook directly.Outlook Mail
There is no read-only Outlook Mail setup.
Mail.ReadWrite is required for the
tool to function, and Mail.ReadWrite.Shared implies it.Mail.Send is optional. To leave it out, untick it under Customize scopes
when you add the tool. Untick Mail.Send.Shared too, since it implies
Mail.Send. Without Mail.Send, agents can still read mail and create
drafts, but they can’t send. If an agent tries to send, it’s told to create a
draft instead, so the user can send it from Outlook.You can also control what agents are allowed to do with the per-tool stake
settings in the agent builder: leave Send Mail as high stake, or simply do not
add it to the agent.Outlook Calendar
Permissions needed
If your users struggle with approval requirements, you can go in the Azure Admin portal and grant permissions at admin level. For that go to the Azure Admin Portal, then Enterprise applications (you can follow this link instead), then Dust - Tools, then Permissions and click the Grant admin consent blue button. Still not working? Try this other process:- Go to this link
- Click on “All (preview)”
- Click on the “Dust - Tools” app
- Click “Review permissions and consent” (or equivalent in your language) in the right panel
Troubleshooting
Outlook tools fail while the tool shows Active
In Spaces → Tools, Active means the tool is set up with a Microsoft connection. It doesn’t check each user’s own connection. In the same way, Connected in a user’s Tools list only means they connected once. A user’s connection can stop working while both still show. The most common cause is a Microsoft Entra ID Conditional Access policy, such as one that requires a compliant device or a trusted location. Conditional Access applies each time Dust renews a user’s access in the background, not only when they first connect. If a policy blocks Dust, the renewal fails with errorAADSTS53003 and Outlook tool calls fail.
To fix it, a Microsoft Entra ID admin should:
- In Entra ID, open Sign-in logs, then the Non-interactive user
sign-ins tab. Filter on the Dust - Tools application and look for
error
AADSTS53003. The sign-in details show which Conditional Access policy blocked it. - Update that policy so it allows Dust - Tools, or exclude the app from it.
- Ask the affected users to reconnect: in Dust, open Tools from their user menu, click … next to Outlook, select Disconnect, then click Connect.