"Azure SSO" - "New Single Sign-On (SSO)" App Name Confusion

Andrew Blackburn

We recently migrated to the 'New Single Sign-On (SSO)' implementation of BBID. Everything is working correctly, and users are able to sign in without issues. However, in Entra, we noticed that the app name is displayed as 'Azure SSO' with the ID 'f32d403d-7a8a-4b58-bd56-72b99b735ab6'. This poses a problem when viewing sign-in logs in Entra, as it's difficult to identify that the app is associated with Blackbaud.

Are there any plans to update this app name to something more recognizable as coming from Blackbaud? For example, 'Blackbaud ID,' 'Blackbaud ID SSO,' 'Blackbaud Entra SSO,' or 'Blackbaud Azure SSO'? Additionally, are there plans to add a logo? Both of these changes seem like straightforward updates that would have only positive impacts on Blackbaud customers.

Unfortunately, we cannot change the name ourselves, as this app was set up in Blackbaud's BBID tenant. With the old implementation, we were able to enter a descriptive name ("Blackbaud") because the application registration was created by us, in our tenant.

Dima Serhiychuk

@Andrew Blackburn:

We recently migrated to the 'New Single Sign-On (SSO)' implementation of BBID. Everything is working correctly, and users are able to sign in without issues. However, in Entra, we noticed that the app name is displayed as 'Azure SSO' with the ID 'f32d403d-7a8a-4b58-bd56-72b99b735ab6'. This poses a problem when viewing sign-in logs in Entra, as it's difficult to identify that the app is associated with Blackbaud.

Are there any plans to update this app name to something more recognizable as coming from Blackbaud? For example, 'Blackbaud ID,' 'Blackbaud ID SSO,' 'Blackbaud Entra SSO,' or 'Blackbaud Azure SSO'? Additionally, are there plans to add a logo? Both of these changes seem like straightforward updates that would have only positive impacts on Blackbaud customers.

Unfortunately, we cannot change the name ourselves, as this app was set up in Blackbaud's BBID tenant. With the old implementation, we were able to enter a descriptive name ("Blackbaud") because the application registration was created by us, in our tenant.

+1, We would also like this changed. “Azure SSO” does not tell us which application it is and makes it hard to identify and manage when we have dozens of other SSO applications to manage.

Lauren Henderson 3

@Andrew Blackburn
Have you added this as an Idea in the Ideas Bank? This seems like a good fit for that forum.

Andrew Blackburn

@Lauren Henderson I have not added it to the Idea Bank yet. The reason I’m hesitant is that I don’t believe this is something that should require votes or customer suggestions; it seems like an oversight that should simply be addressed. In my opinion, it’s a significant issue that the app was registered with Microsoft with zero branding information.

Andrew Blackburn

Mentioning @John Vogel and @Janet Wittenberg directly to get their insight into this one. Thank you!

John Vogel

@Andrew Blackburn
Thanks for this feedback and calling this to my attention! I'll work with the team to get this updated and will be in touch.

John Vogel

Quick update, the app name was updated at the beginning of the month but we just added the Blackbaud icon to it. Please reach out if there's any additional feedback or questions.

Andrew Blackburn

@John Vogel this is great. I see it on my end. Thank you so much and apologies for pinging without checking that the change was made!