FOR MSPS AND INTERNAL IT TEAMS / EARLY ACCESS

Cloud changes.
Clear next steps.

Bring retirement notices, configuration findings and version lifecycle evidence into one review. Keep the source, give the work an owner and leave with a plan you can explain.

Review one estate free →Explore the fictional review

No card or cloud connection needed. Start with fictional data or an anonymised CSV.

Cloud configuration preview · live collection is not enabled.

One estate reviewFICTIONAL EXAMPLE / NO LIVE CLOUD VERIFICATION

RETIREMENT

Runtime change

Vendor source retained · scope needs review

Needs review

CONFIGURATION

Storage access baseline

Expected setting recorded · owner assigned

Planned

VERSION EVIDENCE

Application API version

Declared by the team · dated rule attached

Needs review

ACCOUNT NOTICE

AWS Health change

Fictional matched resource · follow-up recorded

Open

ONE WORKSPACE FOR THE PEOPLE RESPONSIBLEMSP customer portfolios →Internal IT teamsCompany groups

FOUR REVIEWS. ONE WORKING RECORD.

Know what needs a decision.

See exact coverage →

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.

FROM EVIDENCE TO FOLLOW-THROUGH

The finding is
the starting point.

A notice, a version warning or a changed setting still needs a decision. Confirm the scope, agree who owns it and keep the evidence for the next reviewer.

Arctic Parade connects that work across your estates. A passing observation does not silently close a task, and accepting a risk does not erase the technical warning.

Follow the product workflow →

A REVIEW YOUR TEAM CAN PICK UP

Review. Decide. Keep the record.

Bring the evidence

Start with an inventory, a declared version or a fictional cloud scenario. See what the evidence covers and what is missing.

Agree the next action

Assign an owner and internal date. Record the decision and what will demonstrate completion.

Prepare the review

Produce an estate report. Paid teams can coordinate campaigns, approve review packs and prepare ticket handoffs.

WORK ALONGSIDE YOUR EXISTING TOOLS

Keep the source.
Add the working plan.

Continue using Azure Advisor, vendor notifications and your service desk. Arctic Parade keeps their review context beside ownership, internal dates and completion evidence.

Where Azure Advisor and Arctic Parade fit →

Read the access and security boundaries →

SOURCED MICROSOFT RETIREMENT CATALOGUE

Open the original notice.

Browse notices →

Microsoft

Catalogue matches are review candidates. Coverage is not exhaustive; no matches is not an all-clear.

BEFORE YOU START

Know what you are evaluating.

What can I try without a cloud account?

Create a free workspace, explore fictional estates or import a small anonymised CSV. Review retirement candidates, declare API/runtime versions, assign owners and prepare an estate report. Fictional configuration and AWS Health scenarios need no cloud credentials.

What is included for Azure and AWS?

Selected configuration checks, reviewed lifecycle rules and AWS Health notice matching are implemented in preview. Live Azure and AWS configuration collection is disabled pending authorised account validation. Coverage and permission requirements differ by provider.

Why use this alongside Azure Advisor?

Advisor supplies Microsoft recommendations. Arctic Parade adds a shared review process across estates: evidence, decisions, owners, internal dates, campaigns and reports. Keep the original vendor notifications in place.

Does Arctic Parade make changes to my cloud?

No. Cloud adapters request read-only inventory or metadata. Your team reviews findings and carries out changes through its existing change process. Customer communications are drafts and are not sent automatically.

Can members see every estate in a workspace?

Yes. Workspace roles apply across its estates. There are no customer-specific member restrictions or external customer approval portal in this release.

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.

Create a free workspace →Compare plans