How can we improve Azure Active Directory?

Get user membership groups in the claims with AD B2C

As it's possible in the standard AD by changing the API application manifest option "groupMembershipClaims" to "SecurityGroup", is it possible to return user membership group in the claims with AD B2C?

Now, we can have only the default and custom attributes by adding a signin policy, but it's impossible to get user membership groups.

1,020 votes
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Alexandre Blecich shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.

That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.

Apologies for the delay.

/Parakh


Old message:
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?

66 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    I can't believe that this isn't in by default. It makes me not trust what I think I know about this stuff.

  • Don Airey commented  ·   ·  Flag as inappropriate

    How is using the Graph API a solution? You need to burn administrator privs and a secret into the application in order to query the API. This is a HUGE security leak and simply an unworkable solution. Your answer at the moment appears to be "Claims Based Authentication just doesn't work for B2C" which is unworkable for us.

  • Mike DePouw commented  ·   ·  Flag as inappropriate

    @Mark - that's a great question. I would recommend a stack overflow question with the 'azure-ad-b2c' tag.

  • Mark commented  ·   ·  Flag as inappropriate

    How does the workaround work with SPA using MSAL.js? How can we use MSAL.js with groups / roles?

  • Anders Thorsen commented  ·   ·  Flag as inappropriate

    "Because of the cost and the fact that there is a workaround available, other features get prioritized over this one."

    May I ask what the recommended workaround is? The original poster mentions creating separate attributes for this, but is this the recommended workaround?

  • zmorris commented  ·   ·  Flag as inappropriate

    Wow. This is the top feature request for B2C - *for years* - and the team is saying that it is not on a roadmap.

    If this most basic feature has a 'large development cost', then someone has seriously messed up in designing this system.

    Please implement asap.

    As the previous poster mentioned, the very little bit of documentation that exists for an actual implementation of a workaround is quite poor and out of date.

  • SB commented  ·   ·  Flag as inappropriate

    This is such a fundamental feature ... no matter the cost it should be addressed! Do the right thing: take the feedback and build the feature.

    Moreover: The "workaround" is very poorly documented, if at all, and I've had 2 tickets open with MS Support for -a year- to make it work as it should in a standard web app - which is still unresolved. Many times they've tried to find documentation to make it work and failed.

  • zmorris commented  ·   ·  Flag as inappropriate

    Myself and my teams have been *trying* to work with AAD B2C for *years* and this glacial progress has sadly been typical. This is very basic functionality that almost anyone using B2C will run in to almost *immediately* once they try to start using it.

    Please: Be heroes. Disprove the terrible reputation the team behind B2C has earned. Implement this fundamental feature ASAP.

  • Petteri commented  ·   ·  Flag as inappropriate

    Group information is very much needed. I'm surprised it isn't already found here. Don't be bad! Thanks!

  • Hrvoje Kusulja commented  ·   ·  Flag as inappropriate

    We are using B2C and are using Groups for permissions. In regular AAD is fine, but in B2C we need to have groups inside claims. This is more than 2 and half year old topic. Still now progress :(

Feedback and Knowledge Base