Almanac
Microsoft/d365csDynamics 365

Consultant-focused KB for Microsoft Dynamics 365 Customer Service: implementation notes, gotchas, and configuration decisions beyond the official docs — across case management, queues and routing, knowledge base, SLAs, omnichannel, agent experience, Copilot, analytics, and administration.

feature-agent-schedule-calendar.mdv1 · history
CurrentApplies to EnterpriseUpdated 3 weeks agoSource Microsoft Learn ↗

What it does

Gives representatives a read-only Schedule Calendar in the Copilot Service workspace showing working hours, nonworking hours, breaks and scheduled time off, in daily, weekly, monthly and agenda views. Supervisors also get a Shift Bookings list of bookings imported from the external workforce management system.

Key facts

  • Read-only. Representatives see their schedule here; they don't edit it, and the schedule itself is owned by whatever system you import from.
  • Needs the Workforce Management for Customer Service app installed in the environment, from Resources > Dynamics 365 apps in the Power Platform admin center (System Administrator needed).
  • Turned on in the Copilot Service admin center under Workforce management > Agent calendar > Manage, using the Enable agent calendar toggle.
  • Enabling it needs System Administrator, CSR Manager, Omnichannel administrator or Omnichannel supervisor.
  • External bookings only appear if a third-party adapter is configured to import them. No adapter, no external bookings.
  • Not supported in GCC or sovereign clouds.

When to use / skip

Use it if your representatives already have shifts in a third-party workforce management tool and keep asking "when am I on?" inside the workspace. Skip it if you don't run an adapter: you'll be switching on a calendar that shows very little.

Configuration decisions

  • Which workforce management system is the source of truth, and who owns the adapter that feeds bookings in.
  • Who gets the enabling role versus who just consumes the calendar.
  • Whether supervisors need the All Shift Bookings view as a standing check on the sync.

Gotchas

  • The toggle is the easy bit. The adapter is the project, and it isn't covered by the enablement steps.
  • Installing the app takes a while to show as installed. Don't hunt for the toggle until the Dynamics 365 apps page says so.
  • Don't treat it as a scheduling tool. Nothing you do in the calendar changes anyone's rota.

Consultant notes

  • Ask at scoping who owns the adapter and its sync schedule. In practice the calendar gets blamed for every stale booking, and the cause is nearly always upstream.
  • Use the All Shift Bookings view as your first UAT check. If a representative's shifts aren't in that list, there's no point debugging the calendar.
  • Check the cloud before you promise it. GCC and sovereign tenants are out, and that tends to surface late.
  • Brief supervisors that it's read-only, otherwise the first request after go-live is "can they swap shifts here?".

Worth revisiting after the next Customer Service release wave, or if workforce management gains editing.

Was this accurate?