Viva Engage Notifications

For ordinary community email notifications, Microsoft documents user-controlled preferences, not an administrator-enforced default. Its notification FAQ explicitly says administrators cannot set default email settings for the network. I could not verify a supported Microsoft Graph, PowerShell, or admin-center method that silently subscribes every new community member or forces an opt-out model. For your departmental pilot, include notification setup in onboarding: users open their Engage notification settings and select the communities whose new activity they want emailed. Test this with a new member before rolling it out. Keep that separate from announcements: community administrators can use announcements for important updates, including essential email delivery beyond normal preferences where that option is available. That does not enable ongoing emails for every conversation. Use announcements selectively and measure participation in the pilot. I cannot confirm a roadmap date for centrally managed subscriptions; submit that requirement through Microsoft's product feedback channel.