comment out scim

docs/sso-rbac/sso-providers/oidc/azure-ad.md

@@ -270,7 +270,7 @@ Port can query the group membership of users who log in through the AzureAD SSO,
 
 In order to import Azure AD groups into Port, Port will require the connection app to approve the `Directory.Read.All` permission.
 
-## SCIM Configuration (beta)
+<!-- ## SCIM Configuration (beta)
 
 <ScimLimitation/>
 
@@ -289,4 +289,4 @@ You will be provided with:
 
 The `endpoint` and `token` will be used to set up the SCIM integration in your identity provider.
 
-After receiving the SCIM `endpoint` and `token`, follow this [step-by-step guide](https://auth0.com/docs/authenticate/protocols/scim/inbound-scim-for-new-azure-ad-connections#configure-scim-in-azure-ad-for-oidc-apps) to enable SCIM. Begin in step 3, by registering a new application.
+After receiving the SCIM `endpoint` and `token`, follow this [step-by-step guide](https://auth0.com/docs/authenticate/protocols/scim/inbound-scim-for-new-azure-ad-connections#configure-scim-in-azure-ad-for-oidc-apps) to enable SCIM. Begin in step 3, by registering a new application. -->

docs/sso-rbac/sso-providers/oidc/okta.md

@@ -138,7 +138,7 @@ To allow automatic Okta group support in Port, please follow these steps:
    3.3 Click `Save`.
 
 
-## SCIM Configuration (beta)
+<!-- ## SCIM Configuration (beta)
 
 <ScimLimitation/>
 
@@ -189,4 +189,4 @@ The `endpoint` and `token` will be used to complete the setup of the new SWA app
    - Update User Attributes
    - Deactivate Users
    <br/>
-   <img src="/img/sso/okta/OktaSCIMapp.png" width="80%" />
+   <img src="/img/sso/okta/OktaSCIMapp.png" width="80%" /> -->

docs/sso-rbac/sso-providers/saml/azure-ad.md

@@ -66,7 +66,7 @@ Alternatively, if you are syncing your groups from an on-prem AD into Entra, con
 
 <img src="/img/sso/azure-saml/azureSamlGroups.png" width="60%" border="1px" />
 
-## SCIM Configuration (beta)
+<!-- ## SCIM Configuration (beta)
 
 AzureAD SAML applications support [SCIM](https://auth0.com/docs/authenticate/protocols/scim). 
 
@@ -83,4 +83,4 @@ You will be provided with:
 
  The `endpoint` and `token` will be used to set up the SCIM integration in your identity provider.
 
-After receiving the SCIM `endpoint` and `token`, follow this [step-by-step guide](https://auth0.com/docs/authenticate/protocols/scim/inbound-scim-for-azure-ad-saml-connections#configure-scim-in-azure-ad-for-saml-apps) to enable SCIM.
+After receiving the SCIM `endpoint` and `token`, follow this [step-by-step guide](https://auth0.com/docs/authenticate/protocols/scim/inbound-scim-for-azure-ad-saml-connections#configure-scim-in-azure-ad-for-saml-apps) to enable SCIM. -->

docs/sso-rbac/sso-providers/saml/okta.md

@@ -82,7 +82,7 @@ To expose your Okta groups to Port via the application, follow these steps:
 
 These groups will be ingested into Port as teams, enabling you to manage user permissions and RBAC in your Port account.
 
- ## SCIM Configuration (beta)
+ <!-- ## SCIM Configuration (beta)
 
 Okta supports [SCIM](https://auth0.com/docs/authenticate/protocols/scim) for SAML applications.
 
@@ -111,4 +111,4 @@ When configuring SCIM:
 - Set the `Unique identifier field` to `userName`.
 - For authenticating the SCIM connection, choose `HTTP Header`, and use the SCIM `token` provided by Port.
 
-:::
+::: -->