500 Internal Server Error when trying to access the Microsoft Graph API for Viva Engage
I am experiencing an issue when trying to access the Microsoft Graph API for Viva Engage: https://learn.microsoft.com/en-us/graph/api/resources/community?view=graph-rest-1.0 Every time I make an API request, I receive a 500 Internal Server Error response. Here are the steps I have taken so far: Created an App Registration in Azure AD. Assigned the Community.ReadWrite.All permission as per the documentation. Ensured that the token we are using includes the correct and valid permissions. Despite completing these steps, the error persists. Below is a screenshot of the error encountered when testing the API using Postman: Are there any steps I might have missed, or is the API currently experiencing issues?Introducing the newly-launched Viva Training page
We're thrilled to introduce the centralized hub for all Viva training modules and learning paths. Dive right into: Selecting a Viva learning path or training module tailored to your needs. Discovering what's trending with Viva learning paths and training modules. Accessing the Microsoft Viva Adoption Center. Engaging with the vibrant Viva Tech Community. Browsing through detailed technical documentation to seamlessly plan, deploy, and utilize Viva in your organization. Don't miss out! Dive into the future of learning with Microsoft Viva. Check it out now!
PS - concise explanation of difference between culture and engagement surveys
Hello! I have a client who has been doing culture surveys for a couple of years and is now looking to design a more encompassing employee listening strategy incorporating engagement, culture, D&I, exit, onboarding etc. To take to their stakeholders, they would like a good and concise way to explain the difference between culture and engagement. I've been through the materials from trainings and community etc, but can't seem to find anything relevant. If anyone has a good paper to share, or effective anecdotes/metaphors that work well, that'd be greatly appreciated! Many thanks, Pablo
