Hi,
If you're using the VA, this will only be applicable for DNS policies in Umbrella.
Now with Secure Connect, you have a way to easily route all traffic (ie. tunnels, web) to Umbrella for additional inspection. SAML can be used for identity for policies for web traffic.
You should have a bit of flexibility now including:
- setting up DNS policies by SSID on APs
- configuring DNS policies by AD user/group using the VAs you've already configured
- setup Web policies for users on SAML ID after configuring your MXes to send all traffic to Umbrella through the "sites" interface via Secure Connect
If you are considering sending all the traffic to Umbrella for inspection and using SAML then the VAs may no longer be needed in your environment. You may also have segments in your network where you want to configure DNS policies for AD users/groups and the VAs may be useful here.
If you're using the VAs for internal domain resolution, and using the MR/MX Umbrella integration (https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Manually_Integrating_...) you'll want to make sure you include your internal domains in the appropriate location so they aren't sent to Umbrella for resolution.
Hope this helps!