Issue with Default Configuration Profile in Android Zero-Touch Portal
Hi Team,
We are facing an issue with the default configuration profile in the Android Zero-Touch (AZT) portal. We have set up a custom configuration profile as the default, but whenever our reseller adds a device in the AZT portal, the devices are getting assigned to the Enterprise Default Configuration Profile instead of our configured default profile.
At the moment, we are manually assigning the correct profiles in AZT, but this is creating additional effort and delays for our IT team and end users. We are unsure where this enterprise default profile is coming from and why it is overriding our custom default profile.
Could you please help us resolve this issue or provide guidance on why the enterprise default profile is taking precedence?
Also, do you have any recommendations other than unlinking the AZT portal from the Workspace ONE portal?
Thanks in advance for your support.