Microsoft is preparing to inject AI directly into the social fabric of its Viva Engage platform, with community agents now slated for general availability in September 2026. The move, detailed in Microsoft 365 Roadmap ID 499898, will place a persistent, AI-powered assistant inside individual communities to answer employee questions using approved organizational knowledge. It’s a significant shift from Copilot as a personal productivity tool to a shared, public-facing participant in workplace discussions.
What’s actually changing?
Viva Engage – the enterprise social network that evolved from Yammer – will soon let community administrators activate an AI agent for any given group. Once enabled, the agent monitors the community for new questions that haven’t received a satisfactory answer. It then drafts a response using only material that the community’s members are allowed to see: conversations, posts, files, and any explicitly connected SharePoint libraries.
The agent doesn’t scour the open web. If it can’t find sufficient grounding material within the community’s knowledge boundaries, it simply stays quiet. When it does answer, it includes citations that link back to the source posts or documents, letting readers verify the information themselves.
During the public preview that started in September 2025, the agent checks about every 15 to 20 minutes for unanswered questions, skipping threads older than 14 days and those already marked with a Best or Verified answer. Community owners can choose between automatic posting or a mandatory human review workflow, where designated experts approve, edit, or reject drafts before they appear under the agent’s name. Approved responses can carry a verification badge, signaling that a person has signed off on the content.
General availability is now targeted for September 2026 for standard multi-tenant Microsoft 365 environments. Government and sovereign clouds aren’t included in this timeline – yet. And as with any roadmap date, it could shift if testing reveals issues.
What it means for you
For everyday employees
If your company uses Viva Engage communities, you might soon notice an “agent” answering questions alongside your human colleagues. You won’t need a Copilot license yourself to see its responses. For routine queries – where to find the latest sales deck, how to request VPN access, or what the travel reimbursement policy is – the agent could deliver an immediate, sourced answer. That means less waiting for a colleague to respond, and fewer dead-end searches.
But don’t mistake the agent for an infallible oracle. It can only work with the information it’s been given. If your company’s documentation is outdated or contradictory, the agent might serve up confusion. The citation links are your friends – use them to check the original material.
For community managers and experts
Your role will shift from answering the same questions repeatedly to curating the knowledge that powers the agent. That means keeping SharePoint documents up to date, pruning stale threads, and reviewing high-stakes answers. The agent can handle the “what’s the Wi‑Fi password?” tier of queries, freeing you to tackle nuanced discussions, mentorship, and strategic work.
You’ll also need to decide on the approval workflow. For low‑risk communities, automatic posting might be fine. But for groups dealing with payroll, security, legal, or technical procedures, mandatory human review is a must. During the preview, you can see an explanation of how the agent arrived at its draft – a helpful troubleshooting aid, though not a guarantee of correctness.
For IT and knowledge administrators
This feature introduces new governance challenges. Because the agent respects Microsoft 365 permissions, it can only surface what community members already have access to – but that doesn’t mean it’s risk‑free. Before connecting a SharePoint library to a community agent, verify that the library’s permissions align precisely with the community’s membership. An overly broad public community linked to a sensitive document library could create an accidental discovery engine.
Consider information barriers, data loss prevention rules, and conditional access policies. The preview has documented limitations around advanced SharePoint protection and compliance features; audit logging for agent administration is planned for GA, but you may want to track changes manually until that’s confirmed.
Licensing will become tied to Microsoft 365 Copilot once the preview toggle goes away. The administrator who creates the agent needs a license, but unlicensed users can still view the agent’s posts. This asymmetry could let a small number of licensed experts maintain agents whose answers benefit the entire organization – a potentially cost‑effective way to extend AI assistance.
How we got here
Viva Engage’s roots lie in Yammer, the enterprise social network Microsoft bought in 2012. Its core value has always been the informal, conversational knowledge that employees share: troubleshooting tips, policy clarifications, workarounds. The problem was retrieval – that wisdom was buried in threads, hard to search, and easy to overlook.
When Microsoft 365 Copilot emerged, it first focused on individual tasks: drafting emails, summarizing documents. Viva Engage got some of that, but mostly as a private assistant. The community agent concept, first shown in preview last year, represents a deliberate pivot toward group-level AI. Instead of each employee prompting Copilot separately, a single agent operates in a shared space, learning from and contributing to collective knowledge.
This aligns with a broader industry push toward retrieval‑augmented generation – combining large language models with a company’s private data. Microsoft’s advantage is the tight integration with SharePoint, Entra ID, and the Microsoft Graph, which reduces the need to export data to a separate AI platform. But it also deepens platform lock-in.
What to do now
If you’re an IT decision‑maker or community owner, start preparing even though full deployment is a year away:
- Audit your community knowledge. Identify which SharePoint libraries and threads you’d want the agent to use. Clean up outdated content. Resolve conflicting guidance before an AI amplifies it.
- Assess permissions. Run access reviews on any SharePoint site you plan to connect. Ensure community membership doesn’t give broader access than intended.
- Decide on review policies. Map your communities by risk level. For sensitive ones, plan for a panel of experts who will review drafts. Consider using the agent’s reasoning view as part of the approval process.
- Pilot during preview. If you haven’t already, enable the preview toggle in the Viva Engage admin center and test with a low‑stakes community. Document what works and where the agent stumbles – this feedback loop will be invaluable.
- Prepare for the licensing switch. Track which communities have agents and who created them, so you’re not scrambling when the preview toggle disappears and Copilot licensing takes over.
- Educate users. Let employees know that a verified answer has been reviewed by a human, while an unverified post comes straight from the AI. Train them to follow citations and not treat the agent as an official policy voice unless that’s been made explicit.
What to watch next
The September 2026 GA date is a target, not a promise. Keep an eye on the Microsoft 365 Message Center for tenant‑specific rollout details. Look for improvements in auditing, support for more complex SharePoint protection features, and better analytics – community managers will need data on answer accuracy, knowledge gaps, and user engagement to refine the system.
Microsoft is also weaving agents across Teams, SharePoint, and other surfaces. A future update might let Viva Engage agents coordinate with project‑management agents or ITSM tools, blurring the lines between social Q&A and automated workflows. The real test will be whether these agents become trusted members of the community or just generate more noise. As with any AI, the output is only as good as the input – so the cleanup work you do today will pay off when the agent flips the “on” switch next year.