2 MIN 43 SEC PRODUCT WALKTHROUGH / FICTIONAL DATA
Watch the retirement workflow.
Watch the real interface move from a simulated Advisor observation through assessment, evidence, reporting, campaign planning and an internally approved handoff.
The recording below demonstrates the retirement workflow. For the newer configuration, version and AWS Health reviews, use the fictional examples and current coverage guide; those features are not shown in this recording.
Silent recording with embedded explanatory captions and a visible cursor. No production customer data, Azure credentials or live tenants appear.
Jump to a workflow stage
00:05 / START SAFELY
1. Start in a guided workspace
The recording opens the actual onboarding checklist and enters the removable fictional estate. This lets an evaluator learn the workflow without supplying an Azure tenant or customer inventory.
00:17 / TEST A STATE CHANGE
2. Keep evidence separate from conclusions
A simulated recommendation is changed to “disappeared”. Arctic Parade retains the prior observation and keeps the action open for investigation; disappearance alone is not treated as successful remediation.
00:34 / ASSESS & OWN
3. Turn the signal into accountable work
The action queue opens a source-linked retirement. The operator records an owner, internal date, impact state and review notes while the vendor date and observation remain visible.
01:14 / EXECUTE & REPORT
4. Create the checklist and estate report
An evidence-backed execution checklist is started from the action. The estate report then carries the current assessment, ownership, dates, source and coverage caveats into an asynchronous customer or internal review.
01:32 / COORDINATE
5. Build a migration campaign
The retirement becomes a campaign with a service owner, internal target and evidence-gated milestone. Campaign status coordinates the portfolio; it does not overwrite the individual resource assessments.
02:17 / APPROVE BEFORE HANDOFF
6. Freeze and approve the review
A dated monthly snapshot is created and approved internally. Real approved actions can then become communication drafts, ticket CSVs or authorised Freshdesk work. Fictional sample actions remain excluded and no message is sent automatically.
Read the concise video transcript
- Open the onboarding checklist and fictional estate.
- Simulate a recommendation disappearing while preserving the review action.
- Filter the action queue and open the linked retirement.
- Assign Alex Morgan, set an internal target, confirm impact and record the next checks.
- Start the execution checklist and inspect the estate report.
- Create the retirement campaign, assign Service Delivery and add an evidence-gated milestone.
- Create and internally approve the monthly review snapshot.
- Review the controlled handoff options; no fictional action is dispatched.
What the recording demonstrates
It demonstrates the deployed review, ownership, checklist, reporting, campaign and approval workflow with controlled inputs. It does not demonstrate live Azure authentication, completeness of Microsoft coverage, a real customer permission grant or a live Freshdesk notification. Those require validation with an authorised account.
Compare with Azure Advisor · Coverage and limitations · Security boundaries · Support