Update pass-params-idp.mdx

Update for SAML params

Author: clairekinde11

src/content/docs/authenticate/auth-guides/pass-params-idp.mdx

@@ -15,11 +15,11 @@ There's a number of reason why you might want to use upstream params:
 - to create a smoother sign in experience - by passing the email through
 - to offer an account switcher (such as the Google account switcher) during sign in
 
+Upstream params are available for OAuth 2.0 connections, e.g. [social connections](/authenticate/social-sign-in/add-social-sign-in/), [Entra ID OAuth 2.0 enterprise connection](/authenticate/enterprise-connections/azure/), and as part of [advanced configurations](/authenticate/enterprise-connections/advanced-saml-configurations/) in SAML connections. 
+
 ## Limitations
 
-- Each IDP has their own set of supported parameters and values, so you'll need to check their documentation to determine which URL parameters are supported.
-- Applies only to OAuth 2.0 connections, e.g. [social connections](/authenticate/social-sign-in/add-social-sign-in/) and [Entra ID OAuth 2.0 enterprise connection](/authenticate/enterprise-connections/azure/).
-- SAML IdPs do not support upstream parameters.
+Every identity provider has their own set of supported parameters and values, so you'll need to check their documentation to determine which URL parameters are supported.
 
 ## Static parameters