Merge pull request #8494 from feddovanede/patch-98

Document support Mendix versions on Mendix Cloud

Author: MarkvanMents

content/en/docs/deployment/mendix-cloud-deploy/_index.md

@@ -100,6 +100,10 @@ Mendix apps cannot use custom ports. They communicate on the standard HTTP and H
 
 The number of end-users supported for your licensed app depends on your [pricing plan](#plans). End-users of your app are classified as either internal or external. You need to report this for licensing purposes, using either the [USAGE_METRICS_EMAIL_FIELDS custom variable](/developerportal/deploy/environments-details/#custom-environment-variables) (if you are using email domains to distinguish between end-users) or by [populating the user type](/howto/monitoring-troubleshooting/populate-user-type/) for each end-user of your app. Only end-users whose Mendix accounts are marked as **Active** are counted towards the number of end-users of the app.
 
+### Supported Mendix Versions {#mendix-cloud-supported-versions}
+
+Mendix Cloud supports deploying and running all [supported major versions](/releasenotes/studio-pro/lts-mts/#major-version) of Mendix. This includes major versions that are supported via the Extended Support product. It is not possible to deploy unsupported versions to Mendix Cloud.
+
 ## Mendix Pricing Plans {#plans}
 
 Mendix licenses are sold as part of plans. Plans consist of the following items:

content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md

@@ -54,6 +54,7 @@ Before starting the process of deploying a licensed app, make sure to complete t
 * You have [transport rights](/developerportal/deploy/node-permissions/#transport-rights)
 * Your [two-factor authentication](/developerportal/deploy/two-factor-authentication/) is set up
 * The deployment package for your app is not bigger than 1 GB (uncompressed)
+* Your app is using a [supported Mendix version](/releasenotes/studio-pro/lts-mts/#major-version)
 
 {{% alert color="info" %}}You can verify that your app is under the 1 GB limit by creating a deployment package, as described below, and then viewing that package's size in the package details.{{% /alert %}}