Microsoft 365 Integration
On this page
Microsoft 365 Integration is the Admin Center page where you turn on the integration with Microsoft 365 and enter the Tenant ID and Client ID of your registration in Microsoft Entra ID. The Web App calendars use this registration for Outlook Calendar. It is one of the pages that only the Admin Center has: the Settings App has no counterpart for it.
In the Admin Center
The page is Microsoft 365 Integration in the Services and Integrations menu of the Admin Center, beside Calendar Sharing.
The menu entry, like the Calendar Sharing entry, needs the permission to manage the services configuration. For the rights, see Permissions Reference.
What the page holds
- Enable integration with Microsoft 365: "Activates integration with Outlook Calendar. Uncheck to turn it off." When the setting has never been saved, the check box is selected.
- The text "Register your integration in Microsoft Entra ID (formerly Azure Active Directory) to obtain the Tenant ID and Client ID required for calendar access." with a Learn more link.
- Tenant ID and Client ID: the ids of that registration. Both boxes are unavailable while Enable integration with Microsoft 365 is cleared.
Save and Cancel appear once you change the form.
Prepare Microsoft Entra ID
The page needs the Tenant ID and Client ID of an application registered in Microsoft Entra ID. A registration made for incoming mail is not used here. You can get them in one of two ways:
- Request from Alloy Support the Tenant ID and Client ID of the pre-registered multi-tenant application that Alloy Software configures. With the ids at hand, go on to Register the integration.
- Register your own application in Microsoft Entra ID, as described below.
To register your own application:
- Sign in to the Microsoft Entra admin center.
- Browse to Entra ID > App registrations and select New registration.
- Enter a name for the application, for example Alloy Calendar Integration.
- Under Supported account types, select Single tenant only - <your tenant>, and then select Register.
- On the application's Overview page, copy the Application (client) ID and the Directory (tenant) ID. The Application (client) ID goes into Client ID and the Directory (tenant) ID into Tenant ID on the Microsoft 365 Integration page.
- Under Manage, select Authentication, select Add Redirect URI, and select the Single-page application platform.
- Enter the root site address of your Web App as the redirect URI, and then select Configure.
For example, when the Web App URL is
https://example.com/wp/, the redirect URI ishttps://example.com. - Select API permissions > Add a permission > Microsoft Graph > Delegated permissions.
- Select the permissions that the technician's sign-in requests:
User.Read,email,profile,Calendars.ReadandCalendars.ReadWrite.User.Readmay already be listed, because Microsoft Entra ID adds it to a new registration. Select Add permissions. - Optionally, to spare each technician the individual consent prompt, an administrator who can consent on behalf of the organization selects Grant admin consent for <your organization>.
Calendars.ReadWrite belongs in the list beside Calendars.Read: the Web App also creates, updates
and deletes Outlook events.
For Microsoft's description of these screens, see Register an application in Microsoft Entra ID, How to add a redirect URI to your application, Web API app registration and API permissions and Grant tenant-wide admin consent to an application.
Register the integration
- Get the Tenant ID and Client ID of your registration in Microsoft Entra ID; see Prepare Microsoft Entra ID.
- In the Admin Center, open Services and Integrations > Microsoft 365 Integration.
- Make sure Enable integration with Microsoft 365 is selected.
- Enter the Tenant ID and the Client ID.
- Click Save.
To turn the integration off, clear Enable integration with Microsoft 365 and click Save.
What the registration is used for
- In the Web App calendars, a technician signs in to Microsoft 365 with the Tenant ID and Client ID
from this page. The sign-in requests the
User.Read,email,profile,Calendars.ReadandCalendars.ReadWritepermissions. - With that sign-in, the Web App reads the Outlook calendar view and single events, looks up free/busy schedules, and creates, updates and deletes events.
- The Team Calendar looks up a member's Outlook availability only while Enable integration with Microsoft 365 is selected, the viewing technician is signed in to Microsoft 365, and the Microsoft 365 source under Other calendars is checked.
- On the Team Calendar, a member's Outlook availability is looked up under the primary e-mail address of the member's person record and under no other address. It appears only for members that the Assignee filter puts on the page, and only when the member's Microsoft 365 mailbox is that primary address. Changing which address is primary changes the mailbox that is asked, and deleting the primary address stops the member's availability from appearing.
- The lookup runs under the viewing technician's own Microsoft 365 sign-in, so the viewer's Microsoft 365 permission over the member's mailbox decides whether the availability shows. The member does not need to sign in.
- On the Team Calendar, a member whose person record has no primary e-mail address gets no lookup and no error, so on the page that member looks the same as a member whose lookup has not run yet. When a lookup runs and Microsoft 365 has no mailbox for the primary address, the member's row shows an error icon whose tooltip reads "Unable to access this calendar. No mailbox found for <address> in Microsoft 365." Any other error appears in the same tooltip as it arrives; a failed request to Microsoft 365 reads "Error fetching getSchedule (<status code>): <response>".