A module within Microsoft Viva that serves as an enterprise social networking platform. It fosters community building, open dialogue, and knowledge sharing across an organization.
Hi @Rohit Raj
For your scenario, unfortunately, there isn’t a special or temporary “test community” concept available in Viva Engage. Communities are simply standard Engage communities within your tenant, and they are created the same way whether for production or testing.
For testing purposes, the recommended approach is to create a normal community, as AI mentioned. You can create either a private community (recommended so it doesn’t affect other users) or a public one if needed, and then delete it once your testing is complete.
One important point to note is that, currently, there is no documented or supported API approach to create or delete Viva Engage communities programmatically. Because of this, the typical workflow for your use case would be:
- Manually create a test community (ideally private)
- Use that community to validate your automation (posting logic, etc.)
- Once validated, update your code to point to the actual production community
If you need stronger isolation, another option is to use a separate test tenant, which is commonly recommended for development and experimentation scenarios.
Hope this helps. If you have any other questions, please don’t hesitate to ask.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.