Review each estate
Compare inventory and supported lifecycle evidence. Explore selected Azure/AWS configuration and account-notice scenarios without requesting customer credentials.
FOR MSPS / SERVICE LEADS / GROUP IT
Different estates.
One review process.
Give every customer decision a source, an owner and a next step—even when the evidence comes from different cloud services.
Coordinate the work
Assign owners and internal dates. Paid teams can manage shared retirement campaigns, milestones and execution checklists across estates.
Prepare the handoff
Build an estate report and an internally approved review pack. Prepare communication drafts and ticket handoffs through the existing service process.
Manage one Azure retirement across a portfolio—and keep the related work visible.
Continue using Advisor and original vendor notices for their source evidence. Keep a configuration finding, an API-version declaration or a private account notice in its own review context instead of treating every signal as confirmed impact.
Where each tool fits →FOUR REVIEWS. ONE WORKING RECORD.
Know what needs a decision.
CSV workflow available
Retirement reviews
Compare inventory with sourced Microsoft retirement notices. Separate a possible match from confirmed impact, then plan the work.
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.
Evaluate without expanding access first.
Use fictional samples or an anonymised CSV. Cloud and Freshdesk adapters are implemented; authorised live-account validation remains outstanding. Give any later connection a separate, explicit customer scope.
Members can see all estates in their subscribing workspace. Roles do not create customer-specific restrictions. Microsoft SSO and customer-facing approval links are unavailable.
Start with one customer. Expand when the process fits.
The free evaluation supports 1 real estate and 100 shared resources. The £99 monthly founding team plan supports 50 estates and 10,000 shared resources, with up to 25 members on either plan.
Read the offer and founding terms →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.