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.
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?
An error occurred while saving the commentricky zou commented
A MS consultant provided link to this workaround (http://mrochon.azurewebsites.net/2019/05/06/using-groups-in-azure-ad-b2c/) , and it's UGLY! B2C for us provides abstraction layer for handling other Idps in order to reduce complexity, this limitation and the complexity in the workaround is making me rethink if B2C is even a good fit for us. not only is the workaround difficult to setup and maintain, it requires an additional AZ Function service.ricky zou supported this idea ·