![]() ![]() For example, client applications commonly use direct user access and basic or NTLM authentication, whereas a service application likely uses impersonation for mailbox access and OAuth authentication. ![]() What might change from one application to the next is the mailbox access and authentication mechanism. For example, an application that synchronizes contact information from Exchange into a CRM application.Įach of these application models can use a common code base to retrieve information from Exchange - so you don't need to change the EWS code used to retrieve item information between a client, portal, or service application. Service applications - Background jobs used to integrate or synchronize data from Exchange into an existing system. A SharePoint web part that retrieves Exchange data is an example of a portal application. Portal applications - Applications that extend an existing web page by including information retrieved from Exchange, such as free/busy or contact information. Outlook and Outlook Web App are examples of client applications. The EWS and Exchange architecture provides a uniform development model that you can use to create the most common types of applications in a consistent way, including the following:Ĭlient applications - Standalone applications that use EWS to access Exchange data. Find out about the most common types of applications that you can create by using EWS in Exchange.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |