Back in March 2025, Microsoft has retired POST https://www.yammer.com/api/v1/group, so our organisation has switched to Graph API for automated community creation via POST /employeeExperience/communities.
We continue using legacy APIs for posting messages to community (https://api.yammer.com/api/v1/messages.json), setting posting restrictions (PUT https://api.yammer.com/api/v1/groups/{vivaId}), and pinning messages (https://web.yammer.com/graphql). Sadly, new Graph API endpoint /employeeExperience/communities does not support these methods, and we fear that they will be retired as well, leaving no way for automation.
Can Microsoft consider expanding Graph API with the following functionality?
- Expand PATCH /employeeExperience/communities/{communityId} - to allow setting posting restrictions in the community, currently available from UI only.
- New endpoint to post a message/announcement to community through Graph API.
- New endpoint to pin a message to community through Graph API.
No CommentsBe the first to comment