A family of Microsoft word processing software products for creating web, email, and print documents.
Hi @DeanH,
Thank you for reaching out and for outlining the behavior so clearly.
Based on your sharing, this behavior is likely an interaction issue with Teams Word files. In fact, there are two same shortcuts that currently overlapping in Teams and Word:
- Word uses Alt + Left/Right arrow for back/forward document navigation
- Teams also uses Alt + Left/Right arrow for its app navigation
So, when a document is opened from Teams, there is a possibility that those keys can be intercepted which can cause the QAT buttons do not work in that cloud-backed file but working normally when open the same file from the local path. Based on my investigation, this behavior was first reported in 2024 in this thread Back/Forward not available in documents from Teams - Microsoft Q&A and once recently in Microsoft Feedback post Back/Forward navigatie werkt niet meer bij interne hyperlinks in Word-documenten die op SharePoint staan (a bit different because files opened from SharePoint but can also considered as opening from cloud storage).
(The user submitted original feedback in Dutch so you can use translator to read his/her feedback in English)
Your observation is accurate and I understand how important this functionality is for your workflow. However, since I work independently of the product team, I don't have visibility into internal design decisions or the ability to adjust how the feature behaves. If this issue is affecting your workflow, I sincerely encourage you to submit feedback directly to the team through the official Word feedback community: Word · Community. The product team doesn't actively monitor issues on this forum, so submitting feedback through official channels ensures that your input is truly communicated to them.
I understand this may not be the answer you were hoping for. As a forum moderator, I don’t have the ability to modify built‑in Excel behaviors, I can only help confirm how the product currently works and make sure you have clear information.
I really appreciate for taking your time bringing this up. I'm sure there are other users who have been in the same situation but don't know where to share their feedback, so hopefully you will upvote this post as helpful if you can. This will help pin the post to the top, making it easier for other users who may be experiencing the same issue to find your post, understand the context, and support your feedback. Your voice matters, and collective feedback is one of the most effective ways to drive meaningful improvement.
Thank you again for your time and for raising this important usability concern.
Wishing you a great day ahead.
Note: If you wish to receive email notifications related to this thread, please follow the steps in our documentation to enable email notifications.