Microsoft 365 Shared Calendar & Resource Mailbox Documentation

1. Overview

Microsoft 365 (Exchange Online) provides multiple mailbox types designed for different collaboration scenarios. When implementing a shared agenda (shared calendar) for a group of users, choosing the correct mailbox type is critical for governance, automation, and long-term manageability.

This document explains: - Resource mailbox types - Shared mailbox usage for calendars - Auto-mapping behavior - Best practices for implementation - Governance considerations - PowerShell configuration examples

2. Mailbox Types in Exchange Online

2.1 Resource Mailboxes

There are ONLY two official resource mailbox types:

Room Mailbox

Used for: - Meeting rooms - Conference rooms - Flex desks

Features: - Built-in calendar auto-processing - Automatic accept/decline logic - Capacity settings - Booking policies

Equipment Mailbox

Used for: - Projectors - Cars - Laptops - Cameras - Shared devices

Features: - Auto-accept processing - Availability tracking - Designed for reservable assets

Important: Resource mailboxes are intended for booking physical resources, not collaborative team calendars.

2.2 Shared Mailbox

A Shared Mailbox is NOT a resource mailbox, but is the recommended solution for shared team calendars.

Used for: - Shared agendas - Team email addresses - Department communication

Key advantages: - Dedicated calendar - Central permission management - No license required (under 50GB) - Supports Outlook auto-mapping - Works in Outlook Desktop, Web, and New Outlook

For a shared agenda where users only need calendar access, a shared mailbox is the best technical solution.

3. Recommended Solution for a Shared Agenda

Use a Shared Mailbox

Example: teamagenda@company.com

Why this is best: - Clean separation from personal calendars - Easy to manage permissions - No auto-booking conflicts (like room mailboxes) - Fully supported by Microsoft

Users simply ignore the inbox and use the calendar only.

4. Auto-Mapping Explained

Auto-mapping determines whether a shared mailbox automatically appears in Outlook.

It is controlled ONLY via PowerShell using:

-AutoMapping $true / $false

Important facts:

• Auto-mapping is ON by default
• There is NO visible toggle in Exchange Admin Center
• It works only when permissions are assigned directly to users
• It does NOT work when assigned via a security group

5. PowerShell Configuration

Assign Full Access with Auto-Mapping

Add-MailboxPermission -Identity teamagenda@company.com -User user@company.com -AccessRights FullAccess ` -AutoMapping $true

If Auto-Mapping was disabled previously, remove and re-add the permission.

6. Management Strategy Comparison

Direct User Assignment: Pros: - Mailbox auto-appears in Outlook Cons: - Harder to manage at scale

Security Group Assignment: Pros: - Cleaner governance - Easier onboarding/offboarding Cons: - Users must manually add mailbox once

7. Outlook Behavior

Outlook Desktop: - Requires restart - May take 30--60 minutes to sync

Outlook Web: - Usually appears automatically - Can be manually opened once

New Outlook: - May require manual addition once

8. Governance Best Practices

For small teams (<10 users): Direct assignment may be acceptable.

For larger organizations: Use security groups for permission management.

Naming conventions: Agenda - Sales Team Agenda - HR Team Agenda - Planning

Always document: - Owner of the mailbox - Permission model - Business purpose

9. When NOT to Use Other Options

Do NOT use: - Room mailboxes for team calendars - Equipment mailboxes for collaboration - Public folders (legacy) - M365 Groups (if only calendar is needed)

10. Final Recommendation

For a shared agenda where users only need calendar access:

Create a Shared Mailbox. Assign Full Access. Decide between auto-mapping convenience vs governance scalability.

This approach is stable, Microsoft-supported, and future-proof.