One big fault I seem to be having with iOS deployments is that no matter how you go about it, you can’t get around without using Apple for some parts of the setup process.
As a test using Meraki as an MDM (Mobile Device Manager), you can’t install a profile with passwords, wifi settings and apps for deployment without manually configuring the iPad’s wifi connection to get online and download the Meraki profile. The setup for that is annoyingly long and makes the task of enrolling iPads en masse repetitive and drawn out. It’s only meant for the average consumer owning one iPad.
Using Apple’s Configurator, you can configure two profiles, one Apple made with the wifi password and then the Meraki with the real setup, but you can’t choose which comes first (at least not by dragging the profiles in order, maybe you can name them alphabetically).
Finally, I was able to setup the Apple normally through the iPad, add the wifi network settings and then make a back up of that iPad and then use that default image for new iPads and finally install the Meraki profile on top of that. It will finally accept the profile through Apple Configurator or online because the wifi password is installed and working.
Sadly, it’s all moot because it seems that Meraki profiles don’t enforce their own settings and even though I chose to require a password to remove the profile, one isn’t needed and can simply be removed by the user. To top it all off, once I did that, it completely locked up the iPad’s Settings app and the whole unit had to be reset.