From 6482315ef9df6eff73fbcae8945e58a69bba56cd Mon Sep 17 00:00:00 2001 From: Tim Karlsson Date: Mon, 27 Jul 2026 16:18:45 +0200 Subject: [PATCH] Add Copilot Licensing Advisor skill Interview-driven recommendation of the right Microsoft 365 Copilot, Copilot Studio, and Power Platform license mix, with costs fetched live at the time of the conversation instead of hardcoded prices. --- .../copilot-licensing-advisor/README.md | 31 ++++++++ .../copilot-licensing-advisor/SKILL.md | 71 +++++++++++++++++++ .../copilot-licensing-advisor/metadata.json | 11 +++ .../references/sku-rules.md | 52 ++++++++++++++ 4 files changed, 165 insertions(+) create mode 100644 submissions/copilot-licensing-advisor/README.md create mode 100644 submissions/copilot-licensing-advisor/SKILL.md create mode 100644 submissions/copilot-licensing-advisor/metadata.json create mode 100644 submissions/copilot-licensing-advisor/references/sku-rules.md diff --git a/submissions/copilot-licensing-advisor/README.md b/submissions/copilot-licensing-advisor/README.md new file mode 100644 index 00000000..f04fb421 --- /dev/null +++ b/submissions/copilot-licensing-advisor/README.md @@ -0,0 +1,31 @@ +# Copilot Licensing Advisor + +Answer a few questions about who needs what, and get back a license +recommendation and a costed table: Microsoft 365 Copilot, Copilot Studio, and +Power Platform, sized to the actual need instead of the biggest bundle. + +## Why prices aren't in this skill + +Licensing prices, SKU names, and message/Copilot Credit mechanics change +often enough that hardcoding them here would go stale fast. Instead, the skill +fetches current pricing and eligibility from official Microsoft sources at +the time you use it, and states the fetch date next to every number. What *is* +bundled in (`references/sku-rules.md`) is only the slow-moving structural +rules, like which base plan a Copilot add-on requires or which Copilot Studio +path fits which scenario: the kind of thing that doesn't change month to month. + +## What it won't do + +Quote a price it didn't just fetch, or recommend a bigger license than the +stated need requires. If a fetch fails, it says so and points you to the +official pricing page rather than estimating. + +## Reference + +[Microsoft 365 Copilot licensing](https://learn.microsoft.com/microsoft-365/copilot/microsoft-365-copilot-licensing) +· [Copilot Studio licensing](https://learn.microsoft.com/microsoft-copilot-studio/billing-licensing) +· [Power Platform pricing and billing](https://learn.microsoft.com/power-platform/admin/pricing-billing-skus) + +--- + +Skill by Tim Karlsson (╯°□°)╯︵ ┻━┻ Works 60% of the time, every time. diff --git a/submissions/copilot-licensing-advisor/SKILL.md b/submissions/copilot-licensing-advisor/SKILL.md new file mode 100644 index 00000000..31b0016d --- /dev/null +++ b/submissions/copilot-licensing-advisor/SKILL.md @@ -0,0 +1,71 @@ +--- +name: copilot-licensing-advisor +description: >- + Use this skill whenever the user asks which Microsoft 365 Copilot, Copilot + Studio, or Power Platform license or SKU they need, how many seats to buy, + or what a rollout would cost, before quoting any price or recommending a + specific SKU. +--- + +Interview the user about what they're trying to enable, recommend the license +mix that actually covers it, and cost it out, with current prices fetched at +the time of the conversation, never quoted from memory. + +## Instructions + +1. Interview first. Ask (batch related questions rather than one at a time + where they're clearly related): + - How many people need this, and what are they trying to do? Copilot Chat + in Office apps, building agents in Copilot Studio, or both? + - What Microsoft 365 plan do they already have (E3/E5/Business + Standard/Business Premium/F-series/etc.), if any? + - Any existing Power Platform or Dataverse licensing already in place? + - Government cloud (GCC/GCC High/DoD) or commercial? + - Rough seat count, since some licensing (like Copilot Studio message + packs) is usage-based rather than per-seat. + +2. Before recommending or pricing anything, fetch current information. Do not + rely on training data for prices, SKU names, or eligibility rules, all of + which change. Search for and cite: + - Current Microsoft 365 Copilot license prerequisites and pricing. + - Current Copilot Studio licensing (user license, message/Copilot Credit + packs, and the Copilot Studio-in-Teams-plan variant if relevant). + - Current Power Platform per-app / per-user pricing if the use case touches + Power Apps, Power Automate premium connectors, or Dataverse. + State the fetch date next to every price so the user knows how fresh it is. + +3. Match the use case to the minimum license, using the stable rules in + `references/sku-rules.md` as your starting checklist, then verify each rule + is still current against what you fetched in step 2 before relying on it. + +4. Recommend the smallest license mix that covers the stated need. Don't + upsell to a bundle the user didn't ask for. If two paths solve the same + need at different costs (e.g. Microsoft 365 Copilot add-on vs. Copilot + Studio pay-as-you-go for a narrow agent-only use case), present both with + the trade-off and let the user choose. + +5. Produce a cost table: license, unit price fetched in step 2, seat/usage + count, subtotal, total. Separate one-time considerations (e.g. minimum + Copilot Credit pack purchase) from recurring per-seat cost. + +6. Flag anything time-sensitive: an add-on that requires an existing base + license the user doesn't have yet, a feature in preview that could change + licensing before general availability, or a region/cloud (GCC/GCC High/DoD) + where availability lags commercial. + +## Guardrails + +- Never state a specific price without having fetched it in the current + conversation. If fetching fails, say so explicitly and point the user to the + official pricing page instead of estimating. +- Never guess at SKU eligibility rules from memory when they conflict with + what's fetched. The fetched, dated result wins. +- Don't recommend a higher license tier than the stated need requires. +- State clearly when Power Platform licensing is separate from Microsoft 365 + Copilot licensing. The two are commonly confused, and Power Platform + Connectors licenses are **not** included with Microsoft 365 Copilot. + +## Tone + +Consultative and numbers-first. Show the math, name the source, date the +price. No sales pitch. diff --git a/submissions/copilot-licensing-advisor/metadata.json b/submissions/copilot-licensing-advisor/metadata.json new file mode 100644 index 00000000..5dd2425e --- /dev/null +++ b/submissions/copilot-licensing-advisor/metadata.json @@ -0,0 +1,11 @@ +{ + "name": "Copilot Licensing Advisor", + "description": "Interview-driven recommendation of the right Microsoft 365 Copilot, Copilot Studio, and Power Platform license mix, with costs fetched live at the time of the conversation instead of hardcoded prices.", + "platforms": ["Copilot Studio", "Cowork", "Scout"], + "tags": ["licensing", "microsoft-365", "copilot", "power-platform", "cost", "advisor"], + "author": "Tim Karlsson", + "authorUrl": "https://github.com/Timziito", + "version": "1.0.0", + "createdAt": "2026-07-26", + "updatedAt": "2026-07-26" +} diff --git a/submissions/copilot-licensing-advisor/references/sku-rules.md b/submissions/copilot-licensing-advisor/references/sku-rules.md new file mode 100644 index 00000000..a3da3b7b --- /dev/null +++ b/submissions/copilot-licensing-advisor/references/sku-rules.md @@ -0,0 +1,52 @@ +# SKU eligibility rules: starting checklist, not a source of prices + +These are structural, slow-changing eligibility rules, the kind of thing that +doesn't move month to month. **Prices, SKU names, and message/Copilot Credit +mechanics move constantly and are never listed here.** Always verify a rule +below is still current before relying on it; official docs win over this file. + +## Microsoft 365 Copilot (the add-on, Chat/Word/Excel/PowerPoint/Teams/Outlook) + +- Requires an eligible base subscription first: Microsoft 365 Business + Basic/Standard/Premium, Microsoft 365 E3/E5/E7, Microsoft 365 F1/F3, Office + 365 E1/E1 Plus/E3/E5, Office 365 F3, Microsoft 365/Office 365 A-series + (education), or a qualifying Teams plan. No base plan, no Copilot add-on. +- The user's primary mailbox must be in Exchange Online. On-premises or + hybrid mailboxes don't support Copilot's mailbox grounding. +- Microsoft 365 E7 already includes the Microsoft 365 Copilot add-on. Don't + recommend buying it separately for an E7 tenant. +- Power Platform licensing (Power Apps, Power Automate premium connectors, + Dataverse capacity) is **never** included with a Microsoft 365 Copilot + license. It's always its own line item. + +## Copilot Studio + +Three separate paths. Check which one already fits before recommending a new +purchase: + +1. **Included via Microsoft 365 Copilot license.** Agent capability used + inside Microsoft 365 Copilot, Teams, or SharePoint (classic answers, + generative answers, Graph tenant grounding) doesn't consume the separate + Copilot Studio message/credit meter. +2. **Copilot Studio for Microsoft Teams plan.** A subset of Copilot Studio + capability bundled into select Microsoft 365 + Power Platform + Teams + subscriptions, for agents published to Teams using classic orchestration. + Cheaper than standalone Copilot Studio but capability-limited. Confirm the + use case fits before recommending it over the full product. +3. **Standalone Copilot Studio.** A free per-maker user license plus a + prepaid Copilot Credit / message pack at the tenant level. Needed for + generative orchestration, non-Teams channels, or capability beyond what the + Teams plan bundle covers. + +## Government cloud + +GCC/GCC High/DoD availability and feature parity consistently lag commercial. +Never assume a commercial-cloud feature or price applies; verify separately +for the target cloud. + +## When two paths tie + +If a narrow, agent-only use case is covered equally by the Microsoft 365 +Copilot add-on and by standalone Copilot Studio, the deciding factor is usually +whether the org already has (or needs) Microsoft 365 Copilot for other reasons. +Present the cost of each path rather than picking one.