SCSM use EWS which will must change to microsoft Graph before retired

RehamHossam-3731 10 Reputation points
2026-02-10T01:15:48.5733333+00:00

Hello Dears,

Please i need Help ASAP.
we find the SCSM use EWS services for Exchange online connector to send, receive emails also external Notification .

 Now EWS services will retired which must need to be replaced with Microsoft graph.

is that normal and possible with Service manager (SCSM) application to replace EWS with Microsoft graph?  also, Can you give me safe steps to change it on Production environment.

Note: Production Environment and its SCSM 2022 with Update Rollup 2

System Center Service Manager

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Scott A Schering 0 Reputation points
    2026-05-26T15:22:57.5933333+00:00

    This AI answer does not work.. Is there an official documented process to migrate System Center Service Manager Connector 4.1 for Exchange off of EWS?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-02-10T01:15:59.12+00:00

    Yes, it is possible to replace EWS with Microsoft Graph in the context of Service Center Service Manager (SCSM). Microsoft has announced the deprecation of Exchange Web Services (EWS) in Exchange Online, and it is recommended to migrate to Microsoft Graph for accessing mailbox and calendar data.

    To change from EWS to Microsoft Graph in your production environment, you will need to follow these general steps:

    1. Assess Current Usage: Identify all the existing functionalities in SCSM that rely on EWS for sending and receiving emails and notifications.
    2. Review Microsoft Graph Capabilities: Familiarize yourself with Microsoft Graph and its API capabilities that correspond to the functionalities you currently use in EWS. Microsoft Graph offers improvements in security, simplicity, and efficiency compared to EWS.
    3. Update Application Code: Modify the SCSM application code to use Microsoft Graph APIs instead of EWS. This may involve changing the authentication method to OAuth and updating API calls to align with Microsoft Graph's REST-based architecture.
    4. Testing: Thoroughly test the updated application in a development or staging environment to ensure that all functionalities work as expected with Microsoft Graph.
    5. Deployment: Once testing is complete and you are satisfied with the results, deploy the changes to your production environment.
    6. Monitor and Support: After deployment, monitor the application for any issues and provide support as necessary to address any problems that may arise.

    It's important to consult the official Microsoft documentation for detailed guidance on migrating from EWS to Microsoft Graph, as well as to ensure that you are following best practices for your specific version of SCSM.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.