Now this feature is available for crowd server or not..?

abhinav.arae it is Crowd Data Center only feature

Is this feature only added in Crowd Data center version or Crowd Server version 3.6 too?

dl-softwaredelivery-devops this functionality will be available only in our Data Center edition of our products. Data Center is our enterprise offering when it comes to all our core products and I would highly recommend to move into this edition for any of your products.

'Please note that Azure AD filtering is available for Crowd Data Center only. ' - that's currently the case, but is this on the plan for Crowd Server also? At the moment we are afflicted by CWD-5357, so AzureAD syncing simply fails for us. The filtering ticket here is not released on standard server, and the handling of groups with duplicate names has been there since February, so neither fix is available. Making this filter available for standard server would help. Is it planned?

Nested Groups! Heading off to verify...

Hi Peter, I haven't found a way to do a filter based on a prefix, but nested groups do work.  So you can create a group in AD, all-jira-groups, for example and add all of your groups to that one group.  Then from crowd you only have to sync "all-jira-groups". This works when I test it.

Would like an answer on the question from marcus bledsoe. The ability to filter groups based on prefix is a must have.

Crowd 3.6 is out with this improvement, and can be downloaded from here 

https://www.atlassian.com/software/crowd/download

Is there a way to bulk upload groups to be filtered or maybe filter groups based on a prefix.  For example, only sync groups that start with "apac" or something like "apac*"?

Sure we will keep you updated on the following weeks regarding our testing

kaspar.janowsky Yes. This solution is available only in our premium offering - Data Center.

Is there only a solution for the Datacenter version? We use the normal version and have the same problem.

jonesbusy Please let me know if you were able to test our EAP to check whether we address your needs.

Hello everyone, we are looking for customers interested in Early Access Program to get Crowd 3.5 with Ability to Filter users and groups For AzureAD. If you are interested in the EAP please feel free to shoot me a message at mradochonski@atlassian.com

Thanks for the update!

Folks I would like to really thank you for your patience and supporting us as a team on our way of development of this feature. We are working on it currently and once we will be ready for the EAP we will let you know. You can be sure that as you are participating on this ticket you will be the first one to get the information that we are ready. We might also get back to you soon for some validation of specific use cases that we are working on. Stay tuned and thanks again!

Also quite curious for an EAP/Beta version, thank you Marek!

Is this far enough along to release an EAP/beta version?

jonesbusy We had some changes in our priorities and we are working on providing centralized license usage visibility in Crowd. After it we are going to move back to finish Azure AD filtering and we expect to release that in Q3 this year.

Hello,

Any update of the release date of this issue ?

It's very important for us, as our AD is very very huge and synchronizing it fully creates a lot of instability on our Crowd instance.

Thanks in advance for the update.

Valentin

Hello everyone,

We’re happy to say that we have finished the development of this feature and we have confident timeline to deliver it in March 2019.

Thanks again for all your votes and comments.

We’ll let you know once the release is available. Stay tuned!

Best regards,

Marek
Senior Product Manager, Atlassian, Crowd Server & Data Center

Hi All,

Just wanted to clear one thing about this limitation, that the license usage depends only on the number of users allowed to authenticate against any applications in Crowd.

So, for example, if a customer's Azure AD has 10,000 users, but they have allowed only users from 'developers' group of Azure AD which has 1500 users to authenticate using Crowd (via Application Management), then only these 1500 users will be counted towards Crowd license.

The only downside of this mechanism is performance since Crowd will still synchronize changes to all the 10,000 users from Azure AD instead of 1500.

Here's a knowledge base article related to license usage:
https://confluence.atlassian.com/crowdkb/how-are-crowd-users-counted-towards-the-application-user-limit-246481311.html

If this feature is crucial for you and you can't wait for its implementation in Crowd's Azure AD native connector, you might want to take a look at the ODCC plugin (Office 365 Directory Connector for Crowd) which has options to filter Azure AD users and groups: https://marketplace.atlassian.com/plugins/com.cleito.odcc/server/overview

Disclaimer: I work for the vendor of the ODCC plugin