Use case demo

Azure & AI credit usage

Synthetic usage events. Detect budget overrun, unapproved models, shadow spend and weekend spikes. Choice: allow_log / notify_owner / suspend_key_request.

Synthetic demo Proposed design
Shared mailbox · service desk Synthetic demo Proposed design
Inbox · synthetic items
    RulesPolicy in code
    JevChoice · Score · Noul
    Frontier LLMDraft only
    HumanAccountable action
    Inputs

    Select a message.

    Jev + rules

    Judgments appear here.

    Outputs

    Tickets, drafts, queues.

    Pilot card

    What a first pilot of this decision needs. Proposed design, not a measured result.

    DecisionWhich cost lines need a FinOps look this week?
    State Jev seesCost line, resource tags, owner, budget, trend summary, change notes.
    Questions
    • Noul Does the line look like unmanaged or shadow spend?
    • Score How unusual is the movement against its own history (1–5)?
    First action code may takeFlag the line to the resource owner with the tag gaps listed.
    Stays with a personStopping, resizing or deleting anything.
    Measure firstFlags that lead to a saving or a tag fix; false-alarm rate.
    Microsoft surfaceCost Management export to Fabric; weekly pipeline; Teams card to owners.
    Out of scopeAuto-shutdown or auto-spend.