The Copilot Briefing

Send us Fan MailMicrosoft is introducing more role-specific Copilot experiences, including a sales development agent designed to support outreach and prospect management. That potential comes with important questions about cost, grounding, voice, and autonomous communication.The main discussion focuses on a common AI implementation mistake: picking the product before understanding the problem. Copilot Studio, custom-coded agents, Microsoft Foundry, and other approaches each have a place, but none should be treated as the automatic answer. The better method is to assess value, friction, complexity, maintainability, and future growth, then select the simplest solution that properly addresses the need.Topics Covered• Microsoft’s role-specific Copilot agents • Sales outreach and prospect-management agents • Grounding and voice in autonomous communication • Copilot credits and potential operating costs • Preparing a lightning talk for Microsoft Ignite • Why Copilot Studio is not a universal entry point • The range of agent-building options • Risks of prematurely choosing custom AI • High-value, low-complexity use cases • Customer maintenance and self-sufficiency • Right-sized solutions and upgrade pathsKey Takeaways• Begin with requirements and desired business value, not a preferred AI platform. • Compare complexity against the value and friction associated with the problem. • Use Copilot Studio only when it fits the requirements. • Verify how autonomous agents are grounded before they communicate externally. • Avoid custom AI when a simpler Copilot or non-agent solution will work. • Deliver solutions customers can maintain after implementation. • Leave room to expand without overengineering the initial deployment.LinksSales Development Agent - https://learn.microsoft.com/en-us/dynamics365/sales/sales-dev-agent/sales-development-agent-overviewLets meet up at Ignite - https://stevecorey.com/igniteNeed a Copilot solution? https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing

Send us Fan MailSteve Corey examines why Microsoft 365 readiness is a foundational part of Copilot success. The discussion covers Copilot Code, SharePoint knowledge bases, cost controls, authoritative content, duplicate files, excessive access, abandoned workspaces, and inconsistent collaboration practices. Rather than waiting for a perfectly clean tenant, leaders should focus readiness work on defined AI use cases, high-value workflows, sensitive information, and measurable business outcomes. ❓ Need expert guidance with Microsoft 365 Copilot and agents - Let's talk about how I can help your business move forward - https://go.stevecorey.com/copilotbriefing-s1e6Topics Covered• Copilot Code and managed development environments • Copilot feature and cost management • SharePoint knowledge bases and Copilot credits • Tenant context and its effect on AI results • Authoritative SharePoint sites and sources of truth • Duplicate files and outdated document versions • Oversharing and permission risks • Abandoned Teams and SharePoint sites • Repeatable collaboration and knowledge-management patterns • A prioritized Microsoft 365 readiness assessmentKey Takeaways• Microsoft 365 readiness should be managed as a strategic business capability. • Strong AI capabilities can still produce weak results in a disorganized information environment. • High-value knowledge needs a clearly identifiable, maintained, authoritative location. • Copilot surfaces existing access problems rather than creating them. • Durable knowledge should be moved out of temporary collaboration channels. • Important content and workspaces need accountable owners. • Readiness work should begin with high-value workflows and sensitive content. • AI-related change should be measured and reported against business outcomes.⌚ Book your free on 1 on 1 call with me to discuss your business challenges and how AI can help 👉 https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing

Send us Fan MailMicrosoft 365 Copilot may be easy to demonstrate, but determining whether it is a worthwhile business investment requires more than tracking licenses and usage. Steve Corey explains how to evaluate Copilot through role-specific use cases, before-and-after process measurements, data readiness, security controls, ongoing support, and documented business outcomes.Topics Covered• Why polished AI demonstrations do not prove value • The difference between access, adoption, activity, and outcomes • Measuring processes before and after introducing AI • Converting saved time into additional business capacity • Overshared content and broad Microsoft 365 permissions • Assigning licenses according to job roles and tasks • The importance of task frequency in ROI calculations • Ongoing user support and champions programs • Documenting evidence before expanding a rollout • Search, meeting follow-ups, document drafting, and agents as use casesKey Takeaways• A Copilot rollout should begin with business processes and measurable outcomes. • Usage percentages should not be treated as proof that work has improved. • Saved time creates value only when the reclaimed capacity is put to productive use. • Permissions and sensitive-content controls should be addressed as part of readiness. • License allocation should reflect a role’s genuine opportunities to benefit. • Before-and-after evidence supports future licensing and expansion decisions.Chapters00:00 A Business-Focused Copilot Briefing00:49 The Investment Question02:02 What Determines Copilot Value02:54 Meet Steve Corey03:53 More Than a Software Purchase05:16 Transform and Measure Processes06:39 What Happens to Saved Time?08:20 Access, Adoption, and Outcomes10:27 Returning Time to the Business11:39 The Oversharing Risk14:27 Matching Licenses to Job Roles15:53 Cost and Task Frequency17:02 Ongoing Support and New Features19:09 A Fiscally Responsible Approach20:26 Documenting Measurable Outcomes22:09 Practical Copilot Use Cases23:32 Proving the Before and After24:54 Closing and Future Episodes⌚ Book your free on 1 on 1 call with me to discuss your business challenges and how AI can help 👉 https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing

