mcpField
A
azure-pricing

azure-pricing

github.com/vinayaklattheCloud & DevOps17977 installsUpdated 1d ago
Repository

About azure-pricing

A cost-estimation skill for teams budgeting or optimizing Azure security solutions. It identifies consumption, per-resource, and license cost drivers, and advises checking current rates against official pricing sources.

Key features

  1. 01Identify consumption and per-resource charges
  2. 02Estimate Sentinel log ingestion
  3. 03Assess Defender plan coverage
  4. 04Model costs with the Pricing Calculator
  5. 05Optimize log tiers and commitment tiers

Use cases

  1. 01Estimate Microsoft Sentinel and Defender for Cloud costs
  2. 02Build security service costs into workload TCO
  3. 03Check whether existing licenses cover capabilities
  4. 04Reduce duplicate log ingestion and unused resources

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vinayaklatthe/microsoft-security-skills --skill azure-pricing

After installing, type/azure-pricingin Claude Code to confirm it loaded.

Details

From the project README

Azure Security Pricing & Cost Estimation

Security services on Azure mix consumption-based (e.g., data ingestion, transactions) and per-resource/seat pricing. This skill helps reason about and estimate costs and identify optimisation levers. Always confirm current rates on official pricing pages.

When to use

Producing a cost estimate or optimising spend for a security solution.

Key cost drivers

  • Microsoft Sentinel — Driven mainly by data ingestion (per GB) and retention. Use Commitment Tiers, route low-value logs to Auxiliary/Basic logs or ADX, and avoid duplicate ingestion.
  • Defender for Cloud — Foundational CSPM is free; Defender plans are per-resource (e.g., per server/hour, per 10K transactions, per vCore). Enable plans where risk justifies.
  • Microsoft Defender XDR / Purview / Entra ID P2 — Largely per-user licensing (E5 / add-ons) rather than consumption.
  • Key Vault — Per-operation (secrets/keys/certs) and HSM pool charges (Managed HSM).
  • Azure Firewall / Front Door / DDoS — Deployment + data processing charges.

Approach

  1. List components and identify which are consumption vs licensed.
  2. Estimate quantities — e.g., Sentinel daily GB, number of protected servers/resources.
  3. Use the Pricing Calculator to model the estimate; add it to the workload TCO.
  4. Apply optimisation — commitment tiers, log tiering, right-size Defender plan coverage, remove unused resources.
  5. Validate licensing — Confirm whether E5/add-ons already cover a capability before adding consumption cost.

Guardrails

  • Pricing changes — always verify against the live pricing page and your agreement (EA/MCA/CSP).
  • Sentinel ingestion is the most common cost surprise — plan log tiering up front.
  • Don't disable needed protection purely for cost; optimise scope instead.

Example prompts

  • Estimate the cost of Microsoft Sentinel and Defender for Cloud for my environment.
  • What are the main cost drivers for Microsoft security services?
  • How do I optimise security spend across licensing and consumption?
  • Help me budget for security ingestion and per-resource Defender plans.

Microsoft Learn

Comments

Markdown supported