
Helping you and your company achieve more in Microsoft 365
In a recent YouTube tutorial, author Scott Brant demonstrates how to use Copilot Chat far more effectively than most users do. He argues that the key is a simple four-step framework that combines clear goals, relevant context, reliable sources, and a defined output format. Moreover, the video walks viewers through practical examples, showing how those steps map to everyday tasks in Microsoft 365. As a result, professionals can save time and produce more consistent results when they follow Brant’s guidance.
Brant also highlights newer tools that fit into that workflow, including an AI notepad called Granola and collaborative features in Copilot Notebooks. He demonstrates how the free version of Copilot Chat can connect to organizational files, analyze spreadsheets, and help with Outlook workflows. Consequently, the video is framed as a hands-on guide for people who already have access to Microsoft 365 but underuse its AI features. The presentation balances practical steps and feature demos to help viewers adopt these methods quickly.
Brant’s four-step formula—goal, context, source, format—serves as the backbone of the tutorial. First, he asks users to state the goal clearly so the AI understands the intended outcome, such as drafting an executive summary or listing open action items. Then, he recommends adding context like the audience, timeframe, or project name, because these details help Copilot produce a relevant answer. Next, he shows how to reference sources directly so that responses are grounded in actual files or meetings rather than vague web content.
Finally, Brant stresses specifying the output format so Copilot delivers ready-to-use content, for example a three-bullet summary or a table comparing options. He also encourages iteration, telling users to refine outputs with follow-up prompts rather than accepting the first draft. Together, these steps reduce the guesswork and make AI assistance more predictable. Therefore, users can apply the framework across tasks from reporting to scheduling meetings.
Brant demonstrates several immediate use cases to show how the framework works in practice. For instance, he uses Copilot Chat to analyze Excel workbooks, create charts, and generate executive summaries in minutes, which saves repetitive manual work. He also shows how Copilot can prioritize emails and schedule meetings inside Outlook, thereby cutting time spent triaging a busy inbox. In addition, he highlights collaborative capabilities where teams can bring project information together with Copilot Notebooks, making shared work more transparent and searchable.
Another practical tip in the video is to control sources using the built-in source management tools and direct references so the AI only uses allowed files and meetings. Brant briefly shows the AI notepad Granola as a companion for back-to-back meetings, but he frames it as an optional productivity layer rather than a necessary add-on. Overall, the demos emphasize small, repeatable patterns that professionals can adopt right away to boost efficiency.
While Brant praises the productivity gains, he also acknowledges tradeoffs that organizations must weigh. For example, granting Copilot access to corporate files improves accuracy but raises questions about governance and admin settings, so IT teams must set clear policies. Moreover, relying too heavily on AI drafts without review can introduce errors or tone mismatches, which means users should treat outputs as starting points rather than final artifacts. Consequently, balancing convenience with control becomes a core challenge for teams adopting Copilot broadly.
Brant also notes that some advanced features depend on subscription level and organizational configuration, which creates inequality in capability across users. In practice, organizations must decide whether to invest in higher-tier subscriptions and training to gain broader benefits. Therefore, leaders should weigh the cost of additional licenses against the time saved by power users who embrace the framework. This tradeoff shapes rollout strategies and expectations for measurable productivity improvements.
Brant offers actionable tips for overcoming common obstacles, such as vague prompts and insufficient context. He recommends avoiding pronouns and ambiguous time references, and instead using exact dates, names, or files so Copilot can ground its responses. He also advises iterating: follow-up prompts that correct scope or tone often produce much better results than rephrasing the original request. By emphasizing simple habits, he makes the learning curve less steep for busy users.
However, some challenges remain, including varied admin settings across organizations and occasional limitations in web-powered features. Users may find that certain direct references or time-bounded chat analyses require specific permissions to work. Still, Brant’s core message is optimistic: with a consistent prompt structure and a few governance guardrails, most teams can unlock significant value from Copilot Chat and related tools. In conclusion, his video offers a clear, practical roadmap for getting more from Microsoft 365 AI without overpromising instant results.
copilot chat tips, how to use copilot chat, microsoft copilot chat tutorial, copilot chat prompts and examples, advanced copilot chat techniques, copilot chat productivity hacks, copilot chat best practices, copilot chat settings and customization