Hi Jenn, The ask would be to remap any discovered site tags to existing Meraki networks, not just to the networks it auto creates. Example: We have site tags building01 and building02, upon sync of the WLC, if the cloud monitor integration has not seen these site tags before it will create a new networks for each with the naming convention [wlc_network_name]-[site_tag], e.g. campuswlc-building01 and campuswlc-building02 We may already have Meraki networks for these buildings with other devices populated (perhaps containing cameras and switches as an example, things that are not as easily moved as APs) and would like to have the WLC APs synced into those networks instead. It would be (really) nice to instead have a third option for WLC AP network placement. I see this as where we can learn the site tags from the WLC, but not create new networks automatically, i.e. just have newly discovered APs sit in org inventory upon discovery from WLC. Then admins will need to go to a page under the WLC network which shows all the discovered site tags for the WLC and then can manually choose to either A) map the site tag an existing network from drop down, or B) create a new network on the fly and map the site tag to that, then APs are moved to the target networks.
... View more