Based on the current epic template and the latest Microsoft discussion, update the epic in these sections.
1. Key Dependencies
Add this row:
| Feature |
Dependency |
What? |
State |
| Azure Managed Redis adoption and migration |
Microsoft Azure regional capacity |
Availability of the required AMR capacity and suitable migration dates across the requested regions. Confirmation is also pending on the Redis service-extension request for applications affected by capacity constraints. |
Amber – capacity and migration dates pending confirmation from Microsoft |
2. Background & Problem Statement
Background / Current State
Append this to the existing Emerging DB text:
Azure Managed Redis is the Microsoft-aligned replacement for Azure Cache for Redis. However, planned migrations are currently affected by Azure capacity constraints across multiple regions, and suitable provisioning and migration dates have not yet been confirmed for all required instances.
Problem / Need
Add this as point 3:
- AMR adoption and migration timelines depend on Microsoft confirming sufficient regional capacity. Delays in capacity allocation may impact the planned Redis migration deadlines and the overall product-adoption target.
3. Scope – Emerging DBs
Under Migration Assistance for AMR, expand the current entry to:
Migration Assistance for AMR:
- Migration tooling and pipeline support for end users.
- Consolidation of required AMR quantities, regions and migration timelines.
- Coordination with the Microsoft capacity team for suitable migration dates.
- Tracking of capacity blockers and Redis service-extension requests.
- Support in preparing application context and business-impact information for capacity escalation.
For Out of Scope, retain application infrastructure issues and add:
Resolution of Microsoft platform-level capacity limitations.
4. Work & Delivery Approach
Add an Emerging DB row using the following content:
| Field |
Content |
| Platform / DB |
Emerging DBs – Azure Managed Redis |
| Key Deliverables |
AMR migration demand and capacity tracker; confirmed migration dates; capacity-escalation details; service-extension status |
| Approach / Steps |
Collect application-level quantity, region and timeline requirements; document business and customer impact; submit requirements to Microsoft; coordinate suitable migration dates; track capacity and extension decisions |
| Owner / Team |
Emerging DB Pod / Dhirendra Kumar, with Microsoft capacity team |
| Target Date |
Pending Microsoft capacity confirmation |
| Status |
Amber – At Risk |
| Success Criteria |
Required capacity and migration dates confirmed for planned applications, with an agreed mitigation or service extension for any application that cannot migrate within the current deadline |
5. Risks / Mitigations
Keep the existing application-roadmap risk and add a second risk:
Risk: AMR adoption and planned Redis migrations may be delayed due to Microsoft Azure capacity constraints across multiple regions. This may affect the migration deadline and achievement of the product-adoption target.
Mitigation: Maintain an application-level capacity tracker covering quantity, region, required date and business impact. Provide Microsoft with the required justification for escalation, coordinate suitable migration dates, and track the Redis service-extension request for applications that cannot migrate within the current timeline.
Epic status summary
Add this near the beginning of the epic or in the latest status update:
AMR adoption is currently Amber due to Microsoft Azure regional capacity constraints. Required quantities, migration timelines and business-impact details are being consolidated for escalation. Confirmation of capacity dates and the Redis service-extension request remains pending.
The scheduled-shutdown investigation from the Microsoft discussion should be tracked separately under the Cost Optimisation epic, rather than included in this Product Adoption epic.
