This documentation is archived and is not being maintained.

Getting delegates by using the EWS Managed API 2.0

EWS Managed API

Last modified: October 13, 2012

Applies to: EWS Managed API | Exchange Server 2007 Service Pack 1 (SP1) | Exchange Server 2010

Note: This content applies to the EWS Managed API 2.0 and earlier versions. For the latest information about the EWS Managed API, see Web services in Exchange.

You can use the Microsoft Exchange Web Services (EWS) Managed API to get a list of the delegates who have permission to act on behalf of an account.

To get a list of delegates for an account

  1. Create a Mailbox object to represent the account for which to list delegates.

    Mailbox mailbox = new Mailbox("primaryAccount@email.address");
  2. Call the GetDelegates method to get the list of delegates for the primary account. In this example, the result will contain detailed permission information for the delegates.

    Collection<DelegateUserResponse> result = service.GetDelegates(mailbox, true);

This procedure assumes that a valid ExchangeService object is bound to the primary user's account, or that the primary user's account is being impersonated.

The following code example shows how to return a list of delegates for an account.

    Collection<DelegateUserResponse> GetDelegates()
      // Bind to the service by using the primary e-mail address credentials.
      ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2007_SP1);
      service.Credentials = new NetworkCredential(user1Name, user1Password, emailDomain);

      // Create a mailbox object that represents the primary user.
      Mailbox mailbox = new Mailbox(user1Email);

      // Call the GetDelegates method to get the delegates of the primary user.
      DelegateInformation result = service.GetDelegates(mailbox, true);
      return result.DelegateUserResponses;

The GetDelegates method in the code example returns a list of DelegateUserResponse objects, one for each delegate that is associated with the primary account.

For information about compiling this code, see Getting started with the EWS Managed API 2.0.

  • Write appropriate error handling code for common search errors.

  • Review the client request XML that is sent to the Exchange server.

  • Review the server response XML that is sent from the Exchange server.

  • Set the service binding as shown in Setting the Exchange service URL by using the EWS Managed API 2.0. Do not hard code URLs because if mailboxes move, they might be serviced by a different Client Access server. If the client cannot connect to the service, retry setting the binding by using the AutodiscoverUrl(String) method.

  • Set the target Exchange Web Services schema version by setting the requestedServerVersion parameter of the ExchangeService constructor. For more information, see Versioning EWS requests by using the EWS Managed API 2.0.

  • Use HTTP with SSL for all communication between client and server.

  • Always validate the server certificate that is used for establishing the SSL connections. For more information, see Validating X509 certificates by using the EWS Managed API 2.0.

  • Do not include user names and passwords in trace files.

  • Verify that Autodiscover lookups that use HTTP GET to find an endpoint always prompt for user confirmation; otherwise, they should be blocked.