📊 Azure Cost Management
Cloud spend as mesh data. Create a Connection, give it a service principal that may READ costs (Cost Management Reader on the subscriptions) and the subscription ids to pull, and fetch a month: one Statement per subscription lands beneath the connection — the month's actual cost, in the currency Azure reports, stamped with the day it was pulled.
- A statement is a snapshot. Azure restates late usage; re-fetching a month overwrites its statement (subscription × month is the identity), and the pull date says how fresh the figure is.
- Nothing polls. A person clicks; the module schedules nothing and holds no background job.
- The secret is content. The connection stores the client secret in its node — keep the connection in a partition only the operators read.
- Built for billing. The MeshWeaver CRM's consumption-priced plans (Azure pass-through, cost + markup) read these statements by subscription GUID and month (Systemorph/MeshWeaver.Crm#114, Phase C).