Building Agents That Work is for information workers, managers, analysts, and team leads who want to build useful agents in Microsoft 365 Copilot without turning the whole thing into a software project. It is written for people who need agents to do real work more than once, not just survive one impressive test run.
This edition uses M365 Copilot and Agent Builder, and it teaches the subject by having the reader build as they go. It starts with the problem many people hit early: a role prompt or rough instruction block looks fine at first, then starts slipping. The answer is not endless prompt tweaking. The book shows how to give the agent a stronger structure, separate standing rules from task-specific guidance, organize supporting files, route work more deliberately, and test results so the system holds up better over time.
The material builds in sequence. Readers start with how an agent's instructions actually work, then move through starter patterns, a worked example, and the shift from a single-file build to a modular file set. You build and test as you go, which means the ideas do not stay abstract for long.
There is also a companion repository with starter and example files. That matters because the book is meant to leave the reader with something they can use, not just something they understand. By the end, readers come away with a mental model for how dependable agents are put together, along with starter materials they can adapt to their own work in communication, analysis, planning, operations, and other knowledge-work settings.
This is not a coding manual, a hype book, or a bag of prompt tricks. It is a practical learning guide for people who want to build, test, and refine Copilot agents, then leave with a framework and a set of starting files they can actually use.
About the Author :
Jeff Jones is an engineer by training and a researcher by temperament. He has always been curious about how things work, why they break, and what makes them better. He reads widely, keeps learning, and likes hard problems. That shows up in how he writes about AI: from an operator's point of view, with attention to complex systems, failure modes, and the difference between what a tool promises and what happens when real people use it.Jeff grew up in Indiana in a supportive family and was drawn early to math and computers. He studied computer engineering at Purdue, then took his first job after college at a federally funded research center in Los Angeles. While working in cybersecurity, he earned a master's degree in computer engineering from the University of Southern California.Jeff later joined Trusted Information Systems, where he worked on security research and was part of the team that developed one of the first Internet firewalls. After the company was acquired by McAfee, he continued that work before joining Microsoft in 2002, where he still works today in cybersecurity and crisis communications. Across the years, the part he has enjoyed most is learning something difficult and then explaining it clearly enough for other people to use.
