Update enterprise support guide URL (#4617)

* Add new URL

* New URL

docs/components/early-access/alpha/alpha-features.md

@@ -22,7 +22,7 @@ Limitations of alpha features and components include:
 - Not necessarily feature-complete.
 - Might lack full documentation.
 - No guaranteed updates to newer releases.
-- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://docs.camunda.org/enterprise/support/).
+- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://camunda.com/services/enterprise-support-guide/).
 - No maintenance service.
 - (SaaS) No availability targets.
 - Released outside the standard [release policy](/reference/release-policy.md).
@@ -43,7 +43,7 @@ Once features and components are released and considered stable, they become gen
 Stable features and components are:
 
 - Ready for production use for most users with minimal risk.
-- Supported by [L1 Priority-level support](https://docs.camunda.org/enterprise/support/#priority-level) for production use.
+- Supported by [L1 Priority-level support](https://camunda.com/services/enterprise-support-guide/) for production use.
 - Fully documented.
 
 A release or component is considered stable if it has passed all verification and test stages and can be released to production.

optimize/self-managed/optimize-deployment/migration-update/camunda-7/instructions.md

@@ -60,7 +60,7 @@ This approach requires you to manually execute the update script. You can perfor
 
 - Open up a terminal, change to the root directory of your **new** Optimize version and run the following command: `./upgrade/upgrade.sh` on Linux or `./upgrade/upgrade.bat` on Windows. For OpenSearch installations, please make sure to set the environment variable `CAMUNDA_OPTIMIZE_DATABASE=opensearch` before executing the update script.
 - During the execution the executable will output a warning to ask you to back-up your database data. Type `yes` to confirm that you have backed up the data.
-- Feel free to [file a support case](https://docs.camunda.org/enterprise/support/) if any errors occur during the migration process.
+- Feel free to [file a support case](https://camunda.com/services/enterprise-support-guide/) if any errors occur during the migration process.
 - To get more verbose information about the update, you can adjust the logging level as it is described in the [configuration documentation](./../../configuration/logging.md).
 
 #### 3.2 Automatic update execution (Optimize >3.2.0)

optimize_versioned_docs/version-3.10.0/self-managed/optimize-deployment/migration-update/instructions.md

@@ -71,7 +71,7 @@ This approach requires you to manually execute the update script. You can perfor
 
 - Open up a terminal, change to the root directory of your **new** Optimize version and run the following command: `./upgrade/upgrade.sh` on Linux or `update/update.bat` on Windows
 - During the execution the executable will output a warning to ask you to back-up your Elasticsearch data. Type `yes` to confirm that you have backed up the data.
-- Feel free to [file a support case](https://docs.camunda.org/enterprise/support/) if any errors occur during the migration process.
+- Feel free to [file a support case](https://camunda.com/services/enterprise-support-guide/) if any errors occur during the migration process.
 - To get more verbose information about the update, you can adjust the logging level as it is described in the [configuration documentation](./../configuration/logging.md).
 
 #### 3.2 Automatic update execution (Optimize >3.2.0)

optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/migration-update/instructions.md

@@ -71,7 +71,7 @@ This approach requires you to manually execute the update script. You can perfor
 
 - Open up a terminal, change to the root directory of your **new** Optimize version and run the following command: `./upgrade/upgrade.sh` on Linux or `update/update.bat` on Windows
 - During the execution the executable will output a warning to ask you to back-up your Elasticsearch data. Type `yes` to confirm that you have backed up the data.
-- Feel free to [file a support case](https://docs.camunda.org/enterprise/support/) if any errors occur during the migration process.
+- Feel free to [file a support case](https://camunda.com/services/enterprise-support-guide/) if any errors occur during the migration process.
 - To get more verbose information about the update, you can adjust the logging level as it is described in the [configuration documentation](./../configuration/logging.md).
 
 #### 3.2 Automatic update execution (Optimize >3.2.0)

optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/migration-update/instructions.md

@@ -71,7 +71,7 @@ This approach requires you to manually execute the update script. You can perfor
 
 - Open up a terminal, change to the root directory of your **new** Optimize version and run the following command: `./upgrade/upgrade.sh` on Linux or `update/update.bat` on Windows
 - During the execution the executable will output a warning to ask you to back-up your Elasticsearch data. Type `yes` to confirm that you have backed up the data.
-- Feel free to [file a support case](https://docs.camunda.org/enterprise/support/) if any errors occur during the migration process.
+- Feel free to [file a support case](https://camunda.com/services/enterprise-support-guide/) if any errors occur during the migration process.
 - To get more verbose information about the update, you can adjust the logging level as it is described in the [configuration documentation](./../configuration/logging.md).
 
 #### 3.2 Automatic update execution (Optimize >3.2.0)

optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/migration-update/instructions.md

@@ -71,7 +71,7 @@ This approach requires you to manually execute the update script. You can perfor
 
 - Open up a terminal, change to the root directory of your **new** Optimize version and run the following command: `./upgrade/upgrade.sh` on Linux or `update/update.bat` on Windows
 - During the execution the executable will output a warning to ask you to back-up your Elasticsearch data. Type `yes` to confirm that you have backed up the data.
-- Feel free to [file a support case](https://docs.camunda.org/enterprise/support/) if any errors occur during the migration process.
+- Feel free to [file a support case](https://camunda.com/services/enterprise-support-guide/) if any errors occur during the migration process.
 - To get more verbose information about the update, you can adjust the logging level as it is described in the [configuration documentation](./../configuration/logging.md).
 
 #### 3.2 Automatic update execution (Optimize >3.2.0)

optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/instructions.md

@@ -60,7 +60,7 @@ This approach requires you to manually execute the update script. You can perfor
 
 - Open up a terminal, change to the root directory of your **new** Optimize version and run the following command: `./upgrade/upgrade.sh` on Linux or `./upgrade/upgrade.bat` on Windows. For OpenSearch installations, please make sure to set the environment variable `CAMUNDA_OPTIMIZE_DATABASE=opensearch` before executing the update script.
 - During the execution the executable will output a warning to ask you to back-up your database data. Type `yes` to confirm that you have backed up the data.
-- Feel free to [file a support case](https://docs.camunda.org/enterprise/support/) if any errors occur during the migration process.
+- Feel free to [file a support case](https://camunda.com/services/enterprise-support-guide/) if any errors occur during the migration process.
 - To get more verbose information about the update, you can adjust the logging level as it is described in the [configuration documentation](./../../configuration/logging.md).
 
 #### 3.2 Automatic update execution (Optimize >3.2.0)

src/pages/contact.md

@@ -26,7 +26,7 @@ There are a few different channels you can reach us based on your needs:
 
 - For **security-related issues**, review our [security notices](../docs/reference/notices) for the most up-to-date information on known issues and steps to report a vulnerability so we can solve the problem as quickly as possible. Do not use GitHub for security-related issues.
 
-- **Feedback and support** can be submitted or requested via JIRA by following our [Enterprise support process](https://docs.camunda.org/enterprise/support/). All users can also find feedback and support options in the Help Center or [Camunda community forum](https://forum.camunda.io/).
+- **Feedback and support** can be submitted or requested via JIRA by following our [Enterprise support process](https://camunda.com/services/enterprise-support-guide/). All users can also find feedback and support options in the Help Center or [Camunda community forum](https://forum.camunda.io/).
 
 - For sales inquiries, information about Camunda 8 performance and benchmarking, or anything not listed above, use our [Contact Us](https://camunda.com/contact/) form.
 
@@ -43,4 +43,4 @@ Need assistance locating your Camunda 8 credentials? You can obtain these creden
 6. (Optional) Add more details, such as the priority level or authorized support contacts.
 7. Click **Create** at the bottom of the pop-up **Create Issue** box.
 
-After completing these steps, your request is generated. Find additional details on submitting a self-service help request [here](https://docs.camunda.org/enterprise/support/#self-service-help-request).
+After completing these steps, your request is generated. Find additional details on submitting a self-service help request [here](https://camunda.com/services/enterprise-support-guide/).

versioned_docs/version-8.2/reference/alpha-features.md

@@ -22,7 +22,7 @@ Limitations of alpha features and components include:
 - Not necessarily feature-complete.
 - Might lack full documentation.
 - No guaranteed updates to newer releases.
-- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://docs.camunda.org/enterprise/support/).
+- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://camunda.com/services/enterprise-support-guide/).
 - No maintenance service.
 - (SaaS) No availability targets.
 - Released outside the standard [release policy](/reference/release-policy.md).
@@ -43,7 +43,7 @@ Once features and components are released and considered stable, they become gen
 Stable features and components are:
 
 - Ready for production use for most users with minimal risk.
-- Supported by [L1 Priority-level support](https://docs.camunda.org/enterprise/support/#priority-level) for production use.
+- Supported by [L1 Priority-level support](https://camunda.com/services/enterprise-support-guide/) for production use.
 - Fully documented.
 
 A release or component is considered stable if it has passed all verification and test stages and can be released to production.

versioned_docs/version-8.3/reference/alpha-features.md

@@ -22,7 +22,7 @@ Limitations of alpha features and components include:
 - Not necessarily feature-complete.
 - Might lack full documentation.
 - No guaranteed updates to newer releases.
-- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://docs.camunda.org/enterprise/support/).
+- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://camunda.com/services/enterprise-support-guide/).
 - No maintenance service.
 - (SaaS) No availability targets.
 - Released outside the standard [release policy](release-policy.md).
@@ -43,7 +43,7 @@ Once features and components are released and considered stable, they become gen
 Stable features and components are:
 
 - Ready for production use for most users with minimal risk.
-- Supported by [L1 Priority-level support](https://docs.camunda.org/enterprise/support/#priority-level) for production use.
+- Supported by [L1 Priority-level support](https://camunda.com/services/enterprise-support-guide/) for production use.
 - Fully documented.
 
 A release or component is considered stable if it has passed all verification and test stages and can be released to production.

versioned_docs/version-8.4/reference/alpha-features.md

@@ -22,7 +22,7 @@ Limitations of alpha features and components include:
 - Not necessarily feature-complete.
 - Might lack full documentation.
 - No guaranteed updates to newer releases.
-- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://docs.camunda.org/enterprise/support/).
+- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://camunda.com/services/enterprise-support-guide/).
 - No maintenance service.
 - (SaaS) No availability targets.
 - Released outside the standard [release policy](release-policy.md).
@@ -43,7 +43,7 @@ Once features and components are released and considered stable, they become gen
 Stable features and components are:
 
 - Ready for production use for most users with minimal risk.
-- Supported by [L1 Priority-level support](https://docs.camunda.org/enterprise/support/#priority-level) for production use.
+- Supported by [L1 Priority-level support](https://camunda.com/services/enterprise-support-guide/) for production use.
 - Fully documented.
 
 A release or component is considered stable if it has passed all verification and test stages and can be released to production.

versioned_docs/version-8.5/reference/alpha-features.md

@@ -22,7 +22,7 @@ Limitations of alpha features and components include:
 - Not necessarily feature-complete.
 - Might lack full documentation.
 - No guaranteed updates to newer releases.
-- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://docs.camunda.org/enterprise/support/).
+- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://camunda.com/services/enterprise-support-guide/).
 - No maintenance service.
 - (SaaS) No availability targets.
 - Released outside the standard [release policy](release-policy.md).
@@ -43,7 +43,7 @@ Once features and components are released and considered stable, they become gen
 Stable features and components are:
 
 - Ready for production use for most users with minimal risk.
-- Supported by [L1 Priority-level support](https://docs.camunda.org/enterprise/support/#priority-level) for production use.
+- Supported by [L1 Priority-level support](https://camunda.com/services/enterprise-support-guide/) for production use.
 - Fully documented.
 
 A release or component is considered stable if it has passed all verification and test stages and can be released to production.

versioned_docs/version-8.6/reference/alpha-features.md

@@ -22,7 +22,7 @@ Limitations of alpha features and components include:
 - Not necessarily feature-complete.
 - Might lack full documentation.
 - No guaranteed updates to newer releases.
-- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://docs.camunda.org/enterprise/support/).
+- Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See [Camunda Enterprise Support Guide](https://camunda.com/services/enterprise-support-guide/).
 - No maintenance service.
 - (SaaS) No availability targets.
 - Released outside the standard [release policy](release-policy.md).
@@ -43,7 +43,7 @@ Once features and components are released and considered stable, they become gen
 Stable features and components are:
 
 - Ready for production use for most users with minimal risk.
-- Supported by [L1 Priority-level support](https://docs.camunda.org/enterprise/support/#priority-level) for production use.
+- Supported by [L1 Priority-level support](https://camunda.com/services/enterprise-support-guide/) for production use.
 - Fully documented.
 
 A release or component is considered stable if it has passed all verification and test stages and can be released to production.