A: JumpCloud Utilizes OAuth2 to secure and persist its connection with Office 365 to perform our integration tasks.
A: When the OAuth session is deactivated in JumpCloud, all users in Office 365 will remain ‘active’ and functioning. This is by design. Within JumpCloud, all User accounts will remain active as well when de-authorization with Office 365 occurs. Note that when de-authorization occurs, all selected members bound to Office 365 are un-selected. When and if the products are-reactivated, the admin will need to re-bind the users in the Office 365 Directory to re-establish the connection and ownership-control of the accounts in Office 365.
A: While this was previously not a supported configuration, use of the Active Directory Bridge can now indeed be used when either Google Apps or Office 365 User Provisioning are enabled.
A: At this time, only one Office 365 account can be integrated with JumpCloud.
A: At this time, JumpCloud can not import user profile pictures or avatars into JumpCloud's user accounts.
A: At this time, JumpCloud does not support integration with GoDaddy's implementation of Office 365. This version has more limited management capabilities that requires SSO login with GoDaddy's services in order to operate appropriately. Because of these requirements, we are inhibited from making changes to the identity with the integration.
A: Prior to 1 January 2013, generic MX records such as mail.global.frontbridge.com could be used for email. After 15 July 2014, if they weren't updated, service disruption may be experienced. See the Microsoft Communities article for more information.
Q: Can the Office 365 and G Suite Directory integrations be used in tandem, and if so, what configuration requirements are needed?
A: The Office 365 and G Suite Directory integrations can be used together to successfully synchronize both service providers with JumpCloud. The directory integrations utilize the user's email address as the unique identifier for synchronization. Due to this architecture, your domain records may need to be mapped so that the same email address is used between all service providers. For more information refer to the follow vendor-specific documentation:
Add a domain to Office 365
Add a domain to G Suite
A: Upon import, you will see a failure for this user to import as the account with the same email already exists.
A: JumpCloud's Office 365 synchronization UI displays all of your Office 365 users regardless of whether they were previously imported. We will provide filtering mechanisms and improved workflow in the future.
A: At this time, only user accounts are supported between JumpCloud and Office 365.
A: No. Once the Global Administrator credentials have been authenticated once, the connection to Office 365, regardless of Administrator, can perform importation and provisioning tasks.
A: While an admin can prevent a Welcome email from being delivered to the end user when creating the account, binding the user to Office 365 will send an email to the employee. We recommend educating the employee base first before adding them to Office 365.
A: The administrator can unbind the user from the Office 365 in JumpCloud which will trigger the user in Office 365 to be set as "block sign-in." Re-binding the user will un-block the User in Office 365.
A: The user remains unchanged in JumpCloud. If you wish to remove the user from JumpCloud, these actions must be performed manually in the JumpCloud console. PLEASE NOTE: Should the user need to be re-provisioned from JumpCloud to Office 365, Office 365 will often require up to 24 hours until they release the same email address to be re-used again. You may re-bind the user at that time to re-deploy the account back to Office 365.
A: Unfortunately, the min 8 to max 16 character parameters are a hard requirement enforced by Microsoft. You can read this article for more specifics. Please note that JumpCloud password changes will not take affect on an Office 365 if less than 8 or greater than 16 characters and will result in error.
A: JumpCloud's Password Complexity will govern the password being used to sign into Office 365 just as with any other resource the user is connected to. JumpCloud will not prevent a user from changing their password in their Office 365 account to a non-compliant password. JumpCloud in this case, however, will overwrite the non-compliant password in Office 365 with the compliant JumpCloud password.
A: The user’s Office 365 account is suspended, blocking the user from accessing their account. Resetting the user’s password in JumpCloud will re-activate the user’s Office 365 account.
A: The employee can change their password from Office 365's password change system however this will not update JumpCloud. JumpCloud’s version of the password will overwrite the modified one in Office 365 and will log the user out of the Office 365 session, enforcing the JumpCloud credentials to be input.
A: No. Password changes made through JumpCloud in conjunction with Office 365's own MFA option is currently not supported.