Roadmap item 559107 is listed as Launched in Microsoft’s October 19 roadmap record, with June 2026 as its general-availability month and Worldwide (Standard Multi-Tenant) as its cloud scope. That should not be read as an October launch: Microsoft’s August 28 update to Message Center notice MC1268933, preserved in the Microsoft 365 Message Center Archive, scheduled rollout from mid-June through the end of September 2026. The published rollout window has therefore passed, although the notice itself does not verify availability in every tenant.
Two additions with different jobs
The features serve complementary purposes:
- Pinned resources surface important links and files associated with a community.
- Related communities help members discover other relevant Viva Engage communities.
Microsoft says both are enabled by default, with no changes to existing administrator policies or configurations and no deployment action required. This is specifically an update to Viva Engage communities inside Teams for iOS—not a new pinning feature for ordinary Teams chats or channels.
The practical opportunity is straightforward: make the community’s reference shelf useful on mobile, rather than merely making its conversation feed accessible. But a better shelf still needs someone to stock it.
Why related communities might not appear
Here is an important distinction for helpdesks: an absent related-community list does not, by itself, prove that the update is missing.
Microsoft Support’s “Manage a community in Viva Engage” explains that related communities are displayed only when a community administrator has established those relationships. They are curated connections, not a promise that every community will automatically receive recommendations.
For community administrators maintaining those connections, Microsoft documents this procedure:
- Open the community’s settings.
- Select Related communities > Edit.
- Choose a community from the list, or search by its name or title.
- Use Remove to delete an unwanted relationship.
- Close the editor when finished; Viva Engage adds the selected community to the list.
These are Viva Engage administration instructions, not a newly documented sequence of iOS-specific controls. Microsoft advises choosing relationships that make sense for both communities.
Give pinned resources a useful landing point
Microsoft Support’s “Manage pinned links and files in Viva Engage” also provides an existing way to prepare community resources. As a community administrator, navigate to the community you want to maintain, then:
- Locate Pinned links and files in the community’s right panel.
- Select Pin link.
- Enter the destination link.
- Add a descriptive title and select OK.
The link should then appear in the community’s Pinned links and files section. Again, this documents community administration; it should not be mistaken for a confirmed Teams-for-iOS editing workflow.
A sensible content review would prioritize current onboarding material, frequently requested reference documents, and clearly named destinations. That is an editorial recommendation, not an additional Microsoft deployment requirement. The goal is fewer “Where is that document?” conversations—not a mobile-friendly museum of expired links.
The takeaway: this is a modest platform-parity improvement with practical value for organizations using Viva Engage through Teams on iOS. Administrators do not need a new configuration project; they need useful resources, intentional community connections, and support guidance that distinguishes missing content from missing functionality. Microsoft’s rollout guidance recommends reviewing those resources and updating user communications or helpdesk documentation where appropriate.