Tim Jacomb

Thanks will try reproduce in the next few days

Each use-case is specific to how you set it up. It should work just fine if you follow the docs in the README. We have it running with group based...

This is our working config: https://github.com/hmcts/sds-flux-config/blob/b1272bc2a3ee3de7481d487130c68cf9fac14d9e/apps/jenkins/jenkins/jenkins.yaml#L99-L117

How would that work though? AD is a bit different in that you put your username and password into Jenkins which transmits the credentials. With the Azure AD plugin it...

what happens

I can't see anything in 191 that would cause this. Can you provide information to allow this to be reproduced from scratch? JobDSL / configuration as code and Azure CLI...

I don't know unfortunately, these ones can be hard to figure out. If I can't reproduce it, likely can't fix it

Just annotation and icon changes there

Could you give more details please, Why are you doing this? How were you creating the users before? Seems related to https://github.com/jenkinsci/azure-ad-plugin/issues/92#issuecomment-815165936 (The only plugin I'm aware of with support...

Regardless of it working perfectly before that was an implementation detail and not a supported feature. It was likely broken when Azure AD users got support for using an API...