So we have a very similar setup.  We have a vmx100 in Azure.  We have a route table that is tied to the nsg and the route table has the 0.0.0.0/0 route pointed to the vmx100 internal IP which allows us to route all machines tied to the nsg back to our companies primary internet drain and that works, however - I can not get an internal azure IP tied to this nsg to NAT back out externally to our primary firepower that is tied to our public IPs that we want to use.  This is super frustrating.  Either I am missing something or this is just not supported my Meraki or Azure?  I have had Meraki look at this and Cisco TAC and both agree we see everything passing inbound all the way to our Azure vmx100 interface on the site to site vpn but we never see any return traffic.  So either Meraki is attempting to pass this out the public ip of the vmx100 (no packets are captured on this interface either) or azure is not able to accommodate this type of routing when an internal IP is attempting to go back out to a certain public IP that live out in the great big world.  Super Frustrated!!   Edit - We do NOT want to use Azure Firewall! ... View more

Yeah i checked VirusTotal also - very odd - sure hope its a false positive. ... View more

Yep - I am seeing this as well.  I shut down the port the flagged pc is on but don't know the extent of what else this is.  Is this really a windows 10 update to the store????? ... View more

We are using Nagios (snmp) works well.  We are trying to use Solarwinds for Netflow and Syslogging, but have run into a source issue from the MX:   Re: Meraki and netflow with Solarwinds So I am experiencing a similar issue with Solarwinds not receiving Netflow or Syslogging, Through packet captures thou it appears that if you have multiple vlans configured the MX is not using the native vlan as the source.  Once i removed all other vlans from the site to site vpn, i started to see netflow traffic and syslog messages.  Is there something I can do on the dashboard to correct this behavior so netflow and syslogging are being sourced from the native vlan? ... View more

So I am experiencing a similar issue with Solarwinds not receiving Netflow or Syslogging, Through packet captures thou it appears that if you have multiple vlans configured the MX is not using the native vlan as the source.  Once i removed all other vlans from the site to site vpn, i started to see netflow traffic and syslog messages.  Is there something I can do on the dashboard to correct this behavior so netflow and syslogging are being sourced from the native vlan? ... View more