Benefits<\/strong><\/h3>\n\n\n\nThis integration with 探花大神 allows for:<\/p>\n\n\n\n
\n- Secure, persistent connectivity between 探花大神 and M365<\/li>\n\n\n\n
- Importing pre-existing M365 accounts into 探花大神<\/li>\n\n\n\n
- Exporting (provisioning) new accounts into M365 from 探花大神<\/li>\n\n\n\n
- Continual synchronization from 探花大神 to M365 accounts<\/li>\n\n\n\n
- End user self-service account management from the 探花大神 User Portal <\/li>\n\n\n\n
- Security Assertion Markup Language (SAML) Single Sign-on (SSO) users can log in to 探花大神 and M365 with the same set of credentials<\/li>\n<\/ul>\n\n\n\n
Considerations<\/strong><\/h3>\n\n\n\n![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>
Warning:<\/strong> \n\n- Don\u2019t authorize\/create multiple instances of a cloud directory integration to the same M365 domain. If you do, users bound to multiple M365\/Entra ID instances could be suspended in your M365\/Entra ID directory if you unbind that user from one of the instances. You can avoid this by deactivating sync for multiple M365\/Entra ID directory instances for the same domain.<\/li>\n\n\n\n
- Be aware that after you deactivate sync for a M365\/Entra ID instance and domain, all information specific to that M365\/Entra ID directory integration in the 探花大神 Admin Portal will be permanently deleted and cannot be recovered by simply reactivating sync.<\/li>\n<\/ul>\n <\/div><\/div><\/div><\/div>\n\n\n\n
\n- App passwords<\/a> may be necessary to authenticate legacy endpoints where multi-factor authentication (MFA) is configured in M365<\/li>\n\n\n\n
- 探花大神 user accounts are synced with their M365 user account based on the primary email address <\/em>used in M365<\/li>\n\n\n\n
- If multiple M365 tenants are configured for 探花大神’s Directory Sync and a 探花大神 user is bound to more than one M365 tenant, only the M365 tenant with the 探花大神 user’s matching M365 primary email address<\/em> will be synced<\/li>\n\n\n\n
- At this time, 探花大神 doesn’t support integration with GoDaddy’s implementation of M365. This version has limited identity management capabilities that require SSO login with GoDaddy’s services to operate appropriately. Because of these requirements, we are prohibited from making changes to identities with the GoDaddy integration<\/li>\n\n\n\n
- Don’t import users that you don’t intend to manage with 探花大神. You have 48 hours to remove unwanted users and to contact your Technical Account Manager to avoid being charged for any users you remove after import <\/li>\n\n\n\n
- If the password takeover functionality has been disabled for your 探花大神 organization, then the password only syncs when the user or admin changes it. In addition, active users with passwords will receive password reset emails from each Cloud Directory to which the user is associated<\/li>\n\n\n\n
- M365\/Entra ID group management is only supported for security groups at this time<\/li>\n<\/ul>\n\n\n\n
Prerequisites<\/strong><\/h3>\n\n\n\n\n- An active M365 domain<\/li>\n\n\n\n
- A user with the following administrator roles in M365:\n
\n- Privileged role administrator<\/li>\n\n\n\n
- Groups administrator<\/li>\n\n\n\n
- Users administrator<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- We also recommend that you have a Global administrator service account<\/li>\n<\/ul>\n\n\n\n
M365 Integration Scenarios<\/strong><\/h2>\n\n\n\nYou can integrate M365 with 探花大神 in the following two ways:<\/p>\n\n\n\n
\n- Taking over existing M365 accounts<\/li>\n\n\n\n
- Provisioning new M365 accounts<\/li>\n<\/ol>\n\n\n\n
Taking Over Existing M365 Accounts<\/strong><\/h3>\n\n\n\nWhen you import existing M365 accounts and bind them to the M365 directory you\u2019ve enabled for sync, 探花大神 \u201ctakes over\u201d the accounts and becomes the manager and password authority for those accounts. <\/p>\n\n\n\n
Provisioning New M365 Accounts<\/strong><\/h3>\n\n\n\nAccount provisioning involves creating and maintaining user accounts and their attributes. New M365 accounts can be provisioned in M365 or in 探花大神.<\/p>\n\n\n\n
M365-Initiated Provisioning<\/strong><\/h4>\n\n\n\nWhen an account is created in M365, a temporary password can be sent to an alternate email address, which lets users gain access to their account. <\/p>\n\n\n\n
When you create a user account in M365, users are provisioned in the following way:<\/p>\n\n\n\n
\n- Import the user into 探花大神.<\/li>\n\n\n\n
- Bind the user to the M365 directory.<\/li>\n\n\n\n
- The user resets their password in the 探花大神 User Portal.<\/li>\n\n\n\n
- Account synchronization is complete.<\/li>\n<\/ol>\n\n\n\n
探花大神-Initiated Provisioning<\/strong><\/h4>\n\n\n\nWhen you create new users in 探花大神 that don\u2019t exist in Microsoft, 探花大神 creates user accounts (provisions) with the 探花大神 user\u2019s credentials and attributes. For the new account to be provisioned to M365, the account must have an email address of the primary M365 domain that is synced with 探花大神. This is useful if your organization intends to use 探花大神 to manage your M365 deployment.<\/p>\n\n\n\n
When creating an account in 探花大神, an activation email can be sent to an alternate email address. Alternatively, admins can set a temporary password during creation.
To send an activation email to an alternate email address:<\/strong><\/p>\n\n\n\n\n- Add the new user to 探花大神.\n
\n- Bind the user to the M365 directory.<\/li>\n\n\n\n
- Leave Specify initial password<\/strong> unchecked.<\/li>\n\n\n\n
- After saving the user, you will be prompted to send the activation email.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
- The user will click the link in the activation email that was sent to the address you provided in step 1b and set their password.<\/li>\n\n\n\n
- The user logs in to the 探花大神 User Portal with the password they set in step 2.<\/li>\n\n\n\n
- Account synchronization is complete.<\/li>\n<\/ol>\n\n\n\n
Considerations<\/strong><\/h3>\n\n\n\n<\/p><\/div>
Warning:<\/strong> \n\n- Don\u2019t authorize\/create multiple instances of a cloud directory integration to the same M365 domain. If you do, users bound to multiple M365\/Entra ID instances could be suspended in your M365\/Entra ID directory if you unbind that user from one of the instances. You can avoid this by deactivating sync for multiple M365\/Entra ID directory instances for the same domain.<\/li>\n\n\n\n
- Be aware that after you deactivate sync for a M365\/Entra ID instance and domain, all information specific to that M365\/Entra ID directory integration in the 探花大神 Admin Portal will be permanently deleted and cannot be recovered by simply reactivating sync.<\/li>\n<\/ul>\n <\/div><\/div><\/div><\/div>\n\n\n\n
\n- App passwords<\/a> may be necessary to authenticate legacy endpoints where multi-factor authentication (MFA) is configured in M365<\/li>\n\n\n\n
- 探花大神 user accounts are synced with their M365 user account based on the primary email address <\/em>used in M365<\/li>\n\n\n\n
- If multiple M365 tenants are configured for 探花大神’s Directory Sync and a 探花大神 user is bound to more than one M365 tenant, only the M365 tenant with the 探花大神 user’s matching M365 primary email address<\/em> will be synced<\/li>\n\n\n\n
- At this time, 探花大神 doesn’t support integration with GoDaddy’s implementation of M365. This version has limited identity management capabilities that require SSO login with GoDaddy’s services to operate appropriately. Because of these requirements, we are prohibited from making changes to identities with the GoDaddy integration<\/li>\n\n\n\n
- Don’t import users that you don’t intend to manage with 探花大神. You have 48 hours to remove unwanted users and to contact your Technical Account Manager to avoid being charged for any users you remove after import <\/li>\n\n\n\n
- If the password takeover functionality has been disabled for your 探花大神 organization, then the password only syncs when the user or admin changes it. In addition, active users with passwords will receive password reset emails from each Cloud Directory to which the user is associated<\/li>\n\n\n\n
- M365\/Entra ID group management is only supported for security groups at this time<\/li>\n<\/ul>\n\n\n\n
Prerequisites<\/strong><\/h3>\n\n\n\n\n- An active M365 domain<\/li>\n\n\n\n
- A user with the following administrator roles in M365:\n
\n- Privileged role administrator<\/li>\n\n\n\n
- Groups administrator<\/li>\n\n\n\n
- Users administrator<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- We also recommend that you have a Global administrator service account<\/li>\n<\/ul>\n\n\n\n
M365 Integration Scenarios<\/strong><\/h2>\n\n\n\nYou can integrate M365 with 探花大神 in the following two ways:<\/p>\n\n\n\n
\n- Taking over existing M365 accounts<\/li>\n\n\n\n
- Provisioning new M365 accounts<\/li>\n<\/ol>\n\n\n\n
Taking Over Existing M365 Accounts<\/strong><\/h3>\n\n\n\nWhen you import existing M365 accounts and bind them to the M365 directory you\u2019ve enabled for sync, 探花大神 \u201ctakes over\u201d the accounts and becomes the manager and password authority for those accounts. <\/p>\n\n\n\n
Provisioning New M365 Accounts<\/strong><\/h3>\n\n\n\nAccount provisioning involves creating and maintaining user accounts and their attributes. New M365 accounts can be provisioned in M365 or in 探花大神.<\/p>\n\n\n\n
M365-Initiated Provisioning<\/strong><\/h4>\n\n\n\nWhen an account is created in M365, a temporary password can be sent to an alternate email address, which lets users gain access to their account. <\/p>\n\n\n\n
When you create a user account in M365, users are provisioned in the following way:<\/p>\n\n\n\n
\n- Import the user into 探花大神.<\/li>\n\n\n\n
- Bind the user to the M365 directory.<\/li>\n\n\n\n
- The user resets their password in the 探花大神 User Portal.<\/li>\n\n\n\n
- Account synchronization is complete.<\/li>\n<\/ol>\n\n\n\n
探花大神-Initiated Provisioning<\/strong><\/h4>\n\n\n\nWhen you create new users in 探花大神 that don\u2019t exist in Microsoft, 探花大神 creates user accounts (provisions) with the 探花大神 user\u2019s credentials and attributes. For the new account to be provisioned to M365, the account must have an email address of the primary M365 domain that is synced with 探花大神. This is useful if your organization intends to use 探花大神 to manage your M365 deployment.<\/p>\n\n\n\n
When creating an account in 探花大神, an activation email can be sent to an alternate email address. Alternatively, admins can set a temporary password during creation.
To send an activation email to an alternate email address:<\/strong><\/p>\n\n\n\n\n- Add the new user to 探花大神.\n
\n- Bind the user to the M365 directory.<\/li>\n\n\n\n
- Leave Specify initial password<\/strong> unchecked.<\/li>\n\n\n\n
- After saving the user, you will be prompted to send the activation email.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
- The user will click the link in the activation email that was sent to the address you provided in step 1b and set their password.<\/li>\n\n\n\n
- The user logs in to the 探花大神 User Portal with the password they set in step 2.<\/li>\n\n\n\n
- Account synchronization is complete.<\/li>\n<\/ol>\n\n\n\n
<\/p><\/div>
- \n
- Don\u2019t authorize\/create multiple instances of a cloud directory integration to the same M365 domain. If you do, users bound to multiple M365\/Entra ID instances could be suspended in your M365\/Entra ID directory if you unbind that user from one of the instances. You can avoid this by deactivating sync for multiple M365\/Entra ID directory instances for the same domain.<\/li>\n\n\n\n
- Be aware that after you deactivate sync for a M365\/Entra ID instance and domain, all information specific to that M365\/Entra ID directory integration in the 探花大神 Admin Portal will be permanently deleted and cannot be recovered by simply reactivating sync.<\/li>\n<\/ul>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- App passwords<\/a> may be necessary to authenticate legacy endpoints where multi-factor authentication (MFA) is configured in M365<\/li>\n\n\n\n
- 探花大神 user accounts are synced with their M365 user account based on the primary email address <\/em>used in M365<\/li>\n\n\n\n
- If multiple M365 tenants are configured for 探花大神’s Directory Sync and a 探花大神 user is bound to more than one M365 tenant, only the M365 tenant with the 探花大神 user’s matching M365 primary email address<\/em> will be synced<\/li>\n\n\n\n
- At this time, 探花大神 doesn’t support integration with GoDaddy’s implementation of M365. This version has limited identity management capabilities that require SSO login with GoDaddy’s services to operate appropriately. Because of these requirements, we are prohibited from making changes to identities with the GoDaddy integration<\/li>\n\n\n\n
- Don’t import users that you don’t intend to manage with 探花大神. You have 48 hours to remove unwanted users and to contact your Technical Account Manager to avoid being charged for any users you remove after import <\/li>\n\n\n\n
- If the password takeover functionality has been disabled for your 探花大神 organization, then the password only syncs when the user or admin changes it. In addition, active users with passwords will receive password reset emails from each Cloud Directory to which the user is associated<\/li>\n\n\n\n
- M365\/Entra ID group management is only supported for security groups at this time<\/li>\n<\/ul>\n\n\n\n
Prerequisites<\/strong><\/h3>\n\n\n\n
- \n
- An active M365 domain<\/li>\n\n\n\n
- A user with the following administrator roles in M365:\n
- \n
- Privileged role administrator<\/li>\n\n\n\n
- Groups administrator<\/li>\n\n\n\n
- Users administrator<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- We also recommend that you have a Global administrator service account<\/li>\n<\/ul>\n\n\n\n
M365 Integration Scenarios<\/strong><\/h2>\n\n\n\n
You can integrate M365 with 探花大神 in the following two ways:<\/p>\n\n\n\n
- \n
- Taking over existing M365 accounts<\/li>\n\n\n\n
- Provisioning new M365 accounts<\/li>\n<\/ol>\n\n\n\n
Taking Over Existing M365 Accounts<\/strong><\/h3>\n\n\n\n
When you import existing M365 accounts and bind them to the M365 directory you\u2019ve enabled for sync, 探花大神 \u201ctakes over\u201d the accounts and becomes the manager and password authority for those accounts. <\/p>\n\n\n\n
Provisioning New M365 Accounts<\/strong><\/h3>\n\n\n\n
Account provisioning involves creating and maintaining user accounts and their attributes. New M365 accounts can be provisioned in M365 or in 探花大神.<\/p>\n\n\n\n
M365-Initiated Provisioning<\/strong><\/h4>\n\n\n\n
When an account is created in M365, a temporary password can be sent to an alternate email address, which lets users gain access to their account. <\/p>\n\n\n\n
When you create a user account in M365, users are provisioned in the following way:<\/p>\n\n\n\n
- \n
- Import the user into 探花大神.<\/li>\n\n\n\n
- Bind the user to the M365 directory.<\/li>\n\n\n\n
- The user resets their password in the 探花大神 User Portal.<\/li>\n\n\n\n
- Account synchronization is complete.<\/li>\n<\/ol>\n\n\n\n
探花大神-Initiated Provisioning<\/strong><\/h4>\n\n\n\n
When you create new users in 探花大神 that don\u2019t exist in Microsoft, 探花大神 creates user accounts (provisions) with the 探花大神 user\u2019s credentials and attributes. For the new account to be provisioned to M365, the account must have an email address of the primary M365 domain that is synced with 探花大神. This is useful if your organization intends to use 探花大神 to manage your M365 deployment.<\/p>\n\n\n\n
When creating an account in 探花大神, an activation email can be sent to an alternate email address. Alternatively, admins can set a temporary password during creation.
To send an activation email to an alternate email address:<\/strong><\/p>\n\n\n\n- \n
- Add the new user to 探花大神.\n
- \n
- Bind the user to the M365 directory.<\/li>\n\n\n\n
- Leave Specify initial password<\/strong> unchecked.<\/li>\n\n\n\n
- After saving the user, you will be prompted to send the activation email.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
- The user will click the link in the activation email that was sent to the address you provided in step 1b and set their password.<\/li>\n\n\n\n
- The user logs in to the 探花大神 User Portal with the password they set in step 2.<\/li>\n\n\n\n
- Account synchronization is complete.<\/li>\n<\/ol>\n\n\n\n
- Add the new user to 探花大神.\n
- 探花大神 user accounts are synced with their M365 user account based on the primary email address <\/em>used in M365<\/li>\n\n\n\n
- App passwords<\/a> may be necessary to authenticate legacy endpoints where multi-factor authentication (MFA) is configured in M365<\/li>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\"){kind=icon}
<\/p><\/div>