AlertFind Azure AD Connector

Looking to automate AlertFind Data Import? Yes! this is the place to be. Our Azure AD Connector will make automation a breeze!

In order to perform a successful connection to your Azure Active Directory instance, we just need the following information and that's it!

1. Directory ID: This ID can be found in the Azure Active Directory properties. It is a 32 Character long alphanumeric string. Click here in case you need help in finding this.
   
   
2. Username and Password: This should belong to a user having appropriate rights to read the Users Information for all users from the directory. We suggest creating a separate user for the connector purpose. The username is required in the format username@domain.com.
   
   
3. Users.Read.All permission: Should be configured to allow the user to access the rest of the users profiles.
   
   
4. Application Manager Role: Can be removed once the application is enabled.
   

Note: All the required permissions, rights as well as how to check current permissions granted to the user are detailed here.

Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information :

• UserID 
• Name 
• First Name 
• Last Name 
• Email 
• Job Title  
• Mobile Phone 
• Business Phone  
• Office Location
  
  

How does our Azure Active Directory connector works

Detailed Steps Explaining Above Graphic :

1. Azure AD connector fetches the User Information stored in your Azure AD instance via API.
   
   
2. Based on your chosen frequency, our connector running on AWS Lambda, fetches data from Azure AD.
   
   
3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
   
   
4. The CSV is compressed to a Zip file and sent to AlertFind API via the AlertFind connector running on AWS lambda.
   
   

Data Storage Nodes in The Graphic Above:

1. Node 5 : Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution has finished.
   
   
2. Node 6 : Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
   
   
3. Data Safety : All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 validated hardware security modules.
   
   

We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.

AlertFind Connector List