Microsoft has officially launched a dedicated License Requests page inside the Microsoft 365 admin center, built specifically for handling Microsoft 365 Copilot access demands. The feature, tracked as Roadmap ID 561206 and marked as generally available in May 2026, gives IT administrators a single, purpose-built destination to discover, review, and act on employee requests for Copilot licenses. For organizations grappling with the messy intersection of AI enthusiasm and controlled deployment, this new page transforms a previously scattered process into a manageable administrative queue.
What Changed and When
The new License Requests page is accessible via the web‑based Microsoft 365 admin center, available to worldwide standard multi‑tenant organizations in both the Targeted Release and General Availability rings. Microsoft’s roadmap entry describes its goal plainly: to give admins a clearer place to see and manage Copilot license requests submitted by users. Instead of chasing individual emails or digging through the existing Licenses or Active users views, admins now have a single pane that collects all pending Copilot requests.
Crucially, the page doesn’t replace the existing license‑assignment surfaces. Admins can still assign Copilot from a user’s profile or through bulk operations. What’s new is a dedicated queue that turns a user’s request into a trackable item, complete with request date, requester identity, and status. It inherits from Microsoft 365’s existing self‑service license‑request infrastructure—requests are retained for 12 months, and admins can approve, reject, or partially approve them—but it applies that logic exclusively to Copilot, elevating it from a generic function to a governance checkpoint.
Why This Matters for IT and Business Leaders
A Copilot license request is rarely a simple matter of toggling a switch. Granting access to Microsoft 365 Copilot means giving an employee an AI assistant that can search across organizational content, generate documents, interact with connected apps, and become embedded in daily workflows. Because Copilot operates within the security boundaries of the user’s existing permissions, a poorly audited approval can expose sensitive data or enable actions that circumvent corporate policy.
The dedicated request page creates a governance boundary. Before a seat is assigned, admins can check:
- Is the requester’s role and department approved for Copilot?
- Has the required training or acceptable‑use agreement been completed?
- Does the available license inventory match the request volume, or will this trigger an unexpected purchase?
- Are the necessary Copilot app deployment settings (managed through Integrated Apps) already aligned so the user isn’t left with a license but no functional access?
Microsoft’s support documentation makes clear that a license alone doesn’t guarantee a usable Copilot experience. Admins must also manage app‑availability policies; blocking the Copilot app under Integrated Apps can disable access across Teams, Outlook, and the web. The License Requests page becomes the natural starting point to coordinate these three layers: approval, entitlement, and service availability.
How We Got Here: Licensing Meets AI Governance
For years, Microsoft’s licensing model in the admin center allowed requests for blocked self‑service purchases to appear under a generic Licenses area. That workflow (documented at learn.microsoft.com) was designed for any product, not just Copilot. But as Copilot adoption accelerated, the volume and complexity of requests quickly outgrew that catch‑all system. Managers were getting pings on Teams; end users were confused about eligibility; and IT found itself approving seats reactively, often without a consistent policy.
The move to a dedicated page reflects a broader reality: licensing for AI tools is inseparable from governance. Microsoft’s role‑based administration also came into sharper focus. The License Administrator role can assign and remove licenses, while the AI Administrator role manages Copilot configuration but cannot touch human‑user licensing. That separation means organizations must carefully delegate authority—a dedicated request queue makes it easier to split responsibility between the team that validates business need and the team that actually allocates a seat.
Your Action Plan: Setting Up Copilot License Requests the Right Way
The new page is an enabler, not a panacea. To use it effectively, admins should build a lightweight but deliberate operating process around it. Here’s a practical framework:
1. Define eligibility before demand spikes
Publish a short internal policy that identifies who qualifies for a Copilot license. Prioritize employees who routinely create content, analyze business data, or manage complex meetings. Defer departments that haven’t completed readiness activities or where use cases need additional security review. This prevents the “approve everything” default that leads to cost overruns and lackluster adoption.
2. Align request ownership with least privilege
Don’t give Global Admin access to everyone managing requests. Instead, assign the License Administrator role to those who will operate the new page, and partner with AI Administrators or department leaders for business‑case validation. Microsoft’s own guidance warns that a Global Admin has unrestricted tenant access; limiting the scope of request reviewers reduces risk.
3. Use group‑based licensing for scale
Instead of assigning seats one user at a time, map approved cohorts (departments, pilot groups) to security groups, and assign Copilot licenses to those groups. This makes later changes—adding a new hire, revoking access when a role changes—much simpler and leaves a clear audit trail.
4. Coordinate with app‑availability settings
Before marking a request “approved,” confirm that Copilot isn’t blocked under Integrated Apps for that user or group. A license without app access only generates support tickets. Create a checklist that covers licensing, application deployment, and any required Conditional Access or information‑barrier policies.
5. Track more than approvals
Turn the request queue into a measurement tool. Monitor metrics like:
- Requests per department
- Approval, rejection, and deferral rates
- Time from request to working access
- Number of users stuck in “approved but awaiting seat” limbo
- Post‑licensing adoption and support‑ticket volume
This data helps capacity planning and reveals where training or communication might be lacking.
6. Plan for capacity constraints
Microsoft’s subscription rules may limit how quickly you can reduce license counts after a purchase or renewal. A backlog of approved‑but‑unfulfilled requests is not just an annoyance; it’s a signal that either your purchasing cadence or your eligibility policy needs adjustment.
What to Watch Next
The dedicated License Requests page is a foundation. Expect Microsoft to layer on more automated routing, integration with ServiceNow and other ITSM tools, and richer analytics over time. For now, the key is to adopt the page not as a simple approval button but as a central control point for AI enablement. Organizations that pair it with clear policies, least‑privilege role assignments, and full‑stack access coordination will be far better positioned to scale Copilot responsibly.