Exchange module
The Cloud Extender® integrates with Exchange servers and provides complete visibility to all ActiveSync devices that are connected to the mail system.
With the Exchange integration, the Cloud Extender functions in the following ways:
- Queries the Exchange server by using Microsoft PowerShell commands to discover ActiveSync devices and ActiveSync policies.
- Uploads the device list and policy configurations to the IBM® MaaS360® Portal for reporting and management functions.
- Supports all ActiveSync device actions such as approve, block, or remove a device from the mailbox and wipes devices that are initiated by the IBM MaaS360 Portal, either through administrative action or automated rules.
- Supports ActiveSync policy assignments to connected devices.
- Enables Auto-Quarantine to prevent new devices from connecting to Exchange servers. Since existing ActiveSync devices are approved, existing connections are not affected by the quarantine process.
- Supports pre-approval of Secure Mail connections and approval of connections from enrolled devices.
- Supports granular integration against specific mailbox servers and domains.
- Supports automated cleanup of old ActiveSync connections from the environment.
Supported versions of Exchange
- On-Premises: Exchange 2010, 2013, or 2016
- Cloud: BPOS-dedicated (BPOS-shared not supported) and Office 365
Requirements and scaling
The IBM MaaS360 Portal offers a Cloud Extender Scaling Tool at . Enter the number of mailboxes and devices that you plan to enroll for MaaS360 and determine how many Cloud Extenders you might need to support integration with Exchange.
- Gather times for device data does not exceed 60 minutes and averages 25 - 40 minutes for 5,000 devices. Current and average gather times are available on the Cloud Extender Status page in the IBM MaaS360 Portal.
- To determine the number of Cloud Extender instances that you need for your environment, divide the potential number of ActiveSync connected devices by 5,000 and the number of Mailboxes by 10,000 and use the higher of the two values.
- To minimize latency, regional Cloud Extenders might be more appropriate to use.
Item | Requirement |
---|---|
Exchange 2010, 2013, 2016, and BPOS-D (for less than 10,000 mailboxes) | Mailboxes: less than 10,000 mailboxes |
Devices: less than 5,000 devices | |
CPU: 2 cores | |
Memory: 8 GB | |
Exchange 2010, 2013, 2016, and BPOS-D (for more than 10,000 mailboxes) | Mailboxes: more than 10,000 mailboxes |
Devices: more than 5,000 devices | |
CPU: Use more Cloud Extenders | |
Memory: N/A | |
Scaling:
For accurate scaling of your environment, see the Cloud Extender scaling document at . |
|
Office 365 using Remote PowerShell | Mailboxes: All / Devices: All |
CPU: 2 cores | |
Memory: 8 GB | |
Scaling: Office 365 supports multiple instances of the Cloud
Extender. Requires multiple service accounts for load distribution for more than 500 mailboxes. For accurate scaling of your environment, see the Cloud Extender scaling document at . |
|
Network traffic | Traffic exchange between the Cloud
Extender and the Exchange server:
|
Traffic exchange between the Cloud
Extender and MaaS360:
|
|
Test metrics (usage based on 1,000 devices):
|
Exchange Integration requirements
Item | Requirement |
---|---|
Version |
|
Service account |
|
Service account Exchange permissions |
|
Role-based access control (RBAC) |
|
Office 365 only |
|
PowerShell |
|
ExchangeOnlineManagement |
|