How to Configure Microsoft 365 Groups, Teams, Shared Mailboxes, and Resource Management

How to Configure Microsoft 365 Groups, Teams, Shared Mailboxes, Room Resources, and Access Management (2025 Guide)

Microsoft 365 provides powerful collaboration and resource management features that allow organizations to streamline communication, scheduling, and data security. This guide covers the latest updates (2025) for configuring Microsoft 365 Groups, Teams, Shared Mailboxes, Room and Equipment Mailboxes, Shared Calendars, and OneDrive/SharePoint Access Management.

---

1. Create Microsoft 365 Groups & Teams (Advanced Settings and Membership)

Purpose

Microsoft 365 Groups form the foundation for collaboration across Microsoft 365 apps. A Group connects a shared mailbox, calendar, SharePoint site, Planner, OneNote, and optionally a Microsoft Teams workspace. This makes it ideal for departments, project teams, and cross-functional initiatives.

Key Features

• Unified identity and permissions across Outlook, Teams, and SharePoint.
• Shared resources automatically provisioned.
• Supports advanced settings like external sharing control and privacy configuration.

Configuration Steps

Microsoft 365 Admin Center

1. Go to Microsoft 365 Admin Center.
2. Navigate to Teams & Groups → Active Teams & Groups → + Add a group.
3. Choose Microsoft 365 Group → Next.
4. Configure details:
   • Name and Description: For example, “Project Phoenix – Development Team.”
   • Group Email Alias: e.g., projectphoenix@contoso.com.
   • Privacy Settings: Choose Private (invite-only) or Public (visible to everyone).
   • Owners and Members: Add internal users and optional external members (if permitted).
5. Under Advanced Settings:
   • Enable or disable external sharing.
   • Link Group to Microsoft Teams, Planner, and SharePoint Site.
   • Enable Group expiration policies for lifecycle management.
6. Click Create Group → wait for provisioning to complete.

PowerShell

# Connect to Exchange Online
Connect-ExchangeOnline

# Create a new Microsoft 365 Group
New-UnifiedGroup -DisplayName "ProjectPhoenix" -Alias "ProjectPhoenix" `
-EmailAddresses "ProjectPhoenix@contoso.com" -AccessType Private `
-Owners "admin@contoso.com" -Members "user1@contoso.com","user2@contoso.com"

Validation

• Verify the group appears in Outlook and Microsoft Teams.
• Test sending group emails and accessing shared files in SharePoint.
• Confirm Planner and OneNote are linked correctly.

Best Practices

• Follow a consistent naming convention, e.g., Dept_ProjectName.
• Use Private Groups for confidential workstreams.
• Periodically audit membership and remove inactive users.
• Apply sensitivity labels for data protection and compliance.

Use Case

A product team creates a Microsoft 365 Group called “Project Phoenix” to collaborate on a new launch. All team members access shared emails, Teams discussions, and project files through one centralized workspace.

---

2. Manage Shared Mailboxes (Permissions, Quotas, Access)

Purpose

Shared mailboxes allow multiple users to send and receive messages from a common email address—ideal for teams like Support, HR, or Finance. They don’t require individual licenses (under 50 GB) and can be accessed through Outlook or Outlook Web App.

Configuration Steps

Exchange Admin Center

1. Open Exchange Admin Center → Recipients → Shared Mailboxes → + Add.
2. Enter:
   • Mailbox Name and Alias: e.g., “Support Team” (support@contoso.com).
   • Owners: People who can manage mailbox permissions.
3. Assign Permissions:
   • Full Access: Read all emails and send messages from the mailbox.
   • Send As: Send messages using the shared mailbox identity.
   • Send on Behalf: Sends messages labeled “on behalf of.”
4. Configure Mailbox Quotas and Archiving to avoid exceeding storage limits.

PowerShell

# Connect to Exchange Online
Connect-ExchangeOnline

# Create shared mailbox
New-Mailbox -Shared -Name "Support" -DisplayName "Support Team" -Alias "Support"

# Assign Full Access
Add-MailboxPermission -Identity "Support" -User "user1@contoso.com" -AccessRights FullAccess

# Assign Send As permission
Add-RecipientPermission -Identity "Support" -Trustee "user1@contoso.com" -AccessRights SendAs

Validation

• Ensure users can access the mailbox in Outlook under “Shared Mailboxes.”
• Test sending an email as the shared mailbox.
• Verify mailbox storage and permissions via Get-MailboxPermission.

