Finalsite's Azure Active Directory integration syncs constituent data (creating and updating user accounts) from Azure AD into Constituent Manager on an hourly basis. Setup requires configuring an application in Azure and providing Finalsite with access credentials; deployment is handled by a Finalsite specialist.
💡Quick answers
- What does the Azure Active Directory integration do? Syncs user data from Azure AD into Finalsite's Constituent Manager hourly, creating and updating constituent accounts based on Azure group membership.
- How should users in Azure be organized for the integration? Place users to sync in dedicated Azure groups (one per user type, e.g., one for faculty and one for students) so Finalsite can target the correct groups during sync.
- What must you do before the Azure application secret expires? Reach out to Finalsite Support with an updated secret before the expiration date to avoid interrupting the integration; Finalsite recommends setting a two-year expiration.
- Can the integration be combined with LDAP authentication? Yes; the Azure AD integration for constituent data can be used alongside LDAP Authentication so users log into Finalsite with their Azure credentials.
Finalsite offers a constituent integration with Azure Active Directory. This integration can be used to create and update users based on data maintained in Azure Active Directory.
Data detail
The Data Mapping Guide contains a full list of supported data fields. As with all of our integrations, we can modify the mapping to best suit your needs.
Additionally, we can support data and schema extensions to pull additional information in the sync.
The integration runs hourly to create and update your users.
Configuration
To use the integration, you will need to configure an application in Azure Active Directory and provide us with the appropriate access credentials.Â
Note: You are required to set an expiration date on the secret that you create for us. We suggest a two-year expiration. Please reach out to Support with an updated secret before the expiration date to avoid interrupting the functionality of the integration.
We utilize groups to target the requests from Azure, which means you should have a group (or groups) that contains the users you want to be synced with Finalsite. We suggest one group per user type (e.g., if you intend to pull students and faculty, we recommend one group for all of your faculty and one for all of your students).
Deployment
For deployment, you will work with one of our deployment specialists to configure and test the integration. We will assist in configuring the application in Azure, as well as adjusting the mapping to suit your needs. We will test on a clone site so the data can be reviewed and mappings refined before it is deployed on your production site.
Additional information
An additional feature that we offer is a SAML-based authentication option that can be configured to allow constituents and/or admins to log into Finalsite via Azure Active Directory. More information on this option can be found in the article Use an external identity provider.
Comments
Please Sign in to leave a comment if you don't see the comment box below.