• 8
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Azure AD group filtering must be done by adding each desired group's name. This becomes challenging for large organizations with thousands of groups.

      Crowd should allow wildcard filtering or a Group Object Filter (like Restricting LDAP Scope for User and Group Search) option for Azure AD.

          Form Name

            [CWD-5669] Azure AD Group Filtering Improvements

            Our team tried to configure integration Crowd and Azure, but synchronization of groups failed because of the same groups names in Azure. That why was decided to and list of groups to the filter of directory configuration.
            Unfortunately, this filter doesn't support regular expressions and we have to provide need to provide plain list of all required groups. It's inconvenient, because list is quite big.
            Using RestAPI for that is impossible as well (this problem is mention in the following ticket CWD-5603).
            It is not enough to add this list once, we need to update it regularly. For testing purposes only, we have resolved the problem by adding the list directly in database...
            That's why using regular expressions in the filtering is obvious and necessary feature which was not implemented for some reason.
            We hope that it will be implemented as soon as possible.

            aligntechsupport added a comment - Our team tried to configure integration Crowd and Azure, but synchronization of groups failed because of the same groups names in Azure. That why was decided to and list of groups to the filter of directory configuration. Unfortunately, this filter doesn't support regular expressions and we have to provide need to provide plain list of all required groups. It's inconvenient, because list is quite big. Using RestAPI for that is impossible as well (this problem is mention in the following ticket CWD-5603 ). It is not enough to add this list once, we need to update it regularly. For testing purposes only, we have resolved the problem by adding the list directly in database... That's why using regular expressions in the filtering is obvious and necessary feature which was not implemented for some reason. We hope that it will be implemented as soon as possible.

            in our Azure Active Directory we have a lot groups like
            grp_PIA0277_HELP_User
            grp_PIA0277_HELP_lead
            grp_PIA0277_HELP_external
            grp_PIA0277_TEST_User
            grp_PIA0277_TEST_lead
            grp_PIA0277_TEST_external
            and so on...

            we want to sync all this groups with a Groupfilter
            grp_PIA0277_*

             

             

            Restricting Scope for User and Group Search iss allreday woging in the Crowd Server Version for LDAP sync, why not for Datacenter with Azure Sync?

            Plugins like office-365-directory-connector-for-crowd have this funktion/possibility - but this Pligin is not avriable for datacenter

            DKB Service GmbH added a comment - in our Azure Active Directory we have a lot groups like grp_PIA0277_HELP_User grp_PIA0277_HELP_lead grp_PIA0277_HELP_external grp_PIA0277_TEST_User grp_PIA0277_TEST_lead grp_PIA0277_TEST_external and so on... we want to sync all this groups with a Groupfilter grp_PIA0277_*     Restricting Scope for User and Group Search iss allreday woging in the Crowd Server Version for LDAP sync, why not for Datacenter with Azure Sync? Plugins like office-365-directory-connector-for-crowd have this funktion/possibility - but this Pligin is not avriable for datacenter

              Unassigned Unassigned
              caronson Cole Aronson
              Votes:
              9 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: