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-6040746 : US2 : Travel : Issue Identified and Resolved

    10 July 2025 | 4:45 pm

    In the US2 Data Center, travel bookings using the New Concur Travel through the SAP Concur website and SAP Concur mobile app were 10% below expected level. Affected users may have encountered no rates or an error when attempting to complete the travel search and book workflow for all travel segments. The Incident Response Team downgraded a business service tier to a previous version 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 : Root Cause Analysis

    10 July 2025 | 1:14 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. An update deployed to the authentication workflow to migrate single sign-on services still using a legacy SAML endpoint to the current one due to a code defect that had not surfaced during testing resulted in some SSO Identity Providers returning an error and in a failed user log. The Incident Response Team deployed an update to use the encoding that was required for these Identity Providers. This resolved the issue and allowed the logins to authenticate successfully. The following corrective actions were identified: -Deployed an update to use the encoding required by some Identity Providers -Add additional tests to validate SSO response matches encoding requirements for all identity providers