Microsoft has quietly addressed a longstanding scheduling headache for organizations that run executive briefings, customer webinars, and all-hands town halls. As of July 2026, the Teams Events app on Windows and Mac lets authorized organizers create and send invitations from a shared or delegated mailbox—not just their personal account. The change, documented under Microsoft 365 Roadmap ID 561912 and now generally available to commercial tenants worldwide, aims to align the trust and continuity of Exchange mailbox delegation with Teams’ structured event tools.

What’s new with scheduling in Teams Events

When you create a webinar, town hall, or large meeting in the Teams Events app, you now see an additional planning step that asks, “Who is this event from?” Instead of defaulting to your own identity, you can choose a shared mailbox like [email protected] or a delegate mailbox that belongs to a leader or department head. Once the event is saved as a draft, the mailbox selection is locked; you cannot change it later.

The feature adds four identity models to the event creation flow:

  • Your mailbox – the classic way; the organizer’s identity is front and center.
  • A delegate mailbox – allows an authorized assistant to schedule on behalf of an executive. The visible sender can be the executive (Send As) or show the assistant acting for the executive (Send on Behalf).
  • A shared mailbox – uses a department-wide identity such as [email protected]. Multiple authenticated users can manage the event without sharing credentials.
  • An event mailbox – a new, dedicated identity created solely for that event, offering the highest degree of co-organizer parity.

The focus of the June 2026 release is the shared and delegated mailbox options. Microsoft positioned the feature for chiefs of staff, executive assistants, and communications teams, but any group that regularly produces structured events will benefit.

Who needs this (and why sender identity matters)

Executive assistants and chiefs of staff no longer have to choose between sending event invitations from a personal account (which erodes trust) or building a workaround that doesn’t fully work. A CEO’s town hall can now carry the authority of the Office of the CEO, even if an assistant handles every logistical detail.

Communications and HR departments can assert brand consistency by using shared mailboxes for recurring programs—quarterly financial briefings, employee onboarding webinars, leadership Q&As. When an employee leaves or changes roles, the event identity survives.

IT administrators gain a sanctioned path for event governance. Instead of employees sharing passwords for a generic licensed account (a security nightmare), each authorized organizer signs in as themselves while the shared mailbox provides the front-facing identity. This improves audit trails and reduces the risk of orphaned events.

Attendees may never notice the plumbing, but they are less likely to dismiss an invitation from [email protected] than from a junior coordinator they do not recognize. For external audiences, a stable event address builds trust over time.

The prerequisites: permissions and licensing

Selecting a mailbox in the Teams interface is only the surface. Behind the scenes, Exchange Online permissions determine whether you can actually send on behalf of that mailbox. The key pieces are:

  • Calendar permissions – at minimum, you need the ability to create and modify calendar items in the shared or delegate mailbox.
  • Full Access – for a shared mailbox, this permission lets you open the mailbox and manage its contents. It does not, by itself, grant Send As rights.
  • Send As – makes messages appear to come directly from the mailbox. This is a separate assignment, often configured by an Exchange administrator.
  • Send on Behalf – identifies you as acting for the mailbox owner. The recipient sees “Sarah on behalf of CEO Office.”

For an individual’s mailbox (the delegate scenario), Outlook delegate settings can provide the necessary calendar and meeting-request authority, but an admin may still need to enable Send As if the organization requires a clean executive identity.

Microsoft’s support documentation for conventional Teams meetings scheduled through shared mailboxes stipulates that either the shared mailbox or the scheduling user must hold an appropriate Teams license. Structured Teams events can introduce further licensing requirements based on attendee capacity, registration options, branding, and production tools. Teams Premium features were partially reshuffled in April 2026; some former Premium capabilities moved into Teams Enterprise, but advanced protection and intelligence still need Premium. Before testing, validate that your license tier covers the event type you intend to run.

Configuring shared and delegated mailboxes for Teams Events

A controlled rollout avoids high-profile embarrassments. The following sequence, based on Microsoft’s guidance and early adopter feedback, is a safe starting point.

  1. Identify the event ownership model. Will the event be owned by a single leader (use delegate mailbox), a functional department (use shared mailbox), or require maximum co-organizer collaboration (consider an event mailbox)?
  2. Create or audit the mailbox. Confirm the email address, display name, calendar, and that the address is visible in the global address list. Set retention policies to match your event records requirements.
  3. Assign the minimum necessary permissions. Grant Full Access and Send As (or Send on Behalf) only to the individuals who absolutely need to send event communications. Avoid broad distribution-group membership for these rights.
  4. Test in a desktop Teams client. Open the Events app, begin creating a low-stakes event, and verify the mailbox appears in the planning section. Do not rely on web or mobile clients—the roadmap lists Windows and Mac desktop support only.
  5. Validate every communication touchpoint. Send a test invitation, including updates and cancellations. Check that attendee replies go to the correct shared inbox and that registration confirmation emails show the intended sender.
  6. Test with a backup organizer. Have a second authorized user locate the event, edit details, and send an update. Confirm that co-organizer capabilities match your expectations.
  7. Document offboarding. When a staff member changes roles or leaves, remove their mailbox permissions immediately. A checklist that ties to your identity lifecycle process will prevent lingering access.

