For anyone stumbling across this issue, The problem was on our side;
- The Name ID on the app needed to be changed to "Persistent" in EntraID.
- The login type needed to be specified as "unspecified" in Veeam.
- Set EntraID to sign SAML responses and assertion
Some of this information came from here; https://helpcenter.veeam.com/docs/backu ... _saml.html
Luckily our own resident SSO expert (among many other things) - Peter Nield was able to assist me in getting to the bottom of this.
I think what would really help people, would be for more documentation around setting up SAML for EntraID as this is rapidly becoming a base requirement for most large organisations.
![Image]()
![Image]()
- The Name ID on the app needed to be changed to "Persistent" in EntraID.
- The login type needed to be specified as "unspecified" in Veeam.
- Set EntraID to sign SAML responses and assertion
Some of this information came from here; https://helpcenter.veeam.com/docs/backu ... _saml.html
Luckily our own resident SSO expert (among many other things) - Peter Nield was able to assist me in getting to the bottom of this.
I think what would really help people, would be for more documentation around setting up SAML for EntraID as this is rapidly becoming a base requirement for most large organisations.


Statistics: Posted by ashleyw — Oct 09, 2025 4:18 am







