Workativ Logo
Contact us
Microsoft 365 formerly Office 365
Microsoft 365 AI agent that assigns licenses and hands over a leaver's mailbox from chat.

Microsoft 365 AI agent that assigns licenses
and hands over a leaver's mailbox from chat.

The admin center can assign a license, but it does not decide who gets a Copilot seat or what happens to a mailbox before Microsoft's 30-day clock runs out. Workativ asks the right person in Teams or Slack and makes the change in order.

IT Teams of all sizes trusts Workativ AI to automate IT Operations & Support

Companies using Workativ: GoTo, Learnpath, MERIT, Lagardère, Kraft Heinz
Microsoft 365 AI agent what the admin center leaves for the helpdesk

Licenses and mailboxes carry deadlines
and costs that the admin center does not track for you.

Seats stay assigned </br> after people leave

Seats stay assigned
after people leave

A removed license keeps costing until someone reclaims the seat, and the mailbox needs a decision first.

Copilot seats go to </br> whoever asked first

Copilot seats go to
whoever asked first

With no usage data in front of IT, seats sit with people who stopped using Copilot.

A leaver's mailbox runs </br> on a 30-day clock

A leaver's mailbox runs
on a 30-day clock

Mail and calendar are kept 30 days once the license is removed, and the handover has to happen before then.

Microsoft 365 AI agent IT self-service in Teams and Slack

A license or mailbox request is raised in Teams or Slack,
and the person who decides it answers in the same place.

Workativ checks the request against your pools and rules, asks the person who owns the decision, and makes the change in Microsoft 365. Anything it cannot decide goes to IT with the chat attached.

A Visio request is checked against the plan and the department pool, then assigned once the manager approves.

The pool is checked first, so requests beyond it go to IT instead of failing silently

The approval is stored with the license record

Learn more →
License request
Microsoft 365 AI agent workflow automation

Each HR event runs its Microsoft 365 changes
in the order Microsoft's own guidance recommends.

An event arrives from HR, a schedule or a chat request. Workativ works through the tenant step by step and reports back in Teams or Slack.

A new hire's license set, mailbox and team memberships are in place before the start date, from one HR record.

A sales hire and an engineer get different license sets, because the set follows the role

Department team and distribution list memberships are added in the same run

A first-day message waits in Teams

Learn more →
New hire
Microsoft 365 AI agent customer proof

NMDC Group works in Microsoft Teams, and 78%
of its IT tickets are closed without an engineer.

78%

Tickets that never
reach an engineer

Password resets, access requests, and incident triage resolved in chat without a technician, across 6,000 tickets a month.

$37K+

L1 cost removed
each month

Roughly 390 hours a month of engineer time on L0 and L1 requests has been freed up.

"Workativ has been with us every step of the way. From our first IT support use case to HR, and soon Procurement. The platform grows with us, and so does the team behind it. It's rare to find a solution that's both powerful and genuinely easy to manage."

NMDC Group

Imran Abid

IT Operations Leader · NMDC Group

Imran Abid
How to deploy

Deploy a Microsoft 365 AI agent in three steps.

Connect Microsoft 365
Platform

Licensing rules stay in Microsoft 365, and
Workativ handles the requests that fall outside them.

Build without code and answer from your own handbook, with every action tied to the admin role that performs it.

No-Code Builder for Your Microsoft 365 AI Agent

No-Code Builder for Your Microsoft 365 AI Agent

Microsoft 365 license assignment pools, approvers and permission pairs are configured on one screen

Requests that fall outside a pool go to IT with the thread attached

Office 365 AI agent · Microsoft 365 Slack integration · Microsoft 365 Teams integration · no-code Microsoft 365 AI agent

What the admin center handles on its own, and what still waits for a person.

Microsoft's own tooling covers group-based licensing, usage reports and a published offboarding checklist. What it leaves out is the approval step and the order of operations, and anything outside Microsoft.

What matters to IT
Workativ HR chatbot
msOffice365
Microsoft 365 license assignment
Request, approval and assignment in one thread
Request, approval and assignment in one thread
Admin center or group-based licensing, by a License, User or Groups Administrator
Rule-based licensing
Left to group-based licensing; the agent handles exceptions
Left to group-based licensing; the agent handles exceptions
Group-based licensing assigns by group membership
Copilot seat control
Request with a stated use, then a monthly review with the manager
Request with a stated use, then a monthly review with the manager
Usage report and audit data, with reclaiming done by an admin or a script
Leaver mailbox and OneDrive
Steps run in Microsoft's order, with the manager given access
Steps run in Microsoft's order, with the manager given access
A checklist the admin works through by hand
Shared mailbox permissions
Full Access and Send As set together after the owner approves
Full Access and Send As set together after the owner approves
Exchange admin center or PowerShell, with Send on Behalf set by PowerShell only
Tasks outside Microsoft
100+ connectors, including Jira and ServiceNow tasks
100+ connectors, including Jira and ServiceNow tasks
Power Automate or Copilot Studio, built per scenario
HR inbox problem same questions, 40 times a week

Tenants where group rules decide every license, Copilot is rare, and offboarding already follows Microsoft's checklist may not need more than the admin center. The agent helps once exceptions start piling up, or when leaver mailboxes are being handled by whoever has time. It runs beside Microsoft 365, which stays the system of record. For a side-by-side with Microsoft's own assistant, see the Microsoft Copilot comparison.

