Overview
The Microsoft 365 integration brings the power of your Microsoft productivity suite directly into Hatz. Once connected, you get a broad set of tools across Outlook email, Calendar, Contacts, Microsoft Teams, OneDrive, SharePoint, and Excel.
The Microsoft 365 integration uses an Enterprise Application in Microsoft with the necessary permissions to allow Hatz to interact with M365 data.
This is a per-user integration, meaning each user who wants to use Microsoft 365 tools needs to set up the integration.
The Microsoft 365 integration can read, search, and update supported Microsoft resources through the listed tools. It does not save generated files directly to a user's local computer path. For generated files, use the Hatz generated file card or an available Microsoft 365 export/save option.
For Users With the Old M365 Integration
Users who want to access the new tools must disconnect and reconnect the Microsoft 365 integration to obtain the updated permissions.
Steps:
Navigate to the Workshop tab and select Connections on the left
Select the gear icon on the existing Microsoft 365/Outlook integration and delete it
Reconnect using the updated Microsoft 365 integration
Data Safety and Destructive Actions
To keep your information safe, the integration is built around reading, finding, creating, and updating rather than bulk or irreversible removal. It will not delete your emails, OneDrive/SharePoint files, or Teams channels. Within a spreadsheet you are working in, the Excel tools can remove structural elements you ask to change (for example a worksheet, table, row, or column). Everything runs with your own Microsoft permissions and only in response to your instructions, so the integration can never do more than you are able to do yourself.
Common Questions and Troubleshooting
I am attempting to integrate Microsoft 365 and Hatz but I am getting a "Need admin approval" message
This screen is shown when a Global Admin in Microsoft has not configured the integration and granted admin consent
Please reach out to an administrator in your Microsoft 365 tenant and ask them to setup the integration
Once that has been done, try configuring the integration again
Does Hatz need all of the permissions shown when setting up the integration?
Hatz requests access to the permissions for the toolkits that are selected when setting up the integration
You can not select or deselect individual permissions scopes at the time of the integration but once it has been integrated you can edit the permissions within the Enterprise Application in Microsoft if you would like to make it less permissive
Outlook email tools are connected, but I cannot read or draft email
Admin consent and mailbox access are separate. Admin consent allows the Hatz application to request Microsoft permissions for the organization. Each user still needs to connect their own Microsoft 365 account, and Microsoft only returns mailbox data that connected user is allowed to access.
Reconnect Microsoft 365 and make sure the Outlook toolkit is selected during setup. The Outlook toolkit requests mail permissions such as Mail.Read, Mail.ReadWrite, and Mail.Send.
Confirm the signed-in Microsoft user has an active mailbox and can access the same mailbox directly in Outlook on the web. Hatz cannot use a user's connection to bypass Microsoft mailbox permissions.
If the user recently received a new mailbox license, role assignment, or admin consent grant, wait for Microsoft to apply the change, then disconnect and reconnect Microsoft 365 in Hatz.
Will all users have access to all of the data in Microsoft 365?
No - Users will only have access to the data that their user in Microsoft is able to access.
Can I send emails and create OneDrive or SharePoint files with this integration?
Email: the integration creates email and reply drafts (saved to your Drafts folder for you to review and send), and can attach files — but it does not send email on your behalf.
Files: you can create folders and move or copy existing files in OneDrive/SharePoint, but saving a brand-new generated file directly into OneDrive/SharePoint is not available yet. For generated files, use the Hatz generated file card.
Please add this as a feature request or upvote a current request on our Canny board: https://hatz-ai.canny.io/feature-requests
Why can't the assistant see a teammate's Teams status, or list a channel's members?
Reading another person's presence and listing the members of a channel require organization-wide Microsoft permissions that this integration does not request, so those specific actions are not available. You can still check and set your own status, and read and post messages in channels you belong to.
I just created a Teams channel, but updating it fails or says it cannot be found.
Newly created Teams channels take a short time for Microsoft to finish setting up. If an update right after creating the channel fails, wait a minute and try again.
I can't find a past meeting or its transcript.
Past meeting lookups cover roughly the last 90 days, so widen the time range if an older meeting is missing. A meeting's transcript only appears when transcription was turned on for that meeting and you have organizer-level access; otherwise the transcript list comes back empty.
I am not able to perform "X" action within Microsoft 365 through the integration.
This is more than likely due to that action not being supported as a tool for the integration.
Please add this as a feature request or upvote a current request on our Canny board: https://hatz-ai.canny.io/feature-requests
A Microsoft 365 tool shows up but is grayed out when I build an agent
Microsoft 365 is a per-user integration, so its tools stay grayed out in the agent builder until you connect Microsoft 365 with your own account. Select Connect on the tool to link your account, then add it to the agent.
Connecting Microsoft 365 for yourself does not connect it for other people who use the agent. Each user who runs the agent still needs to connect their own Microsoft 365 account, and they will only be able to use the Microsoft data their own account can access.
If the whole tools list is unavailable, check that the agent's selected model supports tools. A model that can't use tools will disable the tool picker.
A Microsoft 365 tool shows a "Locked" badge and I can't turn it on
A Locked badge means an administrator has turned off access to that integration at a higher level, so it can't be enabled where you are.
The lock message names who to contact: if it is locked by your organization, contact your administrator; if it is locked by your Managed Service Provider, contact your MSP administrator; if it is locked by platform-level policy, it is set for the whole platform and can't be changed in your own settings.
To unlock it, the administrator who controls that level re-enables access for the Microsoft 365 integration in their admin access settings. Once access is allowed again, the tool can be turned on.
My Microsoft 365 tools stop working partway through a long chat
Hatz normally refreshes your Microsoft session automatically in the background, so most long conversations keep working without any action from you.
The connection can drop mid-chat if Microsoft ends the session and it can't be renewed — most often after you change your Microsoft password, or an administrator revokes the app's consent or changes a Microsoft policy.
If Microsoft 365 tools start failing during an active chat, reconnect Microsoft 365 from the Workshop tab under Connections, then continue. If it keeps dropping, ask your Microsoft 365 administrator to confirm the integration's consent and any sign-in or session policies that may be ending the connection.
How do Microsoft 365 and SharePoint tools authenticate when an agent is triggered through the API?
When an agent runs through the API, its Microsoft 365 and SharePoint tools act as the user who owns the API key. There is no separate shared or service-account connection for API runs.
That means the API key's owner must have personally connected Microsoft 365 and keep the connection active, and the tools can only reach the Microsoft data that user's own account can access.
If the key owner has not connected Microsoft 365, or the connection has expired, the Microsoft 365 and SharePoint tools return an error asking to reconnect the account. Have the key owner connect or reconnect Microsoft 365 from the Workshop tab under Connections.