Send us Fan MailEpisode SummaryThis episode examines five custom Copilot agents that could reduce administrative work across the sales process. The examples cover CRM maintenance, call coaching, pipeline risk, competitive research, and proposal development. The discussion also explains why governed knowledge, accurate data, human review, and a clear data model are necessary for dependable agent outcomes. [captions | Txt], [Subtitle 1.srt | Txt]Topics Covered• The cost of non-selling work • Custom agents within Microsoft 365 workflows • CRM updates from meeting and email context • Sales coaching based on an organization’s methodology • Pipeline risk and engagement signals • The danger of forecasting from poor CRM data • Approved competitive intelligence and battle cards • Proposal and RFP drafting from curated content • Human review and automated approvals • Data modeling and agent governanceKey Takeaways• Agents are most useful when they reduce friction inside tools sellers already use. • CRM updates can be suggested from customer interactions instead of entered entirely by hand. • Coaching should be aligned to a defined sales methodology. • Forecasting output is only as dependable as the underlying data. • Competitive and proposal agents should use approved, governed content. • Human review remains important for specialist, legal, and compliance decisions. • Reliable deployments begin with a fixed data model and clear governance.Chapters00:00:00 Welcome to the Copilot Briefing00:00:32 Five Sales Agent Use Cases00:01:37 Why Custom Agents Matter00:02:36 The CRM Guardian Agent00:04:49 The AI Sales Coach00:07:09 The Pipeline Forecaster’s Ally00:08:45 The Data Quality Trap00:09:42 Competitive Intelligence Agent00:11:32 Proposal and RFP Agent00:12:55 What Reliable Agents Require00:14:24 Final Takeaways00:14:58 Closing⌚ Book your free on 1 on 1 call with me to discuss your business challenges and how AI can help 👉 https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing

Send us Fan Mail🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/chatcoworkautopilotEpisode SummaryMicrosoft’s new Copilot experience brings Chat and Co-Work together under Home while adding Code and Autopilot as distinct modes. This episode explains how each mode is intended to be used, how the managed runtime could simplify application governance, and why organizations need to prepare for consumption-based costs. It also covers Microsoft IQ, plugins, model access, advanced SharePoint capabilities, OneDrive, and Copilot Search.Topics Covered• Copilot Home, Code, and Autopilot • Chat versus Co-Work • Office editing inside Copilot • The Today screen • Mentioning Copilot in Teams • Personal Autopilot agents • End-user coding • Copilot managed runtime • Microsoft IQ and Dataverse data • Plugin and MCP governance • FinOps for AI and Copilot credits • Model-family access controls • Hybrid billing for SharePoint • Copilot Search in SharePoint and OneDriveKey Takeaways• Communicate the redesigned Copilot interface before users encounter it. • Match quick work to Chat and complex multi-step work to Co-Work. • Use Autopilot for autonomous personal work without abandoning enterprise-agent investments. • Establish spending policies and approval paths before expanding usage. • Decide which business processes are suitable for Code, Autopilot, Co-Work, or enterprise agents. • Treat advanced SharePoint capabilities as a distinct cost and governance category.Chapters00:00:00 Welcome to the Copilot Briefing00:00:32 Microsoft’s Copilot announcements00:00:58 The new Copilot app00:02:31 Office inside Copilot00:04:13 The Today screen00:04:59 Mentioning Copilot in Teams00:05:55 Introducing Autopilot00:06:46 Co-Work versus Autopilot00:08:03 Autopilot triggers and actions00:09:47 Home, Autopilot, and Code00:10:06 End-user application development00:11:38 Copilot managed runtime00:13:18 Microsoft IQ and business data00:14:46 The plugin registry00:15:47 FinOps for AI00:19:06 Agent costs and spending policies00:21:01 Controlling model access00:22:06 Cost visibility and usage limits00:24:38 Copilot in SharePoint00:28:06 OneDrive and Copilot Search00:29:00 Business priorities and takeawaysLinksCopilot in SharePoint updates - https://techcommunity.microsoft.com/blog/spblog/sharepoint-ai-innovations-hit-ga-powering-new-copilot-app-and-agents/4555724?WT.mc_id=MVP_320501The new Copilot app - https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/⌚ Book your free on 1 on 1 call with me to discuss your business challenges and how AI can help 👉 https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing

