When travel time does not appear in the calendar, the cause is often one of a few practical checks. This page helps users narrow down the most common reasons before escalation is needed.
Travel Time only works if the tenant has been approved and the user account is active. Start by checking the portal state to confirm that the account is ready for synchronization and that the tenant is shown as active.
If those states are not correct, the issue is usually not the individual meeting. In that case the tenant admin should be involved first.
Not every calendar entry should create travel time. The most common blockers are missing location details, the wrong calendar, or settings that exclude a meeting from travel planning.
Before assuming sync is broken, check the meeting location, your selected calendars and the visible settings in the portal.
Calendar changes are normally picked up automatically, but there can still be a short delay before the travel block appears. That is especially important to remember right after editing a meeting.
Wait briefly, then check the latest successful run in the portal. If needed, trigger one manual sync to test the situation in a controlled way.
Travel time can only be calculated well if the meeting location is usable. Short free-text notes, incomplete addresses or inconsistent location names cause problems much more often than users expect.
If one specific meeting keeps failing, try a fully written address once. That quickly shows whether the issue comes from the meeting content or from synchronization.
If the account looks active, the meeting has a good location and travel time is still missing even after a manual sync, it is time to involve the tenant admin.
Helpful context for that handoff is the affected meeting, the time of the last change and the sync status visible in the portal. That makes the problem much easier to investigate.
User-focused help for Travel Time: what to do when travel time is missing, meetings are ignored or calendar changes do not show up right away.