Considerations for Entra ID/Azure Active Directory & Office 365 users in our updated Claned version

In February 2025, we are launching an updated, reworked version of Claned. If your organization uses Entra ID/Azure Active Directory (AAD) integration or Office 365 (O365) Single Sign-On (SSO), there are a few important considerations to keep in mind.

General notes for Admins

• No changes are required for existing integrations configured in the prior Claned version.
• Entra ID/AAD integration is a paid extension to your Claned subscription. If the "Active Directory" section in the Admin page is locked, contact [e-mail].
• If you are setting up a new Entra ID/AAD integration in the updated version of Claned, please follow our guide: Integrating your Entra ID (Azure Active Directory) with Claned. If you encounter any issues, contact [e-mail] for assistance.
• Any Claned admin can modify the AD integration configuration, including removing it and syncing/unsyncing AD groups via the Admin page.
• Client ID and client secret are hidden in the Admin UI after being added.
  
  

Troubleshooting O365 SSO Login Issues

• If your organization or users log in with Office 365, they may need to reauthorize the Claned login after the update.
• AAD Admins may be prompted to approve admin consent again for any existing app registration.

• If users experience issues logging in via O365 SSO, instruct them to:

  1. Clear cookies for Claned on the Claned page:
     • Press Ctrl + F5 (Windows) or Command + Shift + R (Mac).
  2. If the issue persists, contact [e-mail] for assistance.
  3. Ensure that all users registering via O365 click the "Office 365" button during sign-up.
     
     

Changes in AD Group Behavior

• When an AD user logs in, they now appear in their AD group immediately, rather than only when a board is shared with the group (previous behavior).
• AD users cannot be removed from AD groups in Claned since group membership is managed in your tenant.
  • If an AD user is removed from the organization but logs in again, they will be re-added to the organization and their AD group in Claned.
  • This happens because Claned checks AD group membership on login.
• If an AD user existed in Claned before an admin synced their group, they will need to log in again for their membership to appear in Claned.

Managing Large AD Group Lists

If your tenant contains many groups, we recommend scoping access to only relevant groups when setting up the new version’s app registration. This will make it easier to:

• Search for groups in Claned.
• Sync and manage groups efficiently within the Claned Admin page.