
Managing Microsoft Copilot users means deciding who gets access to a license, which settings and agents each person needs, and what happens to both when an employee changes jobs or leaves. Microsoft 365 Copilot for Business and Enterprise plans come with admin controls for each of those decisions in the M365 admin center, from licensing recommendations and group assignment to agent approvals and ownership transfers. Licenses still assigned to departed employees and agents left without an owner pile up when nobody tracks those changes after the first Copilot seats go live.
Here are nine steps to manage Microsoft 365 Copilot users as your business adds, moves and offboards employees:
Limit Who Has Admin Access in Copilot
AI Administrator permissions cover day-to-day management of Microsoft Copilot settings, which keeps routine Copilot changes away from Global Administrator accounts. Global Reader accounts see those same settings in read-only form, while group license assignment requires at least License Administrator, Groups Administrator or User Administrator permissions. Only Global Administrators and AI Administrators hold permission to approve agent requests and assign agent ownership across your entire tenant.
The Microsoft 365 Admin agent comes preinstalled in Copilot Chat for every M365 admin at no added license cost and handles Copilot license assignments, readiness checks and pending license requests through plain-language prompts. Each change the agent proposes waits for admin confirmation and appears in the same M365 admin center, Microsoft Entra and Teams audit logs as a manual change. Global and AI Administrators decide whether to block the agent or limit it to specific users and groups through the agent registry.
Choose Who Gets Copilot First
The Microsoft Copilot readiness report in the M365 admin center counts the users who hold prerequisite licenses, run an eligible update channel and already have a Copilot license assigned. Businesses that buy Copilot licenses also get a suggested candidate column, which flags the top 25% of unlicensed users each week based on 28 days of Teams, Outlook and Office document activity. Usernames stay hidden until an admin turns on user details, and the data is intended for license and rollout planning instead of employee performance evaluations.
Suggested candidates fit the pilot phase of a Copilot rollout, where a small group of heavy M365 users across teams receives licenses first and later helps peers as champions. Configuring Copilot settings for that pilot group before anyone else surfaces tenant-specific issues early, and licenses then expand to the rest of your business with oversharing controls and sensitivity labels still in place.
Each user needs a Microsoft Entra ID work or school account, a qualifying base license and an Exchange Online primary mailbox for mailbox-grounded features. The Copilot License Details diagnostic checks one account at a time against those prerequisites before you assign that user a Copilot seat. Guests and other cross-tenant users fall outside Copilot license assignment entirely, which limits seats to accounts in your own Microsoft Entra ID directory.
Assign Microsoft 365 Copilot Licenses by Group
Admins assign seats from your Microsoft 365 Copilot subscription under Billing > Licenses in the M365 admin center, either to individual users or to groups, and reassign those licenses when job duties change. Group-based licensing works with security groups, mail-enabled groups and Microsoft 365 groups, though it skips nested groups and licenses only members of the first-level group. Moving someone between licensed groups means adding them to the new group before removing them from the old one, since reversing that order leaves the user unlicensed until processing finishes.
Copilot settings include a self-service purchase control that allows trials and purchases, allows trials only or blocks employees from buying their own seats. Turning self-service purchases off sends license requests to the Requests tab under Billing > Licenses, where admins approve users directly into a licensed security group. Copilot takes up to 24 hours to appear in Word, Excel and other M365 apps after a license is assigned, and users may need to restart or refresh the app.
Control Copilot Access by User and Group
Copilot settings live under Copilot > Settings in the M365 admin center, split into user access, data access, Copilot actions and other settings, with some controls opening the Teams, Edge or Microsoft Purview admin centers. Admins restrict access to third-party artificial intelligence providers, including Anthropic models, to named users, security groups and nested groups, with up to 999 assignments per provider.
Conditional Access policies apply to Copilot sessions through the same Microsoft Entra sign-in that covers other M365 apps, and every Business plan supports multifactor authentication enforcement for Copilot users. Data loss prevention policies for the Microsoft 365 Copilot location in Microsoft Purview keep labeled files and emails out of the summaries Copilot writes for your users. Changes to those policies take up to four hours to reach Copilot users after an admin saves them.
Users without a Copilot license still open Copilot Chat through an eligible M365 subscription, and the web version stays available to them even after admins remove it from app navigation. Keeping the Microsoft Copilot app away from unlicensed users means limiting installation to a group that holds only licensed users and applying Teams app permission policies to the Teams version. A custom link in Copilot settings sends blocked users to your company AI policy when they try to open the app.
Pay-as-you-go billing for Copilot Chat and SharePoint agents runs through billing policies tied to an Azure subscription, and each policy covers only the users or groups added to it. Each tenant holds up to 50 billing policies, letting admins separate departments or pilot groups that use metered agents from everyone else. Budgets on those policies trigger email alerts as spending nears the limit, though usage continues past the budget and shows up in the Copilot Credits report.
Govern Agent Access and Sharing
Agent settings and agent lifecycle actions in the M365 admin center give your AI and Global Administrators the following controls over the agents your Microsoft 365 Copilot users run:
- User Access – Agent settings let all users, no users or only specific users and groups use agents, with all users as the default.
- Agent Sources – Separate settings allow or block agents built by Microsoft, by your own developers or by external publishers from appearing in the Agent Store.
- Sharing – A sharing control limits broad sharing of agents built in Agent Builder, though employees still share agents directly with individual colleagues when broad sharing is off.
- Activation Requests – Requests to activate an agent wait for an AI Administrator to check its data sources, tools and permissions and choose which users or groups receive it.
- Block and Delete – Admins install an agent for selected groups, block it across the tenant or soft delete it with 30 days to restore it.
Businesses licensed for Microsoft 365 E7 also receive access to Agent 365, which adds monitoring, access policies and audit trails for agents from Microsoft, partners and your own teams.
Onboard Users with Policy and Training
Assigning a Copilot license sends an automatic welcome email that points each new user to Microsoft help and learning content for Copilot. Admins schedule their own adoption, onboarding or training notices through the Microsoft Copilot setup guide in the M365 admin center, reaching selected recipients through Windows notifications, the taskbar and similar spots. Send your own welcome email from IT that explains what Copilot does, where to find training and where to read your artificial intelligence usage policy, starting from the onboarding email template for IT admins.
That usage policy should name the client records, personal data and outside AI tools employees must keep out of prompts, since Copilot draws on email, files, meetings and chats a user already has permission to open. Microsoft also publishes a Success Kit, QuickStart training sessions and an in-product onboarding walkthrough that varies by license type. Turning on feedback settings for Microsoft 365 Apps through cloud policy lets users rate Copilot responses and attach logs and screenshots to their feedback.
Reclaim Idle Copilot Licenses with Usage Data
The Microsoft Copilot usage report compares enabled and active users over 7, 28, 90 or 180 days and lists a last activity date for each user, both overall and by app. Exporting that table and filtering for blank or old activity dates produces a short list of seats to reclaim ahead of your next renewal or license purchase. Check two exceptions before removing a license, since blank dates also appear for users who tried Copilot only within 24 hours of assignment or whose desktop apps delayed their uploads.
This feature can also be leveraged to measure the impact of each license per seat and identify idle licenses from duplicates, empty seats, etc. The readiness report also provides suggested candidates for usage, which together can give you a list of users to receive any Copilot license freed up.
Offboard Copilot Users and Their Agents
The process for removing a former employee runs from blocking sign-in and saving the mailbox to removing the license and deleting the account, with email and OneDrive content held for 30 days after deletion. Microsoft 365 Copilot users add three items to that offboarding checklist for your IT staff to handle before the account is deleted:
- License – Removing the Copilot license frees the seat for reassignment, and the usage report keeps the departed user listed for up to 180 days after removal.
- Copilot Interactions – Prompts and responses sit in a hidden folder in the user’s mailbox, and those under a retention policy move to an inactive mailbox when the account is deleted. eDiscovery searches them under the retention policies placed on that user before the mailbox went inactive.
- Agent Ownership – Admins assign a new owner to agents the employee built in Agent Builder or Copilot Studio, and the previous owner loses all access to those agents, including read access.
Audit SharePoint Access After Rollout
Assigning even one Microsoft 365 Copilot license gives your SharePoint admins these SharePoint Advanced Management features for checking site access after rollout:
- Site Access Review – SharePoint admins hand checks on overshared sites to the owners of those sites through data access governance reports.
- Site Ownership Policy – Sites that fall below the minimum number of owners you set trigger automated notifications to the people responsible for them.
- Inactive Sites Policy – SharePoint detects sites with no recent activity and sends email notifications to the owners of each inactive site.
- Restricted Content Discovery – Specific sites stay out of Copilot and search results unless a user recently interacted with the content on them.
Microsoft Entra access reviews cover group membership as well, though every employee who approves access or has access checked needs a Microsoft Entra ID Governance subscription.
Manage Your Microsoft 365 Copilot License with SWK Technologies
Every hire, job change and departure shifts who should hold a Copilot license and who owns the agents your teams use, which keeps Copilot user management on your IT staff’s list long after setup. As a Microsoft Partner, SWK Technologies will help you match Copilot seats to the people who need them most and manage Purview governance as adoption grows, alongside the IT staff you already have.
Contact SWK here to start with a free Microsoft 365 assessment and see where your Copilot seats and agents stand today.