Microsoft 365 automation · Microsoft 365 Slack integration · Microsoft 365 Teams integration

The systems that sit outside Microsoft 365, connected to it.

Licenses, mailboxes and OneDrive stay in Microsoft 365. A device task or an HR lookup is handed over inside the same thread.

Security & Compliance

Enterprise-grade security for IT environments
where data protection is non-negotiable.

Workativ HR AI assistant security certifications SOC 2 Type II, ISO 27001, GDPR, HIPAA compliant
Immutable audit trail
Role-based access controls
Secrets & token masking
Prompt injection protection
SSO & MFA
SIEM integration

Microsoft 365
AI agent for Teams and Slack.

Handle license requests and leaver handovers in chat, and keep Copilot seats in check. Live in 3–5 days.

Frequently
asked questions

Frequently asked questions about
the Microsoft 365 AI agent

What is a Microsoft 365 AI agent?

A Microsoft 365 AI agent (many admins still search for an Office 365 AI agent) lets people raise tenant requests in Teams or Slack and has them done in Microsoft 365: license assignment, Copilot seats, shared mailbox permissions, OneDrive handovers and leaver clean-up. It asks the right approver, works under the Microsoft 365 admin roles you assign, and replies in the thread where the request began. Workativ's version also answers how-to questions from your IT handbook and passes a case to a person when it needs a decision.

Is Office 365 the same as Microsoft 365?

For admin work, yes. Microsoft folded the Office 365 brand into Microsoft 365, and the admin console is the Microsoft 365 admin center. Many teams still say Office 365, so an Office 365 AI agent and a Microsoft 365 AI agent point at the same tenant. If you are looking at Workativ's earlier Office 365 chatbot page, it covers the same service with a mailbox and distribution-list focus.

What can the Microsoft 365 AI agent do from chat?

Microsoft 365 license assignment and removal, Copilot seat requests and reclaiming, shared mailbox permissions, distribution list and group membership, OneDrive access for managers, and a leaver checklist run in the right order. Sign-in problems such as resets and lockouts belong to the Entra ID side, and Workativ covers those on its Entra page.

How does Microsoft 365 license assignment work through the AI agent?

A user asks for a license in Teams or Slack, the agent checks the plan and the pool, and the approver confirms in the thread. Workativ then assigns the license in Microsoft 365. Microsoft says assigning licenses takes at least a Groups Administrator, License Administrator or User Administrator role, and the agent runs under one of them. Rule-based licensing can stay with group-based licensing, and the agent handles the exceptions.

How are Microsoft 365 Copilot license requests and unused seats handled?

A Microsoft 365 Copilot license request records the use case and goes to an approver before a seat is assigned. Each month the agent can compare seat holders against Copilot activity from the usage report and audit log, then ask each manager whether to keep or release a flagged seat. Microsoft's usage report is thin on how heavily Copilot is used, so the activity window and the rule for flagging a seat are yours to set.

What happens to a leaver's mailbox and OneDrive?

Microsoft's offboarding order is to block sign-in, save or hand over the mailbox, convert it to a shared mailbox or forward it, give someone access to OneDrive, then remove the license and delete the account. After a license is removed, mail, contacts and calendar are kept for 30 days and then deleted permanently. The agent runs Microsoft 365 offboarding in that order. Accounts synced from on-premises Active Directory have to be deleted in the local directory instead.

When does a shared mailbox need a license?

Shared mailboxes usually don't need one. Microsoft says an Exchange Online Plan 2 license is required when the mailbox holds more than 50 GB, uses in-place archiving, or is on litigation hold. New shared mailboxes also have sign-in blocked by default. A converted leaver mailbox is therefore often free to keep, which returns the seat to your pool.

How is this different from Microsoft 365 Copilot and Copilot agents?

Copilot helps people work with their own Microsoft 365 content, and its agents are built per task. The Workativ agent is an IT helpdesk agent: it performs license, mailbox and OneDrive changes with an approval trail, and it reaches systems outside Microsoft such as Jira or ServiceNow. Many tenants run both.

Do I need the Entra ID agent as well?

They split the work. The Entra ID agent handles sign-in: password resets, lockouts, Temporary Access Passes and group access. The Microsoft 365 agent handles what the account is entitled to once it exists: licenses, mailboxes, OneDrive and Copilot seats. You can start with either and add the other later.

How long does deployment take?

Expect three to five days from start to live. The effort goes into registering the app with the Graph and Exchange Online permissions you approve, writing down license pools and approvers, and loading the handbook. License requests and the leaver checklist go live first, and Copilot seat control comes once usage data is flowing.

Which admin roles does the Microsoft 365 AI agent need?

One role per kind of action. Licensing runs under License Administrator or User Administrator, mailbox actions need an Exchange admin role, and OneDrive access needs the role that governs SharePoint and OneDrive. Turn actions on one at a time, and give a role more reach only when the next action needs it. Directory-wide admin tasks are never run from chat.

Which chat platforms does it support, and where is the audit trail?

Both platforms get the same actions and approval rules, so a manager in either can sign off. Workativ keeps its own record of each request, who approved it, what changed and when, and the Microsoft Purview audit log holds the matching Microsoft 365 entry. The Workativ record can also be sent to your SIEM.