Azure AD - Frequently Asked Questions – Home Page

1. Does the integration support local AD or on-premise setups?

No, Keka's Azure AD integration is built specifically for cloud-based Azure AD. On-premise or local Active Directory setups are not supported.

2. Does updating information in Azure AD reflect in Keka?

No, the data flow is one-way—from Keka to Azure AD. Changes made in Azure AD will not sync back to Keka.

3. How do I add employees to Azure AD?

Add employees in Keka, and their Azure AD accounts will be automatically created using the integration.

4. Will existing employees be affected by Azure AD integration?

Yes, if the Update Employees option is enabled during setup, Keka will sync all employee details—including for existing users.

Important: Make sure all existing employees are already present in Azure AD before enabling the integration.

5. Which employee details get updated in Azure AD?

The following fields are synced from Keka to Azure AD:

Attribute
First Name
Last Name
Display Name
Employee Number
Job Title
Reporting Manager
Location
Worker Type
Mobile Number

6. What if the reporting manager in Keka doesn’t exist in Azure AD?

Keka will still update the reporting manager field internally, but Azure AD will not reflect this update.

You can track such sync failures in Apps > Azure AD > Activity Log.

7. What if an employee email in Keka already exists in Azure AD?

If the email matches an existing user in Azure AD, their profile will be updated, not duplicated.

Ensure the email belongs to the same person to avoid mismatches.

8. How does the Azure AD integration work?

Keka uses the Microsoft Azure User Provisioning API to create and update user accounts in Azure AD via API calls. New user credentials are sent to a designated recipient set during the integration setup.

9. How fast is account creation in Azure AD?

As soon as an employee is added in Keka, Azure AD account creation begins immediately—with no delay in user ID and password generation.

10. Where is user data stored during the integration?

User details are not stored anywhere in between. Keka sends data directly to Azure AD via secure API calls.

11. What type of password is assigned to new users?

New Azure AD accounts receive a one-time use password, generated automatically. This password is sent to the recipient defined in the integration preferences.

12. Who receives the new employee's password?

During integration setup, the IT admin specifies a contact (typically an IT team member) to receive new user passwords securely.

13. Can I update integration preferences later?

Yes, you can modify your integration settings at any time. Changes will affect how employee data syncs moving forward.

14. Is there any delay in updating employee details?

No, updates made in Keka (e.g., name, title, department) sync to Azure AD promptly.

15. Can I view integration activity logs?

Yes. Go to Apps > Azure AD > Activity Log to view a full history of:

Employee syncs
Account creations
Updates
Errors and warnings

16. Can I update an employee's email ID in Azure AD via Keka?

No, email IDs cannot be updated through Keka. You'll need to manually update them in Azure AD.

17. What happens if the integration connection breaks?

You’ll need to reconfigure the integration. This will redirect you to the Microsoft login page where you must re-authenticate using valid Azure credentials.

18. What happens if there are mismatched user details?

If Keka and Azure AD have conflicting information, the integration will overwrite Azure AD details with the values from Keka to maintain consistency.

19. Can I limit the integration to only add employees?

Yes. You can configure the integration to only add employees by disabling the Update Employees option. In this case, only new hires will sync to Azure AD.

20. What's the difference between "Add Employees" and "Update Employees"?

Add Employees: Creates new Azure AD accounts for employees added in Keka.
Update Employees: Syncs changes to existing employee profiles in Azure AD.

Enabling both ensures full automation.

21. Will updating employees affect existing (old) users?

Yes, enabling the Update Employees setting will update attributes for all employees—including those added before the integration.

22. Can I manually update employee info instead of syncing?

Yes, you can choose to manually update Azure AD. However, if automatic sync is enabled, manual changes in Azure AD may be overwritten by Keka during the next sync.

23. What happens when a former employee rejoins?

Ensure their original email ID exists in Azure AD before reactivating their profile in Keka to avoid conflicts.

24. How do I remove an employee from Azure AD?

Go to the Azure portal.
Navigate to Azure Active Directory > Users.
Find and select the employee.
Click Delete user.

25. How do I reset an employee’s password?

Employees can use the Azure AD password reset feature. Alternatively, an admin can reset passwords from the Azure portal.

26. Can I remove the Azure AD integration from Keka?

Yes. Go to the Apps > Azure AD integration page and click Disable. This will stop all sync actions immediately.

Azure AD - Frequently Asked Questions