Microsoft 365

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 application wide admin consent 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 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 individual consent if you’d prefer users to give consent on an individual basis, each user can manage ashby’s access from their microsoft 365 settings (within https //app ashbyhq com/settings/personal info ) the same permissions as listed above for application wide admin consent would need to be given by the user a user can click connect with microsoft 365 to connect their account users can also individually disable email sync in the email settings section of their personal settings at https //app ashbyhq com/settings/email if users have the email sync option enabled, they can also opt to include personal email aliases that should also be included in the sync, so if they respond to a candidate using one of their personal aliases in their email client, it will still be detected and synced to ashby please note that all aliases listed under aliases to include in email sync are set to not sync by default and the user would need to opt in to enable the sync for said alias if you have taken the application wide admin consent route, users will still see to send and receive emails and appointments in ashby, connect your microsoft account when navigating to the https //app ashbyhq com/settings/microsoft 365 page within personal settings but they do not need to complete this additional step if they are not organizing interviews with teams or group calendars they can review the list of scopes in the status section of this page to confirm what is functional and currently syncing users who are organizing meetings for interviews using teams, or those looking to schedule interviews to group calendars will need to go through the additional authorizing processes within https //app ashbyhq com/settings/microsoft 365 to use these features this applies even if the application wide admin consent route has been taken to set up the integration individual consent authorise microsoft 365 room and user sync 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 https //app ashbyhq com/admin/integrations/marketplace if you take the individual consent route, you have the following options for syncing users and rooms as part of your integration setup authorise microsoft 365 user sync sync users to ashby from your microsoft tenant authorise microsoft 365 room and user sync sync your users or users and rooms from your microsoft tenant to ashby if you enable the authorise microsoft 365 room and user sync sync option you will need to determine a delegated room sync user the user selected from the dropdown must have the following permissions in your tenant user read all — for user sync and room sync place read all — for room discovery calendars readwrite shared — for shared/room calendar access (the delegated user must be a delegate of the room calendars in microsoft 365 for calendar subscription to work) ashby inherits whatever visibility the delegated sync user has in the tenant for those rooms the system will only sync the rooms that the delegated user has access to in microsoft if only free/busy information is shown, it is because that's the information microsoft is returning for the delegated user's access level if you do not wish to sync users into ashby but do want to sync rooms, ensure that the sync microsoft users? checkbox is unchecked in the general settings section of the integration tile microsoft teams for more information on scheduling via ashby, check out docid\ xw 3irivonbho uf37lbh when scheduling an interview, a meeting can also be automatically scheduled in teams if you have the microsoft 365 integration in place and if microsoft teams is set as the interview’s location the organizer of the teams meeting needs to have set up individual oauth within microsoft 365 settings (in https //app ashbyhq com/settings/personal info to use this (even if the application wide admin consent route is taken) group calendars now, as part of the microsoft 365 integration, you can add a group calendar for scheduling interviews if you’d like to set up a group calendar as part of your integration, please reach out to your csm, or mailto\ support\@ashbyhq com creating the group calendar to get started, create a microsoft 365 group and add people that will be scheduling to that group as members the group comes with a calendar that everyone in the group can has write access to newly created microsoft 365 groups may take up to 24 hours to fully propagate important group requirements it must be public it must be a group (not a distribution list or shared mailbox) teams capabilities should be enabled it must be mail enabled (not a security group) make sure “hide this group from the global address list” is unchecked these requirements are critical for the calendar to sync correctly with ashby authorizing and adding the group calendar in ashby anyone who is scheduling on that calendar will need to go through the individual microsoft 365 authorization in their https //app ashbyhq com/settings/personal info if you’ve done this before august 10, 2023 you will need to revoke access and re auth the user adding the calendar must be an organization admin in ashby and also be a member or owner of the group for workspaces with more than 100 groups, please reach out to mailto\ support\@ashbyhq com for assistance adding a specific group calendar if you don’t see the group calendar listed you’ll be asked to supply the group object id, which can be found either in the url when navigating to the group, or, if you have access to your domain within azure, the id will show within the group object id section to add the group calendar, head to the microsoft 365 integration settings in https //app ashbyhq com/admin/integrations/marketplace you should then see the option to add a calendar the calendar added will then become the default calendar when scheduling interviews things to note to schedule interviews onto this calendar, users will need to authorize with individual oauth the organizer of the meeting will be the group name, and interviewers will be attendees therefore, the group should be named something that can be externally facing as it will show on candidate invites when a new calendar is authorized, users should re authenticate in their personal settings email aliases we now support sending emails from user aliases to successfully send an email from an alias, a microsoft admin needs to enable the turn on from sending aliases option in the https //admin exchange microsoft com/ log in and navigate to settings>mail flow> general check the turn on from sending aliases checkbox if this setting is not enabled, emails will still send but will fallback to the users primary email address unlike google, microsoft does not allow different from names on an alias for example, if an email from your primary email has the from name of julie meadows, most email clients will show messages from your alias with the same from name (so in our example julie meadows would show as the from name for emails sent from the alias email address as well) if you are looking to set up a company specific no reply email address, please check out known limitations currently there are a few options that aren’t supported by the integration currently known limitations for emails email signatures cannot be synced over from microsoft 365 currently known limitations for calendar syncing and scheduling if you are the interview organizer and on the panel interviewing, you will see two events on your calendar if a group calendar is not in place faq w hat access level do i need to authenticate this application? the person who grants access to the application by clicking the 'connect to ms365' button must be someone who can manage azure application registrations and grant application permissions to the graph api do you support two way calendar syncing with microsoft outlook? updating the interview event’s date and time in outlook will update this in ashby as well when updating the outlook event, send the updated invite to interviewer(s) and the candidate so they receive the updated schedule can my team setup a custom application instead of using the ashby integration? review docid\ wlpeo48evoa15qd5ty q6 for guidance on setting up azure application and pointing it to ashby can i set up both google workspace and microsoft 365 integrations in my ashby account? ashby currently supports deep integration with either google workspace or microsoft 365 but not both simultaneously for more information, check out docid 92txkuc2vvmorzxeptmkj i’ve set up the google workspace integration can i use microsoft teams for interviewing? ashby currently supports deep integration with either google workspace or microsoft 365 but not both simultaneously can i reschedule or change the date and time of an interview via the event on my outlook calendar? we support a two way syncing option whereby if you move an interview event on your outlook calendar to a new date and/or time, the changes will be synced and reflected in ashby please note that in most cases, we would recommend rescheduling in ashby (for example, if you’re amending the interview type, or interviewers on the panel) the calendar event would need to be moved on the account’s shared interview calendar (the calendar determined in the communication tab of your interview) if it wasn’t scheduled via the direct booking option for an interview scheduled via a direct booking link, the calendar invite can be moved on the shared calendar or the meeting organiser can move the interview on their personal calendar if they don’t have access to the shared calendar these changes will then be synced back to ashby and new calendar invites will be sent out you do not need to resend the calendar invites if the interview is rescheduled via outlook, an event will be added to the candidate’s feed showing that rescheduling happened outside of ashby how are users pulled into ashby? users can be synced over to ashby via the following routes if you have user sync enabled as part of your google workspace or microsoft 365 integration settings if you migrate data via the greenhouse, workday or lever api migration options, user accounts will be pulled over as part of the migration if you configure a user sync via scim if you have users synced over via an api migration or by enabling user sync as part of the google workspace/microsoft 365 integration and then set up scim, the scim sync will deactivate any user accounts that were initially added but are not in your scim directory to reactivate any users that were deactivated when they shouldn't have been, please add them back to your scim directory if you've enabled the user sync option as part of your google workspace or microsoft 365 integration (and do not have scim configured), then users will be automatically provisioned and deactivated based on their status in your workspace or tenant if users have been added via an api migration from greenhouse, workday or lever, then you can deactivate any users who will not need access manually if you are not planning to configure scim you can read more about deactivating users at docid\ jgh sn34vmmt0v5cezha8 will synced users receive a welcome email? no once a user is added, they can sign in at https //app ashbyhq com/signin i send a large volume of no reply emails each day, can i still use a branded email address? this is possible if an email domain is configured within ashby if you are sending more than 1,000 no reply or automated emails a day, or are looking to set up a company specific no reply and are using microsoft 365, please check out our guide w hat permissions are necessary on the ashby side for a user set as the delegated room sync user in m365 integration settings? the user would need to be an active ashby user in order for them to be an option to delegate room access as such, they would need to be enabled for sign in this user could be setup as a limited access user in ashby, and wouldn't need to authenticate in ashby w here are meeting rooms pulled from in microsoft 365? in microsoft 365, meeting rooms can be seen on the rooms & equipment page within the microsoft 365 admin center i have some non gregorian calendar events on my calendar and they aren't syncing over, why? please note that recurring calendar events which include the "rscale" property in their recurrence rules (or rrules) are not supported at this time and these events will not be synced over to ashby during calendar syncs the "rscale" property is used to specify non gregorian calendars all events on the user's calendar without the "rscale" property will still be synced