When using PowerShell and Office365 integration some devices may not properly receive email after changing compliance status. In some cases the Set-CASMailbox PowerShell command issued by AirWatch is not processed properly by Office365. Devices may see this issue after enrollment, after changing compliance status based on preconfigured rules, or when a manual whitelist/blacklist is performed.
Microsoft has provided the following workaround for this issue for deployments integrated with Active Directory: Set the service account used by AirWatch to an on-premise service account that does not have a mailbox. This will allow all commands to complete successfully.
Microsoft has resolved this issue in all environments
Last Update: March 15, 2016 11:24am EST.