Give every Azure resource group an owner, a purpose, and a runbook.
Capture the Azure Portal walkthrough as you tag, document, and hand off. The cost center, the change ticket, and the deprovision steps live one click from the resource — not in a wiki nobody updated.
Ideal for platform engineers and cloud leads inheriting an Azure tenant with no tags, no owners, and no runbooks.
Your Azure tenant is full of resources nobody can explain.
Resource groups created by people who left. Public IPs nobody approved. A storage account that looks expensive but might be load-bearing. Three months from now, the person who can answer “why does this exist?” will be on a different team.
- Resource groups with unclear ownership
- Production, dev, and sandbox tangled in one subscription
- Resources nobody understands — but nobody wants to delete
- Manual portal changes with no record of why
- New hires asking questions only Slack history can answer
The questions a good runbook answers — once.
UIHike doesn't auto-answer these. Your walkthroughs do. Capture each answer the first time someone asks, and the next person finds it where the resource lives.
The documentation layer your Azure governance has been missing.
UIHike doesn't replace Azure Policy, tags, or Cost Management. It captures the processes and decisions around them — every onboarding click, every ownership review, every “why does this exist?” — as walkthroughs that outlive the person who set them up.
Even if you've never written documentation, you can record one. You're already doing the work in the portal — UIHike just captures it.
Record portal walkthroughs as you tag, configure, or hand off. Every click, screen, URL, and note — captured in one step.
Mark up screenshots with boxes, arrows, and callouts. Redact secrets without losing the original — annotations live as layers.
Every publish creates a revision. Step-level comments accumulate so the next owner finds context exactly where it matters.
Public links auditors can open without logging in. PDF, HTML, Markdown, or PowerPoint for everyone else.
What you can capture, step by step.
Anything you do in the Azure Portal becomes a walkthrough. These are the ones teams capture first.
Resource group runbooks
How a new resource group gets created — naming, tags, RBAC, budget — captured the way your team actually does it.
Ownership handoffs
When the original owner leaves, the next owner gets the walkthrough and the comment thread, not a Slack archeological dig.
Quarterly review walkthroughs
Document the review process once. Rerun it next quarter — same steps, fresh screenshots, new comments.
Change documentation
Resized a SKU? Opened a public IP? Capture the change and the change ticket inline, so the audit answers itself.
Decision capture
Why this VM exists, why this storage account is public, why this exception was approved — recorded next to the actual screen.
Auditor-ready exports
Send a public link. Or export to PDF, HTML, or Markdown. No installs, no logins, no follow-up questions.
From the Azure Portal to a published runbook in one session.
You don't leave the portal to document the work. The recording happens alongside the clicks.
- 01
Start a recording
Open the Chrome extension or desktop app. Hit record.
- 02
Click through the work
Tag the RG. Set the cost center. Apply RBAC. UIHike records each step as you go.
- 03
Add the why
Owner, change ticket, justification — written next to the screen they belong to.
- 04
Annotate and redact
Box the field that matters. Blur the subscription ID. Originals stay intact.
- 05
Publish
Public link, team-only, or token-gated. Export PDF, HTML, or Markdown.
What changes when the runbook lives next to the resource.
One walkthrough, six readers. No re-documenting.
One captured runbook serves five different readers. Nobody has to re-document for each audience.
Cloud platform
Capture the canonical way to onboard a resource group, then point every team at the same walkthrough.
Application teams
Find the runbook for your service without paging the platform team. The why is in the doc, not in someone's head.
FinOps
Pin the cost-center reasoning to the resource. When spend spikes, the justification is one click away.
Security & compliance
Send auditors a public link. Redactions handle subscription IDs and secrets without retouching screenshots.
Engineering managers
Onboarding documentation that doesn't go stale because it's tied to the actual portal screens.
Leadership
A walkthrough is a five-minute read. A wiki is a forty-minute hunt. Status updates get easier.
Every revision saved. Every comment kept.
Each publish creates a revision. Step-level comments persist across versions. When ownership changes, the new owner leaves their note exactly where the change happened — not in a thread that disappears with someone's laptop.
- Revision history per published walkthrough
- Per-step comment threads with reactions
- Stable step IDs, so comments survive reorders
Monday: you inherit 47 untagged resource groups.
The previous platform lead left in March. Half the resource groups have no owner tag. Three are running production workloads. Two are sandbox experiments from 2022. You can't tell which is which without paging six different teams.
You open the Chrome extension and start a recording. You walk through one resource group — open the tags blade, set Owner, set CostCenter, set Environment, leave a note about who you paged to confirm. You publish it as the canonical onboarding walkthrough.
By Friday, every team has the link. They tag their own resource groups by following the walkthrough. The next time someone asks “who owns this?”, the answer is in the resource itself — not in your inbox.
Outcomes you can point to in your next quarterly review.
Document the next resource group before you close the tab.
Capture one walkthrough today. By the end of the week, your team has a runbook for the work everyone was already doing — and the why finally lives where it belongs.