[Brett Wilson (MSBrett)]

Summary

• Add a standalone 60-file cost-management recipe using native Azure Cost Management through the Azure Resource Manager MCP server with 14 tools. It has no FinOps Hubs or Azure Data Explorer dependency.
• Include three subagents (finops-practitioner, azure-capacity-manager, and chief-financial-officer), 13 Python ExtendedAgentTool ARM, Quota, and Resource Graph tools, the azure-cost-management skill with 12 reference guides, the azcapman plugin, 15 knowledge base documents, 17 opt-in scheduled tasks, a Microsoft Teams ConnectorV2, and FinOps custom instructions.
• Update the Bash and PowerShell assembly, apply, and verification scripts to bundle, deploy, and verify custom instructions; use the ExtendedAgentTool envelope and upload tools before dependent skills and subagents; and propagate ConnectorV2 spec.operations.

Validation

• test-dry-run-cost-management.sh: 50/50 passed.
• test-connector-v2.sh: PASS.
• Live verify-agent.sh: 26/26 passed.
• Live UAT covered cost and commitment review with a Teams post, cost-spike investigation with a follow-up Teams post, and AI workload cost and GPU capacity review with a Teams post. The cost and commitment review was manually prompted, not proof of a scheduled trigger. Existing commitment utilization was not established.
• Application Insights audit events independently recorded starts and ends for the three custom Python tools tested. The quota tool response was truncated or malformed in the capture; a clean complete quota response was not established. Two Resource Graph calls in the spike investigation returned HTTP 400 details despite a successful execution envelope. Cost-table rounding and unverified operational causes are documented as limitations.

[Brett Wilson (MSBrett)]

Closing while we complete final R&D UAT verification in our fork.