Concur Support & User Guides

Training

Fox World Travel Concur Support Desk

View All Concur Video Demos and Guides on the Fox Portal

Fox World Travel is available to support your Concur questions. Contact support via phone at 608-710-4172 or via chat in the Concur application.

 

Forgot Password?

Submit a request to Concur for a password reset. Your username is your current institutional email address.

New User Registration

Concur registration for new users. Registration is limited to employees. The use of a university e-mail address is required for user name.

Additional Support

Contact your institution’s travel manager for additional support questions.

Sign up to receive Concur outage notifications

Personalized SAP Concur Open Updates

Personalized up-to-the-minute service availability and performance information

  1. OPI-6033417 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Resolved

    26 June 2025 | 3:28 pm

    In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. The Incident Response Team (IRT) rolled back a recent change to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

  1. OPI-6033417 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Status Update

    26 June 2025 | 3:10 pm

    In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.