none
Outlook Client Session when switching Identity Providers from ADFS to Ping Federate

    Question

  • Hi, 

    When we migrated our O365 Environment from ADFS to Ping Federate, we noticed some sign in issues with Outlook Client.  It was understood that users would not be able to sign in to their Outlook Client during the migration period.  Once we broke the trust with ADFS and Federate the Trust with Ping Federate, there was a period of time where users using Outlook Client could still not sign in.  Web Browsers worked right away.  The issue seems to be with how Outlook Client handles cached sessions or access tokens. After a variable period of time users can all connect using their Outlook Client but is there a way to force Outlook Client to purge the stale sessions and force it to sign in to O365?

    Thanks,

    Kevin C.

    kconway@****.gov


    Monday, March 18, 2019 6:28 PM

Answers

  • Hi,

    This issue can be closed.  We didn't not encounter it when we switched Identity Providers in our Production environment.  The Outlook Client did not present the issue. 

    Thanks,

    Kevin

    • Marked as answer by Kevin Conway Friday, April 12, 2019 3:56 PM
    Friday, April 12, 2019 3:56 PM

All replies

  • Hi,

    We have helped you cover you email address, please don't forget to cover your personal information next time.

    Considering Outlook clients can sign in at last, O365 can establish the new session with Ping Federate successfully. You could try to create a new Outlook profile. If this doesn't help, the delay may occur during the first communication between O365 and Ping Federate. Since Ping Federate is a third party server, you could contact with the supplier for some useful information.

    Regards,

    Lydia Zhou


    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.

    Tuesday, March 19, 2019 7:37 AM
    Moderator
  • Hi,

    Any updates so far?

    If you have solved your problem, could you share with us? Maybe it will help more people with similar problems. Don't forget to mark it as answer, this will be easy for other community members to find the useful one.

    Regards,

    Lydia Zhou


    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.

    Tuesday, March 26, 2019 9:47 AM
    Moderator
  • Hi Lydia,

    We haven't had any updates on this issue.  There does seem to be something in the Outlook Client token session that must relate to this but still not sure what or how to target it from the client or the Cloud Tenant Admin Console.  We tried removing the Outlook Profile but that did not fix the issue. 

    Thanks,

    Kevin

    Tuesday, March 26, 2019 11:37 AM
  • What alert or phenomenon did you get? Can you explain more about "could not sign in"?

    What about use the online mode? The same issue with the cached mode?

    Regards,

    Lydia Zhou


    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.

    Thursday, March 28, 2019 9:53 AM
    Moderator
  • Hi,

    This issue can be closed.  We didn't not encounter it when we switched Identity Providers in our Production environment.  The Outlook Client did not present the issue. 

    Thanks,

    Kevin

    • Marked as answer by Kevin Conway Friday, April 12, 2019 3:56 PM
    Friday, April 12, 2019 3:56 PM