Remember that Gluu is an Federated Identity Provider (IDP), not an Relying Party (RP). In the screenshot above, the Azure devops panel is acting as an RP. It is consuming role information from the IDP (Azure AD), and then enforcing policies in the application, like whether a person can delete a team.
If you want to centralized RBAC, there are ways to do it. For example, you could implement a central authorization server, like OPA or OSO, and have your application call it, or map features to it. You could also map roles to OAuth scopes, and your application could use these for authorization.
This topic is really worth of a Zoom call to discuss. Maybe you can schedule with @Davin.Cooke to discuss.