Charge RosterCan Outlook be used to book an EV charger?
Yes. Microsoft 365 already has a resource-booking model for shared things such as rooms and equipment.
For a workplace charger, the closest fit is usually an equipment mailbox: one mailbox represents one charger, and employees reserve it by including that resource in an Outlook calendar event.
Microsoft documents equipment mailboxes as reservable resources and says they can automatically accept a request when the resource is available or reject it when the request conflicts with an existing booking. The same resource-processing settings can control the booking horizon and maximum meeting duration.
- Microsoft: create room and equipment mailboxes
- Microsoft: manage resource mailboxes in Exchange Online
- Microsoft: Set-CalendarProcessing
That makes Outlook a credible first solution when the problem is simply: who has Charger 1 from 10:00 to 12:00?
It does not make Outlook a charge point management system. The calendar knows about the reservation, not whether a cable is connected or electricity is flowing.
The simplest model: one equipment mailbox per charger
Suppose the workplace has three chargers.
Create three resources such as:
EV Charger 01 — Bay A1EV Charger 02 — Bay A2EV Charger 03 — Bay A3
Each resource gets its own calendar.
An employee creates an Outlook event for the charging period and adds the relevant charger resource. If that resource is already booked for the requested period, Exchange can decline the request automatically rather than allowing two employees to believe they have the same charger.
This one-resource-per-charger model is easier to understand than trying to represent all chargers with one shared mailbox.
Step 1: create the charger as a Microsoft 365 resource
An administrator can create an equipment mailbox in Microsoft 365 or Exchange Online.
The resource should have a human-readable name that matches the physical charger or bay. If employees see EV Charger 02 — Level B, Bay 14 in Outlook, they can connect the calendar booking to the actual parking location.
Keep the resource identity stable. Renaming Charger 2 to “Fast charger” every few months makes historical calendar entries harder to interpret.
Step 2: configure automatic conflict handling
For a simple shared-charger workflow, the useful default is:
- automatically accept valid bookings;
- reject conflicting bookings;
- restrict booking to the relevant employee group if necessary;
- limit how far ahead people can reserve;
- limit the maximum duration of one reservation.
Microsoft's current Set-CalendarProcessing documentation exposes controls including AllowConflicts, BookingWindowInDays and MaximumDurationInMinutes.
A configuration might conceptually look like this:
Set-CalendarProcessing \
-Identity "EV Charger 01" \
-AutomateProcessing AutoAccept \
-AllowConflicts $false \
-BookingWindowInDays 14 \
-MaximumDurationInMinutes 180 \
-AllBookInPolicy $true
Treat that as an example rather than a universal charging policy. A three-hour maximum may suit one workplace and be completely wrong for another.
The important part is to make the calendar enforce the basic scheduling constraint: the same charger should not be reserved by two people at the same time.
Step 3: decide the workplace rules before inviting employees
Outlook can reject a conflicting event, but it cannot decide what “fair” means for your organisation.
Write down a small set of rules first:
- Who may reserve the workplace chargers?
- How many days ahead can employees book?
- What is the normal maximum duration?
- Can one employee hold several future bookings?
- When should a booking be cancelled?
- Does the car need to move when the reservation ends?
- Are company vehicles or operational travel ever prioritised?
The calendar is only the mechanism. The workplace still owns the policy.
Step 4: employees reserve the charger through Outlook
The employee creates a calendar event for the charging period and adds the charger resource.
For example:
- Date: Tuesday
- Time: 10:00–12:00
- Resource:
EV Charger 02 — Bay A2 - Subject:
EV charging — Alex
Once Exchange processes the request, the employee receives the booking response.
If employee names or event subjects are visible to other users, decide deliberately how much information the charger calendar should expose. A shared charging schedule usually needs enough identity for operational coordination, but it does not need unrelated meeting details or personal travel information.
Step 5: block unavailable charger periods
A charger may occasionally be unavailable because of maintenance, construction, parking restrictions or another operational reason.
Block those periods on the resource calendar so Outlook stops presenting the resource as bookable.
This is still a planned availability model. A calendar block does not automatically know that the charger has developed a physical fault unless someone updates the calendar or another system is integrated.
What Outlook does well
For a small Microsoft 365 workplace, this approach has several advantages.
Employees already know the interface
There is little training. Booking a charger feels similar to booking another workplace resource.
Calendar conflicts can be prevented automatically
The resource mailbox can reject overlapping requests rather than relying on employees to notice a clash in a spreadsheet or chat thread.
Booking horizon and duration can be constrained
Microsoft's resource-processing settings can limit how far ahead a resource is reserved and how long an individual booking lasts.
Calendar reminders come for free
Employees already see the charging reservation alongside the rest of their working day.
There is no new employee account to manage
The booking uses the Microsoft 365 identities the workplace already has.
Where the Outlook workaround starts to break down
The limitations appear when the charging problem becomes more than a single shared calendar.
Employees must think in calendar resources, not charging needs
The employee often has to choose a specific charger first. A dedicated scheduling tool can instead start with “I need charging from 10:00” and find suitable capacity.
Fairness is mostly policy, not automation
Outlook can prevent a double booking, but ordinary resource calendars are not designed around equal access to scarce workplace charging. If one person repeatedly reserves the best morning periods, the calendar may still be technically working exactly as configured.
Queues and waitlists are awkward
When every suitable period is full, there is no natural charger-specific workflow for recording unmet demand and offering a cancelled slot to the next driver.
Cross-charger visibility gets cumbersome
With one calendar per charger, an employee may need to compare several calendars to find the best option.
It does not know physical charger state
A confirmed Outlook event does not prove that the charger is online, connected or actually in use.
Charging analytics are limited
Calendar events can tell you what was reserved. They do not automatically answer how many employees tried and failed to find a useful charging period, whether cancellations returned capacity, or when scheduling rather than hardware is the actual bottleneck.
What about Outlook Workspaces?
Microsoft also supports workspaces, which are bookable physical work areas with capacity and minimum-duration settings. Outlook mobile can book them similarly to rooms, and Microsoft Places supports reservable workspace modes.
That can be useful when the resource is a pool — for example, ten interchangeable desks.
A charger is usually easier to model as an individual equipment/resource mailbox because the physical connector and parking bay matter. If your charging area genuinely behaves as an interchangeable pool, a workspace-style model may be worth testing, but do not force a desk-booking concept onto a charger just because both are reservable resources.
When is Outlook good enough?
Outlook is a reasonable long-term answer when:
- there are only a few chargers;
- charging demand is modest;
- employees already use Microsoft 365 heavily;
- one reservation maps cleanly to one charger;
- conflicts are the main problem;
- Facilities is comfortable maintaining resource calendars and rules.
There is no reason to replace a simple process that employees understand if it is still serving the workplace well.
When should you move to dedicated workplace charger booking?
Consider a dedicated scheduling layer when several of these become recurring issues:
- employees check several charger calendars before finding a useful time;
- popular periods are repeatedly monopolised;
- the workplace needs a waitlist or queue;
- bookings need charger-specific rules rather than generic meeting-resource rules;
- cancellations and returned capacity need to be visible immediately;
- administrators need to see unmet charging demand;
- there are several sites or many chargers;
- employees increasingly coordinate exceptions in Teams, Slack or email despite the calendar.
At that point, the manual workaround is creating operational work rather than avoiding software.
Where Charge Roster fits
Charge Roster takes the same basic idea — allocate a shared resource by time — but makes the workflow specific to workplace charging. Employees see charger availability and reserve charging periods, while the workplace applies charging rules and can see where scheduled capacity does not meet demand.
It does not replace Microsoft 365, operate the charger or require OCPP just to schedule access.