Android for Work requires setup through the AirWatch Console before anyone can start using it. There are two ways to configure Android for Work: by using an Android for Work account (preferred) or using a Google account (recommended by Google for G Suite customers).

An Android for Work Account is used when your business does not use G Suite and allows for multiple configurations of Android for Work within your organization. AirWatch manages this account and requires no Active Directory sync or Google verification.

Setting up Android for Work using Google-managed domain requires your enterprise to set up a managed Google domain and must follow a verification process to prove that you own the domain. This domain can only be linked to one verified Enterprise Mobility Management (EMM) account. Consider creating a Google account specifically for Android for Work for your organization to use so as not to conflict with any existing Google accounts. The setup includes creating a Google Service Account and configuring AirWatch as your EMM provider.

The Google Service Account is a special Google account that is used by applications to access Google APIs and is required when setting up Android for Work using the Google Accounts method for your enterprise. The Google Service Account credentials are automatically populated when configuring Android for Work Accounts. If you encounter an error while setting Android for Work Accounts, clear your settings in the AirWatch Console and try again or create the account manually. For Google Accounts, consider creating your Google Service Account before either setup method.

To change the Google account or make changes to your admin settings, you have to unbind the account from the AirWatch Console.


The setup of Android for Work includes the integration of third-party tools that is not managed by AirWatch. The information in this guide for the Google Admin Console and Google Developer Console has been documented with the available version as of January 2017. Integration with a third-party product is not guaranteed and is dependent upon the proper functioning of the third-party solutions.