Scope reviewed
- Azure account access and subscription readiness.
- Budget guard configuration for controlled experimentation.
- Cost management view readiness.
- Evidence required for a FOCUS-style reporting model.
Findings
| Area | Status | Implication | Next evidence |
|---|---|---|---|
| Budget control | Configured | Spend movement can trigger alerts before it becomes material. | Screenshot and alert receipt once controlled usage starts. |
| Billing movement | No material charges | There is not yet enough activity to calculate savings or waste. | Small tagged usage and export after cost appears. |
| Tagging model | To be applied | Finance cannot allocate cost without ownership and purpose labels. | Tags for owner, service, environment and purpose. |
| FOCUS readiness | Planned | Raw cloud data needs translation into a comparable decision model. | Mapped table with service, charge type, usage date and owner. |
| Governance record | Started | The portfolio can show method and controls before client delivery. | Evidence log updated after each action. |
30-day control plan
- Keep the budget guard active and review alerts daily during test usage.
- Create one low-cost, tagged resource and record the purpose before deployment.
- Export the billing record once Azure cost management reflects the usage.
- Map the export into a FOCUS-ready model and publish the updated portfolio view.
- Delete the test resource and record the closure evidence.
The first paid client version will replace sandbox assumptions with client billing exports, service ownership evidence and written approval of the scope.