Microsoft 365 group calendar or a shared calendar: who can cancel, who gets invited
A team schedule in Outlook can live on a Microsoft 365 group calendar or on one person’s calendar shared with the team. They behave differently in two ways that matter in practice: who can cancel an event, and whether members are invited at all. Arte Soft, the developer of Cloud Calendars, compares them.
Choose where the event lives
| Question | Group calendar | Shared personal calendar |
|---|---|---|
| Who can edit or cancel events? | Anyone in the group | The owner and appropriately authorised editors or delegates; meeting actions still need the applicable organising or delegation rights |
| Are members invited? | New/web: add the group or use Invite members. Classic: group alias is pre-populated; remove it if invitations are not intended. | Only the attendees you add |
| Who controls access? | Group membership | You, per person |
| Best for | Rotas, deadlines, shared logistics | Meetings one person must control |
What most people assume
Putting an event on the group calendar invites everyone in the group.
Group calendar: shared ownership
Microsoft says each Microsoft 365 group has a shared calendar where every member can schedule, edit and see upcoming events. It also says that when an event is created on the group calendar, anyone in the group can cancel it — unlike an event on your own calendar, where you are in charge of editing or cancelling.
That suits a rota or shared deadlines list maintained by everyone. It does not suit a client meeting whose time only the organiser should control.
Inspect invitations: the default differs by client
In new Outlook, Outlook on the web and Outlook.com, Microsoft says creating a group-calendar event does not invite every member by default. Add the group to attendees when an invitation is intended; new Outlook also offers Invite members. The creator is automatically added as an attendee and receives the group event on their personal calendar in these documented flows.
Classic Outlook is different: Microsoft says the group alias is already in Required attendees when you create the group meeting. Remove the group if you do not intend invitations to its members. Whichever client you use, inspect the actual attendee list before sending rather than relying on one universal default.
Shared personal calendar: one owner
The alternative is a calendar you own and share with the team at a chosen level: Can view when I’m busy, Can view titles and locations, Can view all details, Can edit or Delegate (the last two only inside your organisation). You decide who can change it, and can remove access later.
Do not try to give a whole team delegate rights through a security group: Microsoft’s best practice says setting a security group as a delegate is not supported.
Worked example: an events team
A fictional events team of six has two needs. First, a shared list of venue deadlines and staff on-site days, which any member updates. Second, client walkthroughs that the team lead schedules and that should not be moved by others.
Deadlines and on-site days go on the group calendar. Before saving, the creator makes sure the group is not in the attendee list when no invitations are intended; in classic Outlook that can require removing the pre-populated group alias. Client walkthroughs go on the lead’s own calendar with the client and relevant staff invited. The team gets Can view titles and locations on that calendar, not editing or delegation rights.
Check: a member opens the group calendar and confirms they can edit a deadline; another member confirms they can see the walkthrough title but cannot move it.
What it looks like
Cloud Calendars overview, using our product images. Provider settings and protocol examples described in this guide are separate from the screens shown here.
What to do
- Put shared, low-stakes items on the group calendar.
- Keep meetings whose time must not change on an owned calendar.
- For group events, inspect attendees before saving: add the group when invitations are needed; in classic Outlook remove its pre-populated alias when they are not.
- Share your owned calendar at the lowest useful level instead of making everyone a delegate.
- Test that a member can or cannot change an event as intended.
Questions
- Why didn’t members get an invitation for a group calendar event?
- In new Outlook, Outlook on the web and Outlook.com, Microsoft says the whole group is not invited by default; add it as an attendee. In classic Outlook the group alias is pre-populated in Required, so check whether it was removed. Inspect the actual attendee list and client rather than assuming one shared default.
- A colleague cancelled an event I put on the group calendar. Is that allowed?
- Yes. Microsoft states anyone in the group can cancel an event created on the group calendar.
- Can I make a security group my delegate instead?
- Microsoft says setting a security group as a delegate is not supported; add individual people.