When you ask Copilot in Outlook to summarize your upcoming travel or prepare a briefing for a trip, it may respond with “I cannot find any travel information in your calendar.” This happens even though you have flights, hotel reservations, or car rentals booked and visible in your Outlook calendar. The root cause is that Copilot only reads travel data from specific Microsoft 365 features and third-party connectors, not from standard calendar events. This article explains why Copilot fails to detect booked travel, provides step-by-step fixes to enable travel detection, and covers related issues you may encounter.
Key Takeaways: Restoring Copilot Travel Detection in Outlook
- Microsoft 365 admin center > Copilot > Data sources > Travel: Enable the travel connector so Copilot can read travel confirmation emails and calendar entries from supported providers.
- Outlook > Calendar > Add calendar > From Internet: Subscribe to a read-only iCal feed from your travel provider to make bookings visible to Copilot.
- Outlook > File > Options > Calendar > Calendar options: Enable “Turn on travel time and directions” to let Copilot parse travel-related calendar items.
Why Copilot Cannot Read Booked Travel from Your Calendar
Copilot in Outlook relies on structured data sources to interpret travel information. Standard calendar events that you manually create or that are imported via email invitations do not contain the metadata Copilot needs to recognize them as travel. Copilot looks for travel data in three specific places:
- Microsoft Travel connector: A Microsoft 365 service that extracts travel details from confirmation emails sent to your Exchange Online mailbox. This connector supports airlines, hotels, and car rental companies that send structured confirmation messages.
- Third-party travel connectors: Services like TripIt or Concur that sync travel itineraries into your Outlook calendar via iCal feeds or API integrations.
- Calendar event properties: Events that include a specific travel category, location field with airport codes, or the “travel time” flag.
If none of these sources are configured or populated, Copilot returns the generic “cannot detect travel” message. The most common cause is that the Microsoft Travel connector is disabled at the tenant level or the user does not have a valid license that includes the connector.
How the Microsoft Travel Connector Works
The Microsoft Travel connector is part of the Microsoft 365 service called “Intelligent Services.” When enabled, it scans incoming email for travel confirmation patterns, extracts the relevant details, and creates a structured travel object in Exchange Online. Copilot then queries this object when you ask about travel. The connector supports major airlines, hotel chains, and car rental agencies. If your travel provider is not on the supported list, the connector will not create a travel object, and Copilot will not see the booking.
Steps to Enable Copilot Travel Detection in Outlook
Follow these steps in order. After each step, test Copilot by asking “What is my next trip?” or “Summarize my travel for next week.”
- Verify your Microsoft 365 license includes Copilot and the Travel connector
Open the Microsoft 365 admin center. Go to Billing > Licenses. Select your user account. Confirm the license includes Copilot for Microsoft 365 and Microsoft Travel. If Travel is missing, contact your admin to assign a license that includes it. Only Enterprise E3, E5, and Business Premium licenses with the Copilot add-on include the Travel connector by default. - Enable the Microsoft Travel connector in the admin center
In the Microsoft 365 admin center, go to Settings > Org settings > Microsoft Travel. Set the toggle to On. Click Save. Wait up to 24 hours for the connector to start processing existing travel confirmation emails in your mailbox. New emails are processed within 15 minutes of arrival. - Check your Outlook calendar for travel time settings
Open Outlook. Go to File > Options > Calendar. Under Calendar options, check the box Turn on travel time and directions. Click OK. This flag allows Copilot to treat events with location and time data as travel-related. - Add a third-party travel connector if your provider is unsupported
If you use TripIt, Concur, or another travel management service, add its iCal feed to your Outlook calendar. In Outlook, go to Calendar > Add calendar > From Internet. Paste the iCal URL from your travel service. Name the calendar and click Save. Copilot can read events from subscribed calendars, but only if the events contain clear location and date fields. - Forward a confirmation email that was missed
If a travel confirmation email arrived before the Travel connector was enabled, forward the original email to your own Exchange Online mailbox. Use the original subject line. The connector will reprocess it. Alternatively, ask your travel provider to resend the confirmation. - Test Copilot travel detection
In Outlook, open a new chat with Copilot. Type: “What travel do I have booked next week?” If Copilot returns travel details, the fix is complete. If it still says no travel is found, proceed to the next section.
If Copilot Still Cannot Detect Travel After the Main Fix
Copilot Returns Generic Output Instead of Travel-Specific Data
This happens when Copilot can see calendar events but does not classify them as travel. Ensure each calendar event has a location field with a city name or airport code. Events with blank location fields are ignored for travel queries. Edit the event and add the location manually.
Travel Confirmation Email Was Not Processed
The Microsoft Travel connector supports a limited set of airlines and hotel chains. Check the list of supported providers in the Microsoft 365 admin center under Settings > Org settings > Microsoft Travel > Supported providers. If your provider is not listed, use a third-party connector or manually add the event to your calendar with a clear location.
Copilot Says Travel Feature Is Not Available for Your Account
This error indicates that the Copilot license is not assigned to your user account, or the Travel connector is disabled at the tenant level. Contact your Microsoft 365 admin to verify both conditions. If the admin recently enabled the connector, wait 30 minutes and restart Outlook.
Travel Data Appears in Calendar but Copilot Ignores It
Copilot only reads travel objects created by the Travel connector or third-party integrations. Standard calendar events that look like travel are not recognized. To force recognition, add the event to a calendar that is connected via iCal feed from a supported travel service. Alternatively, ask Copilot to “show my calendar events for next week” instead of asking for travel specifically.
Copilot Travel Detection: Manual vs Automatic Methods
| Item | Manual Calendar Event | Automatic Travel Connector |
|---|---|---|
| Description | User creates or edits a calendar event with travel details | Microsoft 365 service extracts travel from confirmation emails |
| Copilot detection | Only if location field is filled and travel time flag is on | Always detected as travel object |
| Setup effort | Manual entry each time | One-time admin enablement |
| Supported providers | Any provider | Limited to supported airlines, hotels, and car rental companies |
| Real-time updates | User must update manually | Automatic when confirmation email arrives |
For most business users, enabling the automatic Travel connector is the most reliable method. Manual events work as a fallback when your travel provider is not supported.
You can now configure Copilot in Outlook to detect booked travel by enabling the Microsoft Travel connector and adding third-party iCal feeds for unsupported providers. Test the setup with a specific travel query to confirm detection. For advanced control, ask your admin to review the supported provider list in the admin center and consider using TripIt or Concur if your travel agency is not covered.