Revert "Changed URL + implemented redirects"

This reverts commit 52d22e8.

Author: NicoletaComan

content/en/docs/control-center/apps/deployed-apps.md

@@ -93,7 +93,7 @@ The **Apps with License Keys** tab provides an overview of all apps for which li
 
 License keys are aligned with your Mendix contracts and need to be applied by you to each app. Every app environment (such as test, acceptance, and production) requires its own license key. 
 
-Any changes to licenses require the Technical Contacts to reapply license keys to their respective app environments. For example, when contracts are created or renewed, new license keys are automatically generated. Then these new license keys must be applied to the environments of the app for which the contract was changed. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps/#activate-mendix-license) section in *Licensing Apps*.
+Any changes to licenses require the Technical Contacts to reapply license keys to their respective app environments. For example, when contracts are created or renewed, new license keys are automatically generated. Then these new license keys must be applied to the environments of the app for which the contract was changed. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#activate-mendix-license) section in *Licensing Apps*.
 
 On the **Apps with License Keys** tab, you can do the following:
 
@@ -148,7 +148,7 @@ The list below show the details of the environments with the following columns:
 
 The latest version of license keys created for the apps are shown on the **Apps with License Keys** tab on the **Deployed Apps** page in Control Center.
 
-Several deployment options require the Technical Contact to manually apply license keys to the app environments. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps/#activate-mendix-license) section in *Licensing Apps*.
+Several deployment options require the Technical Contact to manually apply license keys to the app environments. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#activate-mendix-license) section in *Licensing Apps*.
 
 In some exceptional cases, the Technical Contact may also receive license keys for other deployment models. As a Mendix Admin, you are aware of these.
 
