Understanding Microsoft Copilot Licensing - Rev1
Part one of a short, but living series on what Copilot and agents cost. What the Copilot license costs, how Copilot Credits work, which features use them, and what Microsoft has announced next.
Notes from the trenches of real projects. What worked, what didn't, and why — no marketing spin.
Part one of a short, but living series on what Copilot and agents cost. What the Copilot license costs, how Copilot Credits work, which features use them, and what Microsoft has announced next.
A practitioner's reference for Power Platform core, Copilot Studio, Dataverse, Dynamics 365 Contact Center, and Dynamics 365 Customer Service.
Using the Meetings and Daily Briefing skills in Cowork for prep, recap, action items, and a prioritized morning view of your day.
Microsoft's new 'IQ' layers - Work IQ, Fabric IQ, and Foundry IQ - provide AI agents with deep organizational context across work, data, and knowledge domains. Here's what they are, why they matter for enterprise AI, and how developers can use them to build smarter agents.
Cowork's Scheduling and Calendar Management skills — finding times, sending invites, reviewing the week, and defending focus time.
Using Cowork's Email skill to triage, draft, and send mail in Outlook end-to-end — with approval prompts before anything leaves your tenant.
Hands-on custom skills in Cowork — the SKILL.md format, OneDrive layout, a working weekly-report example, and the limits that still apply.
Cowork's 13 built-in skills named and scoped — Word, Excel, PowerPoint, PDF, Email, Scheduling, Meetings, Deep Research, and more.
Microsoft MVP & MCT | Low Code Hacker | Copilot, Copilot Studio, Power Platform & Azure Architect
I’m a Microsoft MVP focused on agentic AI, intelligent agents, and enterprise AI solutions. Using Microsoft Copilot Studio and Azure AI Foundry, I design and build systems that help people and organizations work smarter. This blog is a collection of field notes, practical insights, and real-world experiences—from architecture and orchestration patterns to lessons learned along the way. Your feedback is always welcome—let’s continue the conversation.