Hi Meraki, Matthew, 
 
Thank you for your response @Mloraditch 
 
Can there be a "product manager" response as to what the roadmap is estimated to be please? 
 
cisco would normally share some forward roadmap slides in customer / partner events, so is similar available from meraki in this area ? - even if it's an uncommitted ball-park estimate of Q4 2025 to Q2 2026 ?   
 
Azure date 
Azure required Hardware  - so can provide hardware costs 
Launch regions 
TImescales 
 
Any things preventing availability soon? 
 
needs new hardware? - what will it run on ?
bedding in period till know stable? 
drivers?
restrictions on software / routing & features ? 
exclusivity period with other providers /forwarding ? 
does it do routing only & no VPN ? 
sustained throughput figures ? 
 
Whatever the deal is, please say so can think about as either available, 6months, or discount as not available soon, but would be in 3months, 6 months,  1year / 3 years etc. 
 
It's a case of looking at solutions for existing traffic and how to re-engineer, and if this option is something to consider or no chance / look elsewhere.  
vMX-L currently, what alternative options are avialable for traffic plan and design of alternative arrangements.
 
Product guide link you shared [ AWS vMX-XL Deployment Guide  - Last updated Oct 4, 2024] was last updated, almost a year ago. 
 
You would hope there's been some time since then for testing - I am looking for some forward guidance, not "hard" committed dates.  
We can either discount this as an option completely, In the mean time how far do we go down the [split traffic to different devices] path, to reduce the load on existing devices, and what can they realistically take in terms of throughput before users see/ feel traffic issues.  
 
Many thanks
Stuart