Any risks with SAML with Entra Enterprise Applications?

We’ve recently moved from Openvpn to Pritunl, and as we use Entra, I decided to set up the auth through SAML/Enterprise applications so that we can use Conditional access rules. I noticed that there aren’t any guides or options for this, but it works just fine when using the basic “SAML” setting in Pritunl and editing some attributes/claims.

Now my question is: Is there any specific reason for there not being any guides or documentation for it? Any known risks or anything like that?

Without using one of the provider APIs there is no check at connection and no hourly checks while connected to verify the user is active on the single sign-on provider. The connection single sign-on can be enabled to verify the single sign-on user when connecting but there would still be no hourly verification while the connection is active.

Great to know, thank you for the quick response!