Do you have an Android Enterprise Binding associated with your instance and the enrollment rule that you're using for AE? The devices will get a service account assigned to them during enrollment if you have the enterprise binding set up. If the devices are in a firewalled internal network without access out to the Google Play servers then this step can hang (Account Activation Pending). You can either open your network to allow communication from the devices go Google Play or you can skip the Google Account creation during enrollment as part of the Enrollment Rule configuration. Note that the service accounts are what the devices use to download updates from the Play Store so if you skip that step you are effectively committing to an on premise / AOSP style approach. 

That's a good question Matt.  Thank you for the reply.  I'm not sure if I'll make sense here, but....  I believe we used to use binding when we originally started using Soti because we were using phones and we had our own google play store.  We may have taken this out (not sure exactly how to check).  We don't plan on using google play for anything, just pushing the apps we need on the devices.  Do I just need to look into setting up the binding again and they should fix the issue?

If you want to use Google Play for any reason now or in the future (e.g. OEMConfig, WebView updates, Chrome Updates, etc) then you will need to:

• Set up an Enterprise Binding in the Global Server settings
• Associate your Enrollment rule for the devices with that Binding
• Enroll the devices while they are connected to a network that has access to both the SOTI server and play.google.com/work

If you do not intend to ever use Google Play to install anything on the devices then you can simply edit your Enrollment rule and change the Android Enterprise configuration to Skip Account creation.