EWS Managed API

The Microsoft Exchange Web Services (EWS) Managed API 1.1 provides an intuitive managed API for developing client and server applications that leverage Exchange 2010 data and business logic, whether Exchange is running on premise or in the cloud. The EWS Managed API 1.1 makes Exchange Web Services SOAP calls under the covers, so many environments are already configured for EWS Managed API 1.1.

System Requirements
You must have the following items to complete this lab:

• Microsoft Visual Studio 2010
• Exchange Web Services Managed API 1.1 SDK
• Two accounts configured to have Microsoft Exchange mailboxes, referred to as the primary and secondary lab users in this lab.

http://msdn.microsoft.com/en-us/library/exchange/dd633710%28v=exchg.80%29

What do you need in order to use the EWS Managed API?

To use the EWS Managed API, you need to have the following:

• The EWS Managed API, which you can download from the Microsoft Download Center. The EWS Managed API works with all versions of Exchange starting with Exchange 2007 SP1.
  
• A mailbox on an Exchange server that is running Exchange 2007 SP1 or a later version, or Exchange Online Preview. You must have the user name and credentials of the account. By default, direct EWS access is enabled for all Exchange Online Preview plans except for the Kiosk plan.
  
• The .NET Framework version 3.5 or later. Versions of the EWS Managed API starting with the EWS Managed API 2.0 Beta 2 require the .NET Framework 4.
  
• Familiarity with web services and managed programming.

Architecture
Exchange Web Services is deployed with the Client Access server role. Microsoft Exchange Server 2010 clients connect to the computer that is running Exchange 2010 that has the Client Access server role installed in an Active Directory directory service site by using an HTTPS connection. If the target mailbox is in another Active Directory site, the source Client Access server creates an HTTPS connection to the target Client Access server. The target Client Access server obtains the information by communicating over MAPI to the Exchange server that has the Mailbox server role installed and then sends it back to the source Client Access server. If the target mailbox is in the same Active Directory site, the Client Access server uses MAPI to communicate with the Mailbox server to obtain the information. The Client Access server then provides the data back to the client.