Setting up delegate access for an executive’s mailbox

For a chief of staff or executive assistant creating an event on behalf of a leader, the mailbox owner must first grant delegate access through Outlook or Exchange Online PowerShell. The available levels are:

  • Delegate (Can read and create items) – sufficient for creating and modifying events, but the assistant appears in meeting requests as acting on behalf of.
  • Send As – requires additional administrative assignment; makes the sender appear as the executive directly.

Microsoft recommends granting Send on Behalf for transparency or Send As when a singular identity is essential. Before granting broad Send As, check your organization’s compliance policy. Regulated industries may require a visible delegation trail.

Once permissions are in place, the assistant follows the same Teams Events workflow but selects the leader’s mailbox in the planning step. Other delegates who also have access can then collaborate on the event; however, be cautious about concurrent editing. Two delegates changing the audience list or date simultaneously can cause confusion.

Important constraints and dead ends

  • Mailbox selection is irrevocable after saving as draft. If you pick the wrong identity, you must create a new event from scratch. Double-check before that first save.
  • Co-organizer parity isn’t guaranteed. Microsoft warns that only the dedicated event mailbox model offers full scheduling parity for co-organizers. With shared or delegate mailboxes, a co-organizer listed in the event may not be able to edit all details—such as date, time, or registration settings.
  • Cross-platform availability is limited. The feature requires the Teams desktop app on Windows or Mac. Organizers who need to make urgent changes from a browser or mobile device cannot yet use a shared mailbox identity; they will revert to their personal mailbox.
  • Private items may leak. Outlook delegate permissions can allow a delegate to see calendar items marked private. When assigning delegate rights, review the private-item view settings to avoid unintentional exposure of sensitive appointments.
  • Audit trails require careful parsing. The visible sender in an invitation may not be the person who performed the action. Compliance teams must correlate Exchange audit logs (which show the actual user) with Teams event metadata.

What the launch means for IT administrators

This feature shifts event ownership from person-centric to service-centric. Recurring town halls, training series, and customer briefings can now be attached to a functional identity, which is easier to govern, back up, and hand off. The key administrative tasks are:

  • Review existing shared mailboxes for suitability. Many organizations already have events@, webinars@, or department-specific addresses. Ensure they are not also being used for other workflows that could conflict (e.g., automatic responses, forwarding rules).
  • Implement a permissions lifecycle. Treat mailbox access like any privileged role. Automate removal when an employee’s status changes. Consider using Privileged Identity Management (PIM) for temporary approvals, though direct integration with this feature has not been announced.
  • Update support documentation. End users will need a simple guide explaining how to select the mailbox and what to do if it is missing. Include a troubleshooting note: permission changes can take up to 24 hours to propagate across all Microsoft 365 services.
  • Plan for event recovery. Because you cannot transfer a draft’s mailbox identity, create a fallback process. For executive events, pre-authorize a second individual with identical permissions who can rebuild the event quickly if the original draft is corrupted or locked under the wrong identity.

Steps to test before going live

Before you trust this feature for a board meeting or investor briefing, run through these checks:

  1. Assign permissions and wait 24 hours. Do not assume that a newly granted Send As right will appear immediately in Teams.
  2. Create a test event using the shared mailbox. Check the sender identity in Outlook, both in the invitation header and any subsequent update messages.
  3. Have an unauthorized user attempt to select the same mailbox. They should not see it listed.
  4. Simulate an organizer departure by removing a test user’s permissions and verifying they can no longer edit the event (though they may still see it if they were added as a co-organizer).
  5. Send a cancellation from the shared mailbox. This is often overlooked but is critical for crisis communication.
  6. Validate calendar processing. Make sure attendee responses go to the correct mailbox and that the event appears on the intended calendar—not the organizer’s personal calendar.

The road ahead: features we’re still waiting for

Shared and delegated mailbox scheduling is a foundational improvement, but it does not erase every friction between Exchange calendars and Teams structured events. Several additions would make the experience truly enterprise-grade:

  • Mailbox transfer and event migration. Accidents happen. A tool to change the owning mailbox after draft save—or even after publication—would prevent hours of rework.
  • Cross-platform parity. Organizers need the ability to manage shared-mailbox events from mobile and web clients, especially when responding to last-minute changes.
  • Fine-grained event roles. Currently, co-organizer capabilities are not uniform across mailbox types. A future model might allow assigning separate “scheduling admin,” “registration manager,” and “production lead” roles, each with distinct permissions.
  • Administrative reporting. A dashboard that shows all events owned by a given shared mailbox, along with which delegates can edit them, would simplify audits and incident response.
  • Time-bound permissions. The ability to grant Send As or delegate rights that automatically expire after a specific event date would reduce the risk of dormant access.

For now, the June 2026 release closes a gap that forced many organizations into awkward compromises. By letting authorized users harness the trust of a departmental or executive identity, Microsoft has made Teams Events more reflective of how organizations actually work. The key to success will be pairing the new capability with disciplined permission management and a clear ownership strategy.