🤖 Auto-merge documentation from branches

nightly/api-management/dashboard-configuration.mdx

@@ -3621,10 +3621,6 @@ To enable request and response logging, please take a look at [useful debug mode
 **A warning on detailed logging:** This mode generates a very large amount of data, and that data exponentially increases the size of your log data set, and may cause problems with delivering analytics in bulk to your MongoDB instances. This mode should only be used to debug your APIs for short periods of time.
 
 
-<Note>
-Detailed logging is not available for Tyk Cloud Classic customers.
-</Note>
-
 
 ### Activity by API
 

nightly/api-management/mdcb.mdx

@@ -743,7 +743,7 @@ The most important elements here are:
 |`api_key`      |This the API key of a user used to authenticate and authorize the Gateway's access through MDCB. The user should be a standard Dashboard user with minimal privileges so as to reduce risk if compromised. The suggested security settings are `read` for `Real-time notifications` and the remaining options set to `deny`.|
 |`group_id`    |This is the "zone" that this instance inhabits, e.g. the cluster/data center the gateway lives in. The group ID must be the same across all the gateways of a data center/cluster which are also sharing the same Redis instance. This id should also be unique per cluster (otherwise another gateway's cluster can pick up your keyspace events and your cluster will get zero updates).
 |`connection_string`     |The MDCB instance or load balancer.|
-|`bind_to_slugs` | For all Tyk installations except for Tyk Classic Cloud this should be set to false.|
+|`bind_to_slugs` | For all Tyk installations this should be set to false.|
 
 Once this is complete, you can restart the Tyk Gateway in the Data Plane, and it will connect to the MDCB instance, load its API definitions, and is ready to proxy traffic.
 

nightly/api-management/plugins/javascript.mdx

@@ -41,9 +41,6 @@ We've provided the following guides:
 
 
 
-    <Note>
-    Tyk Cloud Classic does not support custom middleware.
-    </Note>
 
 ## Using JavaScript with Tyk
 

nightly/api-management/request-quotas.mdx

@@ -316,7 +316,6 @@ export TYK_GW_ENFORCEORGQUOTAS=true
 
 Refer to the [Tyk Gateway Configuration Reference](/nightly/tyk-oss-gateway/configuration#enforce_org_quotas) for more details on this setting.
 
-{/* Why we are commenting org quotas: Organization quotas are a hangover from the Classic Cloud, where all clients shared a deployment. They are not documented anywhere presently, and I’m not sure why we would start to do so - but if we’re going to, we need to be very careful not to add complexity to the way users configure things. */}
 
 {/* ### Organization-Level Configuration
 

nightly/api-management/traffic-transformation/request-size-limits.mdx

@@ -56,9 +56,6 @@ A value of zero (default) means that no maximum is set and the system-wide size
 This limit will be evaluated before API-level or endpoint-level configurations. If this test fails, the Tyk Gateway will return an error `HTTP 413 Request Entity Too Large`.
 
 
-<Note>
-Tyk Cloud Classic enforces a strict request size limit of 1MB on all inbound requests via our cloud architecture. This limit does not apply to Tyk Cloud users.
-</Note>
 
 
 <hr />

nightly/api-management/traffic-transformation/virtual-endpoints.mdx

@@ -55,9 +55,6 @@ Inline mode is mainly used by the dashboard to make code injection easier on mul
 We have put together a [library](https://github.com/TykTechnologies/custom-plugins#virtual-endpoints) of JS functions that you could use in your virtual endpoints. We welcome submissions from the Tyk community so if you've created a function that you think would be useful to other users, please open an issue in the Github repository and we can discuss bringing it into the library.
 
 
-<Note>
-Virtual endpoints are not available in Tyk Cloud Classic.
-</Note>
 
 
 <hr />

nightly/api-management/user-management.mdx

@@ -475,7 +475,7 @@ A user that does not belong to an Organization is sometimes referred to as an *u
 
 
 ## Single Sign-On integration
-You can integrate your existing identity management server with the Tyk Dashboard, as explained in our detailed [Single Sign-On (SSO) guide](/nightly/api-management/external-service-integration#single-sign-on-sso). **This functionality is available with all Tyk licenses except Tyk Classic Cloud.**
+You can integrate your existing identity management server with the Tyk Dashboard, as explained in our detailed [Single Sign-On (SSO) guide](/nightly/api-management/external-service-integration#single-sign-on-sso). **This functionality is available with all Tyk licenses.**
 
 By default all users who login via SSO are granted admin permissions. You can change this behavior by setting either default permissions for *[users](/nightly/api-management/user-management#manage-tyk-dashboard-users)* or by creating a default *[user group](/nightly/api-management/user-management#manage-tyk-dashboard-user-groups)* to which all new users are assigned. With some IDPs you can automatically assign different SSO users to different *user groups* by dynamically mapping the IDP's user groups, for example with [Azure AD](/nightly/api-management/single-sign-on-oidc#user-group-mapping).