Repository navigation
docs(announce): add v15 release announcement draft - #2394
Michael Flanakin (flanakin) wants to merge 13 commits into
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
151200b to
862ee97
Compare
Center the plugin on AI assistants, add Agent Plugins platform list, clarify private networking changes, add FinOps hubs quality and ecosystem sections, reframe open data section, positive framing, and refresh social copy. Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…dards Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Michael Flanakin (flanakin)
left a comment
There was a problem hiding this comment.
🤖 [AI][Claude] Chief of Staff review
Summary: Strong structure and mostly accurate against the v15 changelog and release. Four claims need fixing before publish (version/roadmap, install command, ecosystem framing). Several links 404 today, tone and voice need a pass. Checked against the changelog, v15 release, roadmap, milestones, plugin docs, Deploy-FinOpsHub, and link status; I did not read other reviewers' comments.
🚫 Blockers (4)
- "FOCUS 1.5 is coming in v17" contradicts the milestone (issue 2120 is v16). "By the end of the year" has no source.
- "FinOps toolkit MCP server" is listed as on the roadmap but isn't there and has no issue.
claude plugin add microsoft/finops-toolkitisn't a valid Claude Code command.- Ecosystem section singles out Allyte (the author's company) and FinOpsHubs.com. The ecosystem page and listing template promise no ranking or featured placement.
⚠️ Should fix (6)
- "Cowork" and the supported-client list (ChatGPT/Codex, Kiro, VS Code, Copilot) aren't backed by the repo or agent-plugins.org.
- "October 28 office hours" claim has no source.
- Learn and docs-site links 404 today (plugin overview, run-hubs-locally, Initialize-FinOpsHubLocal, both Get-FinOps* data cmdlets, AOE reference). Confirm they're live at publish.
- Title, preview, and internal post use "FinOps toolkit 15"; the PR's own new standard says "FinOps toolkit v15".
- The quality section and others dwell on errors and internals, against the new "stay positive" rule and hard for non-engineers.
- "Deployment options aren't remembered" is unsourced and negative.
💡 Suggestions (4)
- Voice pass: intro is boilerplate, sections open on features, "great time" appears twice, "meeting you where you already work" reads generic.
- "Programmatic access" for the two new cmdlets is stronger than the changelog ("generate open data files").
- Private networking framing: changelog says v15 added VNet and private modes; also note
-DisablePublicAccessis now deprecated. - Guideline wording: "positive spin".
Michael Flanakin (flanakin)
left a comment
There was a problem hiding this comment.
🤖 [AI][Claude] Release Manager review
Summary: Structure and section order match v13/v14, and almost every feature and fix claim traces to the v15 changelog, release body, and code. Four things need fixing before publish: the Claude Code install command doesn't exist, several links 404 today, the v17 claim contradicts the milestone, and one claim has no source. Checked against the v15 tag (changelog, release body, roadmap, Bicep, Deploy-FinOpsHub.ps1, Learn docs), the v15/v16/v17 milestones, and live URLs.
🚫 Blockers (3)
- Install command
claude plugin addisn't a Claude Code command (L17) - Six links return 404 today (L15, L31, L33, L63, L111)
- "FOCUS 1.5 is coming in v17" contradicts the milestone (L126)
⚠️ Should fix (8)
- "October 28 office hours" attribution has no source (L95)
- Ecosystem section singles out Allyte and FinOpsHubs.com (L71-74)
- Missing upgrade caveat:
Az.Accounts2.17.0 minimum (L116-120) - Missing upgrade caveat:
-DisablePublicAccessis deprecated (L41) - AOE ingestion change: state what existing users must do (L112)
- Stay-positive violations (L17, L35, L43, L45, L52, L61)
- Opening paragraph is the boilerplate intro, not Michael's voice (L3)
- "Deprecated in September 2026" is the wrong tense (L112)
💡 Suggestions (3)
- Link the reingest steps (L67)
- Add the AOE Reservations Usage workbook regression fix (L113)
- Don't promise "more by the end of the year" (L126)
Checked and fine: five agents, Costs()/Prices()/Recommendations()/Transactions(), Database Viewer and az login, 16 GB / PowerShell 7 / Parquet / read-only mount, -NetworkMode values and the NAT Gateway UI label and Advanced tab path, ISF and eligibility claims, the Agent Plugins client list, section naming and order, version and product-name qualifiers, and the social posts.
- Fix Claude Code plugin install commands (marketplace add, then install) - Remove unverified Cowork claim; list all compatible clients from agent-plugins.org - Reframe hub fixes and private networking positively; add upgrade notes (-DisablePublicAccess, -NetworkMode private, Az.Accounts 2.17.0, AOE ingestion) - Fix AOE reference link; add Advisor, Reservations Usage workbook, and gzip thanks - Use "FinOps toolkit v15" in title, preview, and internal post - Disclose Allyte relationship; refine voice and openings - Tighten Stay positive guideline; align announce title template Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Reframe AI plugin section, plugin compatibility, and install steps - Warm intros for local hubs and private networking - Restructure FinOps hubs quality and commitment discount sections - Generalize first-reference guidance in announce command Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…stall commands - Fold office hours into the Allyte official support bullet - Remove single-contributor thank-you - Match AOE upgrade line to the Upgrading AOE docs - Fix Claude Code install commands in the plugin overview and docs site Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Use "FinOps toolkit 15" / "FinOps hubs 15" naming; "v15" only standalone
- Reframe AI plugin as collaboration; verified agents, install steps, MCP link
- Rework local hubs, private networking, quality, ISF, and ecosystem sections
- Generalize spell-out standard in Coding-guidelines and announce command
- Revert announce title format to {N}
Co-Authored-By: flanakin <flanakin@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Intro summarizes what's new for private networking and commitment data - Add inline ChatGPT and Codex CLI install steps - Clarify local hub as an additional option, compare network modes with cost direction - Drop redundant "ready-made" and "in FinOps toolkit 15" Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: Michael Flanakin <flanakin@users.noreply.github.com>
- Reframe fixes as improvements; move first ingestion and Data Explorer items to other updates - Clarify consistent savings fix; reorder commitment discount section (eligibility first) - Frame agents as staff you direct; focus on NAT Gateway in intro, preview, and social Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
| ## Private networking for FinOps hubs | ||
|
|
||
| Many organizations can't leave their cloud data reachable over the public internet. If yours is one of them, FinOps hubs 15 makes private networking easier to adopt with explicit network modes and an opt-in NAT Gateway for private mode. Pick the mode that fits your environment: | ||
| Many organizations can't leave their cloud data reachable over the public internet. If yours is one of them, FinOps hubs 15 gives you more control with an opt-in NAT Gateway for private mode and explicit network modes. Pick the mode that fits your environment: |
There was a problem hiding this comment.
"opt-in NAT Gateway": Just NAT Gateway support or an option for NAT Gateway over VNet peering? Then you mention network modes as if it's separate, but isn't it the same thing? Clean up all refs to this, not just here. The intro and all summaries in the final sections.
| - **More regions are supported.** Deployments now work in regions like Sweden Central, and managed exports deploy cleanly in Japan. | ||
| - **First ingestion completes on the first try.** The first time you ingest a scope, dataset, and month, which reservation recommendation exports hit most often, ingestion now completes without a `PathNotFound` error. | ||
| - **Upgrades preserve your data.** Redeploying or upgrading keeps your data retention settings unless you specify a new value. | ||
| - **Managed exports run out of the box.** FinOps hubs now assign Data Factory the Azure role it needs, so managed exports work right after deployment. |
There was a problem hiding this comment.
Move this to other updates. It doesn't sound interesting at all. Sounds like a minor bug fix. If I'm wrong, make it sound that way.
| - **First ingestion completes on the first try.** The first time you ingest a scope, dataset, and month, which reservation recommendation exports hit most often, ingestion now completes without a `PathNotFound` error. | ||
| - **Upgrades preserve your data.** Redeploying or upgrading keeps your data retention settings unless you specify a new value. | ||
| - **Managed exports run out of the box.** FinOps hubs now assign Data Factory the Azure role it needs, so managed exports work right after deployment. | ||
| - **More regions.** FinOps hubs now deploy in more regions, including Sweden Central, and managed exports are supported in Japan. |
There was a problem hiding this comment.
Move to other updates. This also sounds like a bug fix, yet I'm still unclear what the problem was and why anything changed. This is a horrible update note. I've asked 3-4x for this and it's no better.
| **Faster queries.** Hub queries, including the query catalog, run faster on large datasets because they use the engine's term index instead of scanning every row. | ||
|
|
||
| **Smoother deployments and upgrades.** Deployments, upgrades, and first-time data loads work in more situations: | ||
| **Smoother deployments and upgrades:** |
There was a problem hiding this comment.
Drop the list and make this a single paragraph with the one option left.
| - **A clearer audit trail for contracted cost.** FinOps hubs record the changes they make to each row during ingestion in the `x_SourceValues` column. Contracted cost values that were already correct were being recalculated anyway, because tiny floating-point differences looked like changes, and that added millions of unnecessary entries. FinOps hubs now recalculate contracted cost only when the value needs to change and keep an existing contracted cost when the unit price is missing, so `x_SourceValues` shows only meaningful changes. | ||
| - **More complete recommendations.** The SQL VMs without Azure Hybrid Benefit recommendation now includes every eligible VM. Matching used the VM name and was case sensitive, which skipped VMs with uppercase names and dropped VMs that share a name. The recommendation now matches each VM by its resource ID. | ||
| - **Consistent savings.** The Summary page in the Data Explorer dashboard now excludes commitment purchases the same way the Rate optimization page does, so savings and effective savings rate (ESR) match across both. Commitment discount savings also compare against the Production price when a reservation price has Dev/Test variants. | ||
| - **A focused change history for contracted cost.** FinOps hubs record the changes made to each row during ingestion in the `x_SourceValues` column. Contracted cost is now updated only when the value needs to change, so `x_SourceValues` shows only meaningful changes. An existing contracted cost is also kept when the unit price is missing. |
There was a problem hiding this comment.
Lead with the change to Contracted cost, not the source values. Nobody cares about source values. It's a debug and data lineage tool.
| ## Preview snippet | ||
|
|
||
| > FinOps toolkit 15 brings FinOps expertise and your cost data to the AI tools you already use with a new agent plugin, adds a guide to run FinOps hubs locally, improves private networking for FinOps hubs, and delivers new reservation and commitment discount data. | ||
| > FinOps toolkit 15 brings FinOps expertise and your cost data to the AI tools you already use with a new agent plugin that gives you a team of AI agents to direct, adds a guide to run FinOps hubs locally, adds an opt-in NAT Gateway for private FinOps hubs, and delivers new reservation and commitment discount data. |
There was a problem hiding this comment.
"team of AI agents to direct" is missing context of the story and over-selling it.
NAT Gateway ref is still inaccurately represented
Same issues in other update summaries
| > - AI agents you direct, in a new agent plugin | ||
| > - Run #FinOpsHubs locally | ||
| > - Private networking with opt-in NAT Gateway | ||
| > - Opt-in NAT Gateway for private FinOps hubs |
There was a problem hiding this comment.
Everything's opt in, so just "NAT Gateway support for private FinOps hubs"
| > FinOps toolkit 15 is out! #FinOpsToolkit | ||
| > | ||
| > - Agent plugin for your AI assistant | ||
| > - AI agents you direct, in a new agent plugin |
There was a problem hiding this comment.
Revert - was fine before
Co-Authored-By: flanakin <flanakin@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This reverts commit 40022f9. The rewrite went beyond the requested changes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Draft of the v15 announcement (
announce/2026/2026-10_v15.md), built from the v15 changelog, the published release, and the roadmap, following the v13 and v14 structure.Needs a voice pass before publishing: the standard release intro and the feedback-ask closing are kept from v12 to v14.
🤖 Generated with Claude Code