If you run an executive’s calendar, a small office, an ops desk, or a 6-person admin team — and your company is on Microsoft 365 — Friday May 1, 2026 is the day the IT department launches something called Microsoft Agent 365 into your tenant. By Monday morning, your CFO will email the office manager asking what it costs and whether the company is paying for it. By Tuesday, your executive will ask whether they should be using it. By Thursday, three of your colleagues will have shared an “agent” inside a Teams chat that nobody on your team has approved.
Here’s the unfortunate part: nobody is going to brief you on this in non-IT language. The Microsoft Tech Community announcement is written for system admins. The SAMexpert pricing guide reads like a software-licensing exam. The Reddit threads are 95% IT consultants arguing about E5 versus E7. The audience that’s going to feel the change first — office managers, executive assistants, admin coordinators, ops managers — is the audience nobody is writing for. We searched X/Twitter for office-manager and EA voices on Agent 365 across the eight days before launch, and found zero. The conversation is happening in IT-buyer rooms, in CIO Slack channels, in LinkedIn newsletters for Microsoft MVPs. Not where you are.
This guide is the briefing IT will not write for you. Thirty minutes between now and Friday. By the end of it you’ll know what an “agent” actually is in plain English, what the $15 line item on next month’s invoice is for, what changes in your Microsoft 365 admin app on Monday morning, what to ask IT before they spin everything up, and which five recurring tasks you should hand the agent in week one — and which two you should keep for yourself.
What Agent 365 Actually Is (In 90 Seconds, No Jargon)
Microsoft 365 Copilot is the AI assistant your company has been rolling out for the last twelve to eighteen months — the one that summarizes meetings, drafts emails, searches across your SharePoint and OneDrive. That’s the assistant. Agent 365 is not an assistant. It’s the dashboard that tracks every assistant your company is running.
The Microsoft Learn documentation calls Agent 365 a “control plane for AI agents.” The plain-English version of that phrase is: it’s the tab inside the Microsoft 365 admin app that lists every AI helper anyone in your company has built or installed, who built them, what each one is allowed to do, and what data each one is allowed to touch. Think of it like the staff directory — except for AI helpers instead of people. Each agent gets an identity (like an employee badge), a manager (the human who created it), a job description (what it’s allowed to do), and a set of company rules it has to follow.
Why this matters for you: starting Monday, every Microsoft-built agent (the ones that ship with Copilot, the ones that ship with Sales Copilot or Service Copilot or any of Microsoft’s Copilot family), every agent your colleagues have built using the in-house Copilot Studio tool, and every external agent your IT department has approved — all of those will appear inside one inventory list. Your CFO is going to see that list. Your CEO is going to ask the EA whether the company really needs all of those things. The office manager is going to be the person who explains, in non-IT language, why each one is there.
Six things change on Monday morning, and only two of them require any action from you:
Things that change but don’t need action: A new menu page in the Microsoft 365 admin app called “Agents.” A new monthly line item on your Microsoft invoice. A small banner inside Microsoft Teams or Outlook that surfaces “agents you can use” alongside your usual Copilot prompts. Some new compliance reports your IT team will run quarterly.
Things that change and need action: First, somebody needs to walk into the Agent Settings panel and confirm what kinds of agents are allowed in the tenant. Second, somebody needs to know what to do when a colleague hands them an agent and says “can you check if this is approved?” Most of the time that “somebody” is going to default to whoever owns the day-to-day relationship with IT — which is to say, often, the office manager.
The Pricing in Plain Numbers
Two pricing options, both of which you’ll need to be able to explain when your finance team asks.
Option A — buy Agent 365 by itself: $15 per user per month, starting May 1, 2026, on top of whatever Microsoft 365 plan your company already has. This is the “we want agent governance, but we don’t want the full E7 bundle” path. If your company is on Microsoft 365 E5 (the higher-end enterprise plan most large organizations are on by 2026) or E3, this is the smaller commitment.
Option B — Microsoft 365 E7 Frontier Worker Suite: $99 per user per month, all-in. The E7 bundle includes Microsoft 365 E5 (the underlying enterprise productivity tier, around $60/user/month), Microsoft 365 Copilot ($30), the Entra Suite for advanced identity and access management ($12), and Agent 365 ($15). Add those numbers up à la carte: $117. The E7 bundle is positioned as roughly 15 percent cheaper than buying the four products separately, if you were going to buy all four. The additional Defender, Intune, and Purview features included in some E7 SKUs are the security and compliance pieces that justify the rest of the price gap.
The decision is genuinely one for the CIO, not the office manager — but the implication for you is worth knowing: if your company is buying E7, every employee with a license has access to Copilot, Agent 365, and all the rest. If your company is buying Agent 365 standalone, only specific licensed users will have agent governance applied. That distinction shows up in week one when somebody from the marketing team asks why their agent doesn’t show up in the inventory: the answer is probably that they don’t have the license tier the inventory feature requires.
The Frontier preview program — Microsoft’s early-access track that has been running for several months — gave participating organizations 25 free Agent 365 licenses through GA. If your IT team mentions a “Frontier” badge in the licenses page of the admin app, that’s what they’re referring to. After May 1, the 25 free seats roll into paid licenses unless your IT team explicitly opts out before the conversion deadline.
What You’ll Actually See in the Microsoft 365 Admin App on Monday
If you have access to the Microsoft 365 admin center (most office managers and senior EAs do, even if they rarely use it), here is the walkthrough. If you don’t have access — your first job is to ask IT whether you should, because much of the day-one configuration that affects shared agents in your team’s chats is set in panels you currently can’t see.
Open admin.microsoft.com. The left sidebar should now show two new things in the rollout-wave most tenants will see:
Settings → Integrated apps → Agents. This is the agent inventory. The columns are: agent name, creator, creation date, host products (so you’ll see “Teams” or “Outlook” or “SharePoint” depending on where the agent runs), and availability status. There are filters for agent status, owner, and product. The two actions IT will use are block (turn off an agent that’s misbehaving or non-compliant) and export (download the full list, usually for the quarterly governance review). You probably won’t be the person blocking agents — but you absolutely should know how to read this list, because when your CEO asks “how many AI agents does our company have?”, this is where the answer is.
Settings → Org settings → Agent settings. This is where the company-wide rules live. Three panels worth knowing:
- Allowed agent types — three checkboxes: “Allow apps and agents built by Microsoft,” “Allow apps and agents built by your organization,” and “Allow apps and agents built by external publishers.” Most companies will start by allowing the first two and disallowing the third for the first quarter, then opening up external publishers selectively.
- Templates — a “default template” with pre-configured security and compliance controls (it plugs into Entra for identity, Purview for compliance, and SharePoint for content access), plus the option to create custom templates for stricter rules (for example, “no external content sharing for any agent”).
- Who can access agents — three options: “all users” (default), “no users,” or “specific users/groups.” This is the panel your IT team will pre-configure to match your company’s sensitivity level. Don’t be surprised if it’s set to “specific users/groups” for the first sixty days while governance bedding-in happens.
Billing → Licenses. This is where you can confirm what the company is actually paying for. If you were in the Frontier program, expect a line that reads something like “25 Microsoft Agent 365 Frontier” — those are the preview licenses, converting to paid on May 1 unless IT ended the trial. The total Agent 365 line on May 1’s bill is the one your CFO is going to email about. The number to remember: $15/user × the number of licensed users.
If menu labels look slightly different in your tenant — Microsoft rolls out these UI changes in waves over four to six weeks — the conceptual layout is the same. Inventory (who’s running what), Settings (what’s allowed), Licenses (what the company is paying for).
The Four Questions to Walk Into IT With This Week
This is a four-question script. Print it. Send it as a Teams message. Walk into the IT director’s office with it Wednesday morning. The point is to get the answers in writing now, before May 1, so you’re not chasing them on Monday May 4 when your boss is asking.
Question 1: “Are we on Microsoft 365 E7, or buying Agent 365 standalone?” This determines who in the company has access to which features. Get the SKU name. If you’re given a different label (“Frontier Worker Suite,” “M365 Premium with Agents,” anything else), ask whether it includes Copilot and Entra Suite — those are the two add-ons that distinguish E7 from E5+Agent 365 standalone.
Question 2: “Who owns approving new agents inside the tenant?” There will be a person — probably the IT director, possibly the security lead, occasionally a “Copilot champion” the company has named. Their name is the name you’ll route every “can my team build this?” question to. If the answer is “we haven’t decided yet,” that’s the answer; flag that the office manager will be the funnel for those requests in the meantime, and offer to help draft a one-page request template for the team.
Question 3: “What data, calendars, files, and messages can the default agents access on Day 1?” The honest answer for most tenants is: agents inherit the permissions of the user who runs them, which means an agent your CEO uses can see anything your CEO can see. Confirm whether that’s the configuration in your tenant. Confirm whether shared agents (agents one colleague shares with another) inherit the original creator’s permissions or the runner’s permissions — that’s the question whose answer differs by tenant configuration and matters for confidentiality.
Question 4: “What’s the escalation path if an agent does something unexpected?” The classic example: an agent drafts a meeting note that summarizes a confidential conversation incorrectly, and a copy gets shared in Teams. Who do you tell? In what order? What happens to the audit log? IT may not have a polished answer yet — most companies are figuring this out in week two — but the written answer you get this week becomes the script for “what to do when something goes wrong” the moment something goes wrong.
Print the answers. Keep them in the same OneNote section as your standard “what to do when the printer breaks” runbook. They serve the same function.
The Five Tasks to Hand the Agent in Week One — and the Two to Keep
Once Agent 365 is live and your IT team has greenlit the default agents, here is the operational triage. These are the recurring tasks where a built-in or shared agent earns its $15/month many times over. The Microsoft Learn documentation lists Microsoft-built agents that ship across Copilot — the ones below are the ones that map best to the office-manager / EA workload.
Hand off 1 — The pre-meeting brief. A built-in agent reads the calendar invite, the attendees’ recent emails, the SharePoint folder linked in the invite, and the open Teams channels with those attendees, then assembles a one-page brief for your executive. You used to spend forty-five minutes a day on this for a busy executive. Hand it off, then spend ten minutes reviewing the brief and adding the human context the agent missed (the “she’s still upset about the budget call last Thursday” type of context).
Hand off 2 — The expense report pre-fill. A purpose-built agent (Microsoft has a sample one, or your IT team can adapt the template) reads receipts emailed to the executive, classifies them, drops them into the Concur or SAP Concur form, and surfaces the four it’s not sure about. The EA’s job becomes “review the four uncertainties,” not “type seventy entries.”
Hand off 3 — Calendar conflict resolution. This is where the agent earns its keep. When two meetings overlap, an agent can pull the original meeting purposes, the participants’ recent communication, and the executive’s stated priorities for the quarter, then propose three resolutions ranked by priority. You make the call; the agent does the legwork.
Hand off 4 — The “where is X?” lookup. A shared agent that searches across SharePoint, OneDrive, Teams, and email for a specific document, decision, or thread. (“Where is the September pricing memo?” “Which Teams chat had the discussion about the Q4 vendor switch?”) This is the task that, manually, takes fifteen to twenty minutes of clicking around. With an agent, thirty seconds.
Hand off 5 — Vendor status quick-pulls. For office managers responsible for outside vendor relationships, an agent can pull the latest invoice, the open ticket, the most recent email thread, and any contract changes — assembled into a one-paragraph status. Use it before any vendor call so you walk in with the full picture instead of the partial picture.
Keep for yourself — emotional context calls. When the executive’s daughter is sick, when there’s tension between two department heads, when somebody on the team just had a death in the family — these moments are not delegated to an agent. Ever. The agent doesn’t read tone, doesn’t hold confidences with judgment, doesn’t know which colleague is the right person to mention something to and which to absolutely not. That’s still the EA’s work. The point of handing off the brief, the expense report, the calendar resolution, the lookup, and the vendor pull is to free the time that gets spent reading those rooms correctly. Don’t let an agent do the part that requires being human.
Keep for yourself — the “do I trust this email?” judgment call. Phishing has gotten exponentially better in 2026. Vendor impersonation, executive impersonation, spoofed Microsoft alerts inside the company — they all exist, and they target office managers and EAs because we’re the people with calendar access and travel-booking authority. Agents will help you spot some patterns, but the judgment call about whether to act on something suspicious stays human. If anything, the existence of agents raises the bar on this — bad actors can now build agents too, and the social engineering will get more sophisticated, not less.
Three Traps to Avoid in Week One
Trap 1 — Saying yes to every “can you share that agent?” request. Inside the first week, several colleagues will share agents with you and ask you to share them onward. Some of those will be excellent. Some will be poorly built. Until the IT team has run a governance pass, route every share request through “let me check with IT first.” This sounds fussy. It is. It’s also the difference between you getting blamed for the agent that leaked the wrong information and you not getting blamed.
Trap 2 — Assuming the $15/user line is your problem to manage. It is not. The license decision belongs to IT and finance. The office manager’s job is to know the number, explain it cleanly when asked, and route any questions about license changes back to whoever owns the M365 contract. Do not get pulled into a “should we have fewer licenses next quarter” conversation without IT in the room.
Trap 3 — Letting the executive build their own shadow agents. Several executives — especially technically curious ones — will discover the Copilot Studio agent builder in week one and start building their own. Some of those will be brilliant. Some will accidentally connect to data they shouldn’t, with permissions they don’t fully understand. Your role is not to stop them; it’s to gently route them to IT before the agent is shared more widely. Phrasing that works: “That’s a great agent — IT is going to want to see this before we share it on the team. Let me forward it to them this morning.”
What This Means for Your Job (Honest Answer)
Microsoft Agent 365 is not your replacement. It’s not a calendar manager, an emotional reader of rooms, or a substitute for the institutional knowledge a seasoned EA carries. What it is, structurally, is a force multiplier — it makes the agents and assistants that already exist in the tenant more visible, more governable, and more useful, and it shifts the office manager / EA role one rung up the ladder: from “the person who does the thing” to “the person who decides what the thing should look like, then reviews the agent’s draft.” That’s a more senior version of the role. It’s also a version that’s harder to cut.
If you want to stay ahead of where the role is going, the practical posture for the next ninety days is: become the person on the team who understands what agents are running, who owns each one, what they’re configured to do, and where the trip-wires are. The CFO who emails about the $15 line item, the CEO who asks how many agents the company runs, the IT director who needs help routing “can my team build this?” requests — they all want one human being to be the quiet, calm, well-informed source of truth. That’s a position the office manager / EA is structurally well-suited to hold, and Agent 365 is the moment that position becomes more clearly defined.
Bottom Line
Agent 365 launches Friday, May 1, 2026. By Monday, you’ll have a new menu in the admin app, a new line on the invoice, and (probably) a colleague in a Teams chat sharing an agent. The thirty minutes you spend this week on the four questions to IT, the inventory walkthrough, and the five-task handoff list is the difference between Monday morning being a manageable transition and Monday morning being twelve interrupted “what is this?” conversations.
Microsoft is not going to brief you on this. IT might. If they don’t, this is the briefing.
