The Problem: Manual Scheduling Does Not Scale
Recurring bandwidth schedules handle the predictable pattern — peak hours on weekdays, off-peak overnight. But enterprise environments have irregular events that fall outside that pattern: an all-hands meeting with 500 participants, a live product launch stream, a DR failover test at 2am, a month-end close with heavy financial data transfers.
Manually creating a bandwidth event in your IoD scheduler for each of these is exactly the kind of operational overhead that automation is supposed to eliminate. Microsoft 365 calendar integration solves this by turning calendar events directly into bandwidth pre-stage triggers.
How the Integration Works
Apptifi’s M365 sync reads designated Microsoft 365 calendars via the Microsoft Graph API. When a matching calendar event is detected, Apptifi automatically creates a bandwidth scheduling event for the corresponding time window — spiking to the pre-configured high-bandwidth tier before the event starts and dropping back afterward.
The integration is read-only. Apptifi requests Calendars.Read and User.Read.All permissions on your Azure Entra ID app registration. It never writes to your calendar, modifies any M365 data, or requires delegated user permissions.
Setting Up the Azure App Registration
To enable M365 sync, you need an Azure Entra ID app registration with the following configuration:
1. Create a new app registration in the Azure portal under your tenant 2. Add Microsoft Graph API permissions: Calendars.Read (Application) and User.Read.All (Application) 3. Grant admin consent for both permissions 4. Generate a client secret under “Certificates & secrets” 5. Note the Application (client) ID and Directory (tenant) ID
Enter these values in Apptifi’s Settings under the Microsoft 365 section. Apptifi will authenticate using the client credentials flow and begin reading the designated calendars.
Configuring Calendar Sync Rules
In Apptifi, configure which calendars to monitor and what bandwidth tier to pre-stage for matching events. Common configurations:
- • **Network operations calendar:** Any maintenance window or planned event automatically triggers a bandwidth pre-stage
- • **All-company calendar:** All-hands meetings, town halls, and company-wide events trigger the high-bandwidth tier
- • **Conference room calendars:** Large conference rooms with video conferencing setups get bandwidth pre-staged when booked
Set a pre-stage lead time (typically 15–30 minutes before the event) so the bandwidth change is already in effect when the event begins.
What Qualifies as a Calendar-Driven Bandwidth Event
Not every calendar event should trigger a bandwidth change. Configure filters to match only relevant events:
- • **By calendar:** Only specific calendars, not every user’s personal calendar
- • **By duration:** Events longer than 30 minutes, to avoid false triggers from brief check-ins
- • **By keyword:** Events with specific keywords in the title (e.g., “All-Hands”, “Live Stream”, “DR Test”)
The Result: Zero-Touch Bandwidth Management for Events
Once configured, calendar-driven bandwidth scheduling runs without any manual intervention. Network teams no longer need to remember to pre-stage bandwidth for company events, and the IoD circuit automatically returns to its off-peak tier when each event ends — without anyone needing to submit a manual order.
This is the difference between a bandwidth scheduler and a bandwidth intelligence layer. The M365 plan in Apptifi is the only IoD scheduling solution with native Microsoft 365 calendar integration.