@DBesa I sell / support both Meraki, ASA, and Sourcefire solutions for customers. In your case I would have recommended keeping the ASA for VPN, and simply moving your primary internet traffic over to Meraki.
I have several customers that still maintain support on their aging ASA5515-ASA5525 firewalls just to provide Anyconnect VPN continuity to their user base, while they have upgraded to Meraki for the default network exit point. It is very simple to point a few routes over to the ASA for Anyconnect and L2L VPN, while keeping the default route pointed at the MX appliance. This provides the best of both worlds, easy cloud managed security with deep VPN solution offerings from the ASA.
Think of the ASA as the swiss army knife that you really don't want to be stranded on a deserted island without, while the Meraki is the sleek speedboat that gets you where you want to go in style.
Not to speak for Cisco too much on the matter, but I am sure that they are well aware of how quickly their ASA business would dry up if they supported Anyconnect on Meraki. I also believe they would experience a massive load of support tickets on their cloud platform that they do not currently have to manage.
Anyconnect has an update schedule that keeps pace with Microsoft updates, while Meraki has a quarterly update schedule. It is unlikely that an appliance deployed software package which requires frequent updates and supports thousands of different settings would be a good fit for a cloud managed appliance.
