You will have to explicitly configure which Anyconnect headend the users will be connecting to.
Such as setup ion your case could look like this:
This could also be working the other way around, but you'll have to keep in mind that there are possible limitations posed by Azure for outgoing traffic from your Anyconnect clients.
Thanks,
But what if we are in a DR scenario where our prem MX goes down and users need to connect to Azure vMX using Anyconect?
Will it be...
For on-premise : https://mx100-whatever-dynamic-m.com/
For vMX Azure - https://mx100-whatever-1-dynamic-m.com/
Something like that? Is there a way to do automatic failover if on prem MX goes down?
I also noticed the below on Reddit....are these solutions possible?
https://www.reddit.com/r/meraki/comments/q7szpt/custom_meraki_hostname/
https://www.reddit.com/r/meraki/comments/dp9hhj/point_dns_a_record_to_meraki_firewall_hostname/
Will this work with Meraki?
So in the profile editor I put
https://mx100-whatever-dynamic-m.com/
https://mx100-whatever-1-dynamic-m.com/
Note we currently have Anyconnect deployed through our ASAs (moving to Meraki), and I don't believe we use .pcf files or anything.
As written above: I'd simply configure https://mx100-whatever-1-dynamic-m.com/ as Backup Server using the Profile Editor and push out that profile via GPO.