Effective, 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 Hub
Sensitivity 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
Monday Masterclass Season 2 – Week 2: AI Powered Engagement in Viva Engage
AI has officially moved from an interesting add‑on to a core part of how modern organizations communicate and connect. In Week 2 of the Viva Engage Masterclass – AI‑Powered Engagement, we explored what that shift really means for employees, leaders, and communicators—and how Viva Engage is becoming the place where human connection and AI scale together.Introducing Viva Engage Masterclass: Your Guide to the Viva Engage Essentials (Season 2)
Last year, we launched the Viva Engage Masterclass: Your Guide to the Viva Engage Essentials to help communicators, community managers, and IT leaders build confidence with Viva Engage, and we were blown away by the engagement from customers around the world.and we were blown away by the engagement from customers around the world. So we’re excited to bring the series back for Season 2 in 2026. This year’s masterclass includes four live sessions designed to go beyond the basics, helping you explore new capabilities, apply AI thoughtfully, and design experiences that truly resonate with employees. Whether you’re just getting started or looking to elevate how you use Viva Engage today, these sessions are built to help you take the next step, practically and confidently. What is the Viva Engage Masterclass? The Viva Engage Masterclass is a customer focused learning series that covers the essentials of Viva Engage. From foundational concepts to real world strategies you can apply immediately. Each session is: Comprehensive Overview: Get an in-depth look at the core capabilities for all roles who will be using Viva Engage, including admin and governance, moderations to how to create and manage communities, start and participate in conversations, and organize virtual events. Expert Guidance: Learn from Microsoft experts who will share best practices and tips for maximizing the use of Viva Engage in your organization. Interactive Q&A: Have your questions answered in real-time by our product group experts, ensuring you leave the session with a clear understanding of how to leverage Viva Engage in your organization. Hands-On Experience: Participate in live demonstrations and interactive activities that will help you get comfortable with the platform's functionalities. Register for the Masterclasses You can join one session or attend all four. Each masterclass stands on its own while also building toward a stronger, more connected Viva Engage strategy over time. Add Season 2: 2026 Masterclass sessions to your calendar! Week 1: Beyond the Basics Move from setup to scale with practical guidance on community structure, assigning roles, governance, and moderation, plus how Copilot and AI can streamline management. We'll also touch on the feed and notifications. 📼 Monday Masterclass Season 2 – Week 1: Beyond the Basics in Viva Engage Week 2: AI-Powered Engagement Discover how Microsoft Copilot and AI can amplify engagement, simplify moderation, and help leaders and communicators create content faster and smarter. Monday, February 9, 2026 | 8:00 am PT https://aka.ms/VivaEngage/AIEngagement Monday, February 9, 2026 | 3:00 pm PT https://aka.ms/VivaEngage/AIEngagement/2 Week 3: Campaigns and Storytelling Learn how to run campaigns that spark participation, amplify leader voices, and craft compelling narratives that turn announcements into conversations. Monday, February 23, 2026 | 8:00 am PT https://aka.ms/VivaEngage/Campaigns Monday, February 23, 2026 | 3:00 pm PT https://aka.ms/VivaEngage/Campaigns/2 Week 4: Designing Events Employees Remember Plan and promote events that feel intentional and engaging, with tips for discussions, Q&A, moderation, and post-event follow-up that keeps the momentum going. Monday, March 9, 2026 | 8:00 am PT https://aka.ms/VivaEngage/Events Monday, March 9, 2026 | 3:00 pm PT https://aka.ms/VivaEngage/Events/2 View the full schedule and register here: https://adoption.microsoft.com/en-us/customer-hub/monday-masterclass-your-guide-to-the-viva-engage-essentials/ Who should attend? The Viva Engage Masterclass is designed for: Corporate communicators Community managers Employee experience leaders IT admins and adoption leads Anyone responsible for building connection, culture, and conversation at scale No matter your role or experience level, each session offers practical guidance you can apply right away. Join us live (and earn recognition!) and in case you miss it, they’ll be recorded All sessions are held live, giving you the opportunity to learn from experts, ask questions, and connect with other Viva Engage customers. Each session has a blog post with dedicated resources and information including the recording. New for 2026: attendees will have the opportunity to earn certificates and badges, recognizing their learning and participation throughout the series. See you in the masterclass!Viva Engage Email Sender Domain Update
As part of the final phase of the Yammer to Viva Engage rebranding, we are updating the email sender domains used for all Viva Engage communications. This change ensures a consistent and secure brand experience across all surfaces and completes the transition from the Yammer brand to Viva Engage. Please see Message ID MC1117814 for earlier communications on this release. The new email domains continue to leverage industry-standard email authentication (such as SPF) to help prevent tenant spoofing and improve deliverability. When will this happen? The rollout of the new email sender domains will occur in phases over several months starting in early September 2025: We plan to complete the transition by the first quarter of 2026 but may adjust the timeline based on feedback. Any updates will be sent via the Message Center. During this transition you should expect to receive emails from both the old and new domains. This is very important if your tenant has custom email rules or is processing emails sent by Engage in a special manner. Please ensure that you are prepared to receive emails using the old and new sender domains until communication has been sent notifying you of the completion of these changes. How this affects emails across mailbox and organizations All emails from Viva Engage will now come from a new domain instead of yammer.com or eu.yammer.com The exact sender domain depends on the data residency for your Viva Engage network: US geo: from @yammer.com to @engage.mail.microsoft EU geo: from EU.yammer.com to @eu.euengage.mail.microsoft In addition to the domain change, Viva Engage email addresses will now include a tenant-specific prefix to help differentiate your organization’s environment such as test and production tenants. This prefix will use your organization’s tenant name in Microsoft Entra ID and will appear in the sender address. For example, fabrikam.onmicrosoft.com will result in a “fabrikam” prefix. Continuing with this example, sender addresses may include: noreply_fabrikam@engage.mail.microsoft – for digest emails, leader identification, community expert identification, delegate notifications and others. notifications_fabrikam@engage.mail.microsoft – for community posts, storyline updates, and other user activity notifications. announcements_fabrikam@engage.mail.microsoft – for leadership announcements and other broad communications. For networks in the EU geo, you should change the sender domain in the examples above to noreply_fabrikam@eu.engage.mail.microsoft, etc. Including this identifier makes it easier for admins, users, and mail systems to distinguish between tenants, reducing confusion and improving traceability. It also adds an additional layer of protection by making it easier to identify and authenticate emails originating from your tenant. Scope of impact: This change applies to all Viva Engage customers and all email notification types, regardless of your Viva license tier (Viva Engage Core, Viva Suite, etc.). It affects all Viva Engage emails, including user notifications, community announcements, storyline digests, and any other Viva Engage–generated emails. Most end users will only notice that the “From” address looks different Custom email transport rules: If you rely on specific email address formats in rules configured within your tenant, please ensure that the configuration is updated to cover both the old and new email address formats accounting for the data residency of your network. Third-party integrations: If your organization uses any third-party services (such as email journaling/archiving systems, security gateways, or custom email workflows) that filter or classify emails based on the sender domain, those will need adjustment to include the new email sender domain. Any tool explicitly looking for only @yammer.com or EU.yammer.com in email addresses will fail to recognize the new addresses. You should review such configurations and update them to accept or recognize the new @engage.mail.microsoft and @eu.engage.mail.microsoft domains. This will ensure continuity in archiving, compliance journaling, or application of custom routing rules that were targeting the old domain. Finally, note that this is not an optional change, it’s an automated part of the service rebranding. After the coexistence period, emails from the old Yammer domains will stop. We will communicate via the Message Center at the completion of this transition so that you know when the old email address has been discontinued. What you need to do to prepare Admins should review and update the following configurations before and during the rollout: Email Transport Rules / Mail Flow Rules: Update any Exchange transport rules, mail flow policies, or email gateway allowlists that reference @yammer.com (or EU.yammer.com) to also include the new domain(s) @engage.mail.microsoft and EU.engage.mail.microsoft. This ensures that automated rules (for encryption, forward, etc.) continue to work with the new sender addresses. For example, if you have a rule that flags or redirects Yammer emails, edit its conditions to accept the new domain as well. Security Filters: Check your anti-spam or email security filtering configurations. The new domains are Microsoft-managed and authenticated, so in general they should be treated as trustworthy senders. If your organization had any custom filter allowing all @yammer.com mail, you should add the new domains to those allowlists. Likewise, if you blocked @yammer.com anywhere (some organizations temporarily block Yammer emails prior to launch), you’ll need to update those blocks to use the new domain. Outlook Inbox Rules (User Mailbox Rules): Inform users that any personal Outlook rules they created that filter or sort emails by the sender domain will need to be updated. For instance, a user might have an Outlook rule moving all Yammer emails to a folder. After the change, that rule (looking for @yammer.com) would no longer catch the notifications. Users should update such rules to the new domain or adjust their logic. (If a user does nothing, the worst case is that Viva Engage emails will start landing in their inbox instead of the expected folder.) Safe Senders and Allow Lists: To proactively prevent any Viva Engage notifications from being misclassified as junk email and treated as external, consider adding the new domain to your organization’s safe sender lists. In Exchange Online, this might mean adding engage.mail.microsoft (and the EU variant if applicable) to tenant allow lists. See more here- https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/manage-accepted-domains/manage-accepted-domains Users can add the new addresses to their personal Outlook Safe Senders list. Email addresses and domains on the Safe Senders list are never treated as junk mail. For instructions, see Add recipients to safe sender list in Outlook. This step can help ensure smooth delivery during the transition. No action needed if no custom configurations: If your organization has no custom mail rules or integrations related to Yammer, then in most cases no administrative action is required for basic email delivery. The domain change will happen automatically. For admins, communicating these changes in advance to users in your organization is highly recommended. Compliance considerations No new compliance or privacy impact has been identified with this change. The content of the emails remains the same; only the sender domain is changing. Data residency and compliance for Viva Engage continue to follow the existing policies and region of your network as the domain rebranding won’t affect that. As always, you should review this change against your organization’s policies. For example, if your organization had any internal compliance rule specifically referencing the old domains, update those references. Otherwise, standard email compliance (retention, eDiscovery, auditing) for Viva Engage messages is unaffected by the domain change. By updating your configurations and informing users, you can ensure a seamless transition as Viva Engage completes its rebranding. After the transition is complete, all your Viva Engage emails will arrive under the new domain names, offering a more coherent experience. Learn more For more background on the Viva Engage rebranding journey, see the blog post “Yammer is evolving to Microsoft Viva Engage” on the Microsoft Tech Community. Official documentation is updated to reflect these new domains. Please refer to the Message ID (MC1117814) for the Viva Engage email rebranding updates.Teams, SharePoint, Viva Engage - which to use for dept comms?
I lead a 300‑person department, and I’m looking for guidance on the best Microsoft tool(s) to improve employee engagement and awareness across our organization. Right now, most of our communication happens in Microsoft Teams (channel posts, group chats), but we have dozens of channels and each group has its own space, which makes it hard to share department‑wide news, cascade annual strategic initiatives, report monthly progress, and celebrate wins or employee recognition. We don’t currently have any SharePoint sites built out, and we’re not using Viva Engage or communities. For those who’ve tackled similar challenges: Which Microsoft tools or combinations have worked best for broad communication, engagement, and consistent messaging across a large department? I’d love to hear what’s been effective for you. Thanks in advance for any insights!Customer Spotlight: Copilot Adoption in Viva Engage with Micron
One of the most effective ways to accelerate adoption and build confidence is by learning from the experiences of others. Gaining insights from customers who have already navigated similar journeys provides invaluable real-world examples and practical lessons, helping organizations avoid common pitfalls and capitalize on proven strategies. It's especially beneficial to connect with other customers who have gone first, as their firsthand knowledge can guide and inspire your own approach to Copilot adoption. Join us and discover how Tiffany Terry-Hughes, Senior Manager of IT Communications at Micron, is advancing Copilot adoption through Viva Engage. In this webinar, Tiffany shares actionable strategies and lessons learned from Micron’s journey, offering guidance for organizations eager to integrate Copilot into their digital workplace. Key takeaways include: Micron’s approach to leveraging Viva Engage communities for accelerating Copilot adoption Best practices for empowering employees and building confidence in AI-powered solutions Effective methods for tracking adoption success and keeping engagement strong Tiffany Terry-Hughes is Senior Manager of IT Communications and Training at Micron Technology. She leads efforts to boost AI adoption by producing multimedia resources, running social campaigns, and building an influencer network. Her aim is to drive a 50% productivity improvement at Micron in five years through innovative communication and learning programs. To wrap up, we’ll do a quick recap of the latest developments and what’s on the horizon for Copilot and Viva Engage. Stay tuned as we highlight new features and share what you can expect next, ensuring you’re equipped to make the most of these powerful tools in your organization. Whether you’re launching Copilot for the first time or scaling existing efforts, gain insights from Tiffany and the product group to help you onboard efficiently and establish Copilot as a trusted tool in your organization’s digital toolkit.
Moderation strategies to scale participation and communications in Viva Engage
Viva Engage brings people together around org-wide communications, communities, and knowledge sharing. Leaders, frontline workers, employees, and corporate communicators want the benefits of two-way dialog and community participation, but often wonder how to make sure relevant content reaches the right audiences while keeping public spaces safe for all. When your network is thoughtfully crafted to match your business needs and reflect your culture, users can contribute openly with lots of benefits and minimal risk. To ensure it remains a productive and safe space for all, Engage provides capabilities for network administrators and corporate communicators to moderate content and for end users to control over what reaches them. Set your Engage network up for success Like a great party, first you must set up the room to create a welcoming vibe people can lean into right away. Careful planning at the network level can jumpstart engagement and save trouble later. Define the purpose for the All Company community By default, everyone in the organization is in this community, creating a central hub for connection and engagement. Some organizations use this as a valuable peer-to-peer sharing channel, while others find it to be noisy with a lack of purpose and flood of irrelevant information. Many organizations see success turning “All Company” into more of a broadcast channel for company news while encouraging employees to post their content in specific communities or on their storylines. Consider renaming All Company to reflect its purpose, and restricting who can post to it. Define a few Official Communities with dynamic group membership Official Communities give people a signal around where to spend time and for what business purposes your organization intends to use Engage. Map them to important topics like leadership updates, business units, employee groups, company initiatives, or geographies, and then use dynamic group membership to get the right people in the community on day one. Restrict communities to reduce new post noise Restricting a community means only admins can post, but everyone can comment. In addition to considering this for All Company, you may want to consider restricted communities for communities with large membership, where you want to share leader and company news with control over who starts new conversations. Post your usage policy Ask users to accept your usage policy, and any behavioral expectations aligned with your culture and values, before they use Engage. You can edit and restart the acceptance flow any time. Consider letting users know you moderate this space in that policy; open communication about moderation helps users feel comfortable posting content because there are rules of engagement Enable Report a Conversation Users can notify admins of questionable or inappropriate content. Define a process to review and respond to issues when enabling this powerful feature. Report a Conversation is off by default in the Engage Admin Center. Govern the “Move conversation” feature Move conversation is great for getting discussions into the right place, but sometimes creates confusion among network and community members if someone moves a post without warning. Network administrators can decide if end users can move conversations with a setting in the Engage Admin Center. In communities, community admins can decide if members should be able to move conversations into their spaces. When members can’t move a conversation, roles like network administrators and corporate communicators can put conversations in the right place. Decide who needs a role Creating a healthy network requires network admins, corporate communicators, and community admins to work together. Moderation at scale: How corporate communicators can shape discussions and interactions Users with the corporate communicator role can do most moderation actions in Engage. This role sets the tone for others to follow, so know what’s available to prepare and plan for impact. Use theme moderation for broad oversight and automatic action Theme moderation is a powerful new AI capability in the Communications Dashboard that allows you to input themes that you want to monitor. You may want to monitor themes to understand employee sentiment or to reduce amplification of conversation on certain topics. Themes pick up conversations based on contextual matches, not straight text. When a conversation matches a theme, you can notify moderators, automatically mute the conversation, and/or take additional action such as blocking a post. 1 Themes created are automatically applied across all languages, unlike keywords monitoring. Theme moderation is available with Viva Employee Communications and Communities or Viva Suite license. Create a targeted list for keyword monitoring Keywords lists are best for terms that require moderation or intervention. Keyword monitoring looks for exact matches of characters, so consider common spellings for deep coverage. Mute communities for the network You can remove entire communities from everyone’s Home Feed or email digests, unless they’re a member. Consider this approach for groups that are lively but not necessarily of interest to non-members. Social or special interest communities are good candidates to mute for the network, allowing more focus on relevant news, team updates, and other org-wide communications. Mute conversations If something doesn’t need to be in broadly visible in everyone’s home feeds or email digests, use the mute option on the conversation. This keeps the thread visible in communities or storylines, and all aspects of the conversation continue to function as before. Users do not know when moderators mute their conversations. Close, move, or delete conversations Depending on the context, it may make sense to limit new comments by closing the conversation, move the thread to a new community, or delete the content entirely to avoid further issues. Have a plan for how to use these content moderation features aligned with your communication goals and company culture and values, and share widely with community admins, corporate communicators, and other admins. User controls: Helping people get the most out of Engage Moderation at the network, community, and conversation levels goes a long way. Even still, there are often calls from users to further finetune their experience. Users can close, move, or delete their own conversations in Engage. Admins and corporate communicators can also take these actions if necessary. Notification settings Stop further notifications from a conversation with the Unfollow control in the overflow menu. Unsubscribe or re-subscribe to email digests in the user settings notifications center. Mute a community Building on the network-wide control, any user can mute a community from their home feed and email digests. This is a great tool if posts from a community are popular in the network but not relevant to you. Hide someone’s messages Users can reduce the visibility of others’ content, removing posts from the home feed and email digests and visually obscuring that content if seen elsewhere. Hide messages is coming soon to general availability. Learn more about moderation in Engage View the Engage Masterclass for in-depth walkthroughs and best practices. Episode 1: Mastering admin and governance Episode 4: Effective training and adoption strategies Watch our moderation webinar, covering features and strategies for new and mature networks. See how AI theme moderation and keyword monitoring work together for holistic, proactive coverage across a network. 1 Theme blocking feature coming soon to general availability.
Introducing Community Experts in Viva Engage
We’re thrilled to announce the addition of a new role within a Viva Engage community, community experts. A community expert is a member of a community who is assigned by a community admin to serve as a subject matter expert within a specific community. Adding a community expert role to your community ensures additional support and engagement throughout the community. A community expert can mark the best answer, pin posts, and ensure valuable insights and accurate information flow within the community. However, a community expert does not have the ability to manage members, assign roles etc. like a community admin. Once designated as a ‘community expert’, that label will only show within that community. Note: This feature is available as part of your existing Microsoft 365 licensing. Community expertise is determined by community admins within your organizations, not Microsoft. Microsoft does not have the ability to define a community expert in your organization. Who can be a community expert? The role of community experts is to support peers, share valuable insights, and ensure knowledge flows across departments, making information accessible and reliable for everyone. Community experts aren’t limited to high-level executives—in fact, you should seek individuals who are deeply knowledgeable, actively engaged, and approachable. Below is a guide to identify potential community experts, with examples and scenarios to illustrate ideal candidates. Community expert capabilities today: Marking “Best answer”: With the new role, community experts can now mark an answer as the best answer on a question post. Pinning/Unpinning a post: Community experts can now pin posts that they want to highlight in a community. 1. Defining an effective Community Expert: Subject Matter Expertise: Has specialized knowledge in a field or topic that benefits others across the organization. They can answer technical questions or provide insights into niche areas. Active & Engaged: Participates regularly in community discussions, contributing thoughtful responses and guiding discussions constructively. Approachable & Helpful: Willing to share their knowledge openly, whether through direct answers or by directing people to the right resources. Trusted by Peers: Known within their team or department as a reliable source of accurate information, with a reputation for being insightful and dependable. 2. Examples of community expert personas by department Technical (Engineer): Someone who may not be the head of a department but has extensive experience in specific technical stacks (e.g., cloud infrastructure, coding languages, hardware troubleshooting). Scenario: A mid-level software engineer, often answers questions related to backend development and cloud computing in a 'teams' chat or via email or even in an Engage community, providing clear explanations and solutions. Their insights are practical and resonate with peers. Legal: A non-executive legal team member who has detailed knowledge of compliance, intellectual property, or contract law. Scenario: An associate in the legal team within a company has guided several product teams on compliance questions. While they are not in management or a senior level leader, their guidance on data protection protocols has become invaluable across departments. And they are likely to have the most accurate information or help verify what is accurate. Communications Management: A mid-level comms lead who excels in crafting messaging strategies, managing internal and external communications, and navigating crisis communications. Scenario: A communications manager frequently advises teams on tailoring messaging for key audiences. When the company has faced an issue, they have been involved and instrumental in responding to the crisis and can be trusted to speak on behalf of the organization/team. Supply Chain Operations: A logistics coordinator or mid-level operations manager with deep insight into vendor relations, inventory management, or distribution channels. Scenario: A logistics coordinator known for their in-depth understanding of vendor logistics and delivery timelines. They regularly share tips on optimizing supply chain processes, helping various departments troubleshoot and improve. Facilities Management: Someone with an understanding of facilities operations, maintenance scheduling, or building management systems. Scenario: A facilities specialist within a specific office location, consistently advises teams on equipment maintenance schedules and energy efficiency projects. Their practical experience makes him the go-to person for questions on facilities management within that office. Note: Self-nomination and peer nomination for community experts are currently in progress and coming soon. Managing community experts Assignment Assigning a community expert: Community admins in a community may assign community experts based on their knowledge and the abilities of members in that community. In the member panel in the right rail, community admins will see a new section called: “Community Experts.” In this section, there is a link to, “Assign.” Once an admin clicks on assign, it opens a modal where the admin may add experts by clicking the “Mark as expert” button. Removal Removing an expert: After assigning a community expert, an admin can remove the expert by doing the following: Navigate to the member panel in the right rail. Click on the “+” sign in the Community Experts section. Withdrawal Withdrawing from the community expert role: After being made a community expert, a user may withdraw from this role at any time by taking the following steps: In the member panel in the right rail, click on the number of experts in the community expert section. This shows all the experts in that community with the user at the top and an option to, “Withdraw.” This then opens a modal that informs the user of the action they are taking. And the user may withdraw. Community experts play a crucial role in fostering a knowledgeable and collaborative environment, enhancing community effectiveness within Viva Engage. Stay tuned for additional capabilities that will further empower community experts.