@@ -168,27 +168,27 @@ There might be multiple reasons for this. However, it is likely that your app is
 
 1. [Request new license keys](https://newnode.mendix.com/) for the app environments.
 2. Download the license keys.
-3. Reapply license keys for apps with discrepancies. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps/#activate-mendix-license) section in *Licensing Apps*.
+3. Reapply license keys for apps with discrepancies. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#activate-mendix-license) section in *Licensing Apps*.
 
 #### How Can Our License End Date Differ from Our License Keys End Date? How to Correct this?
 
 The end date of license keys is configured to match your Mendix contract end date. These license keys are published in Control Center and have correct dates.
 
-In case of discrepancy, email the license keys to the Technical Contacts of these apps, and ask them to reapply the license keys for the apps with discrepancies. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps/#activate-mendix-license) in *Licensing Apps*.
+In case of discrepancy, email the license keys to the Technical Contacts of these apps, and ask them to reapply the license keys for the apps with discrepancies. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#activate-mendix-license) in *Licensing Apps*.
 
 #### Do We Have to Download New License Keys Once We Renew Our Contract?
 
 Upon renewal of a Mendix contract, new license keys will be automatically emailed to the Technical Contacts of the apps. Additionally, you can also download them on the **Apps with License Keys** tab on the **Deployed Apps** page in Control Center.
 
 #### Do We Have to Manually Activate License Keys After Contract Renewal?
 
-Yes, the Technical Contact of the app needs to manually apply new license keys to the app after the contract is renewed. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps/#activate-mendix-license) in *Licensing Apps*.
+Yes, the Technical Contact of the app needs to manually apply new license keys to the app after the contract is renewed. For details on how to apply license keys, see the [Activating a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#activate-mendix-license) in *Licensing Apps*.
 
 #### What Happens If We Do Not Update Our License Keys After the License Key End Date? Will We Lose Our Data?
 
 After the end date of the license key has passed, your apps enter a 30-day grace period. During this grace period, the app will continue to run normally using the expired license. However, you may notice extra warning messages in the app logs during this period.
 
-If the Technical Contact of the app does not update the license keys by the end of this period, the app may be forcefully stopped by the Mendix runtime. Upon restart, the app will switch to trial mode and will follow the limitations of trial mode. For details of license limitations, see [Licensing Apps](/developerportal/deploy/licensing-apps/).
+If the Technical Contact of the app does not update the license keys by the end of this period, the app may be forcefully stopped by the Mendix runtime. Upon restart, the app will switch to trial mode and will follow the limitations of trial mode. For details of license limitations, see [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).
 
 #### Our App Stopped Working Because the License Key Expired. What Should We Do?
 

content/en/docs/control-center/entitlements/end-users.md

@@ -39,7 +39,7 @@ Mendix differentiates between these types of users:
 * External user – A user who is not an employee or a contractor of the customer or of the affiliated company or group.    
   The associated licensing model is **External User Subscription**.
 
-For details on user types, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps/#user-types-and-definitions) section of *Licensing Apps*.
+For details on user types, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps-outside-mxcloud/#user-types-and-definitions) section of *Licensing Apps*.
 
 ## Overview Tab
 

content/en/docs/deployment/general/_index.md

@@ -14,7 +14,7 @@ However, several topics relate to multiple platforms. These topics are covered i
 
 The subjects covered in this documentation section are as follows:
 
-* [Licensing Apps](/developerportal/deploy/licensing-apps/)
+* [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/)
 * [Secure Outgoing Connections from your Application](/developerportal/deploy/securing-outgoing-connections-from-your-application/)
 * [Two-Factor Authentication](/developerportal/deploy/two-factor-authentication/)
 * [Version Downgrade Protection](/developerportal/deploy/version-downgrade-prevention/)

content/en/docs/deployment/general/pad/_index.md

@@ -27,9 +27,9 @@ Portable App Distribution offers the following benefits:
 
 ## Licensing
 
-You can test Portable App Distribution on a [Free App](/developerportal/deploy/mendix-cloud-deploy/#free-app). For more information about Free Apps and their limitations, as well as licensing apps outside of the Mendix Cloud, see [Licensing Apps](/developerportal/deploy/licensing-apps/).
+You can test Portable App Distribution on a [Free App](/developerportal/deploy/mendix-cloud-deploy/#free-app). For more information about Free Apps and their limitations, as well as licensing apps outside of the Mendix Cloud, see [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).
 
-To license a Mendix app on the Portable App Distribution, add it to your configuration. For more information, see [Obtaining a Mendix License](/developerportal/deploy/licensing-apps/#get-license).
+To license a Mendix app on the Portable App Distribution, add it to your configuration. For more information, see [Obtaining a Mendix License](/developerportal/deploy/licensing-apps-outside-mxcloud/#get-license).
 
 ## Prerequisites
 

content/en/docs/deployment/general/salt.md

@@ -9,7 +9,7 @@ aliases:
 ---
 
 {{% alert color="info" %}}
-SALT-based licenses are issued only to selected customers. If you received an email explicitly referencing a SALT license and directing you to this page, follow this guide. Otherwise, refer to the [guide for non-SALT Mendix licenses](/developerportal/deploy/licensing-apps/).
+SALT-based licenses are issued only to selected customers. If you received an email explicitly referencing a SALT license and directing you to this page, follow this guide. Otherwise, refer to the [guide for non-SALT Mendix licenses](/developerportal/deploy/licensing-apps-outside-mxcloud/).
 {{% /alert %}}
 
 ## Introduction

content/en/docs/deployment/general/subscription-management/_index.md

@@ -110,4 +110,4 @@ To prevent any disruptions to your Mendix services and avoid data loss, follow t
 
 ## Read More
 
-* [Licensing Apps](/developerportal/deploy/licensing-apps/)
+* [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/)

content/en/docs/deployment/general/subscription-management/licensing-apps.md

@@ -1,10 +1,8 @@
 ---
 title: "Licensing Apps"
-url: /developerportal/deploy/licensing-apps/
+url: /developerportal/deploy/licensing-apps-outside-mxcloud/
 weight: 10
 description: "How to obtain and activate a Mendix license for apps on various clouds"
-aliases:
-    - /developerportal/deploy/licensing-apps-outside-mxcloud/
 #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps.
 #NB have left out AWS and Azure Marketplace offerings for now, pending further research.
 ---

content/en/docs/deployment/general/subscription-management/user-metering/_index.md

@@ -19,7 +19,7 @@ Mendix subscriptions include user-based pricing plans. With user-based pricing,
 * Single-App Internal User
 * External User
 
-For more information, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps/#user-types-and-definitions) section of *Licensing apps*.
+For more information, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps-outside-mxcloud/#user-types-and-definitions) section of *Licensing apps*.
 
 ### Key Features
 
@@ -97,4 +97,4 @@ These users are licensed under the Multi-App Internal User Subscription, and no
 
 ## Read More
 
-* [Licensing Apps](/developerportal/deploy/licensing-apps/)
+* [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/)

content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md

@@ -46,7 +46,7 @@ User identification strategies can vary across application portfolios, particula
 
 4. Integrating with existing application logic: If your current applications use varying `system.user.name` values or different provisioning methods, you can implement `UserCommons.namedUserIdentifier.value` without altering existing logic. Continue using your existing application logic for `system.user.name` if necessary, but additionally implement logic to populate `UserCommons.namedUserIdentifier.value` with your chosen consistent cross-app identifier (for example, email address or `oid` claim). This ensures the metering mechanism has a reliable, consistent identifier to use. If your applications are already consistently storing the same identifier for a multi-app user in `system.user.name`, you do not have to use the `UserCommons.namedUserIdentifier.value`.
 
-For more information on user types and definitions, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps/#user-types-and-definitions) section of *Licensing Apps*.
+For more information on user types and definitions, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps-outside-mxcloud/#user-types-and-definitions) section of *Licensing Apps*.
 
 ## User Classification
 

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

@@ -57,7 +57,7 @@ In a licensed node, you have everything you need to stage and deploy your app. Y
 
 To license an app, you must have a licensed cloud node available:
 
-If you have an existing contract that allows for more licensed nodes, use the [Request New App Node](https://newnode.mendix.com) app to request a new node from Mendix Support. For more information, see [Licensing Apps](/developerportal/deploy/licensing-apps/).
+If you have an existing contract that allows for more licensed nodes, use the [Request New App Node](https://newnode.mendix.com) app to request a new node from Mendix Support. For more information, see [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/).
 
 {{% alert color="info" %}}
 If your contract does not allow for more licensed nodes, contact your Customer Success Manager (CSM).