This Microsoft discussion confirms that the AMR capacity issue is still open and should remain reported as an Amber risk. You can now make the epic wording more specific.
Key Dependencies
| Feature | Dependency | What? | State |
|---|---|---|---|
| Azure Managed Redis migration | Microsoft capacity and migration coordination | Required AMR quantities, regions and migration timelines must be shared with Microsoft. Capacity availability and suitable migration dates are pending confirmation from the Microsoft capacity team. | Amber – capacity and dates pending confirmation |
| Redis migration timeline | Microsoft service-extension decision | Confirmation is required on whether the existing Redis service deadline will be extended for applications affected by AMR capacity constraints. | Open – extension request under review |
Risks / Mitigations
Risk: Azure Managed Redis migrations may not be completed within the planned timeline because the required Microsoft Azure capacity and migration dates have not yet been confirmed. This may affect product-adoption targets and applications approaching the existing Redis service deadline.
Mitigation: Consolidate the required capacity by application and region, provide Microsoft with the relevant business impact, KPI and customer-impact justification, and coordinate proposed migration dates with the Microsoft capacity team. Continue tracking the Redis service-extension request and prioritize migrations where capacity becomes available.
Work and Delivery Approach
Add:
Maintain an application-level AMR migration tracker covering required capacity, target region, business impact, proposed migration date, Microsoft capacity status and service-extension dependency. Provide the consolidated requirements and business justification to support capacity escalation.
Current status update for the epic
AMR adoption remains Amber due to Microsoft Azure capacity constraints. Microsoft has requested consolidated capacity requirements, expected migration timelines and supporting business-impact details for escalation. Confirmation of suitable capacity dates and the Redis service-extension request remains pending.
The discussion about scheduled shutdowns is better captured as a separate enhancement or cost-optimization action, rather than as part of the main capacity risk:
Investigate whether AMR supports scheduled shutdown or other cost-saving options for lower environments and assess any impact on reserved or allocated capacity.





0 comments:
Post a Comment