Skip to content
All workshops

Private, hands-on workshops with the toolkit maintainers

Securing your cost data: Kusto & RBAC

A least-privilege access model for your cost data, built on Entra groups.

You bring

A running FinOps hub and your org’s access requirements.

We build together

Your access model on Entra groups, worked through and documented as we decide it.

You leave with

A documented least-privilege access model for your cost data, applied through the standard pattern, and a clear view of what stricter controls would take.

Is this for you?

  • More people need cost data than should see all of it
  • Automation queries the hub with more rights than it needs
  • Someone asked who can see contract rates, and it took a week to answer

Decisions we’ll make together

We work through the standard identity-based access pattern for FinOps data: one or more Entra groups with reader access to what an audience actually needs. We cover how that controlled access works through FinOpsHubs.com, Power BI, dashboards, and AI assistants, and what the next level of control costs if you need it.

  • What your hub collects, and whether anything in it counts as PII
  • The standard pattern: Entra groups with least-privilege read access to what an audience needs
  • Controlled access in practice: FinOpsHubs.com, Power BI, dashboards, and AI assistants
  • Segmenting further: separate databases, row-level security, and data masking, and what each costs to operate
  • What ADX and Fabric give you for monitoring, audit logs, and audit trails

What stays with your team

  • A documented least-privilege access model built on Entra groups
  • The standard read-access pattern, applied to your agreed audience
  • A decision on each stricter control: what it would take, and whether you need it
  • The patterns to extend the model as your org changes

What the price covers

Included

The standard identity-based least-privilege pattern: one or more Entra groups given reader access to the FinOps data an agreed audience needs, and how that access works through FinOpsHubs.com, Power BI, dashboards, and AI assistants. PII handling, separate databases, row-level security, data masking, monitoring, audit logs, and audit trails are explained as options, with what each one costs to run.

What we tailor to you

Which audiences you segment, what each of them needs to see, and how the standard pattern maps onto your Entra structure.

If you need more than this

Building a segmented or PII-aware data estate, or an org-wide governance program, is a natural next step, and one we scope with you separately so you can see what it involves before committing.

Related workshops