Introduction
It's two days before Relecloud's marketing organization gathers for a company-wide Copilot training session, and IT confirms every seat is covered. Monday morning, more than a quarter of that room opens Word, Excel, and Outlook—and Copilot simply isn't there.
Nothing flags this in advance. No errors. No warnings. You assign the license, and the confirmation screen says exactly what you want to see: All licenses assigned.
Group1, the security group covering marketing, has 40 direct members. It also contains Group2—a nested group of 15 more marketing employees, added last quarter for reasons nobody quite remembers.
The assignment succeeds. So what, exactly, does it succeed at—and why doesn't anything on your screen warn you it isn't everyone?
What you'll learn
- Assign Microsoft 365 licenses at scale using direct assignment, group-based licensing, and per-service-plan enablement.
- Verify a license assignment actually reaches everyone it should, and troubleshoot the failures—including nested groups—that hide behind a clean confirmation screen.
- Compare the four AI-service licenses (Microsoft 365 Copilot, Copilot Chat, Copilot Studio, and Agent 365) and match each to the usage pattern it fits.
- Recognize how Microsoft 365 billing is structured across billing accounts, billing profiles, and invoices.
- Configure a pay-as-you-go billing policy that meters AI-service consumption against an Azure subscription for a specific group of users.
By the end of this module, you can license and bill Microsoft 365 and AI services at scale, verify that those licenses resolve correctly, and choose the right access model and administrator role for the job.