Copilot in Outlook With Shared Calendars: Cross-User Event Drafting

You want to draft a meeting event in Outlook using Copilot, and that event needs to appear on a shared calendar that other people in your organization can see. The standard Copilot calendar command only writes to your own primary calendar, so a direct request like “create a meeting on the shared Sales calendar” will fail or produce unexpected results. This article explains why Copilot cannot natively write to shared calendars and shows a reliable workaround to draft events that land on the correct shared calendar.

Why Copilot Cannot Write to Shared Calendars in Outlook

Copilot in Outlook uses a calendar skill that is designed to interact with your primary mailbox calendar. This skill reads your calendar data and creates events only in the default calendar folder associated with your Exchange mailbox. Shared calendars, delegate calendars, and group calendars are separate folders that the Copilot calendar skill does not have write permissions for by design.

The technical root cause is the permission model that Microsoft 365 uses for Copilot. The Copilot service authenticates against your mailbox and can perform actions that you are allowed to do, but the calendar skill is scoped to the primary calendar folder. When you ask Copilot to create an event on a shared calendar, the skill cannot resolve the target folder. Instead, it either creates the event on your primary calendar or returns an error message stating that it cannot complete the request.

This limitation applies to all shared calendar types, including:

• Calendars shared by individual users within your organization
• Microsoft 365 group calendars
• Resource mailbox calendars such as conference rooms
• Delegate calendars where you have editor or author permissions

Microsoft has not announced any change to this behavior as of early 2025. The workaround described in the next section is the only reliable method to get Copilot-generated events onto a shared calendar.

Steps to Draft an Event on a Shared Calendar Using Copilot

Follow these steps to create a meeting event with Copilot and then move it to a shared calendar. This method works in Outlook for Windows, Outlook on the web, and Outlook for Mac.

1. Open Copilot in Outlook
   In the Outlook ribbon, select the Copilot icon. The Copilot pane opens on the right side of the window.
2. Compose the event draft on your primary calendar
   Type a prompt such as: “Create a meeting on Friday at 2 PM titled ‘Q1 Review’ with a 45-minute duration and include a Teams meeting link.” Copilot creates the event and adds it to your primary calendar.
3. Open the event after creation
   Double-click the newly created event on your calendar to open it in a separate window. Verify all details are correct before moving it.
4. Move the event to the shared calendar
   Select the event on your calendar. Right-click and choose Move to Calendar or Copy to Calendar from the context menu. If you use Outlook on the web, click the event and select Move from the toolbar.
5. Choose the target shared calendar
   A dialog box lists all calendars you have access to. Select the shared calendar you want the event to appear on. Click OK.
6. Delete the original event if you copied
   If you used Copy to Calendar, two identical events exist. Delete the event on your primary calendar to avoid duplicates. If you used Move, the original is removed automatically.

After moving the event, all users with access to the shared calendar can see it. Attendees receive invitations based on the attendees you added during the Copilot draft step.

If Copilot Still Has Issues After the Main Fix

Copilot Returns an Error When Creating the Event

If Copilot fails to create the event on your primary calendar, check that your mailbox is connected to Exchange Online. Copilot calendar features require an active Exchange Online mailbox with a Microsoft 365 Copilot license. Verify your license in the Microsoft 365 admin center under Users > Active Users > Licenses and Apps.

The Move Option Is Grayed Out or Missing

The Move to Calendar option is available only for events you own. If the event was created by another user or a delegate, you cannot move it. Create a new event using Copilot from your own account. Also confirm that you have at least editor permissions on the target shared calendar.

Copilot Creates the Event but Omits Attendees or Details

Copilot may not include all attendees or meeting details if your prompt is too vague. Rephrase the prompt to include specific names and details. For example: “Create a meeting with Alex Chen and Jamie Lee on Monday at 10 AM titled ‘Project Sync’ with a one-hour duration and a location of Conference Room B.” After the event is created, open it and add any missing attendees manually before moving it to the shared calendar.

Copilot Primary Calendar vs Shared Calendar Drafting: Key Differences

Item	Primary Calendar Drafting	Shared Calendar Drafting
Copilot direct support	Yes, fully supported with a single prompt	No, Copilot cannot write to shared calendars directly
Permission requirements	Your own mailbox	Editor or author permissions on the shared calendar
Event creation location	Your default calendar folder	Requires manual Move or Copy after drafting
Attendee management	Copilot adds attendees from your prompt	Copilot adds attendees from your prompt; move preserves them
Duplicate risk	None	Possible if you use Copy instead of Move

The primary difference is that shared calendar drafting requires a manual transfer step. All other event properties such as title, time, attendees, location, and meeting link are preserved during the move.

You can now use Copilot to draft meeting events and place them on any shared calendar you manage. Start by composing the event on your primary calendar, then use the Move to Calendar command. For recurring events, repeat the move process for each occurrence or create the series on your primary calendar and move the first occurrence before setting recurrence. This method keeps your workflow fast while respecting Copilot’s current calendar limitations.