In the PowerShell model of deployment, AirWatch adopts a PowerShell administrator role and issues commands to the Exchange ActiveSync (EAS) infrastructure to permit or deny email access based on the settings defined in the AirWatch Console.
PowerShell deployments do not require a separate email proxy server, and the installation process is simple. Once installed, AirWatch sends commands to PowerShell in accordance with the established email policies, and PowerShell executes the actions. The PowerShell model is for organizations using Microsoft Exchange 2010,2013, 2016, or Office 365 environments.
The diagram highlights the communications flow for an implementation with Office 365. For Office 365 implementation, AirWatch does not recommend routing the PowerShell traffic through the VMware Enterprise Systems Connector.
Exchange 2010/2013/2016 for AirWatch Cloud-Based Deployments
The following diagram highlights the communications flow for a cloud-based implementation with hosted Exchange 2010/2013/2016 deployments. AirWatch recommends installation of one VMware Enterprise Systems Connector per MEG Q server to avoid processing delays.
Exchange 2010/2013/2016 for AirWatch On-Premises Deployments
The following diagram highlights the communications flow for an on-premises implementation with hosted Exchange 2010/2013/2016 deployments.
If you want to enable PowerShell with an outbound proxy, then you need to configure WinHTTP on the AirWatch server to use the proxy. AirWatch automatically uses WinHTTP proxy configuration to establish a PowerShell session.