Viva Engage pinned-links page briefly loads then redirects to /all – pinned resources not accessible for some users

Question

Viva Engage pinned-links page briefly loads then redirects to /all – pinned resources not accessible for some users

Filip Scibor 0

Hello,

We are experiencing an issue in Microsoft Viva Engage with the community pinned resources page.

When users open the following URL:

https://engage.cloud.microsoft/main/groups/<group-id>/pinned-links

the page briefly displays the list of pinned links (approximately 30 resources) and then automatically redirects to:

https://engage.cloud.microsoft/main/groups/<group-id>/all

The behavior is inconsistent:

Some users can access the pinned links page normally.
Other users see the list for a second and are then redirected to /all.
The issue occurs in both Microsoft Edge and Google Chrome.
The issue also occurs in InPrivate/Incognito mode.
In one test, the page displayed about 20 links and a Show more button, but clicking Show more redirected the user back to the community feed (/all).
The problem affects only some users in the same tenant/community.

Has anyone seen a similar issue with the pinned-links page, pinned resources, or recent Viva Engage navigation changes?

Is this expected behavior related to a recent rollout MC1384422, or is there a known workaround to ensure all pinned links remain visible and accessible?

Thank you.

Filip Scibor 0 Reputation points

2026-08-10T08:24:50.28+00:00

We analyzed the browser network trace (HAR) and found that the new pinned-links page loads items in batches of 20. The first batch loads fine, but when it tries to fetch items 21+, the server returns an error (SERVER_ERROR: "Field temporarily unavailable"). The page then crashes and redirects to /all.

Most probably this is caused by the MC1384422 rollout (new design/navigation): a user in our tenant who still has the old Viva Engage design can view and manage all pinned links without any problem. The old design expands pinned links inline on the community page without pagination. The new design introduced a separate /pinned-links page with pagination — and that pagination is broken.

This also creates a deadlock: you can only delete pinned links from the /pinned-links page, but that page crashes, so you cannot remove items to fix the problem.

The backend data is fine — other queries load all pinned links correctly. The bug is only in the new paginated page.

Correlation IDs: [Moderator note: Personally Identifiable Information removed] / [Moderator note: Personally Identifiable Information removed] (2026-08-10T07:09:06Z). HAR file available on request.

1 answer

Your answer

Filip Scibor 0 Reputation points

2026-08-10T08:24:50.28+00:00

We analyzed the browser network trace (HAR) and found that the new pinned-links page loads items in batches of 20. The first batch loads fine, but when it tries to fetch items 21+, the server returns an error (SERVER_ERROR: "Field temporarily unavailable"). The page then crashes and redirects to /all.

Most probably this is caused by the MC1384422 rollout (new design/navigation): a user in our tenant who still has the old Viva Engage design can view and manage all pinned links without any problem. The old design expands pinned links inline on the community page without pagination. The new design introduced a separate /pinned-links page with pagination — and that pagination is broken.

This also creates a deadlock: you can only delete pinned links from the /pinned-links page, but that page crashes, so you cannot remove items to fix the problem.

The backend data is fine — other queries load all pinned links correctly. The bug is only in the new paginated page.

Correlation IDs: [Moderator note: Personally Identifiable Information removed] / [Moderator note: Personally Identifiable Information removed] (2026-08-10T07:09:06Z). HAR file available on request.

Answer 1

Hi @Filip Scibor,

Based on the behavior you've described, this does not appear to be expected functionality for community pinned resources.

I tested the feature in my environment by accessing the/pinned-links URL for a Viva Engage community, and the page remained accessible without redirecting to/all, so I was unable to reproduce the issue. This suggests the functionality itself is still supported and that the behavior may be specific to certain users, communities, or service configurations.

The fact that the/pinned-links page initially loads and displays the resources before redirecting suggests that the content is being retrieved successfully, but a client-side navigation or feature evaluation is subsequently redirecting the user to the community feed (/all). The fact that only some users are affected within the same community also makes this look less like a permissions issue and more like a rollout, configuration, or service-side behavior.

Regarding MC1384422, Microsoft is currently rolling out a simplified Viva Engage navigation experience that changes community navigation and consolidates some modules. However, the published information does not indicate that pinned community resources or the/pinned-links page are being removed.

To help narrow down the cause, I'd recommend the following tests:

Compare an affected user and an unaffected user:
- Community membership and role (Member vs. Admin)
- Assigned Microsoft 365/Viva licenses
- Whether both users see the same Viva Engage UI experience
Test direct access to: https://engage.cloud.microsoft/main/groups/<group-id>/pinned-links and note the exact URL after the redirect occurs.
Test the same community in:
- Viva Engage on the web
- Viva Engage within Microsoft Teams
- Another device, if available
If possible, add a new test user to the community and verify whether they can access the pinned resources page.
Since you observed a Show more button before the redirect, it may also be worth checking whether the issue is triggered when Viva Engage attempts to load additional pinned resources.

At this point, I would suspect either a service-side issue related to the ongoing navigation rollout or a feature-flight difference affecting a subset of users. If the issue continues, I recommend opening a Microsoft support case and providing the community ID, affected user UPNs, HAR traces, and a screen recording showing the redirect behavior. This would help determine whether affected users are receiving a different Viva Engage experience or configuration.

Note: To open a support case, you must have the appropriate Microsoft 365 administrator role. If you are not an administrator or are unsure who your Microsoft 365 admin is, please refer to Microsoft's official guidance on finding your admin contact: How do I find my Microsoft 365 admin? | Microsoft Support

Please let me know if you need any further assistance, I'm here and happy to help!

Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Roebe Ta 1,110 Reputation points Independent Advisor

2026-08-10T10:33:58.75+00:00

Thank you for the detailed investigation and for sharing your findings, @Filip Scibor.

Based on the test results and HAR analysis you've provided, this does appear to be a product issue rather than an expected behavior.

At this point, I recommend opening a Microsoft support case and including:

The HAR trace showing the failed RefetchablePinnedLinksContentQuery request.

Community ID(s) where the issue can be reproduced.

Confirmation that the issue reproduces in a newly created community with 21+ pinned links.

Screenshots comparing the old and new experiences.

The impact on pinned-link management when the page redirects to /all.

This information should provide Microsoft engineering with a reliable reproduction scenario and clear evidence of the regression.

Thank you again for posting the root cause and reproduction steps. This will be very helpful for anyone encountering the same issue.