Decision view
The reviewed Azure environment is currently controlled by a very low monthly spend guard. That is the correct first move for a portfolio sandbox: prove the method, prevent accidental cost exposure, and build the evidence pack before creating material cloud usage.
GBP 2 budget guardMonthly cost alert control configured before further activity.
Owner access confirmedThe account can be governed, reviewed and exported for cost evidence.
No material charges yetThe initial review shows the account is not carrying uncontrolled spend.
Next actionGenerate small controlled usage, then export cost data for FOCUS mapping.
Commercial conclusion
The immediate finding is not a savings number. It is a control finding: cloud spend should not be analysed after it has already escaped governance. A budget guard, billing visibility, named owner, and evidence log are the minimum conditions before building the worked-example model.
Recommended next step
- Create a tiny, tagged Azure resource with a deliberate short life.
- Record the budget alert, cost movement and service classification.
- Export the billing data and map it into a FOCUS-ready cost model.
- Update the public portfolio with the before-and-after cost evidence.