CSV workflow available
Retirement reviews
Compare inventory with sourced Microsoft retirement notices. Separate a possible match from confirmed impact, then plan the work.
THE PRODUCT / EVIDENCE TO OWNED WORK
One place to review.
A clear next step.
Bring different kinds of cloud change into the same working process: understand the evidence, agree a decision and follow it through.
FOUR REVIEWS. ONE WORKING RECORD.
Know what needs a decision.
Fictional preview available
Configuration baselines
Agree expected settings for selected Azure and AWS resources. Review deviations and changes with evidence, owners and internal dates.
Declared evidence available
API and runtime lifecycles
Record declared versions and compare supported scopes with reviewed vendor schedules. Keep source dates and follow-up work together.
Fictional preview available
Account-specific notices
Explore AWS Health notices matched to explicitly approved resources. Keep private account evidence separate from the public catalogue.
01 / UNDERSTAND THE EVIDENCE
Keep different signals distinct.
A catalogue match suggests where to investigate. A declared version records what your team supplied. A provider observation reports a setting at a particular time. A private AWS Health notice can add account-specific context. Their strength and scope stay visible; one does not stand in for another.
02 / AGREE THE BASELINE
Review the settings that matter.
Selected Azure checks cover App Service, Storage, Key Vault, networking, diagnostics and VM backup metadata. AWS checks cover security groups, S3 controls, RDS settings, CloudTrail logging and ACM expiry. Approve the relevant baseline before comparing evidence.
Public-IP attachment, explicit diagnostic requirements and supported VM backup review are implemented in the preview. These settings do not prove reachability, log delivery or a successful restore.
See resource scopes and excluded cases →03 / REVIEW THE LIFECYCLE
Review the versions your tools and services use.
Record declared API/runtime evidence against an identified resource or import it from CSV. Current rules cover the Key Vault management API and selected Lambda, EKS and RDS schedules. Each result retains the reviewed source and dates.
The provider-observed AWS version preview covers explicit RDS major engines, managed-ZIP Lambda $LATEST and regional EKS control planes. AWS Health review matches supported private notices to approved resources. Both live collection paths remain disabled pending authorised validation; Health API access also needs an eligible AWS support plan.
How to use version evidence →04 / OWN THE FOLLOW-UP
A result is not a completed task.
Assign an owner, internal date and completion evidence. Keep changes and decisions in the history. Later evidence can reopen work, and expiring administrator risk acceptance leaves the technical warning visible.
Prepare an estate report on either plan. Paid teams add cross-estate campaigns, milestones, execution checklists, internal review packs, communication drafts and ticket handoffs.
Read the fictional estate report →Evaluate the workflow before connecting an account.
Fictional estates exercise compliant, deviating and permission-denied scenarios without cloud credentials. CSV review and declared evidence are available now. Azure, AWS, Google Cloud, DigitalOcean and Freshdesk adapters are implemented; authorised live-account validation is outstanding.
Workspace members can see all estates in their workspace. Microsoft SSO, customer-specific member restrictions and external customer approval links are unavailable.
START WITH ONE USEFUL REVIEW
Give the next step an owner.
Try a fictional estate, review its evidence and prepare a report. No card or cloud connection needed.