Standalone Sentry setup for real-time push notifications

the following sections provide the authentication to the exchange and ews service and the supported standalone sentry setup • exchange, real time push notifications, and standalone sentry setup docid 9brbuy ltsr8bagw4etqv • ews service and standalone sentry setup docid 9brbuy ltsr8bagw4etqv exchange, real time push notifications, and standalone sentry setup the following table shows the standalone sentry setup based on the required authentication and whether you are deploying real time push notifications what is the authentication to exchange? do you want real time push notification? supported standalone sentry setup basic, ntlm no enable activesync on standalone sentry basic yes enable activesync and apptunnel on standalone sentry set up an apptunnel service to tunnel exchange web services (ews) device user experience device users are prompted for user name and password for authentication to ews basic yes enable apptunnel on standalone sentry set up an apptunnel service for to tunnel exchange web services (ews) and exchange activesync (eas) traffic device user experience device users are prompted for user name and password for authentication to ews and exchange activesync (eas) basic yes set up per app vpn with tunnel email+ must be an mdm managed app so that it can use tunnel device user experience device users are prompted for user name and password certificate no enable activesync on standalone sentry certificate, ntlm, modern auth yes setup per app vpn with tunnel email+ must be an mdm managed app so that it can use tunnel if you are using certificates for authentication the certificate chain (root and intermediate) must be trusted by the exchange server the certificate can be issued per user by a third party ca or adcs on exchange the certificate is configured as a key value pair in the email+ configuration in the uem for modern auth, standalone sentry setup is supported the pkcs 12 and x 509 certificates should be configured on ivanti epmm modern auth uses adfs that is exposed to the internet the apptunnel sentry rules should be set to \<any> for adfs company com on ports 443 and 49443 device user experience device users are not prompted for authentication ews service and standalone sentry setup the following table provides the supported authentication methods to the ews service setup basic auth certificate auth ntlm auth modern auth activesync + apptunnel yes uses apptunnel for ews no no no apptunnel only yes uses apptunnel for ews and eas no no no tunnel yes yes yes yes no sentry yes yes yes yes