Exchange Web Services (EWS) is a SOAP-based API that is used to access Exchange Online and Exchange Server. Microsoft has announced the deprecation of EWS for Exchange Online in favor of Microsoft Graph API, which provides access to many Microsoft 365 workloads including Exchange Online.
This repo contains tools to help you identify apps within your tenant that are using EWS and help you migrate them to Microsoft Graph API.
M365 provides reports of EWS usage in the Microsoft 365 admin center. This your first port of call to identify apps using EWS. The reports are available in the Microsoft 365 admin center under Reports > Usage > Exchange Web Services (EWS) Weekly Usage for tenants in the worldwide cloud.
If your tenant is in an isolated cloud (e.g. government or sovereign cloud), these reports are not available in the admin center at this time.
The tools in this repo can be used to identify EWS usage in all clouds with access to the Microsoft Graph AuditLog API.
The EWS Usage Reporting tools are located in folder /src/Ews.AppUsage and build on Jim Martin's excellent and versatile scripts for detecting EWS usage in Exchange Online at Exchange App Usage Reporting.
See the EWS App Usage Reporting Readme for more information on how to set up and run the tools.
Once you have identified applications in your tenant using EWS, you can use the EWS Code Analyzer to identify all EWS references in your code and get suggestions for migration to equivalent Microsoft Graph APIs from related documentation and GitHub Copilot.
The code analyzer is a Roslyn analyzer that can be used in Visual Studio and Visual Studio Code. At this time it supports any EWS application built using .NET SDKs for EWS.
The EWS Code Analyzer is located in folder /src/Ews.CodeAnalyzer.
See the EWS Code Analyzer Readme for more information on how to set up and run the tools.
We welcome your feedback on the tools in this repo and also on your migration experience from EWS to Microsoft Graph API. You can provide feedback by creating an issue in this repo or by posting questions on StackOverflow with the tag exchangewebservices.
- Deprecation of Exchange Web Services in Exchange Online
- Microsoft 365 Reports in the admin center – EWS usage
- Exchange Web Services (EWS) to Microsoft Graph API mappings
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.