The Exchange Web Services (EWS) Managed API provides a managed interface for developing .NET client applications that use EWS. By using the EWS Managed API, you can access almost all the information stored in an Office 365, Exchange Online, or Exchange Server mailbox. However, this API is in sustaining mode, the recommended access pattern for Office 365 and Exchange online data is Microsoft Graph
Starting July 19th 2018, Exchange Web Services (EWS) will no longer receive feature updates. While the service will continue to receive security updates and certain non-security updates, product design and features will remain unchanged. This change also applies to the EWS SDKs for Java and .NET. More information here: https://developer.microsoft.com/en-us/graph/blogs/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/
Download EWS Managed API via nuget.
See the following articles to help you get started:
- Get started with EWS Managed API client applications
- How to: Reference the EWS Managed API assembly
- How to: Set the EWS service URL by using the EWS Managed API
- How to: Communicate with EWS by using the EWS Managed API
- How to: Trace requests and responses to troubleshoot EWS Managed API applications
Documentation for the EWS Managed API is available in the Web services node of the MSDN Library. In addition to the getting started links provided, you can find how to topics and code samples for the most frequently used EWS Managed API objects in the Develop node. All the latest information about the EWS Managed API, EWS, and related web services can be found under the Explore the EWS Managed API, EWS, and web services in Exchange topic on MSDN.
You need the following to work with the EWS Managed API:
- A C# compiler to build the DLL files. We recommend Visual Studio 2013.
- A mailbox on Office 365 or an Exchange server that is running Exchange Online or a version of Exchange starting with Exchange Server 2007.
- A version of the .NET Framework starting with the .NET Framework 3.5.
Exchange has an active developer community that you can turn to when you need help. We recommend using the Exchange Server Development forum on MSDN, or using the [ews] tag on StackOverflow.
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.