
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.
A removed license keeps costing until someone reclaims the seat, and the mailbox needs a decision first.
With no usage data in front of IT, seats sit with people who stopped using Copilot.
Mail and calendar are kept 30 days once the license is removed, and the handover has to happen before then.
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.
The pool is checked first, so requests beyond it go to IT instead of failing silently
The approval is stored with the license record

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 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

"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."
IT Operations Leader · NMDC Group


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

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
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 | ||
|---|---|---|
Microsoft 365 license assignment | Admin center or group-based licensing, by a License, User or Groups Administrator | |
Rule-based licensing | Group-based licensing assigns by group membership | |
Copilot seat control | Usage report and audit data, with reclaiming done by an admin or a script | |
Leaver mailbox and OneDrive | A checklist the admin works through by hand | |
Shared mailbox permissions | Exchange admin center or PowerShell, with Send on Behalf set by PowerShell only | |
Tasks outside Microsoft | Power Automate or Copilot Studio, built per scenario |
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.
Licenses, mailboxes and OneDrive stay in Microsoft 365. A device task or an HR lookup is handed over inside the same thread.

Handle license requests and leaver handovers in chat, and keep Copilot seats in check. Live in 3–5 days.
Frequently asked questions about the 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.