none
[Exchange-Online][EWS][SOAP] Cannot retrieve the WSDL for Exchange Web Services RRS feed

  • Question

  • I want to set up test suites using SoapUI for Exchange Online (EWS) on Office365.
    My Office 365 mail and calendar have been properly setup, I can access them using OWA or Outlook2007.
    My other SOAPUI testsuites succesfully talk to Exchange2011 and Exchange2013.

    The blog post How to get services.wsdl for Office 365? at  pointed me to the Microsoft Remote Connectivity Analyzer for determining the actual server for my Office 365 mailbox; it points to https://pod51046.outlook.com/ews/exchange.asmx

    So I tried https://pod51046.outlook.com/ews/exchange.wsdl, as well as https://outlook.office365.com/ews/services.wsdl, but both don't work:

    If I put these into SOAPUI I don't get past the login (SOAPUI keeps prompting me for basic authentication).
    If I put these into the IE address bar I get an endless loop of login prompts.
    This is in 2 different Win7/64 environments.

    Tuesday, October 14, 2014 1:29 PM

Answers

  • Mystery resolved.


    The actual link to use is https://pod51046.outlook.com/ews/***services***.wsdl
    instead of https://pod51046.outlook.com/ews/***exchange***.wsdl (which Oleg's blog actually mentioned, and I overlooked).

    The *EWS endpoint* is https://pod51046.outlook.com/ews/***exchange***.asmx

    The generic https://outlook.office365.com/ews/services.wsdl also works, so I'm using that one now.
    I think that after having read somewhere that the actual URL is a pod... one, I doggedly kept trying that one after resolving it (and actually mistyped that info in my question too, but I can no longer edit it).

    An additional complication why I did not get this correct in the first place:
    SOAP UI asks me 2 times 3 = 6 times for the login credentials when setting up the test project. I just was not persistent enough.

    (Sorry for the ugly ***, what I see as bold while editing does not turn up bold in the final post)



    • Marked as answer by JanDoggen Wednesday, October 15, 2014 3:06 PM
    • Edited by JanDoggen Wednesday, October 15, 2014 3:18 PM
    Wednesday, October 15, 2014 3:05 PM

All replies

  • What error do you get? Are you getting redirected?


    Michael | Microsoft Exchange Developer Content

    The Exchange Development Forum Guide has useful information for using the Exchange Development Forum.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, October 14, 2014 6:28 PM
    Moderator
  • Mystery resolved.


    The actual link to use is https://pod51046.outlook.com/ews/***services***.wsdl
    instead of https://pod51046.outlook.com/ews/***exchange***.wsdl (which Oleg's blog actually mentioned, and I overlooked).

    The *EWS endpoint* is https://pod51046.outlook.com/ews/***exchange***.asmx

    The generic https://outlook.office365.com/ews/services.wsdl also works, so I'm using that one now.
    I think that after having read somewhere that the actual URL is a pod... one, I doggedly kept trying that one after resolving it (and actually mistyped that info in my question too, but I can no longer edit it).

    An additional complication why I did not get this correct in the first place:
    SOAP UI asks me 2 times 3 = 6 times for the login credentials when setting up the test project. I just was not persistent enough.

    (Sorry for the ugly ***, what I see as bold while editing does not turn up bold in the final post)



    • Marked as answer by JanDoggen Wednesday, October 15, 2014 3:06 PM
    • Edited by JanDoggen Wednesday, October 15, 2014 3:18 PM
    Wednesday, October 15, 2014 3:05 PM