New Outlook: Not Sending Calendar Invites to Attendees on MacBook

Based on the provided information and context, this behavior is not covered by a specific documented bug or fix. However, the following targeted steps are supported by the context and align with how New Outlook for Mac calendar and event sending work:

1. Confirm the account type in New Outlook for Mac
   • New Outlook calendar sending features (Scheduling Assistant, Room Finder, RSVP, etc.) are designed for Microsoft 365 or Exchange accounts.
   • In Outlook for Mac, verify that the VP is using a Microsoft 365 or Exchange account for the calendar where the event is being created.
   • If the event is being created on a non‑Exchange calendar (local/Internet-only), move to an Exchange/Microsoft 365 calendar and test again.
2. Recreate the event using the supported New Event flow
   • In New Outlook for Mac:
     1. Click the drop‑down next to New Message and select New Event.
     2. In New Event, enter the event name.
     3. Use Add required people to add attendees (internal and external).
     4. Set the time, recurrence (if needed), and location.
     5. Click Send (not just Save) so Outlook sends the invite rather than only saving an appointment.
   • This flow is explicitly supported for sending invites and should result in invitations being delivered and tracked.
3. Use Scheduling Assistant to validate attendee resolution
   • In the New Event window, select … → Scheduling Assistant.
   • Confirm that each attendee resolves correctly (shows as a row with availability) and that there are no invalid or unresolved addresses.
   • If attendees appear correctly here, Outlook should treat the item as a meeting and send invitations when Send is clicked.
4. Compare behavior with Outlook on the web and Legacy Outlook
   • Since OWA and Legacy Outlook successfully send invites for the same mailbox, the mailbox and server-side configuration are working.
   • Use OWA/Legacy Outlook as a baseline: create a test meeting with the same attendees and confirm that:
     • The meeting appears in the VP’s calendar.
     • Attendees receive the invite.
   • Then repeat the same test in New Outlook for Mac using the New Event flow above and compare results.
5. Reset New Outlook local state (if New Outlook is malfunctioning)
   • If New Outlook is generally misbehaving (e.g., similar to the “Something went wrong” or startup issues described in the context), clear the New Outlook local state and reconfigure:
     • Close Outlook.
     • Run the New Outlook reset command (olk.exe --clearLocalState) as documented in the similar troubleshooting case.
     • Reopen New Outlook, sign in again, let it fully resync, and then test sending a new event.
   • This step has resolved other New Outlook issues where local state corruption prevented normal behavior.
6. Validate that the event is a meeting (not just an appointment)
   • After sending from New Outlook, open the item in the VP’s calendar:
     • Confirm that attendees are still listed under Required or Optional.
     • If attendees disappear (as described), New Outlook is treating it as an appointment rather than a meeting.
   • Recreate the item ensuring attendees are added via Add required people and that Send is used, not Save.
7. If the issue persists only in New Outlook on Mac
   • Since the same mailbox works in OWA, Legacy Outlook, and mobile, and the problem reproduces on multiple Macs, this points to a New Outlook for Mac client issue.
   • In that case, use Legacy Outlook for Mac as a workaround for meeting scheduling until a client update resolves the behavior.

References:

• Event scheduling, room finder, and RSVP in Outlook for Mac
• Create a meeting or appointment in Outlook for Mac
• New Outlook has stopped working, Fails when starting after 30 to 60 seconds - Microsoft Q&A