Azure Redis Migration Accelerator
Problem
Teams planning Azure Redis migrations need an inventory of their estate and actual usage data before deciding on target capacity and a migration plan.
My contribution
I built the discovery and inventory toolkit to collect resource configuration and usage metrics for assessment, right-sizing, and migration planning.
Key decisions
- Separate lightweight resource discovery from deeper usage assessment so teams can begin with an inventory before collecting sizing evidence.
- Use read-only Azure resource and monitoring interfaces rather than reading cache keys, values, or exporting connection strings.
- Support Python, PowerShell, Bash / Cloud Shell, and Resource Graph workflows so teams can use their existing operational tools.
Evidence
The public AzureManagedRedis repository contains the discovery and assessment tooling. Inventory and usage metrics inform sizing decisions; they do not by themselves validate application compatibility, a cutover plan, or production performance.
Technical detail
This repository provides two structured phases for migration planning. First, a lightweight discovery scan identifies Redis resources, SKUs, configurations, and provisioned capacity. Second, an inventory/assessment phase collects real usage metrics (like ops/sec, used memory, and connections) so migration decisions are based on real consumption rather than guesswork. The tooling supports multiple operational preferences (Python, PowerShell, Bash/Cloud Shell, and Resource Graph queries) and is designed explicitly for read-only access with clear security boundaries (no keys/values read, no connection strings exported).
Challenges & Solutions
Gathering actionable migration data while staying strictly read-only and non-invasive.
Creating a workflow that works for both “quick inventory” and “deep sizing assessment” needs.
Making outputs usable for planning (inventory and metrics) without requiring direct cache access.
Outcomes
A practical, phased workflow for migration planning: “what do I have?” then “how is it used?”
Clear privacy/security guarantees: no cache data reads, no secrets collected, no PII scanning.
Tech Stack
Explore
Philip Laussermair
Global Azure Managed Redis Lead Architect at Redis.