Skype Directory search URL isn't working RRS feed

  • Question

  • Hello,

    I'm currently setting up SfB - Skype integration on our business environment using Skype for Business 2015 Server. Our PIC provisioning was completed successfully, but still, nothing seem to work. I've setup using standalone on-premesis server and single edge server.

    I've been looking around and I can't find anything wrong with our settings (I can provide them if needed), but I did find something; In server event logs it's saying 404 error (Event id 62044). After banging my head on the wall, I decided to useSkype Directory search URL https://skypegraph.skype.com/search/v1.0, but as I write this, it just isn't working, simply giving error 404.

    Is this normal, or is there really a some sort of issue on skype's side? I've tripled checked that every required port is open and can be accessed over telnet in correct direction, even outbound 443 skypegraph.skype.com over edge server.

    Also, while running test-CsFederatedPartner test over MSN gives unknown error;

    PS C:\Windows\system32> test-CsFederatedPartner -targetFqdn xxx -domain msn.com -verbose
    VERBOSE: Reading access proxy port from topology process started.
    VERBOSE: Reading access proxy port '5061' from topology process successfully finished.
    VERBOSE: Reading certificate process started.
    VERBOSE: Reading certificate process successfully finished.
    VERBOSE: Searching for certificate with issuer name = 'CN=Go Daddy Secure Certificate Authority - G2,
    OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US' and serial number =
    VERBOSE: Successfully found certificate with the matching issuer name and serial number.
    VERBOSE: Workflow Instance Id '423b605c-ca51-4c57-9e17-78a1aad1e541', started.
    VERBOSE: Command line executed is 'test-CsFederatedPartner -targetFqdn xxx -domain msn.com -verbose'.

    Target Fqdn   :
    Result        : Failure
    Latency       : 00:00:00
    Error Message : 504, Server time-out

    Diagnosis     :

    VERBOSE: Workflow Instance ID '423b605c-ca51-4c57-9e17-78a1aad1e541' completed.
    VERBOSE: Workflow run-time (sec): 0.1561745.

    (And yes, diagnosis is empty, didnt censor it)

    Friday, April 27, 2018 2:39 AM

All replies

  • Hi,

    Would you please tell us did the issue only happen to specific user?

    For this issue, you should double check your firewall settings, you can see the troubleshooting link

    If the issue persists, please disable Skype federation on edge server in topology, publish. Run Setup on edge server.
    Re-enable Skype federation on edge server in topology, publish. Run Setup on edge server.
    For details, please refer to

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Best Regards,
    Alice Wang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, April 30, 2018 1:52 AM
  • Deleted
    Monday, April 30, 2018 9:32 AM