ARCTIC PARADE / PRACTICAL GUIDANCE
Your first useful estate review.
Start with fictional data or an anonymised CSV. Review the evidence and leave with an owner, a next step and an estate report.
1. Create the right workspace
Choose an MSP, company or company-group workspace. Members can see every estate in that workspace, so use the boundary deliberately. Start with fictional or anonymised data while evaluating.
2. Explore the fictional workflow
Open a sample estate to review sourced retirement candidates. In configuration review, try fictional compliant, deviating and permission-denied scenarios. No cloud credentials are needed and samples do not use your real estate/resource allowance.
3. Bring a small inventory
Use the inventory CSV template and recognised technology reference. Customer and Technology are required; stable Resource_ID values help later imports update the same resources. Current inventory limits are 5,000 rows and 2 MiB per file. Removing a CSV row is not a deletion instruction.
4. Review versions and selected settings
Declare a supported API/runtime version against an identified resource, or import declarations from its own template. Read the reviewed source and date. For configuration, approve a baseline before comparing evidence. Keep declared values, fictional examples and actual provider observations distinct.
5. Give the work an owner
Open the finding or lifecycle review, record the decision and assign an owner and internal date. A passing observation does not automatically close human work. Use completion evidence, and keep unknown or stale evidence visible.
6. Prepare the report
Open the estate report and use Print / Save as PDF. Paid teams can coordinate campaigns, prepare internal review packs and ticket handoffs. Communications remain drafts until your team reviews them; they are not sent automatically.
7. Connect only after scope and readiness are agreed
Cloud connection access is separate from workspace login. Adapters are implemented, but authorised live-account validation remains outstanding. Azure/AWS configuration collection is currently disabled by the platform. Review coverage, permissions and connection consent before any later live use.