Lakshya

Book

Microsoft 365 & Copilot in the Enterprise

How a Microsoft 365 estate is actually built, licensed and governed — tenant, identity, workloads, devices, Purview and Defender, every licence tier with current prices, and then Copilot and Copilot Studio from the request path to the evidence on whether they deliver.

The corpus behind this site mentions Microsoft Entra ID in 8.1% of 3,010 job descriptions — a real hiring market — but Microsoft 365 itself in 0.7%, Intune and Purview in about 0.1% each, and Microsoft 365 Copilot and Copilot Studio in none at all. Chapter 1 states that up front. Written from Microsoft Learn, official pricing and licensing pages, dated Microsoft announcements, and independent evaluations — every price observed August 2026 and dated as such. Two claims are flagged in-text as unresolved because live Microsoft pages contradict each other, and one widely-repeated statistic is identified as a citation-chain error rather than repeated.

CHAPTER 1 The tenant, and the decision you cannot undo Everything in Microsoft 365 hangs off one object. Understanding it properly makes the rest of the estate legible. CHAPTER 2 Identity — the spine everything else hangs on Directory sync, the three ways to authenticate, conditional access, and precisely which licence tier unlocks what. CHAPTER 3 The workloads, and what actually breaks Exchange, SharePoint, OneDrive and Teams — what each replaces, and the specific failure that catches each migration. CHAPTER 4 Devices, and getting software onto them Intune, Autopilot and update channels — how a laptop goes from a sealed box to a managed corporate machine without IT touching it. CHAPTER 5 Governance — Purview, Defender, and which licence buys what Two large product families with overlapping names, mapped to the tier that actually includes each capability. CHAPTER 6 Licensing — the part you actually came for Every tier, what each really includes, the Teams unbundling in all four of its acts, and the twelve months of changes that compound. CHAPTER 7 Microsoft 365 Copilot — how it actually works The request path, what the semantic index is, what happens to your data, and the three-tier structure most coverage still gets wrong. CHAPTER 8 Oversharing — the thing that actually stops deployments Copilot respects permissions perfectly. That is the problem, and two-thirds of organisations have delayed a rollout over it. CHAPTER 9 Copilot Studio — building your first agent What you actually construct, what it costs per interaction, and the billing rule that decides where you publish it. CHAPTER 10 Extending with code, and choosing your platform Declarative agents, Graph connectors, and a clear rule for when Copilot Studio is the wrong tool. CHAPTER 11 Does it actually work? The evidence, both ways Time savings are real and replicate. Whether they become productivity is genuinely unproven — and the best study says no. CHAPTER 12 The rollout, start to end What a real programme looks like in phases, and the four places it actually stalls — none of which are the configuration work.