Thank you for your post and I'm glad that you were able to resolve your issue!
From your issue, I understand that the fingerprint of the SAML based certificate is only displayed in SHA1, even when changing or creating a new certificate with the Certificate signing algorithm set to SHA256.
- Related issue - https://github.com/MicrosoftDocs/azure-docs/issues/11624
Note: The thumbprint is used to identify the certificate and it is not related to the signing algorithm.
I've reached out to our SAML team to see if they can share any inputs on this limitation within the Portal, and I've also created an internal feature request so our engineering team can look into implementing this.
Thank you!