New Viva Engage Capabilities Now Available to All Engage Customers
Many of you told us that creating, organizing, and sharing content in Engage could be easier and we’ve taken that to heart. We’re excited to announce that several highly requested features: draft and schedule posts, storyline cover photos and AMAs, featured posts and ‘post on behalf of’ are now available for all Engage customers. These updates are designed to give employees more flexibility and help leaders and communicators share their messages more effectively. Draft and Schedule Posts We heard you, timing matters. Employees can now draft and schedule posts in their communities or storyline. Whether you want to plan for a big announcement or simply polish your message before sharing, this feature makes it simple to organize your posts and publish them when the moment is right. Learn more about drafting and scheduling posts here. New Storyline capabilities Storyline Cover Photos Storyline in Viva Engage is a personal feed where employees and leaders share updates, ideas, and experiences to connect and engage across the organization. Now, give your Storyline a more personal, branded look. With cover photos, everyone can customize the visual identity of their Storyline, helping their posts stand out and feel more connected to their organization’s culture. Storyline Delegate Posting Communication teams can now help leaders shine. With delegate posting or post on behalf of (POBO), designated communicators can draft and publish posts for leaders directly in their Storyline — keeping voices consistent and messages impactful. Read more about how to set up delegate posting here. Storyline can be enabled for certain groups within your organization, empower leaders or subject matter experts to test these new experiences. Learn more about how to get the most out of Storyline in our Storyline playbook. Featured Posts Sometimes a message needs extra visibility. With featured posts, admins and corporate communicators can spotlight important content, so it reaches more people: Featured posts get priority placement in the Home Feed and in Discovery emails. They may also appear in digest emails and other recommendation slots powered by machine learning. In private communities, featured posts respect boundaries and are only shown to members of that community. Learn more about featuring a post here. AMAs Employees want more direct access to leaders. With Ask Me Anything (AMA) sessions, leaders can host open Q&As on their storyline, where employees can submit questions and comment anonymously, and get real-time responses, all in one familiar place. Organizers can also moderate questions and export them for analysis, making it easier than ever to understand what’s top of mind for employees. It’s a simple, authentic way to build trust and spark dialogue. Learn more about hosting successful AMAs in our AMA playbook. For more information on setting up AMAs read our support docs. We’re thrilled to bring these new features to life and can’t wait to see how they empower you to connect, share, and lead more effectively across Viva Engage. Stay tuned—there’s even more innovation on the horizon.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.Microsoft 365 Copilot is coming to Viva Engage
We’re excited to announce that Microsoft 365 Copilot is coming to Viva Engage. Copilot in Engage is now smarter, faster, and personalized-designed to boost your productivity. Operating as an assistant, it helps you stay informed, catch up quickly, and get more out of your interactions across Viva Engage. Catch up on community conversations, get insights from colleagues, find posts from leaders, see what’s trending, and recall key updates-Copilot in Engage brings you the information you need, right when you need it. Stay in flow with context-aware productivity Copilot in Engage is context-aware and recognizes when you're in a community, storyline, campaign, or a single conversation. It tailors responses to your current workspace, helping you catch up faster and find what you need, all while staying focused on your current context. Copilot in Engage also includes contextual, pre-populated prompts designed to help you maximize value. Contextual prompts adapt dynamically as you navigate from one surface to another on Viva Engage, providing AI-powered assistance throughout your experience. Stay in the loop with smart catch-up cards Get the latest updates across your network and inside specific communities on Engage by asking Copilot to catch you up – all in a single click. You’ll get clean, organized summaries that help you focus on what truly matters. Curious about what people are buzzing about across your organization? Prompt Copilot to show you what’s trending across Engage. You’ll see popular content grouped by themes. Clicking on a theme takes you to a new Themes Feed, where you can explore all the conversations that contribute to that trend. It’s never been easier to see what captures your organization’s attention. Find what you need when you need it with effortless search Whether you’re hunting for a specific post in a community or catching up on everything shared in communities you follow, Copilot now has enhanced contextual search to track down what you’re looking for in Viva Engage. Here are examples of how Copilot in Engage search can assist you: Find the post my teammate shared in the PM Learnings Community What are the latest updates across all the communities I follow Show me posts from the last week related to <insert subject> Catch me up on where I’ve been mentioned Whether you’re asking something broad or diving into specifics, Copilot in Engage is here to help you stay connected, informed, and in control Write better with Copilot’s improved writing assistance Sharing updates just got smarter. Want to post a quick recap of what your team’s been up to this past month? Copilot in Engage now has enhanced writing assistance that can pull in relevant context from Teams and Outlook. Effortlessly connect the dots and craft more complete, informed updates, without starting from scratch. The future of workplace productivity in your communities and conversations is here. With new Copilot capabilities in Engage, you’re a step ahead—more connected, more informed, and more empowered. Now rolling out to general availability, customers can unlock the full potential of the Copilot experiences in Viva Engage with a Microsoft 365 Copilot license. We’d love your feedback If something works well or could be improved, just click the thumbs up or thumbs down icon on any Copilot response. This feedback goes directly to the Copilot team and is regularly reviewed to help us refine the experience. You can also share your thoughts through the Message Center posts or in the comments below — we’d love to hear from you. Learn more: Viva Engage set up requirements Get Started with Microsoft 365 Copilot in Viva Engage Set up Microsoft 365 Copilot in Viva Engage (IT/admins)
Copilot Adoption Community Now Available for All Viva Engage Customers
We’re excited to announce a major update: the Copilot Adoption Community is now available to all Viva Engage customers. This means that whether you’re exploring M365 Copilot, leveraging Copilot Chat, or simply seeking to build Copilot fluency, you can now deploy the Copilot Adoption Community and enable a new level of peer-driven AI learning and support within your organization. What is the Copilot Adoption Community? The Copilot Adoption Community is a ready-to-use experience within Viva Engage. Originally, access required a M365 Copilot license, and now available to every employee on your Viva Engage network. With the expansion of Copilot Chat and the broader availability of Microsoft AI-powered tools, organizations need a central, easily accessible space to: Discover what Copilot tools can do Exchange best practices, prompts, and success stories Ask questions and get peer or expert support Track what’s working and where further support is needed What’s Included? Community banner and easy setup checklist Welcome post and suggested Copilot adoption content to jumpstart engagement Suggested members based on M365 Copilot licenses Scalable Q&A capabilities via Answers in Viva Analytics to monitor reach, activity, and unanswered questions Real-World Impact Organizations who have enabled the Copilot Adoption Community report: Significantly higher Copilot adoption rates compared to those without a community Increased sharing of helpful prompts and creative use cases Faster peer-to-peer learning and more confident experimentation Lower support overhead for Copilot and AI-related questions Customers using Copilot Adoption Communities have a 35% higher M365 Copilot adoption rate than those who don't. How to Enable the Copilot Adoption Community Follow the instructions here: Microsoft 365 Copilot adoption community in Viva Engage | Microsoft Learn Get started today: Check your Viva Engage admin panel Look for the Copilot Adoption Community Activate, welcome your members, and start posting Want to learn more and see the Copilot Adoption Community in action? Watch the info video or the recording of the Training and Adoption Masterclass (one of our six Viva Engage Masterclasses). Check out other Copilot adoption resources: Create a Viva Engage Copilot passport campaign Read how Microsoft is using the Viva Engage Copilot Community Use the Copilot Champs Community Framework Microsoft's guide to deploying Copilot for Microsoft 365
Viva Engage Public Content is Now Available in Microsoft 365 Copilot
We understand the value of information in your Viva Engage network, whether it’s a post from a leader, an answer to a question or in a community. So, we’ve made public information from across Viva Engage available in Microsoft 365 Copilot — starting with Q&A and now including discussion posts. This includes public discussion posts from public communities, events, Answers and Storylines. We are delighted to bring this new content source to Copilot, making the everyday conversations, Answers, events and leadership posts more discoverable so that, if a user asks a question and relevant information is available in Engage, it will be highlighted in the Microsoft 365 Copilot response. This ensures users receive high-quality answers that fully address their queries. Engage content is also available in agents like Researcher (built into the default Copilot experience) where users can scope the source to just Viva Engage as necessary. Eager to get started? Try out some of these prompts in Copilot: Tip: when using these prompts specifying “Viva Engage or Engage” in the prompt will return better results. “What did I miss in Engage in the past 2 weeks?” “What has <your favorite coworker> posted recently in Engage?” “What are my coworkers saying about <topic>? In Engage” “Show me the post regarding <topic> that <your favorite coworker> posted in Engage” “From the discussions in Engage, what is the AI strategy in my company and how are people reacting to it?” We can’t wait for you to test out this new Copilot capability. It’s all about helping you stay informed, inspired, and connected with your Engage content. We encourage you to send us feedback with a thumbs up/down and “#GraphConnector” in the text box. For additional information check out our support documentation.
Introducing Teams Q&A export API on Microsoft Graph Beta
We are thrilled to announce the availability of the Teams Q&A Export API in Microsoft Graph Beta: Use the Microsoft Graph API to work with Microsoft Teams. It enables programmatic access to Q&A content across Microsoft Teams meetings, webinars, and town halls, addressing a key need for data portability and cross-platform interoperability of question & answer (Q&A) conversations messages for a tenant. The new Export API, the API returns a just-in-time snapshot of all Q&A activity in JSON format. The API supports app-only access and does not support delegated permissions. We encourage you to try out these APIs and reach out to us with your feedback. See Microsoft Graph REST API beta endpoint reference to learn more about the MS Graph beta program and best ways to provide feedback. Pre-requisites to test the API: Testing instructions below require Bruno API platform setup Some steps require tenant admin approval To test the API, follow the steps below: Register a new app in Azure Active Directory (Entra) a. Go to Register an application - Microsoft Azure and register a new application. b. Specify your custom callback URL. Note the Application (client) ID and Directory (tenant) ID. This information will be required in the following steps. Note the OAuth 2.0 endpoints. This information will be required in the following steps. Request API permissions: a. In the API permissions tab, select Add a permission and select Microsoft Graph. b. Select Application permissions to use app-only access, without a signed-in user. c. Select EngagementMeetingConversation.Read.All. Share your app’s API permission URL with a tenant admin to get admin consent for your app to use these permissions. Create a new client secret under the Certificate & secrets tab. A refresh is recommended every 6 months as a security best practice. Note the Secret ID. This information will be required in the following steps. Set up Q&A messages GET request on Bruno: a. Request type: GET b. Request URL: https://graph.microsoft.com/beta/communications/getAllOnlineMeetingMessages?$expand=conversation c. Set up Auth: i. Select type as OAuth 2.0 ii. Input Access Token URL: This is the token endpoint noted in step 3. iii. Input Client ID: This is the Application (client) ID noted in step 2. iv. Input Client Secret: This is the Secret ID noted in step 7. v. Input Scope: https://graph.microsoft.com/.default d. Select Get Access Token Send request: If the request is submitted successfully, a 200 OK response will be returned along with a response body containing question and answer (Q&A) conversation messages. Get a list of reactions by setting up a List reactions GET Request: https://graph.microsoft.com/beta/communications/onlineMeetingConversations/{onlineMeetingEngagementConversationId}/messages/{engagementConversationMessageId}/reactions. If the request is submitted successfully, a 200 OK response will be returned along with a response body containing question and answer (Q&A) conversation message reactions. We hope you like this new API capability, helping you get the most out of your Teams Q&A experience.Calling Legacy Viva Engage (Yammer) APIs via an Entra application
The Yammer application platform that enabled access to legacy Viva Engage (Yammer) REST APIs via OAuth2 tokens will be officially retired on June 30, 2025. To ensure uninterrupted access, all customers must transition to using Microsoft Entra applications as soon as possible. The good news? The legacy Yammer APIs are fully supported through modern, secure Entra apps — and getting started is easier than you might think. This blog provides a step-by-step walkthrough for calling Yammer APIs using an Entra application with PowerShell 7, leveraging MSAL for interactive authentication. We will call /users/current.json - Yammer | Microsoft Learn API to fetch the details of the user, who completes the authentication flow. Note: The examples in this post assume you have PowerShell 7 and the MSAL module pre-installed. If you're looking for a Postman-based guide to access Yammer APIs, you can find detailed instructions here. Let’s dive into how you can make this transition smoothly and start using Entra-authenticated API calls today. Step 1: Register an Entra App For detailed information on Entra application registration flow, refer to this guide. Go to Azure Portal: https://portal.azure.com Navigate to: Azure Active Directory → App registrations → New registration Fill in the form: Name: e.g., Yammer API Test Supported account types: Choose based on your org (e.g., "Accounts in this organizational directory only") Select platform: Choose “Public client/native (mobile & desktop)” Redirect URI: Set the right redirect url, e.g., http://localhost Click Register Step 2: Configure the App Authentication Go to the Authentication tab Under Advanced settings, set: Allow public client flows → Yes Click Save API Permissions Go to API permissions Click Add a permission Select Yammer Select Delegated → access_as_user Click Add permissions to save Step 3: Prepare the PowerShell Script Save the following as YammerAPI.ps1: # Clear MSAL token cache Clear-MsalTokenCache # Define app credentials $clientId = "YOUR_CLIENT_ID" $tenantId = "YOUR_TENANT_ID" $redirectUri = "http://localhost" $scopes = @(" https://www.yammer.com/.default") # Trigger interactive login $authResult = Get-MsalToken -ClientId $clientId -TenantId $tenantId -RedirectUri $redirectUri -Scopes $scopes -Interactive $token = $authResult.AccessToken # Call Yammer API $response = Invoke-RestMethod -Method Get -Uri "https://www.yammer.com/api/v1/users/current.json" -Headers @{Authorization = "Bearer $token"} $response Now, replace YOUR_CLIENT_ID and YOUR_TENANT_ID with values from your app registration. Step 4: Run the Script In PowerShell 7: > pwsh "C:\Path\To\YammerAPI.ps1" You will be prompted to sign in interactively. Once authenticated, the script will call the Yammer API and return your user info. We’re looking forward to hearing your feedback and thoughts about using the legacy Viva Engage (Yammer) APIs via modern Entra-based authentication and how you’ll use it to better manage users, conversations, and communities within Viva Engage. Stay tuned! Aditi is a product manager at Microsoft
Modern External Networks is now generally available to all Engage customers
We are excited to announce the modernization of external networks with Viva Engage! Modern external networks will continue to promote collaboration between users and teams from different companies, known as external participants, to communicate and share information in an industry-standard secure environment. Admins can configure these modern external networks to partners, consultants, and other outside companies to conduct team discussions, share files, and collaborate on projects.New for communicators: Theme moderation in Viva Engage
Moderation in Viva Engage just got easier and more impactful, thanks to new proactive, AI-powered capabilities. Engage network admins and corporate communicators can now use theme moderation to keep an eye on conversations. Theme moderation is available as part of the new Communications Dashboard within Engage. Theme moderation is now rolling out for Viva suite and Employee Communications & Communities customers. Theme moderation requires a user to have the corporate communicator, network admin, or global admin role. How does theme moderation work? Creating and moderating with themes in your network allows you to customize how you target and track messages. Themes are not required to be exact matches like keywords, instead they can be either broad topics or specific words or phrases. Once enabled, theme moderation is always-on, working tirelessly on your behalf to scan and monitor conversations. It leverages the power of AI and LLMs to detect conversations across languages and context to extend the powers of moderators beyond what is possible through traditional keyword monitoring or human effort. Setting up theme moderation Simply define themes by typing in the word, phrase, or concept you’d like to monitor. You have the option to automatically mute all matched conversations upon detection. Muting removes conversations from the Engage home feed and email digests, significantly reducing reach. Auto-mute and themes work together to help moderators keep conversations professional and productive within their network. When conversations match themes, they show up in the detected conversations table. From there, moderators can take further action or adjust criteria to meet their needs. Conversations can be manually muted and reviewed after detection How do themes and keywords fit together? Themes and keywords work together to moderate conversations across Engage. While themes benefit from contextual matches and LLM technology, keywords monitoring looks for exact matches based on your criteria. Themes are best for capturing broadly specific discussions where language evolves and automatic actions like mute are necessary. Keywords are well suited for unique, relatively static terms. Customers with access to both themes and keywords may find that over time, themes are the primary path to monitoring and moderating at scale. Consider the impact moderators can have with both tools together. Learn more about moderation in Engage Moderation is an important part of the communications lifecycle. Check out our other related resources: Communications dashboard: Advanced moderation - Microsoft Support Moderation in Engage webinar recording: Viva Engage Digital Safety Moderation Webinar Engage Masterclass: Mastering admin and governance Watch session: Mastering admin and governance in Viva Engage (Customer Hub) – Microsoft Adoption Share, move, and mute conversations in Viva Engage - Microsoft Support Spencer Perry is a Principal Product Manager at MicrosoftIntroducing Viva Engage Role Management APIs on Microsoft Graph API
The Viva Engage team is consistently working to prioritize customer requests, so we're excited to introduce Viva Engage Role Management APIs now available in Microsoft Graph Beta: Use the Microsoft Graph API to work with Viva Engage (preview). These APIs will help admins and those with appropriate non-admin privileges to automate the role assignments, reading, assigning, and demoting users from a specific Viva Engage role not defined in Entra. Other Viva Engage roles such as Yammer administrator and Knowledge Managers were already supported in Microsoft Graph API via Entra. The new APIs will be supported via app-delegated (user auth) and app-only access. Feel free to try out these APIs and reach out to us with your feedback. See Microsoft Graph REST API beta endpoint reference to learn more about the MS Graph beta program and best ways to provide feedback. The prerequisites for testing these APIs are: Admin access to run APIs using Graph Explorer Some APIs require tenant admin approval. Ensure to use the correct role id for assignment. The role ids supported by these APIs are: Corporate Communicator: 77aa47ad-96fe-4ecc-8024-fd1ac5e28f17 Network Administrator: ec759127-089f-4f91-8dfc-03a30b51cb38 Verified Administrator: 966b8ec4-6457-4f22-bd3c-5a2520e98f4a Please make sure to read through the Use the Microsoft Graph API to work with Viva Engage (preview)guide before you begin Read Viva Engage admin/non-admin roles via role management API To start with the testing of these APIs, please follow the steps below. Register a new app in Azure Active Directory (Entra) Go to Register an application - Microsoft Azureand register a new application. Specify your custom callback url. Select tokens to be issued by authorization endpoint Click on ‘Authentication’ tab -> Check ‘Access tokens’ and ‘ID tokens’ -> Click save Request API Permissions Go to ‘API permissions’ tab -> Click on ‘Add a permission’ -> Select ‘Microsoft Graph’ Choose ‘Delegated permissions’ if testing the API with your own credentials. Choose ‘Application permissions’ if you wish to use app-only access, without a signed in user. Choose between Read.All or ReadWrite.All permissions. Role assignment/creation requires EngagementRole.ReadWrite.All permission, but if you only want to test the roles read operation, less privileged access EngagementRole.Read.All should be used: Before your app can use these permissions, an admin must approve them. Share your app’s API permission url with a tenant admin, and ask them to grant admin consent: After admin consent is granted, you will see it as shown below. Create Role Management POST request url & body Login to Graph Explorer and get required permissions to test the APIs. Set up the Add a user as a corporate communicator POST request on Graph Explorer. Set, Request type: POST and Request URL: https://graph.microsoft.com/beta/employeeExperience/roles/{engagementRoleId}/members Click on ‘Request Body’ tab & provide required parameter. https://graph.microsoft.com/beta/users(‘targetUserEntraId’) o TIP: To find Entra id of the target user to be added a role, visit Users - Microsoft Azure portal and click on the specific user you are looking for. Copy the ‘Object id’ Send request. If the request is submitted successfully, a ‘204 No Content response will be returned. Read the assigned roles for a role Id/role type Use a new Graph Explorer tab to poll for created role status: Set Request Type: GET and Request URL: https://graph.microsoft.com/beta/employeeExperience/roles/{engagementRoleId} /members Send request. Once, role assignment is complete, the API will return a ‘200 OK’ response, with a list of users with a specific Viva Engage role. Read role assigned to the logged in user Use a new Graph Explorer tab to read your assigned roles: Set Request Type = GET & Request URL = https://graph.microsoft.com/beta/me/employeeExperience/assignedRoles Upon success, a ‘200 OK’ response is returned along with Response body containing Role id and name. To check the roles assignment for various roles, feel free to look up the assigned roles on Viva Engage Admin Center.
