AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cost-optimization

Optimize existing Azure resources and analyze Reservations or Savings Plans. WHEN: "optimize Azure costs", "reduce cloud spending", "rightsize resources", "find idle resources", "orphaned disk", "deleted VM still charged", "public IP still charging", "reservation utilization", "Savings Plan coverage", "commitment recommendation", "why is pay-as-you-go still charged". DO NOT USE FOR: cost spikes, forecasts, pricing estimates, budgets, or governance.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--cost-optimization at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 9

references/services/storage-lifecycle.md

Storage Lifecycle Guidance

Use this reference only after Azure Advisor or observed access evidence indicates that tiering may reduce cost. Verify retention requirements, redundancy requirements, retrieval latency, and live prices before recommending a policy.

Access tiers

Compare Hot, Cool, Cold, and Archive against the workload's observed access frequency and retrieval requirements. Do not derive a tier recommendation from a generic age threshold.

Include minimum-retention, retrieval, early-deletion, and rehydration costs. Do not recommend Archive for data with unpredictable or urgent retrieval.

Policy example

{
  "rules": [
    {
      "name": "example-tier-inactive-base-blobs",
      "type": "Lifecycle",
      "definition": {
        "actions": {
          "baseBlob": {
            "tierToCool": { "daysAfterLastAccessTimeGreaterThan": 30 },
            "tierToArchive": { "daysAfterLastAccessTimeGreaterThan": 180 }
          }
        },
        "filters": { "blobTypes": ["blockBlob"] }
      }
    },
    {
      "name": "delete-expired-copies",
      "type": "Lifecycle",
      "definition": {
        "actions": {
          "snapshot": { "delete": { "daysAfterCreationGreaterThan": 90 } },
          "version": { "delete": { "daysAfterCreationGreaterThan": 90 } }
        },
        "filters": { "blobTypes": ["blockBlob"] }
      }
    }
  ]
}

The day values are placeholders, not recommendations. Derive them from observed access evidence and the user's retention requirements. daysAfterLastAccessTimeGreaterThan requires last-access tracking; verify it through ARM MCP or the Storage Resource Provider API fallback. If that evidence is unavailable, leave the recommendation unresolved.