To follow up on this topic for historical context, the support case was concluded through the assistance of one of our senior engineers.
The resolution ended up being in this particular situation the dashboard TRY option initiates a login request to Azure AD with the inclusion of
prompt=consent parameter. Below is a direct quote for more context.
You can confirm this by, instead of clicking the button, copying the target link address and then inspecting the URL in your text editor of choice.
You can even remove the
prompt=consent parameter and then paste the modified URL into a new browser tab which should allow you to do the login request without consent being requested if consent was already given (if you do this on a browser session with a user already authenticated in Azure AD you will likely even not see any Azure AD screens).
The reason that the dashboard always includes this parameter is to allow for the try flow to always go through the full login flow. Your client application will, in general, not include this parameter so end-users themselves should not experience this behavior.