Hi everyone,
I found several previous discussions stating that there is no supported way to control the order of social login buttons in New Universal Login.
However, I wanted to confirm whether this is still the case as of June 2026.
Our tenant has multiple identity providers (e.g., Google and Microsoft Entra ID), and we’ve noticed that the order of the login buttons differs between client applications. For example, one client displays Google first, while another displays Microsoft Entra ID first, even though both applications use the same tenant.
From a Single Sign-On (SSO) user experience perspective, this behavior seems inconsistent and can be confusing for end users.
Has support for customizing the order of social login buttons been added since the previous discussions? If not, is there any recommended or supported approach to ensure a consistent button order across client applications?
Thank you!
hi @KouYuume
Thank you for reaching out to us!
I understand that you are looking for information about changing the order of the social login buttons when using the New Universal Login.
You are correct that at this moment, there is no out-of-the-box solution for changing the order of the Social or Enterprise buttons in the New Universal Login experience. By default, the buttons are rendered based on the creation date of the Connections in your tenant and the oldest will appear at the top followed by the other Connections based on the order in which they were created.
To achieve a consistent single sign-on (SSO) user experience across all client applications, you can utilize the following supported and recommended approaches:
-
Re-create the Connections ( no code fix )
Once you determine the preferred layout/order, you can document the configuration details of your existing connections, then delete and create them again in the order you want them to be displayed. Please note that this action will generate new a connection_id for each one, which you will likely need to account for and change in any setting that could reference them specifically.
-
Advanced Customizations for Universal Login (ACUL) ( pro-code fix)
ACUL extends the capabilities of Universal Login allowing you to build custom client-rendered interfaces for a more seamless user experience, by building the login screens using your preferred frontend frameworks and designs. By rendering the UI components yourself, you have absolute control over the layout, enabling you to place, style, and strictly order the Google and Microsoft Entra ID buttons exactly as your design guidelines dictate.
We warmly invite you to submit a Feature Request detailing the capability that you are looking for. Our Product team monitors the page and has visibility over all submissions where others can cast their vote on the features that they would most like to see implemented. More votes can help accelerate the development of a feature.
I will mark this topic as resolved since at the moment we do not offer an out-of-the-box solution, but please reach out to us for any other issues or requests and we will gladly look into it for you.
Have a great one,
Gerald
Hi Gerald,
Thank you for the detailed explanation.
The first option works for us, so we’ll proceed with re-creating the connections in the desired order.
That said, I would also like to submit this as a feature request.
Having the display order determined by the connection creation date seems unintuitive, especially because the order can differ between client applications within the same tenant. From an SSO user experience perspective, it would be much more useful if administrators could explicitly configure the order of the login buttons on a per-application basis.
I hope this capability can be considered for a future enhancement.
Thank you again for your help!