LearnGlossary

What are FinOps personas?

Updated 26 October 2026 · Published by Zoorik

FinOps personas are the roles that take part in FinOps, the shared work of managing cloud cost. Each one has its own FinOps roles and responsibilities.

They come from the FinOps Foundation’s FinOps Framework. Microsoft’s guidance builds on it and calls them stakeholders.

Core and allied personas

Microsoft lists 7 FinOps core personas:

  • Procurement buys resources and negotiates contracts.
  • Finance budgets, forecasts and reports on cloud cost.
  • Leadership gets the most business value from the cloud.
  • Business owners drive strategy and budgets.
  • Product owners rank product work by user needs and business value.
  • Engineering teams deliver high-quality, cost-effective services.
  • FinOps practitioners teach, standardize and promote FinOps practices.

Microsoft also names 5 FinOps allied personas: the sustainability, IT financial management, IT service management, IT asset management and security teams.

Who owns which lever

Your cloud cost moves with what you use and the rate you pay. Microsoft’s principles spread usage decisions across teams and keep rate negotiations central.

Engineering teams own usage, a central team owns rates Diagram with no amounts. On the left, a box labelled Engineering teams, drawn as a stack of cards for many teams, and below it a box labelled Central team, with finance and procurement. On the right, one box labelled Your cloud cost. An arrow labelled usage, node counts, disk sizes and idle resources, runs from Engineering teams to Your cloud cost. An arrow labelled rate, contracts, commitment discounts, runs from Central team to Your cloud cost. Engineering teams own usage, a central team owns rates Engineering teamsusagenode counts, disk sizesand idle resourcesCentral teamwith finance and procurementratecontracts, commitment discountsYour cloud cost
Diagram, with no amounts: usage decisions are spread across many engineering teams (the stacked cards are an illustration, not a count), while one central team, with finance and procurement, sets the rate, as Microsoft’s and AWS’s FinOps guidance advises.
  • Engineering teams own usage: node counts, disk sizes and idle resources.
  • A central team owns rates. Microsoft suggests one team or person buys commitments.
  • AWS says finance should advise on commitment discounts.

Why it matters for your cloud cost

  • Engineers can weigh cost only when they see it. Microsoft asks for clear cost data, fast.
  • A discount reduces only the rate. Usage changes reduce your cloud cost by running less.
  • If engineers reduce usage below a commitment, it goes under-used. Microsoft warns that this can lose money, though rarely.
  • The free assessment works out what your clusters and disks could save.

Read next: How to reduce cloud costs

Sources: Microsoft Learn, “FinOps Framework overview” (opens in a new tab); Microsoft Learn, “Rate optimization” (opens in a new tab); AWS, “COST01-BP02 Establish a partnership between finance and technology” (opens in a new tab) (Cost Optimization Pillar).

Find your own number

One line in your cloud console. One PDF report with your estimated saving at list price.

Estimate your saving

Talk to the builders

Thirty minutes with the people who build Coral and Amoeba.

Book a demo (opens in a new tab)

Or write to founders@zoorik.com