Within AIOps there are many integrations available, one of which is the Microsoft Exchange Web Services (EWS) Probe. Due to the EWS API being deprecated, a new Microsoft Graph Email Probe which leverages the Microsoft Graph API is being released which customers can migrate to. The Microsoft Graph Email Probe is being released separately to assist customer’s as they migrate from the EWS Probe.
Before migrating, it is important to check the Graph Email Probe documentation for any changes in properties, notably:
- ResyncInterval: Should not be set to 0, this will stop the probe from retrieving emails due to a change in the model used to fetch emails.
- FolderName: No longer supports paths, this does not limit the probe from monitoring subfolders. Set to the name of the target folder.
- ServiceURL: Set to
https://graph.microsoft.com/v1.0
- Scope: Set to
https://graph.microsoft.com/.default
Ensure the application has admin consent for the application type Mail.ReadWrite permission. It is strongly recommended that the configured user and Object Server which the probe will run against do not contain live data as customers migrate.
To begin migrating, first shutdown any running EWS Probe instances before starting the Graph Email Probe in case of potential interference and to ensure minimal downtime when migrating, as seen below.
Note: When migrating from a peer-to-peer (P2P) setup. Start by shutting down the backup EWS probe instance, once the backup is down, shutdown the primary EWS probe instance. When starting the Microsoft Graph Email Probe, first, start probe intended as the primary instance, once the primary instance has started, the backup probe can be started.