From Leadership Engagement, Town Halls to Communities: Put Viva Engage to Work at Comms Camp
The best way to learn Viva Engage is not by watching someone else publish another perfectly prepared demo post. It is by starting with a real communications challenge. Maybe you are planning a leadership campaign and want employees to do more than simply read an update. Perhaps you are trying to build a community with a clear purpose, improve an AMA, make a town hall part of an ongoing conversation, or understand what employee questions are telling you. Bring that challenge to Comms Camp, a free, hands-on workshop taking place October 12–13, 2026, at Microsoft in Redmond, Washington. Comms Camp is designed for corporate communications teams and the IT, adoption, employee experience, and community partners who support them. Participants will use Viva Engage, Microsoft 365 Copilot, and practical agent patterns to turn real communications scenarios into reusable plans and workflows. Start with the outcome, not the feature Viva Engage can support leader visibility, employee conversation, community building, campaigns, events, and knowledge sharing. But successful communications programs rarely begin with a list of product features. They begin with questions: Who needs to understand or do something differently? What does meaningful participation look like? Which leader, community, or conversation can create trust? What should happen after employees respond? Which signals will tell us whether the communication worked? Where can AI help without replacing the communicator’s judgment? At Comms Camp, you will start with those questions and use Viva Engage as part of a practical communications plan. What you will work through The workshop takes participants through a complete communications scenario, from the original ask to activation and measurement. Choose your challenge and bring a scenario or select a sample. Define your audience, intended outcome, risks, and the action you want employees to take. Design the Viva Engage activation Determine how Viva Engage, Copilot and other Microsoft products can support the communication. Depending on your scenario, that could include: A leader or executive communication A community activation A campaign moment An AMA or event An employee prompt designed to encourage useful participation A follow-up plan that keeps the conversation moving Turn conversations into signals Publishing is not the finish line. Employee questions, comments, reactions, and event inputs can provide important context about what people understand, what remains unclear, and what should happen next. You will explore how to organize those signals into themes, actions, and a practical measurement approach. Share what you built Participants will share their developing playbooks, learn from one another, and get feedback they can apply when they return to their organizations. Explore Copilot and agent workflows Identify where AI could save time or improve consistency across planning, drafting, summarizing, and follow-up. You will also explore a simple communicator agent canvas for a repeatable workflow. AI can help make the work faster, but the communicator remains responsible for context, quality, tone, and final judgment. Use Copilot-supported prompts and peer feedback to turn a rough stakeholder request into a more focused communications brief. What you will take home Comms Camp is designed to create reusable outputs, not just inspiration. Depending on your chosen scenario, you can leave with: A strategic communications brief A Viva Engage activation plan Copilot prompts and workflows A leader communication, event, AMA, campaign, or community plan A communicator agent canvas A signal and measurement plan A reusable communications playbook You will also leave with ideas from other communicators who are navigating many of the same challenges, including channel complexity, leader visibility, responsible AI adoption, employee participation, and demonstrating impact. Who should attend? Comms Camp is intended for: Corporate and employee communications professionals Leader and executive communications teams Viva Engage community managers Change and adoption professionals Employee experience leaders IT partners supporting communications and communities Organizations may send multiple participants, and communications and technology partners are encouraged to attend together. Participants should have access to Microsoft 365 and Viva Engage. Microsoft 365 Copilot access is recommended. Register for Comms Camp in Redmond Join us October 12–13, 2026, at Microsoft in Redmond, Washington. The workshop is free, and registration is required. Explore the Comms Camp experience: https://adoption.microsoft.com/comms-camp Register directly for the Redmond Comms Camp: https://aka.ms/CommsCamp/Joinus Cannot join us in Redmond? Comms Camp is planned as a multi-city experience. Visit the Comms Camp site to learn when more locations are announced. Tell us where you want us to bring camp next! Bring the complicated ask, the half-built campaign, or the community challenge you have been meaning to tackle. We will help you turn it into something you can use. Learn. Share. Build.Build your own Engage Governance agent
The best governance guidance often comes from real conversations with customers: the questions they ask, the decisions they are working through, and the practices they have already built. And organizations already have the answers somewhere: an adoption deck, an admin guide, a community manager checklist, an acceptable use policy, or a launch plan. That is where a Governance for Viva Engage Agent can help. Grounded in Microsoft guidance and your organization’s approved materials, it can give admins, communicators, adoption leads, and community managers quick, practical answers without replacing the people who own governance. Give each source the right job Mix Microsoft guidance with your own approved materials but be clear about which source wins. Your internal governance and policy documents should be the authority for organization-specific decisions. Microsoft Learn explains admin capabilities and roles. Microsoft Support covers the end-user experience. Microsoft Adoption offers planning and adoption best practices. The agent should make approved guidance easier to use, not invent policy or replace the people accountable for it. Useful starting points: Viva Engage adoption Monday Masterclass: Viva Engage essentials Viva Engage admin center overview Get started with Viva Engage Overview of security and compliance To keep the agent useful and safe, define how it should treat each type of source. This prevents end-user help content from being mistaken for governance policy and helps IT teams understand which source should be used for each type of answer. Source type Use it for Authority level Internal governance and policy documents Tenant-specific rules, ownership model, escalation paths, community lifecycle decisions, and approved operating model Highest authority for organization-specific decisions Microsoft Learn admin documentation Admin capabilities, admin roles and responsibilities, admin center guidance, configuration surfaces, and security/compliance options Authoritative for admin capabilities and product administration Microsoft Support end-user documentation User-facing experiences, getting started, Teams app setup, posting, participation, and end-user help Authoritative for end-user product help, not governance policy Microsoft Adoption materials Adoption best practices, planning, launch readiness, community management, and success measurement Best-practice guidance for planning and adoption In the agent instructions, explicitly state that internal governance documents take precedence for organization-specific decisions, while Microsoft Learn and Microsoft Support explain product capabilities and user experiences. How to create the agent Microsoft Copilot Studio could be a good starter place because it lets you connect approved knowledge, define behavior, test responses, and control publishing. But the instructions below are intentionally builder-agnostic, so you can adapt them to the agent platform they already use. Copy-and-paste agent instructions You are the Governance for Viva Engage Agent for this organization. Your role is to help IT teams, Viva Engage admins, governance owners, adoption leads, corporate communications teams, and community managers understand how to plan, launch, manage, and govern Viva Engage. Use the connected knowledge sources as your primary source of truth. These may include Microsoft Viva Engage adoption materials, Microsoft end-user support documentation, Microsoft admin documentation, Viva Engage essentials guidance, and this organization's internal governance documentation. Source authority hierarchy: 1. Approved internal governance and policy documents are the source of truth for tenant-specific or organization-specific decisions. 2. Microsoft Learn admin documentation is the source of truth for admin capabilities, admin roles, admin responsibilities, configuration surfaces, security and compliance options, and Viva Engage admin center guidance. 3. Microsoft Support end-user documentation is the source of truth for user-facing experiences, basic usage, Teams app setup, posting, participation, and end-user help. 4. Microsoft Adoption materials are the source of truth for adoption best practices, planning, community management, launch readiness, and success measurement. 5. Do not treat end-user support documentation as governance policy. Use it to explain how the product works for users, not to decide organizational rules. Important Microsoft reference areas: - Viva Engage adoption guidance: https://adoption.microsoft.com/en-us/viva/engage/ - Viva Engage essentials / Monday Masterclass content: https://adoption.microsoft.com/en-us/customer-hub/monday-masterclass-your-guide-to-the-viva-engage-essentials/ - End-user support documentation: https://support.microsoft.com/en-us/viva/engage/get-started-with-viva-engage - Admin support documentation / Engage admin center overview: https://learn.microsoft.com/en-us/viva/engage/eac-overview - Admin roles and responsibilities are especially important when answering governance, operating model, ownership, and escalation questions. You can help users with: - Viva Engage governance planning - Community creation standards - Community ownership and admin roles - Community lifecycle management - Moderation and healthy conversation guidance - Acceptable use guidance - Launch readiness - Adoption planning - Measurement and success metrics - Escalation paths - IT operating model considerations - Admin roles and responsibilities - End-user setup and participation guidance when it supports governance or adoption planning - Guidance for leaders, community managers, and champions When answering: - Be practical, concise, and structured. - Assume the audience is technical or IT-adjacent unless told otherwise. - Reference the relevant source material when possible. - Distinguish between Microsoft best practices, Microsoft admin capability documentation, Microsoft end-user help, and the organization's own policies. - Do not invent tenant-specific rules, policy decisions, dates, licensing terms, compliance requirements, or admin settings. - If the answer depends on the customer's tenant configuration, licensing, legal requirements, HR policy, compliance posture, or internal governance model, say so clearly. - Recommend that users validate final decisions with the appropriate internal owner, such as IT, compliance, legal, HR, corporate communications, or the Viva Engage governance team. - Do not provide legal, HR, regulatory, or compliance advice. Use these as suggested prompts: What governance decisions should we make before launching Viva Engage? What roles are needed to govern Viva Engage? What should IT own versus communications or business owners? How should we decide when to create a new community? What should our community lifecycle model include? How should inactive communities be reviewed or retired? What should be included in a community manager checklist? How should moderation and escalation work? What technical controls should IT consider before rollout? What metrics should IT and adoption leads monitor? Create a launch readiness checklist for Viva Engage governance. Create a sample operating model for Viva Engage governance. Start small, then make it yours Before you publish, test with a small group that knows the admin experience, community management, communications, and policy boundaries. Ask the agent to build a governance model, name approvers, explain admin roles, or recommend what to do with inactive communities. A strong response should offer a framework, cite the right source, and ask for context when needed. It should never turn a best practice into a made-up company rule. As you use your agent, continue to edit and improve the instructions and refine your list of knowledge sources to improve responses. The best governance agent is not the one with the longest instructions. It is the one people trust enough to use. Start with your most common questions, connect the sources you already rely on, test the boundaries, and improve it as your governance model evolves. If you build one, or end up building off of this, I would love to hear how it works for your organization! Let me know in the comments or join our Customer Community and share with others!What’s new and next in Engage: June 2026
Stay up to date with the latest innovations coming to Viva Engage in June 2026. This update highlights new capabilities designed to enhance community engagement, streamline leadership communication, and empower employees to connect, share, and collaborate more effectively across your organization.
Communities tab in Teams
Hi there I've recently had the Communities tab pop up in my Teams alongside the Teams and Channels tab. No one else in my organisation can see this yet and we aren't sure why. I know it's being rolled out on a timeline but I was also wondering if it might be because I'm the only one in the org who has an Microsoft Viva Employee Communications and Communities licence? Does anyone have any insights into this? We'd like to make a bit of a roll out plan once this appears in our colleagues Team's set ups.Planning for Communities in Teams: What Admins and Communicators Should Do Next
Imagine if employees could spend less time sorting through messages and more time engaging with what actually matters, whether it’s a leadership update, a company announcement, or an important change…all in one place where they can understand, react, and respond. Communities are becoming a more visible part of Teams, making now the right time for admins and communicators to align on readiness, governance, and content. This 3-step post helps you plan your rollout: How to get ready How to reset All Company How to address concerns about noise as adoption grows You’ll also learn the key decisions admins and corporate communications teams should make to ensure Communities add clarity, not noise as adoption increases. And in case you missed it, the Teams blog covers what’s new and why it matters. (If you haven’t read the announcement yet, start here: Introducing communities in Teams: Unifying company communication and connection) What’s changing... and what’s not What’s new: Communities are easier to discover and access in Teams Visibility of posts and announcements increases What’s not changing: Governance is still in your control Communities still follow your existing structure and purpose The opportunity isn’t to rebuild everything, it’s to refine what already works. Start from where you are We recognize that not every customer is starting from the same place. For organizations already using Viva Engage, Communities in Teams is less about reinventing your strategy and more about extending it into the flow of everyday work. Communities are now easier to find and engage with inside Teams, raising the stakes for clarity, governance, and content design. As access becomes simpler and participation grows, it’s important to have your policies, onboarding, and launch plan in place. "Bringing our Viva Engage communities into Teams was an instant win for our organization. By standardizing on a single pane of glass, inside of Teams, we've made it easier and more enjoyable for staff to communicate with other, using a trusted tool that requires no additional enablement overhead. Cognizant has over 350,000 employees - and managing communities at scale requires us to leverage Viva Engage - by now having those live inside of Teams, we get the best of both worlds: the ability to participate in communities with 30k+ employees while still maintaining the notification and organization we've come to depend upon inside of ad-hoc Teams groups and more traditional Teams channels. This further reinforced the idea that Viva Engage Communities are where work gets done - they aren't an optional location for employees - and staying on top of groups and communities together helps make us better at supporting our clients! Best of all - we like to say we "drink our own champagne" here at Cognizant - we can now go to those clients and use our story to show them how an integrated Teams/Viva environment can drive positive business outcomes and enhanced employee experiences." Reed Wiedower, Cognizant, Innovation and Enablement Leader If you are new to Viva Engage, or have not used it strategically in some time, start by defining a few high-value communities, setting clear governance, and giving employees simple guidance on where to go, what to expect, and how to engage. Start by understanding where your organization is today: What governance looks like the next 30 days: Revisit All Company and determine if its purpose or usage should change. Define “official communities” strategy. Start with a small set (e.g., employee news, leadership updates, IT help, communities of practice), seed them with content, and actively promote them. Establish a naming convention to support discovery as Communities become visible in Teams. Define governance and moderation: who creates communities, who can post announcements, and how moderation works. Communicate these changes to community admins and encourage them to activate or refresh key communities. Not using Viva Engage yet? Start here. If you’re unsure where to start, start small: define the purpose, set expectations, and publish a simple guide for employees on how to follow, post, and manage notifications. With a few well-run communities in place, you’ll have the proof, and the playbook, to expand with confidence. Once you’ve defined your starting point and aligned on governance, the next critical step is resetting how your most visible community, All Company, should be used. If you need more guidance or a starting point, check out the Communities in Teams Playbook! Reset All Company for the Teams experience As Communities become more visible in Teams, All Company becomes even more important. This is the moment to reset its purpose: one place for company-wide updates that matter to everyone. For Admins (IT / Network Admins): Set the guardrails Your role isn’t just to enable Communities, it’s to prevent noise before it starts. Start here: Limit who can post (e.g., Corp Comms + delegated leadership voices) Document what qualifies as a post vs. what belongs elsewhere Define when announcements should be used (not every post needs one) For Corporate Comms: Reset how you use All Company Think of All Company as your broadcast + engagement layer inside Teams. Use it for: Leadership narratives and context (not just links) Major moments that need visibility and dialogue Posts that invite reaction, questions, and discussion Decide: What qualifies as a new post vs. a reply Who moderates, and when to step in Expected cadence (not every update = an announcement) Write for Teams behavior: Lead with “what this means” (not just “what’s new”) Keep posts scannable (short, clear, structured) Use announcements sparingly—overuse reduces trust Once All Company is clearly defined, look for follow-on communities (like Copilot Adoption Community) where more targeted conversations can happen. Address concerns about noise early As Communities expand in Teams, one concern comes up quickly: Will this create more noise? Done right, the answer is no. Start with this mindset: more posts ≠ more value. Engagement doesn’t mean more content. It means more relevant content, in the right place. If everything is posted everywhere, or if everything is an announcement employees will tune out. Admins: Control where content shows up Next Steps: Ensure communities are purpose-driven (not duplicates of the same topic) Guide teams to use the right community for the right audience Review the Governance of the network and Watch session: Mastering admin and governance in Viva Engage for community management, moderation capabilities and more. Review moderation and theme moderation in Viva Engage Corporate Comms: Be intentional with reach More visibility is powerful, but only when used carefully. Clarity reduces noise more than volume control ever will. Reminders: Use announcements for high-signal moments only Reserve broad reach for content that applies to most employees Let smaller or targeted communities carry more specific conversations The goal is trust, not volume As Communities become easier to access in Teams, the priority is making them feel useful, intentional, and worth employees’ attention. Done well, Communities don’t add noise, they make important communication easier to find, easier to understand, and easier to trust. Continue the journey Join Us live via Start Strong Webinar Deep Dive with the Engage Masterclass Series Modern Employee and Corp Comms Resources Click Through Demo Join our customer community! PS. Want access now? Communities in Teams is available now for Engage customers who opt into public preview, with no migration required. All existing community content, permissions, and governance settings carry over automatically. Review the network and tenant requirements to ensure your network meets the criteria. Make sure the engage experiences in Teams toggle is on for your tenant. Opt-in to the public preview through Teams. Learn more about the full experience for communities in Teams.Leadership communication in the flow of work
Leadership today is less about occasional broadcasts and more about consistent, credible presence. Employees expect leaders to: Provide clarity amid constant change Show follow-through, not just direction Communicate in ways that feel human and accessible Why this matters This playbook scales based on a leader’s scope and audience size – from company-wide executives to function and team leaders. Research from Engage UX Researcher Paula Wellings, shared during our Masterclass series, outlines what employees expect from leader communications. This research (and our internal experience) consistently show that visible, two-way leadership communication is a key driver of trust, engagement, and successful change. When leaders participate directly, downstream employee engagement increases. Ongoing dialogue—through posts, responses, and visible follow-through—is the foundation of leadership presence on Engage. Structured moments such as ask-me-anything (AMA) sessions and organization-wide events can reinforce that dialogue and deepen trust at scale. At the same time, leaders face real constraints: limited time, channel overload, and high scrutiny. Engage is designed to help leaders communicate once, in the right place, and stay visible in the flow of work without adding meetings or increasing email. Where Engage fits in the flow of work Leaders communicate across many channels today, including email, meetings, and the intranet. Each has a role, but not all support visibility, persistence, or two-way engagement at scale. Engage is designed for leadership communication that benefits from reach, context, and dialogue—where updates need to travel beyond immediate teams and employees can respond, not just receive. Read about Microsoft executive Ravi Vedula’s Viva Engage adoption journey, and chart your own course. Choosing the right surface based on intent Engage gives leaders two complementary avenues for communication. Each serves a different leadership intent. The choice between storyline and communities depends on the leader’s scope, audience size, and communication intent. Storyline Storyline enables leaders to reach both their intended audience and people across teams and hierarchies, making it well suited for visibility, alignment, and leadership presence. Share perspectives, priorities, or decisions Recognize people or progress publicly Cascade or amplify important updates Close the loop in a visible way Communities Communities bring together people organized around a shared variable (org, role, region, topic). They typically feature multiple voices, curated content, and ongoing discussion aligned to the purpose of the community. Use communities when you want to: Engage a specific group or function Invite discussion, Q&A, or feedback Go deeper on a topic over time Build shared understanding within a domain Communities are ideal when the goal is conversation rather than broadcast. How leaders typically use both Leaders do not choose between storyline and communities based on title or level. They choose based on audience scope and communication intent. Storyline is typically used when the goal is broader visibility: Sharing perspective or context that benefits cross-team awareness Reinforcing leadership presence beyond a single org Public recognition or commentary that should travel widely Communities are typically used when the goal is focused dialogue: Communicating with a defined audience (org, region, function, topic) Hosting discussion aligned to the purpose of that group Sustaining ongoing conversations within a curated space In practice, leaders often use both surfaces together — for example, sharing a visible update on storyline and continuing deeper discussion within a community. Leadership presence isn’t just posting Leaders often pair posting with lightweight engagement—replying to comments, acknowledging questions, or reacting—to reinforce trust and dialogue. Building blocks for effective leadership communication To ensure clarity and reach, two things need to be in place: Leader identification Leaders must be identified as such in the system. This enables: Appropriate visibility across Engage Access to leader-level insights and analytics A consistent experience for audiences This ensures that leadership communication is surfaced and measured correctly. Delegates enabled Leaders can designate delegates to support their communication on Engage. Delegation is about support, not outsourcing leadership voice. Delegates can: Draft posts on behalf of the leader Publish updates with the leader’s voice and attribution Help manage cadence, timing, and follow-up Help leaders stay engaged by surfacing conversations, questions, and moments worth responding to This allows leaders to maintain an authentic presence while scaling communication – especially during busy periods or major moments. Audiences built in (no set up required) Engage provides built-in audiences based on organizational data, such as the reporting hierarchy, so leaders can reach the right people by default from their Storylines. Leaders and delegates can define audiences when they publish, with no setup required. Audiences provide: A built-in followership Confidence that messages are seen Less reliance on follow-up email Clear expectations for who an update is for Core leadership use cases Engage helps leaders put leadership behaviors into practice in a way that’s visible, consistent, and part of the flow of work. Narrate what’s happening Share priorities, decisions, and context at the appropriate scope so teams stay aligned. Keep updates concise and focused on what changed, why it matters, and what’s next. Acknowledge people and progress Recognize wins, milestones, and contributions publicly to reinforce morale and culture. Specific recognition lands better than generic praise. Call out teams, behaviors, or moments. Close the loop Reflect back what you heard, what changed, and what’s next. This is a key driver of trust. Follow-up posts that reflect what you heard build trust and increase engagement. Even brief responses signal listening and build credibility, especially during change or uncertainty. Host interactive leadership moments In addition to ongoing posts and dialogue, leaders strengthen trust through live and structured interaction. Ask-me-anything (AMA) sessions and broadcast events are powerful ways to: Provide clarity in moments of change Address questions transparently and at scale Demonstrate accountability Reinforce alignment across teams A common pattern is to use Engage end-to-end: Solicit questions in advance on storyline or in communities Host the live broadcast event Follow up with key takeaways or clarifications Interactive moments often become anchor points in a leader’s communication strategy, complementing regular posts and dialog. For setup guidance and event mechanics, refer to Ask me anything events in Engage. Measuring leadership impact Engage provides leadership analytics to help leaders understand how their communications land. Leaders and delegates can view: Reach: how many people saw a post Engagement: reaction, replies, and sentiment to understand the tone and quality of responses, not just volume. Conversation signal: whether people are responding, not just reacting Trends over time: consistency and momentum in leadership communication These insights are not about scoring or ranking leaders. They are designed to help leaders: Understand what resonates Know when follow-up is needed Communicate with more intention over time Leaders who consistently respond and engage tend to see stronger momentum over time, not just higher reach. Getting started (10 minutes) Choose the right surface: Storyline for broad context and visibility Communities for focused dialogue Confirm your audience and delegates Writing guidance: Quality over quantity: Consistency matters more than volume. One thoughtful post a month is better than frequent updates if there isn’t something meaningful to say. Sound human: write conversationally. Share perspectives – not corporate language. Be timely and relevant: Address what’s top of mind for your audience right now. Invite engagement: Ask a question or prompt reflection when appropriate. Use visuals when possible: Images or short videos help posts stand out and travel further. Choose the right tone: Use announcements, polls, or praise intentionally based on your goal. Plan time to engage after posting: even a few replies can meaningfully increase trust and participation. Example posts that leaders can model Employees value leaders who show up, respond, and follow through — not just those who post. Team recognition: “Proud of the team for delivering this milestone. The collaboration across groups really showed up in the final result. Thank you for the focus and persistence.” Leadership reflection: “This month I’ve been reflecting on how we balance speed with quality. Both matter, and I’m encouraged by the conversations I’m seeing across the org.” Amplifying an announcement: “Today’s company announcement is an important step forward. I appreciate the work behind it and encourage everyone to take a look at the full update.” Culture and values: “One thing I consistently see here is people showing up for each other. Those moments define our culture more than any slide ever could.” Change and transparency: “As we move through this transition, I want to acknowledge the adaptability I’m seeing across teams. I’m committed to keeping communication open as we go.” The bigger picture When leaders use Engage intentionally: Important context travels faster Teams feel more informed and connected Reliance on broadcast email goes down Leadership presence becomes more continuous and human Note: Storyline announcements, targeting, the ability to identify leaders, some advanced analytics, and related capabilities described in this blog post are available with a Premium Viva Engage license (for example, Viva Employee Communications & Communities or Viva Suite). Resources Case study: Authentic leadership at scale Identify and manage leaders View analytics for posts and engagement Leadership corner Engage adoption resourcesEffective, engaging events in communities and storylines
Whether you’re running a company-wide broadcast, a training session, a Reddit-style “ask me anything” (AMA) or an in-person gathering, Viva Engage and Microsoft Teams help you host and manage more effective and engaging events. Events have always been central to employee communications. Viva Engage and events play a critical role in building trust, encouraging authenticity, and listening at scale. From highly produced hybrid all-hands to asynchronous AMAs, the new Viva Engage features are helping our leaders connect with employees, address what matters most, and build trust—all in one platform. - John Cirone, Senior Director of Global Employee and Executive Communications We are upgrading existing community live events and storyline AMA features with a simple model: three event types—broadcast, meeting, async—from any community or storyline, super-powered with a long list of event features you have asked for. The result: improved experiences for organizers, presenters and attendees both before, during and after the event. This blog post will detail what this means for you! These new events features start rolling out April 27 th . And guess what? All of these new features will be available to all Microsoft 365 commercial customers with access to Engage and Teams—no “premium” license will be required for events up to 10,000 attendees. New features: the highlights The new capabilities of Engage events—particularly the moderated feed with support for anonymous questions and upvotes—has transformed the way we empower our leaders to listen and respond to questions from employees. - Alexander Bradley, Senior Director of Executive Communications With that in mind, let’s start by exploring the new features for every event in every community and storyline: Events listing: Each community and storyline has a calendar of upcoming and past events—a destination for people to register for future events and catch up with events they missed. Event page: The home for your event is a branded landing page with a custom cover photo (coming soon), the event details and description. This is the “micro site” for your event to which you drive attendees. They can learn about the event, engage with it, join the live session, and catch up with the event if they missed it. Event feed: A new event feed enables you to share updates, solicit questions, ideas and feedback, and support engagement between attendees and presenters. The new event feed introduces support for optional anonymous posting and moderation which allows organizers to approve posts before they are made visible to attendees. The feed allows you to tune the event experience for the engagement you want to encourage and support; you can enable or disable questions, comments, reactions, and upvoting; and you can change the settings at any time. The event feed is available before, during and after the event, showing up on the event landing page in Engage and in the “Q&A” panel of Teams. Event recording: After the event, the recording is available on the event page, so attendees can review both the recording and the feed. You can now update the recording link, allowing you to make edits to the video. Calendaring options: Events in Engage support two models to support your efforts to drive demand and attendance. First, you can invite attendees directly from Outlook, putting an invitation directly in their calendar. This model supports scenarios where their attendance is expected. Or, you can drive attendees to the event page where they can add to calendar, supporting an “opt-in” model that gives attendees control of what is on their calendar. Or you can mix and match, inviting those attendees who really need to have it on their calendar and letting others opt in. Event analytics: You’ll have access to analytics throughout the lifecycle of your event. You’ll be able to see how many people attended, how they engaged in the event feed, and how people consumed the recording after the event. For broadcasts, you can also access Teams insights. Mobile app choice: Attendees can join events from either the Teams or Engage mobile apps, across both iOS and Android. Integration with enterprise search and Copilot: Content from public events serves as grounding for Microsoft 365 Copilot and enterprise search, amplifying the reach and impact of the knowledge and information you share in your event. Event types Now, let’s explore the three event types and what is different. BROADCAST is best for company-wide or large-scale events, launches, keynotes and organizational “town hall” or “all hands” events. Key characteristics: Deliver a high‑quality live stream that scales to large audiences Organizers control what appears on screen Attendees watch the event and participate using Q&A and reactions This experience is an upgrade to the legacy “live event” broadcast, with an advanced feed and a rich suite of production features. MEETING is best for collaborative sessions, presentations, training workshops, expert panels, and all of the regular “rhythm of business” events your team or department conducts. Key characteristics: Share camera, microphone, and screen in real time Organizers can control who can present and share Up to 1,000 people can participate in the live event A collaborative event can feel exactly like a Teams meeting, where anyone can share. Or it can be like a presentation or webinar, where only presenters can share. Or anything in between. ASYNC is best for soliciting questions, collecting feedback, and crowdsourcing ideas from employees. Conduct an offline, asynchronous event with no live presentation or video stream Host an "ask-me-anything" (AMA) during which leaders or experts answer questions Enhance an in-person event by engaging your audience before and after This experience features an event page and event feed, but no real-time video experience powered by Teams. You can gather questions, ideas and feedback before an in-person event, or host a text-only (asynchronous) event like a Reddit-style AMA that can connect people with experts even over longer periods of time. Why host events in a community instead of creating them from your calendar? Until now, you’ve had one way to create events: From your Teams or Outlook calendar, you can create a Teams meeting, a Teams webinar, or a Teams Town Hall. Why would you want to change where you create and host events? An event isn’t just a calendar entry; its impact continues outside of the event confines. New event features help employees who missed the live event catch up quickly, help moderators engage attendees, and help leaders close the loop by responding to remaining questions. The result is a richer, more durable record of the event, so your organization benefits from the information and knowledge long after the event ends. Here’s the short list of what you can do better when you create your event from a community: Provide a calendar of upcoming and past events. Communicate effectively to drive awareness and attendance. Engage your audience before, during and after the event. Leverage event analytics to measure and improve effectiveness. Amplify information and knowledge shared at the event, after the event. Integration with community objectives and experiences. If you have experience with Microsoft 365 and events, think of it this way: By creating an event in a community, you’re taking a Teams event and wrapping it with the superpowers of Engage to reach and engage your audience at scale, before, during and after your event. And remember communities are not just for Engage anymore! Communities (powered by Engage) will be available in Teams Chat, alongside your chats, channels, and meetings; so, your events and their content will be seamlessly integrated into the flow of work in Teams. Preview customers have used these new event capabilities at scale, for company-wide “all hands” events, departmental rhythm-of-business meetings, and an extraordinary number of internal AI learning events. We look forward to celebrating your successful events as you apply these features to share news and information, train people, and engage employees. Resources Organize an Engage event - Microsoft Support Attend an Engage event - Microsoft Support Monday Masterclass Season 2 – Week 4 Designing Events Employees Remember | Microsoft Community HubSensitivity Labels Are Coming to Viva Engage Communities Here's What You Need to Know
If you've seen MC1250283 in your Message Center and have questions, you're not alone. In the past few weeks we've heard from customers across industries — financial services, manufacturing, healthcare, government — all asking variations of the same questions. This post is our attempt to answer them all in one place. You can find out more via this article Sensitivity labels in Viva Engage. | Microsoft Learn What's changing Starting March 31, 2026 sensitivity labels will be available in Viva Engage community creation. When someone creates a new community, they'll see a sensitivity label picker, the same kind of label selector that already exists in Microsoft Teams and SharePoint. This is Engage joining the rest of Microsoft 365. Sensitivity labels for groups and sites have been supported in Teams, SharePoint, and M365 Groups for years. Engage communities, which are built on top of M365 Groups and SharePoint sites, are now part of that ecosystem. How it works Labels come from Purview, not Engage. There is no new admin setting in the Viva Engage admin center to turn this on or off. Your sensitivity labels are configured and published in Microsoft Purview, and those settings now apply to Engage communities the same way they apply to Teams and SharePoint. Labels are synced across all three surfaces. An Engage community's sensitivity label is shared with its linked M365 Group and SharePoint site. When a label is applied to one, it synchronizes across all three. This means your label governance is consistent — not fragmented. Existing communities are not automatically labeled. Communities created before this rollout will remain in an unlabeled state. They won't have a label auto-assigned. Admins can apply labels to existing communities in bulk using existing PowerShell scripts against the linked M365 Groups or SharePoint sites, no new tooling is needed. Applying a label via those surfaces will trigger the sync to Engage. Labeling can be mandatory or optional. Whether users must pick a label when creating a community is controlled by your Purview label policy. In the label policy publishing flow, under "Groups and sites > Settings," there's a checkbox to make site labeling mandatory. If you check it, users will be required to select a label when creating a community. If you don't, the label picker appears but community creation is still allowed without a selection. Default labels are set in Purview. If mandatory labeling is enabled and a user hasn't picked a label, the creation flow pre-populates a default. That default is determined by your label policy settings in Purview — Purview suggests the lowest-priority label with the right scope, but you can configure a different one. On Day 1, before an Engage-specific default is configured, the existing site default label (if set) will pre-populate. Community admins and owners can change labels after creation. This isn't locked to tenant admins. Community admins and owners will be able to update the label via community settings in Viva Engage or through the M365 admin center group listings. ttings. Programmatic community creation still works. If you create communities via the Graph API's /community endpoint, the label won't be set through that call — there's no Graph API support for setting labels directly on communities in this release. However, after creation, you can apply the label via PowerShell targeting the linked M365 Group or SharePoint site, which will sync to Engage. Your existing automation flows won't break; they just need a label-setting step added if you need one. The governance tension we've heard The most substantive concern we've received, and it's a legitimate one, comes from organizations that have configured their Purview label policies to enforce private-only labels for groups and sites. These organizations allowed public Engage communities precisely because Engage wasn't subject to sensitivity label governance. When Engage joins that ecosystem, their Purview policy will apply — and if their policy only permits private-supporting labels, new Engage communities will only be creatable as private communities. We want to be direct about this: Purview sensitivity label policies are tenant-wide and can't be scoped to individual workloads. There is no way to say "apply this policy to Teams and SharePoint but not Engage." Engage communities are built on M365 Groups and SharePoint sites, and they share the same label scope in order to stay in sync. If your organization has strict private-only governance and you need to continue creating public Engage communities, the practical path is: Create a public-supporting sensitivity label (e.g., "General - Internal Communications") Publish it to admins only — not your entire user base — so it doesn't accidentally appear in Teams or SharePoint creation flows for end users Apply this label to Engage communities via the admin center or PowerShell scripts Optionally, publish the label to your entire user base and use automated scripts to monitor Groups and Sites for misuse of that public label and correct them This is a workaround, not an ideal solution. We've heard the feedback clearly: Engage's use case — broad internal communication and knowledge sharing, is fundamentally different from SharePoint or Teams collaboration, and a one-size-fits-all label scope creates real tension. We're tracking this as a design consideration and have raised it with the Purview team. If you want to formally register this feedback, submit a Design Change Request (DCR) with your Microsoft Account team asking for per-workload label scoping support. What sensitivity labels do NOT change Community discoverability. All Engage communities remain discoverable to all users regardless of sensitivity label. Labels don't create "hidden" communities. A private community is visible in search — users just can't read the content without being a member. What users can see in search. Search results are governed by access control lists (ACLs), not sensitivity labels. Users will only see content they have permission to access. Your custom label taxonomy. Labels like "Confidential" or "Highly Confidential" are defined by your organization in Purview. There's no universal label structure — your configuration is yours. Frequently asked questions Can I test this in a staging tenant before it hits production? This rolls out to production tenants starting March 31. There isn't a separate staging path for this feature. We recommend using this window before rollout to review your Purview label policies, identify any communities where label assignment may create issues, and prepare admin and end user documentation. What happens if we have no sensitivity labels configured in Purview at all? If you don't use sensitivity labels for groups and sites, this change will have no impact. Community creation will support the privacy picker as it always has. Will this affect Copilot? Yes, and this is worth thinking through. Verified answers and content in private communities are scoped to members of that community. If your governance pushes more communities to private, that content becomes less accessible to Copilot for org-wide knowledge retrieval. If broad knowledge sharing is a goal, this is a factor to weigh in your label policy decisions. Will there be any visual change for end users? Users creating communities will see a sensitivity label dropdown in the creation flow. If your organization has labels published to users, they'll be able to select from those labels. If mandatory labeling is not enabled, they can leave it blank. If a community has a label, it will be visible in the community header. What to do before March 31 Review your Purview label policies. Specifically check whether you have mandatory labeling enabled for groups and sites, and what default label is configured. This will determine what your users see in community creation. Check for existing communities with label mismatches. If your linked Groups or SharePoint sites already have labels applied, confirm that those labels are ones that make sense for public community use. Prepare your community admins. Let them know the label picker is coming and what they should (or shouldn't) select. Prepare end user guidance if needed. For most organizations this will be low-friction. But if you have a complex label taxonomy or strict governance, proactive communication helps.Viva Engage masterclass season 2—Session 3: Campaigns and storytelling
When communication is intentional, it doesn’t just inform. It creates clarity and connection. In Session 3 of the Viva Engage Masterclass (season 2), we covered practical ways to build that impact with Storylines, Campaigns, and series-based storytelling. Below is a recap of the key takeaways you can apply right away. Why storytelling matters right now Work is full of constant signals: email, chat, posts, meetings, and in-person interruptions. Microsoft Work Trend Index research describes this as the “infinite workday,” where employee attention is limited and company communications are easy to miss. What helps is narrative coherence over time: messages that connect into a story employees can recognize, follow, and act on. The goal is to build understanding and momentum. Use Storylines to build leadership presence If leaders want to build trust and ongoing connection, their Storyline is an important place for them to show up in Viva Engage. A simple way to think about it: Email is delivery Meetings are moments Storyline is presence In Viva Engage, Storyline gives leaders a consistent way to share updates, add context, and invite conversation in one place. What Storylines provide: Intelligence and targeting: reach defined audiences with the right message. Multi-way dialogue: make communication two-way, so people can respond, ask questions, and build on the message. Measurable impact: understand what landed through engagement and analytics. To set a leader up for success with Storyline, start by making sure they’re identified as a leader in the product, assigning delegates who can help draft and publish posts, and defining the audience they want to reach. Then confirm they have the right profile details and a short “about” that matches their role. Agree on a simple cadence (for example, one post a week), draft the first few posts together, and keep a short list of topics they can pull from. Strong posts are clear about what they’re trying to do. The session shared a simple way to pressure-test drafts before posting following the 3C model: Context: What’s happening? Clarity: Why does it matter? Connection: What do I want people to do? One more reminder that came through clearly: engagement doesn’t happen by accident—ask for it. End with a question or prompt that makes it easy to respond. Used well, Storyline becomes a reliable place for employees to hear directly from leaders and respond in the moment. It helps leaders show up consistently, keep updates connected over time, and build trust through two-way conversation. Identify leaders and manage audiences in Viva Engage | Microsoft Learn Storylines in Viva Engage - Microsoft Support The Engage Chronicles: Leadership Lessons for the Digital Age Run social campaigns that invite participation Campaigns help the organization rally around a shared theme through repetition and participation. In the session, we discussed how campaigns can support different goals, such as: Driving business initiatives Crowdsourcing ideas and experiences Creating belonging through employee stories We also covered the difference between: Official (global) campaigns that roll up content across Storylines and communities Community campaigns that stay within a specific community (lighter-weight, designed for local participation) A key takeaway: campaigns work best when they’re designed so employees can join the story—not just read it. Here are a few campaign examples we shared in the session that translate well to Viva Engage: Win. Win. Win. Invite people to share weekly wins, shout-outs, or lessons learned—and encourage others to add their own. Product launch or roll out. Announce a new tool or change, then keep everything in one place: tips, FAQs, help resources, and Q&A. 30 days of ____. Pick a theme and post a prompt each day (or each week) to keep the story moving and make it easy to join in. Leadership series. Have leaders take turns sharing what they’re learning, reading, or trying, then ask employees to share their own. Recognition and gratitude. Spotlight individuals and teams who are making an impact and invite peers to add praise. A simple recipe for success: be clear on the goal, make it easy to participate, and keep a steady posting rhythm. Even though it’s quick to create a campaign, the work is in the planning. The session shared a straightforward timeline: Two+ weeks before: define the theme, align stakeholders One week before: define success (KPIs), finalize messaging Days before: prep content and resources, remind contributors Kickoff: publish the Campaign and start the rhythm Bring it together with a simple plan: set a clear goal, give people an easy way to participate, and keep the Campaign active with a steady rhythm. Track what’s landing as you go, and close the loop by sharing progress and outcomes. Campaigns in Viva Engage - Microsoft Support Set up official campaigns in Viva Engage | Microsoft Learn Think series, not a post One of the clearest themes from the session: if you want adoption or behavior change, one message won’t do it. We talked about the “rule of 7” concept. People often need repeated exposure before they act. The practical takeaway is to build a series with: A consistent theme A recognizable visual style A predictable rhythm When employees “watch for the next drop,” your #campaign has started to stick. The session also introduced “trend-jacking”: using safe, current memes and social trends to make internal communications feel more creative and fun. Why this works: relevance, clarity, and connection We closed with research on how communications cut through the noise—especially for younger employees who have learned to filter fast. The three elements of communication that cut through the noise are: Relevant: tailored to an employee’s context (not just “for everyone”). Start with what the update means for people’s day-to-day work. Make the “why it matters to me” clear up front. Clear: easy to scan and understand quickly, with optional depth. If you need to include detail, put the most important point first and add the rest below, so people can read more when they have time. Clarity also means being specific, not vague, about dates, owners, and decisions. Connected: designed for dialogue, not “do not reply” broadcasting. End posts with a question that’s easy to answer, or a prompt that invites examples. Respond to early comments so people see that engagement is welcome and valued. Over time, this builds trust and helps employees feel like they’re part of the story, not just receiving updates. One important point: it’s not that people can’t focus—it’s that they’ve built faster filters. If content doesn’t signal value quickly, it won’t land. What’s next The Masterclass continues with Session 4: Designing events employees remember. You’ve got live events coming up soon at your company, this next session will help you plan moments that drive real participation—and follow-through. You can register for upcoming sessions and explore the full schedule at: 👉 https://aka.ms/VivaEngage/Masterclass