Best Practices

• Use shared mailboxes for group communications instead of personal delegation.
• Avoid assigning too many users directly—use Microsoft 365 Groups for access control.
• Monitor mailbox size and configure auto-archiving if needed.

Use Case

A customer support team uses the “support@contoso.com” mailbox to handle customer inquiries. Multiple agents access the same inbox, ensuring continuity and faster response times.

---

3. Configure Room & Equipment Mailboxes

Purpose

Room and Equipment mailboxes automate scheduling for shared resources like conference rooms, vehicles, and laptops. They simplify booking management through Outlook or Teams.

Configuration Steps

Exchange Admin Center

1. Go to Recipients → Resources → + Add Resource.
2. Select Room Mailbox or Equipment Mailbox.
3. Define:
   • Name and Email Address: e.g., ConferenceRoom1@contoso.com.
   • Booking Options: Auto-accept meetings, prevent double bookings, and set duration limits.
4. Assign Permissions: Choose who can book directly or require approval.

PowerShell

# Create Room Mailbox
New-Mailbox -Room -Name "ConferenceRoom1" -DisplayName "Conference Room 1" -Alias "ConfRoom1"

# Set booking options
Set-CalendarProcessing -Identity "ConfRoom1" -AutomateProcessing AutoAccept `
-AllowConflicts $false -BookingWindowInDays 180

Validation

• Try booking the room via Outlook or Teams to confirm auto-accept behavior.
• Verify scheduling limits are enforced.

Best Practices

• Use AutoAccept for frequently used rooms to streamline scheduling.
• Limit bookings to 3–6 months ahead to prevent misuse.
• Audit booking logs regularly to optimize resource usage.

Use Case

“Conference Room 1” is configured to automatically accept meeting requests for available times, eliminating double bookings and improving efficiency.

---

4. Configure Shared Calendars & Scheduling Permissions

Purpose

Shared calendars allow teams to coordinate projects, deadlines, and meetings efficiently. They help visualize availability and manage shared resources.

Configuration Steps

Outlook or Outlook Web App

1. Open Calendar → Share Calendar.
2. Add users or groups.
3. Assign permissions:
   • Can View: For basic visibility.
   • Can Edit: For collaboration.
   • Delegate: For full scheduling control.

PowerShell

# Grant calendar access
Add-MailboxFolderPermission -Identity "user1@contoso.com:\Calendar" `
-User "user2@contoso.com" -AccessRights Editor

Validation

• Have another user check access through Outlook.
• Create a meeting to confirm shared visibility and updates.

Best Practices

• Use shared mailboxes for team-wide calendars.
• Avoid granting full delegate access unless necessary.
• Train staff to use shared calendars for transparency and workload balance.

Use Case

The project management team shares a calendar to track milestones, ensuring all members stay aligned with upcoming deadlines.

---

5. OneDrive & SharePoint Access Management

Purpose

Managing permissions in OneDrive and SharePoint ensures data is accessible to the right users while protecting sensitive information from unauthorized access.

Configuration Steps

Microsoft 365 Admin Center

1. Navigate to SharePoint Admin Center or OneDrive Settings.
2. Manage Site Permissions:
   • Owners: Full control.
   • Members: Edit access.
   • Visitors: Read-only access.
3. Configure Sharing Settings:
   • Restrict to internal users only or allow external sharing.
   • Set link expiration policies.

PowerShell

# Connect to SharePoint Online
Connect-SPOService -Url "https://contoso-admin.sharepoint.com"

# Grant access to user
Set-SPOUser -Site "https://contoso.sharepoint.com/sites/ProjectX" `
-LoginName "user1@contoso.com" -IsSiteCollectionAdmin $false

Validation

• Test file access using a member and external guest account.
• Confirm external sharing policies are enforced.

Best Practices

• Enforce least privilege—grant minimal required access.
• Conduct quarterly permission audits.
• Apply Sensitivity Labels to secure confidential files.
• Use Conditional Access Policies for external users.

Use Case

The “Project X” SharePoint site is configured to grant edit permissions only to internal project members, ensuring secure collaboration on sensitive documents.

---

Final Recommendations

• Standardize all resource names and permissions through naming policies.
• Automate membership reviews using Azure AD Access Reviews.
• Use Microsoft Purview to monitor compliance across shared resources.
• Educate users on safe collaboration practices and external sharing guidelines.

---