New Viva Engage Communities Will Email Members by Default. Plan for It.
Microsoft says admins don’t need to act. Your community owners and your members’ inboxes may still feel it.
By mid-October 2026, Microsoft will have finished updating newly created Viva Engage communities so that Microsoft 365 group settings for member calendar and email subscriptions are switched on by default. In practice, people who join a new community will be subscribed to its emails and calendar invitations unless the settings are changed.
Microsoft’s reason is to support awareness and participation in new communities. That is a fair goal. It also means the first thing many people see from a new community may be an email or a meeting invite, so it pays to decide what those should say, and who is responsible for them.
What’s changing
Two details are worth noting. First, this applies to newly created communities. Existing communities follow later this fall, so you have time to prepare. Second, the control Microsoft describes sits with community owners, not with a central admin setting.
A default email is a first impression. Make sure someone decided what it says.
Why this matters for your intranet and community strategy
Awareness goes up. So does the risk of noise.
Default subscriptions help a new community get noticed. They can also add to inbox load, especially if your organization creates many communities or if owners schedule frequent events. That is our view, not Microsoft’s, and it is a reason to decide your approach rather than leave it to chance.
Community owners are the control point
Microsoft’s recommended action is for owners to review and adjust the settings in the My Account portal as needed. That puts a lot of weight on owners, many of whom may not know the setting exists. If your community owners are volunteers or champions rather than administrators, they need short, clear guidance. This is the same community-of-practice model we describe on our Community page.
Treat it as a communications decision, not just a setting
Microsoft’s own compliance note says this is a new way community communications are delivered. Even with no admin action required, it is worth a short conversation with your internal comms, HR and governance teams about when community email is appropriate, what should go through the intranet instead, and how you will handle questions.
Your intranet still carries the content
Emails and invites tell people a community exists. They shouldn’t be the only place the “why” and “how” live. Your intranet home site, hub or Community page should explain what each community is for, who owns it and how to take part, so that the email has somewhere useful to point.
A practical plan
None of this needs a project. Three steps cover it.
- Tell owners and support teamsNew communities may subscribe members to emails and calendar invitations by default. This is Microsoft’s own recommendation.
- Take stockFind out how many communities are planned or recently created, and who owns them.
- Decide the first messageWhat should a first community email or invitation say, and who sends it?
- Add a launch checklist step“Check email and calendar settings” before announcing a community.
- Point owners to the right placeThe My Account portal, under Groups I own.
- Test itCreate a test community and see what a new member actually receives.
- Document member optionsWrite down how members can manage what they receive in your tenant, so support has an answer ready.
- Watch your Message CenterMicrosoft says it will share timing before that rollout begins.
- Start with the biggestReview your largest and most active communities first.
- Update guidanceRefresh your owner guide and support scripts so nothing changes by surprise.
“New Viva Engage communities will now subscribe members to community emails and calendar invitations by default. You can review and change these settings in the My Account portal under Groups I own: myaccount.microsoft.com/groups/groups-i-own. Before you launch, decide what members should receive and when, and check how it looks in a test community.”
Training your champions and owners together is one of the cheapest ways to keep communities useful. Our persona-based training is built for that kind of short, role-specific briefing.
Key takeaways
- Newly created Viva Engage communities will have Microsoft 365 group email and calendar subscription settings enabled by default, with rollout completing by mid-October 2026.
- Members are subscribed to community emails and calendar invitations by default.
- Community owners can adjust the settings in the My Account portal. No admin action is required.
- Existing communities will be updated later this fall, and Microsoft will share timing before it begins.
- Microsoft notes this changes how community communications are delivered. Review it with your own governance teams.
- Use the quiet window to brief owners, add a launch-checklist step and test what members actually receive.
Conclusion
Default subscriptions make new communities easier to find. They also make the first email or invite part of your community experience, whether or not anyone planned it. A short owner guide, a launch checklist step and a test community are enough to turn a default into a deliberate choice.
Want to see how your communities and portal fit together? Start with an honest, no-obligation read of where you are today. Start your assessment →
Make every community email
a deliberate one.
An honest, no-obligation read of where you are today, and a clear map of what’s within reach.