Why doesn't app registration federated credentials support wildcards for branch entity type?

Question

According to this, Azure doesn't support pattern matching for the branch entity type when adding a federated credential to an app registration. Why is this the case and will this be supported in the future. As mentioned by this, I could just use an environment, but that seems jank and I don't want to do that if I don't have to.

Answer 1

Hi Clay Casper,

Update: I heard back from the product team. You are correct that Azure does not support pattern matching for the branch entity type when adding a federated credential to an application registration.

This is a limitation that the product team is aware of, and they are working on a fix. There is a design planned for this with the intent of fixing the way that this limitation affects Github branching. It is being worked on currently but the ETA may change based on a number of variables. I will update this thread if I hear more.

In the meantime, you are also welcome to leave a feature request in the Feedback forum so that the product team can reply directly there as well: [https://feedback.azure.com/

-

If the information addressed your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar issues.

Answer 2

Hello @Marilee Turscak-MSFT
Could you kindly offer an update regarding this matter? A significant amount of time has elapsed since the initial question was raised, and it remains an obstacle to our feature branch strategy or wildcard strategy. To address this issue, we've had to resort to creating application passwords.

Thanks for you Answers :)

Answer 3

If you still have the issue, please try to upvote this user feedback: https://feedback.azure.com/d365community/idea/2068fe95-45ec-ee11-a73d-0022484c4e0d