Send us Fan Mail🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/chatcoworkautopilotEpisode SummaryMicrosoft Copilot Cowork tasks can produce very different costs even when they initially appear similar. This episode explains the major factors behind that variation, including model choice, context retrieval, tool usage, reasoning depth, runtime, and generated outputs. It also presents a practical framework for distinguishing light, medium, and heavy tasks and describes how the /cost command can be used to review the credits consumed by a completed task. The central recommendation is to compare Cowork’s cost with the time and labor required to perform the same process manually.✅ Connect With Steve ☑️ Socials - https://stevecorey.social 🌍 Web - https://stevecorey.com Topics Covered• Copilot credits and usage-based billing • Model selection and AI workload complexity • Context retrieval from files, email, chats, and transcripts • Connectors, MCP servers, agents, and plugins • Runtime and long-running Cowork processes • Light, medium, and heavy task categories • Additional files and presentation outputs • Reviewing task usage with /cost • Comparing AI costs with manual labor • Choosing between Copilot, agents, Researcher, and Cowork Key Takeaways• Cowork costs reflect the full workload, including context, tools, reasoning, runtime, and outputs. • Broad organizational searches generally require more resources than single-document tasks. • The /cost command provides a concrete way to inspect the cost of a completed run. • Not every task requires Cowork; some may be better suited to regular Copilot or an agent. • Business value should be evaluated by comparing AI usage with the cost of the existing manual process. Chapters00:00:00 Introduction00:00:32 Why Cowork task costs differ00:00:52 Usage-based billing and Copilot credits00:02:07 Different AI workloads require different resources00:02:44 Document summaries versus deep analysis00:03:15 Models, context retrieval, and tool calls00:05:10 How runtime affects cost00:06:08 Cowork as a long-running agent harness00:07:16 How additional outputs increase cost00:07:37 Light, medium, and heavy tasks00:07:45 Characteristics of a light task00:08:43 Characteristics of a medium task00:09:12 Characteristics of a heavy task00:10:20 Checking task cost with /cost00:11:20 Comparing Cowork with manual labor00:12:00 Choosing between Cowork, agents, and Researcher00:13:07 The podcast takeaway00:13:56 Measuring process time and business cost00:14:16 Business outcomes and closing ⌚ Book your free on 1 on 1 call with me to discuss your business challenges and how AI can help 👉 https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing

Send us Fan MailEpisode Description 🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/chatcoworkautopilotRunning AI at scale is expensive, and consumption-based services can make budgets harder to predict. Steve Corey explains Microsoft’s MAI family of in-house models, the role of multi-model orchestration, and why routine work should not automatically be sent to the most expensive model. The episode reviews MAI models for reasoning, coding, image generation, voice, and transcription, then considers how efficient routing could affect Copilot credits, pay-as-you-go usage, custom agents, and AI return on investment.✅ Connect With Steve ☑️ Socials - https://stevecorey.social 🌍 Web - https://stevecorey.com📝 Show Notes and Resources 📝 Topics Covered• The cost of operating AI at scale• Copilot licensing and consumption-based pricing• Copilot credits and variable AI costs• Microsoft’s MAI model family• Multi-model orchestration and automatic routing• Reasoning, coding, image, voice, and transcription models• Pay-as-you-go cost management• Cost-conscious custom agent design• Matching model capability to task complexity• AI solution feasibility and return on investmentKey Takeaways• Not every request requires a frontier model.• Efficient routing can reserve expensive models for genuinely complex work.• Model choice directly affects the consumption profile of AI solutions.• Custom agents can use different models for routine and critical steps.• Organizations should continually reassess which models their workloads use.• Lower-cost models may make usage more manageable, but consumption remains variable.Chapters00:00:00 Welcome to the Copilot Briefing00:00:32 Why AI Costs Matter00:01:37 The Copilot Pricing Challenge00:03:14 Introducing Microsoft MAI00:03:49 Why Microsoft Built Its Own Models00:05:19 Multi-Model Orchestration00:06:12 How Model Routing Works00:06:56 MAI Model Lineup00:07:01 Reasoning Model00:07:53 Coding Model00:08:23 Image Model00:09:25 Voice Model00:10:11 Transcription Model00:10:49 Implications for Copilot Costs00:12:18 Pay-As-You-Go Economics00:13:20 Custom AI Cost Control00:13:52 The Bottom Line00:15:20 Podcast Takeaways🔗 LinksMAI Models - (Microsoft Techcommunity)⌚ Book your free on 1 on 1 call with me to discuss your business challenges and how AI can help 👉 https://go.stevecorey.com/copilotbriefing🔴 Need help with Microsoft 365 Copilot adoption, governance, and employee training? Let's build your strategy ➡️ https://go.stevecorey.com/copilotbriefing