Once you’ve been given access to the integration, we have two routes to authorize Ashby with Microsoft 365; application-wide admin consent and individual consent.
<aside> 💡 This is the fastest route to get the integration in place for all users. We automatically sync all users of a Microsoft domain if application wide consent has been given.
</aside>
This method allows an admin of both Ashby and an organization's Microsoft tenant to authorize all permissions that Ashby requires for everyone in their organization.
A user from your Microsoft organization with the permission to administer applications should log into Ashby and head to the Integrations page. Microsoft 365 is in the Platform section of the Integrations Marketplace.
To get started, click on Microsoft 365, then Enable Microsoft 365 and then Connect to Microsoft 365.
From there, the admin will be able to confirm the account and review the permissions requested. They can then click Accept to allow Ashby access.
Once accepted, you should see a message confirming that the integration has been enabled.
Admins can also opt to disable the user sync and opt to not automatically enable synced users by unchecking the checkboxes in the General Settings section of the Microsoft integration.
If you’d prefer user’s to give consent on an individual basis, each user needing access can manage Ashby’s access from their Microsoft 365 Settings (within Personal Settings). The same permissions as listed above for application-wide admin consent would need to be given.
Users will not be synced over automatically via the individual consent route. A user that has been granted the User.Read.All permission in Microsoft can enable user syncing in the Additional Authorization section of the Microsoft 365 integration settings in the Integration Marketplace.
<aside> 💡 For more information on scheduling via Ashby, check out Scheduling and Interviewing.
</aside>
When scheduling an interview, a meeting can also be automatically scheduled in Teams if set as the interview’s location.
The organizer of the Teams meeting needs to have set up individual OAuth within Microsoft 365 Settings (in Personal Settings) to use this (even if the application-wide admin consent route is taken).