What it does

The event record is the container every other part of the module hangs off — sessions, speakers, registrations, check-ins, passes, streaming. Venue management is a separate three-level set of tables (buildings, rooms, layouts) that the event and its sessions point at for location and capacity.

Key facts

• The event form is tabbed: General, Form, Agenda, Registration and attendance, Additional information, Room reservations, Recovery items. A business process flow sits across the top of the form and is customisable like any other BPF.
• Venue hierarchy is strict and enforced on create: a room must belong to a building, a layout must belong to a room. A building stands alone. A room can carry several layouts, each with its own capacity, because seating arrangement changes the number.
• Selecting a building, room or layout updates the event's Capacity field to match. You can then type over it — the manual value wins and does not re-sync.
• Registration count and Check-in count on the General tab display up to 50,000. The platform stores more than that; the tile just stops counting up. Anything above that, query the registration table.
• Event type is descriptive only. Nothing in the product branches on it, so treat it as a reporting field and set your own option set values.
• Event URL is read-only when you use the default portal. Tick Custom event URL to make it editable and point at your own site.
• Publishing settings — where and how attendees register — now live in the Publishing section on the General tab. Older docs and older blog posts put them on a "Website and form" tab, which no longer exists in that shape.
• The Form tab carries Create leads for event registrations (one lead per registration, related to the contact), Allow attendees to register for sessions, and the registration window: registration start, registration end, and the event time zone, plus a Preregistration notification and a Registration closed notification you can word yourself.
• Event team members can be either Users (licensed staff, no contact details shown) or Contacts (externals, vendors, unlicensed internal helpers). There is a global list under Events > Event > Event Team Members and a per-event list on the Additional information tab.
• Recovery items is an admin-only tab that surfaces customisation errors on the event. Non-admins get a generic "ask your system admin" banner with no detail, which is a fun support call if nobody knows the tab exists.
• Recurring events are supported, and an event can be created from an existing event as a template.

When to use / skip

If the client runs anything more structured than a single webinar with a sign-up form, use the event module properly rather than bolting registrations onto a marketing form and a custom table. You get the registration/session/check-in data model, the Teams wiring and the passes machinery for free, and rebuilding that yourself is a genuinely bad trade.

Venue management is the part people over-invest in. If every event is virtual, or the client hires a different hotel each time and nobody reports on rooms, don't build a building/room/layout tree — set capacity on the event and move on. Venue records earn their keep when the organisation owns its space, runs repeat events in it, and cares about room double-booking, which the Room reservations tab actually helps with. Otherwise it's data entry with no consumer.

Configuration decisions

• Whether venue data is modelled at all, and if so how deep — building only, or down to layouts with per-layout capacity.
• Where capacity is the source of truth: the layout, the event, or (once sessions are in play) the sessions. Pick one and make the rest follow, because the fields do not stay in sync on their own.
• Whether Create leads for event registrations is on. This is a demand-gen decision, not a technical one, and it will flood the lead table for a large consumer event.
• The event time zone convention for a global client — the registration window and displayed times key off the event's time zone, not the viewer's.
• Event type option set values, since the out-of-box ones are a placeholder and you own the reporting taxonomy.
• Whether event team members are modelled as Users, Contacts, or both — it changes who can be assigned work and who just appears in a list.
• How much of the standard business process flow survives. Most clients want stages trimmed rather than added.

Gotchas

• Capacity silently drifts. Change the room layout after someone has hand-edited Capacity and the number stays wrong, with waitlist and session logic quietly working off the stale value.
• The 50,000 display cap on registration and check-in counts catches people running large consumer events. It looks like a data problem and isn't.
• Time zone on the event drives the registration open/close evaluation. A UK event set to Pacific time will open registration eight hours late and nobody will notice until the complaints arrive.
• Deleting or re-creating an event to "start clean" during UAT takes the registrations, session registrations and check-ins with it. Clone from an existing event instead.
• The Recovery items tab only shows for system administrators. If a client-side admin without that role is testing customisations on the event form, they get the generic banner and no diagnostics.

Consultant notes

• Demo the event record end to end early — General, Agenda, Registration and attendance — before anyone starts designing a custom table. It usually ends the "can we just build our own" conversation in ten minutes.
• Push back hard on venue modelling for virtual-first clients. It is the most common piece of unused configuration in this module.
• Agree the capacity source of truth in writing during design. It is the single field most likely to cause a waitlist argument later.
• Before go-live, check that the event time zone, registration window and the two notification messages are set on every template event, not just the one you built in the demo.
• Clone-from-event is the underused feature here. If the client runs the same roadshow six times a year, set up one good source event and teach them to copy it.

---

Worth another look if Microsoft moves the publishing or registration settings between tabs again, which they have form for.