- Countries that can transact SUSE Rancher Support through the AWS Marketplace
-
-
Australia, AU
- Austria, AT
- Bangladesh, BD
- Belgium, BE
- Bulgaria, BG
- Cameroon, CM
- Canada, CA
- Chile, CL
- Croatia, HR
- Cyprus, CY
- Czech Republic, CZ
- Denmark, DK
- Egypt, EG
- Estonia, EE
- Finland, FI
- France, FR
- Germany, DE
- Greece, GR
- Hungary, HU
- Iceland, IS
- India, IN
- Indonesia, ID
- Ireland, IE
- Isle of Man, IM
- Italy, IT
- Kenya, KE
- Kingdom of Saudi Arabia, SA
- Korea, Republic of, KR
- Latvia, LV
- Lithuania, LT
- Liechtenstein, LI
- Luxembourg, LU
- Malaysia, MY
- Malta, MT
- Netherlands, NL
- New Zealand, NZ
- Norway, NO
- Poland, PL
- Portugal, PT
- Romania, RO
- Russian Federation, RU
- Singapore, SG
- Slovakia, SK
- Slovenia, SI
- South Africa, ZA
- Spain, ES
- Sweden, SE
- Switzerland, CH
- Taiwan, Province of China, TW
- Turkey, TR
- United Kingdom, GB
- United States, US
-
-
-
-
- Countries that cannot transact SUSE Rancher Support via the AWS Marketplace
-
-
Afghanistan, AF
- Åland Islands, AX
- Albania, AL
- Algeria, DZ
- American Samoa, AS
- Andorra, AD
- Angola, AO
- Anguilla, AI
- Antarctica, AQ
- Antigua and Barbuda, AG
- Argentina, AR
- Armenia, AM
- Aruba, AW
- Azerbaijan, AZ
- Bahamas, BS
- Bahrain, BH
- Barbados, BB
- Belarus, BY
- Belize, BZ
- Benin, BJ
- Bermuda, BM
- Bhutan, BT
- Bonaire, BQ
- Bolivarian Republic of Venezuela, VE
- Bosnia and Herzegovina, BA
- Botswana, BW
- Bouvet Island, BV
- Brazil, BR
- British Indian Ocean Territory, IO
- Brunei Darussalam, BN
- Burkina Faso, BF
- Burundi, BI
- Cambodia, KH
- Cape Verde, CV
- Cayman Islands, KY
- Central African Republic, CF
- Chad, TD
- China, CN
- Christmas Island, CX
- Cocos (Keeling) Islands, CC
- Colombia, CO
- Comoros, KM
- Congo, CG
- Cook Islands, CK
- Costa Rica, CR
- Côte d'Ivoire, CI
- Curaçao, CW
- Democratic Republic of the Congo, CD
- Djibouti, DJ
- Dominica, DM
- Dominican Republic, DO
- Ecuador, EC
- El Salvador, SV
- Equatorial Guinea, GQ
- Eritrea, ER
- Ethiopia, ET
- Falkland Islands (Malvinas), FK
- Faroe Islands, FO
- Federated States of Micronesia, FM
- Fiji, FJ
- Former Yugoslav Republic of Macedonia, MK
- French Guiana, GF
- French Polynesia, PF
- French Southern Territories, TF
- Gabon, GA
- Gambia, GM
- Georgia, GE
- Ghana, GH
- Gibraltar, GI
- Greenland, GL
- Grenada, GD
- Guadeloupe, GP
- Guam, GU
- Guatemala, GT
- Guernsey, GG
- Guinea, GN
- Guinea-Bissau, GW
- Guyana, GY
- Haiti, HT
- Heard Island and McDonald Islands, HM
- Holy See (Vatican City State), VA
- Honduras, HN
- Hong Kong, HK
- Iraq, IQ
- Israel, IL
- Jamaica, JM
- Japan, JP
- Jersey, JE
- Jordan, JO
- Kazakhstan, KZ
- Kiribati, KI
- Kuwait, KW
- Kyrgyzstan, KG
- Lao People's Democratic Republic, LA
- Lebanon, LB
- Lesotho, LS
- Liberia, LR
- Libyan Arab Jamahiriya, LY
- Macao, MO
- Madagascar, MG
- Malawi, MW
- Maldives, MV
- Mali, ML
- Marshall Islands, MH
- Martinique, MQ
- Mauritania, MR
- Mauritius, MU
- Mayotte, YT
- Mexico, MX
- Mongolia, MN
- Montenegro, ME
- Montserrat, MS
- Morocco, MA
- Mozambique, MZ
- Myanmar, MM
- Namibia, NA
- Nauru, NR
- Nepal, NP
- New Caledonia, NC
- Nicaragua, NI
- Niger, NE
- Nigeria, NG
- Niue, NU
- Norfolk Island, NF
- Northern Mariana Islands, MP
- Oman, OM
- Pakistan, PK
- Palau, PW
- Occupied Palestinian Territory, PS
- Panama, PA
- Papua New Guinea, PG
- Paraguay, PY
- Peru, PE
- Philippines, PH
- Pitcairn, PN
- Plurinational State of Bolivia, BO
- Puerto Rico, PR
- Qatar, QA
- Republic of Moldova, MD
- Réunion, RE
- Rwanda, RW
- Saint Barthélemy, BL
- Saint Helena, Ascension and Tristan da Cunha, SH
- Saint Kitts and Nevis, KN
- Saint Lucia, LC
- Saint Martin, MF
- Saint Pierre and Miquelon, PM
- Saint Vincent and the Grenadines, VC
- Samoa, WS
- San Marino, SM
- Sao Tome and Principe, ST
- Senegal, SN
- Serbia, RS
- Seychelles, SC
- Sierra Leone, SL
- Sint Maarten, SX
- Solomon Islands, SB
- Somalia, SO
- South Georgia and the South Sandwich Islands, GS
- South Sudan, SS
- Sri Lanka, LK
- Suriname, SR
- Svalbard and Jan Mayen, SJ
- Swaziland, SZ
- Tajikistan, TJ
- Thailand, TH
- Timor-Leste, TL
- Togo, TG
- Tokelau, TK
- Tonga, TO
- Trinidad and Tobago, TT
- Tunisia, TN
- Turkmenistan, TM
- Turks and Caicos Islands, TC
- Tuvalu, TV
- Uganda, UG
- Ukraine, UA
- United Arab Emirates, AE
- United Republic of Tanzania, TZ
- United States Minor Outlying Islands, UM
- Uruguay, UY
- Uzbekistan, UZ
- Vanuatu, VU
- Viet Nam, VN
- Virgin Islands, British, VG
- Virgin Islands, U.S., VI
- Wallis and Futuna, WF
- Western Sahara, EH
- Yemen, YE
- Zambia, ZM
- Zimbabwe, ZW
-
-
-
-#### My AWS account is in the USA, but I want to deploy Rancher in another AWS region, a region that is in a country where I currently cannot transact Rancher Prime. Is this possible?
-
-Yes. As long as your AWS account is billed to one of the allowed countries, it is possible to deploy Rancher in any AWS regions.
-
-#### Is this listing available in China?
-
-While it is not possible to transact/bill Rancher Prime in China, it is possible to deploy into AWS regions in China.
-
-#### Can I still deploy Rancher using the "Rancher Setup" listing from the AWS Marketplace?
-
-"Rancher Setup" is no longer available via AWS Marketplace. Customers should deploy an EKS Cluster to host Rancher. Follow the steps in this [guide](../../../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md) except for the Rancher installation. The Rancher product installation should be carried out as per [installing the Rancher Prime PAYG offering on Amazon's AWS Marketplace](installing-rancher-prime.md).
-
-### Billing
-
-#### I have an existing Rancher Prime subscription. Can I use this on AWS?
-
-BYOS (Bring Your Own Subscription) Rancher deployments are supported on AWS; however, billing will not be via the AWS Marketplace. Once the existing subscription term ends, you can purchase Rancher Prime via the AWS Marketplace and reconfigure your cluster to support monthly billing via AWS.
-
-#### I have an existing Rancher Subscription purchased via the ’Rancher Premium Support’ listing on AWS. Isthis transferable to the new model?
-
-No. A new deployment of Rancher Prime is required to benefit from the new monthly billing model.
-
-#### I have an existing deployment covered by a Rancher subscription; can I use this new listing in AWS for new deployments?
-
-Yes. the listing works independently from your existing subscriptions. Please remember that support processes may be different for deployments using your existing subscription and those billed via the AWS Marketplace.
-
-#### Tell me more about how the billing for Rancher Prime works via AWS?
-
-When purchasing Rancher Prime via the AWS Marketplace, the billing is as follows:
-
-- Billing is monthly and handled via AWS Marketplace.
-- Managed nodes are counted hourly when Rancher is active and added to a usage
-total.
-- An average node count is calculated for the month.
-- There is a monthly usage charge for each node in the average node count.
-- The monthly usage charge depends on the number of nodes in use.
-- There is a 5-node minimum; if the average node count is less than 5 nodes, the
-charge will be for 5 nodes.
-
-#### What are the pricing tiers?
-
-Rancher Prime has different pricing tiers when purchasing via the AWS Marketplace. This is based on the number of nodes which Rancher is managing. Details of the tiers are below. Please check the listing for further pricing information.
-
-| Tier | Nodes (from) | Nodes (to) |
-| :------: | :----------: | :---------: |
-| **1** | 5 | 15 |
-| **2** | 16 | 50 |
-| **3** | 51 | 100 |
-| **4** | 101 | 250 |
-| **5** | 251 | 1000 |
-| **6** | 1001 | |
-
-#### Is there a way to try Rancher before purchasing?
-
-If using the Rancher Prime listing in the AWS Marketplace, billing will commence from the time of deployment.
-
-Rancher can be deployed manually using the standard documentation and repositories. When ready to benefit from a supported platform and have this billed via the AWS Marketplace, follow the available [documentation](../../../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) to deploy Rancher Prime from the AWS Marketplace and migrate.
-
-#### How does SUSE calculate the ‘average number of managed nodes’ to bill for?
-
-The average node count is calculated by adding the number of managed nodes (counted hourly) and dividing by the number of hours Rancher has been active in the billing cycle.
-
-Below are three examples of how the average node count is calculated. Check the table below for the details.
-
-:::note
-
-In our example month, we are using 730 hours; this may differ depending on the number of days in the month and the billing cycle.
-
-:::
-
-- **Static usage:** Using Rancher to manage 10 nodes, for 1 month (730 hours) with no additional nodes added in the month.
-- **Bursting Model:** Using Rancher to manage 10 nodes for 3 weeks (562 hours) in the month, bursting to 30 nodes for 1 week (168 hours).
-- **Transient cluster:** A temporary deployment of Rancher on 20 nodes for 2 weeks (336 hours).
-
-| | Hours Active (Hours Rancher is active in the month) | Nodes (Managed Nodes counted at each check-in) | Usage total (Sum of nodes reported at each check-in) | Average Node Count (Usage total / hours active) | Note |
-| ----------------- | :--: | :------------------------: | :----: | :--: | :------------------------------: |
-| **Static Usage** | 730 | 10 | 7300 | 10 | 10 @ Tier 1 |
-| **Bursting Model** | 730 | 10 (562 hrs), 30 (168 hrs) | 10660 | 15 | 15 @ Tier 1 (rounded from 14.6) |
-| **Transient Cluster** | 336 | 20 | 6720 | 20 | 20 @ Tier 2 |
-
-#### Are special commercial terms available?
-
-Depending on the deployment, securing special commercial terms (e.g., an annual subscription) may be possible. This will be handled via an AWS Private offer. Please contact SUSE for more information.
-
-#### Can my spend on Rancher Prime count towards my AWS Enterprise Discount Program?
-
-Yes. Please contact your AWS Sales Team for more details.
-
-#### How do I purchase Rancher for additional nodes?
-
-Once Rancher has been deployed from the listing on AWS and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes Rancher is managing. Just deploy or onboard additional clusters to Rancher as needed.
-
-#### Is this an annual commitment, will it auto-renew?
-
-By default, the Rancher Prime listing in AWS is billed on a monthly cycle, based on usage. Billing is ongoing for as long as Rancher is deployed.
-
-It is possible to set up an annual commitment via an AWS Private Offer; these will need to be reviewed and renewed at the end of the term, or the deployment will drop back to the default monthly billing cycle.
-
-### Technical (Billing)
-
-#### Do I need a Kubernetes cluster running in AWS to install Rancher and be billed via the AWS Marketplace?
-
-Yes. To benefit from monthly billing via the Marketplace, the primary Rancher cluster must be an EKS Cluster running in your AWS Account.
-
-#### Which Kubernetes distributions can the AWS Marketplace listing be deployed on?
-
-The AWS Marketplace listing for Rancher Prime with Marketplace billing must be deployed on Amazon EKS. Downstream clusters / managed worker nodes can run on any CNCF compliant Kubernetes platform, EKS, EKS-A, Rancher Kubernetes Engine, etc.
-
-#### What is the deployment mechanism?
-
-The AWS Marketplace listing for Rancher Prime is deployed using Helm.
-
-#### What is the easiest way to get started?
-
-One of the easiest ways to get started is to deploy the AWS Marketplace listing for Rancher Prime to an existing EKS cluster. Follow the instructions in the usage section, a Helm chart takes care of the installation and the setup for billing.
-
-#### What is the minimum version of Rancher required to support AWS Marketplace billing?
-
-The minimum version supporting marketplace billing is Rancher 2.7.9.
-
-#### What version of Rancher is installed when using the Marketplace listing?
-
-The AWS Marketplace listing for Rancher Prime is tied to a specific version of Rancher, typically the latest version available at the time of the listing update. Please check the listing for further information.
-
-#### I need a prior version of Rancher, can I still use the listing?
-
-No. There is no choice over the Rancher version when deploying using the AWS Marketplace listing. If a prior version of Rancher is required, this must be installed manually using the standard documentation.
-
-:::note
-
-Billing through AWS Marketplace may not be supported with previous versions.
-
-:::
-
-#### How often is the listing updated (including the version of Rancher, etc.)?
-
-The marketplace listing is tied to a specific version of Rancher, usually the latest version available at the time of listing. Typically, these are updated quarterly, or more frequently if there are security issues.
-
-#### I have many Kubernetes clusters across multiple AWS accounts, does the Rancher Prime billing still work and enable tiered pricing?
-
-Yes. Downstream clusters managed by Rancher can be deployed across single or multiple AWS accounts, on-premises, or even in other public clouds. Downstream nodes will report up to the primary Rancher deployment. Tiered pricing is enabled and billing will be routed to the AWS account in which the primary cluster is running.
-
-#### I have multiple independent clusters, each running a separate installation of the AWS Marketplace listing for Rancher Prime. How is this billed?
-
-As the Rancher Prime deployments are independent, each deployment is billed separately from the others. It is not possible to benefit from tiered pricing.
-
-#### If managing multiple independent Rancher clusters, consider custom terms from SUSE. How can I benefit from tiered pricing across all Rancher deployments?
-
-The primary Rancher cluster must be running on EKS in the AWS Cloud and running the AWS Marketplace listing for Rancher. To benefit from tiered pricing, managed clusters (downstream clusters) should be connected to the primary Rancher cluster.
-
-#### I have purchased multiple SUSE products from the AWS Marketplace (e.g., SUSE Manager, NeuVector Prime and now Rancher Prime). Does the AWS Marketplace billing method still work?
-
-Yes. The billing mechanism of each deployment is independent, each product will be billed separately via the AWS Marketplace.
-
-#### I already have an existing EKS cluster in place and want to add Rancher and have this billed via Marketplace. Is this possible?
-
-Yes. Simply deploy the AWS Marketplace listing for Rancher Prime.
-
-#### I already have an existing cluster, with Rancher deployed. Can I just install the marketplace version and have support billed via the AWS Marketplace?
-
-In order to benefit from monthly billing via the AWS Marketplace, the primary Rancher cluster needs to be deployed from the listing, it is then possible to migrate the existing Rancher configuration to the new deployment.
-
-Please follow the [documentation](../../../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) and be sure to back up the existing Rancher configuration.
-
-### Technical (Product)
-
-#### How do I get support?
-
-It is very simple to [open a support case](https://scc.suse.com/cloudsupport) with SUSE for Rancher Prime. Create a ‘supportconfig’ via the Rancher UI and upload the output to the SUSE Customer Center. The support config bundle can be exported from the Rancher console using the ‘Get Support’ button at the bottom of the page. For deployments when Rancher is managing multiple downstream clusters, export the support config bundle from the primary cluster only.
-
-If the billing mechanism on the primary cluster is active, a support case will be opened. Further details can be found in the [documentation](../supportconfig.md).
-
-#### What are the resource requirements for installing Rancher on EKS?
-
-Please check the documentation for best practices.
-
-#### Is there any difference between Rancher Prime from the AWS Marketplace and the versions I can run in my own data center?
-
-Rancher Prime available in the AWS Marketplace is the same product, with the same functionality that you would run on-premises or with a manual installation. The only difference between deploying manually and deploying via the AWS Marketplace listing is the billing route.
-
-#### Does the primary cluster (responsible for billing) need to run 24/7?
-
-To ensure continuity with support, it is recommended that the primary Rancher cluster always remains active.
-
-#### What if the primary cluster responsible for billing is unable to connect to the AWS Billing framework?
-
-There may be multiple reasons why the primary cluster is unable to connect to the AWS framework, but it is the customer’s responsibility to ensure that the primary cluster is active and connected. Whilst the cluster is not connected to the billing framework, it is not possible to raise a support request.
-
-#### My primary cluster has been offline. What will happen with billing when reconnected?
-
-If the primary cluster is offline or disconnected from the AWS billing framework for a period of time, when it reconnects, the stored usage data will be uploaded to AWS and will appear on your next AWS bill.
-
-Depending on when in the month the primary cluster gets reconnected you may have several months of usage on your next billing cycle.
-
-#### Can the managed worker nodes reside on premises, at the edge or even on another cloud provider?
-
-Yes. Nodes can run anywhere. SUSE Rancher will count the total number of nodes managed regardless of where they are deployed.
-
-#### How do I get fixes and updates for Rancher?
-
-To update to the latest version of the Rancher Prime PAYG offering supported in the marketplace listing, please see [upgrading Rancher Prime PAYG cluster in AWS](upgrading-rancher-payg-cluster.md).
+2. [Install the Rancher Prime PAYG offering on the AWS Marketplace](installing-rancher-prime.md).
\ No newline at end of file
diff --git a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/azure-marketplace-payg-integration.md b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/azure-marketplace-payg-integration.md
index 33c6cb21924..326cf40e2c3 100644
--- a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/azure-marketplace-payg-integration.md
+++ b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/azure-marketplace-payg-integration.md
@@ -21,215 +21,3 @@ Rancher Prime integrates with the [Azure Marketplace](https://azuremarketplace.m
1. Complete the [prerequisite steps](prerequisites.md).
2. [Install the Rancher Prime PAYG offering on the Azure Marketplace](installing-rancher-prime.md).
-
-## FAQ
-
-The following is a list of frequently asked questions.
-
-### Marketplace Listing
-
-#### What is the Rancher Prime listing on the Azure Marketplace?
-
-By selecting the Rancher Prime listing in the Azure Marketplace, customers can deploy Rancher to their Microsoft Azure Kubernetes Service (AKS) cluster environment to manage any downstream CNCF-certified Kubernetes distribution with the advantage of having monthly billing for Rancher Prime via Microsoft Azure.
-
-**Where do I find the Rancher Prime listings?**
-
-There are two listings in the Azure Marketplace. They are:
-
-- [Rancher Prime with 24x7 Support](https://portal.azure.com/#view/Microsoft_Azure_Marketplace/GalleryItemDetailsBladeNopdl/id/suse.rancher-prime-llc/selectionMode~/false/resourceGroupId//resourceGroupLocation//dontDiscardJourney~/false/selectedMenuId/home/launchingContext~/%7B%22galleryItemId%22%3A%22suse.rancher-prime-llcpay-as-you-go%22%2C%22source%22%3A%5B%22GalleryFeaturedMenuItemPart%22%2C%22VirtualizedTileDetails%22%5D%2C%22menuItemId%22%3A%22home%22%2C%22subMenuItemId%22%3A%22Search%20results%22%2C%22telemetryId%22%3A%221dafcf16-920e-46ea-80c9-dc85c6bd3a17%22%7D/searchTelemetryId/c2300fb7-ba7b-462a-ba57-a37cb5e2822d)
-- [Rancher Prime with 24x7 Support (EMEA Orders Only)](https://portal.azure.com/#view/Microsoft_Azure_Marketplace/GalleryItemDetailsBladeNopdl/id/suseirelandltd1692213356027.rancher-prime-ltd/selectionMode~/false/resourceGroupId//resourceGroupLocation//dontDiscardJourney~/false/selectedMenuId/home/launchingContext~/%7B%22galleryItemId%22%3A%22suseirelandltd1692213356027.rancher-prime-ltdpay-as-you-go%22%2C%22source%22%3A%5B%22GalleryFeaturedMenuItemPart%22%2C%22VirtualizedTileDetails%22%5D%2C%22menuItemId%22%3A%22home%22%2C%22subMenuItemId%22%3A%22Search%20results%22%2C%22telemetryId%22%3A%22c6b1d79a-b577-47b0-90e5-41e6c49688ab%22%7D/searchTelemetryId/1793144d-e0d9-466e-8e36-dfeddc73163b)
-
-#### Why are there two listings? Which one should I use?
-
-There are two listings for Rancher Prime to accommodate Microsoft Azure billing regions. You should pick the listing that reflects where your Azure account gets billed.
-
-#### Are these listings available in all countries?
-
-No. Due to billing limitations and other restrictions, the Rancher Prime Azure Marketplace listing may not be purchasable in all countries. The Azure account you use for deployment determines your billing country. Contact your Azure Sales Team for more details.
-
-#### My Azure account is in the USA, but I want to deploy Rancher in another Azure region, a region that is in a country where I currently cannot transact Rancher Prime. Is this possible?
-
-Yes. As long as your Azure account is billed to one of the allowed countries, it is possible to deploy Rancher Prime in any Azure region.
-
-#### Is this listing available in China?
-
-While it is not possible to transact/bill Rancher Prime in China, it is possible to deploy into Azure regions in China.
-
-### Billing
-
-#### I have an existing Rancher Prime subscription; can I use this on Azure?
-
-Self-installed BYOS (Bring Your Own Subscription) Rancher Prime deployments are supported on Azure; however, billing will not be via the Azure Marketplace. Once the existing subscription term ends, you can purchase Rancher Prime via the Azure Marketplace and reconfigure your cluster to support monthly billing via Azure.
-
-#### I have an existing deployment covered by a Rancher subscription; can I use this new listing in the Azure Marketplace for new deployments?
-
-Yes. the listing works independently from your existing Rancher Prime subscriptions. Only deployments through the marketplace listing will be billed through Azure. Support is always direct from SUSE.
-
-#### Tell me more about how the billing for Rancher Prime works via Azure?
-
-When purchasing Rancher Prime via the Azure Marketplace, the billing is as follows:
-
-- Billing is monthly and handled via Azure.
-- Managed nodes are counted hourly when Rancher is active and added to a usage total.
-- An average node count is calculated for the month.
-- There is a monthly usage charge for each node in the average node count.
-- The monthly usage charge depends on the number of nodes in use.
-- There is a 5-node minimum; if the average node count is less than 5 nodes, the charge will be for 5 nodes.
-
-#### What are the pricing tiers?
-
-Rancher Prime has different pricing tiers when purchasing via the Azure Marketplace. This is based on the number of nodes that Rancher is managing. Details of the tiers are shown below. Please check the listing for further pricing information.
-
-| Tier | Nodes (from) | Nodes (to) |
-| :------: | :----------: | :---------: |
-| **1** | 5 | 15 |
-| **2** | 16 | 50 |
-| **3** | 51 | 100 |
-| **4** | 101 | 250 |
-| **5** | 251 | 1000 |
-| **6** | 1001 | |
-
-#### Is there a way to try Rancher before purchasing?
-
-If using the Rancher Prime listing in the Azure Marketplace, billing will commence from the time of deployment. You can try Rancher by deploying it per standard documentation. When ready to benefit from a supported platform and have this billed through Azure, deploy Rancher Prime via the Azure Marketplace and migrate your configuration.
-
-#### How does SUSE calculate the ‘average number of managed nodes’ to bill for?
-
-The average node count is calculated by adding the number of managed nodes (counted hourly) and dividing by the number of hours Rancher has been active in the billing cycle. Three examples are shown in the table below.
-
-:::note
-
-In our example month, we are using 730 hours; this may differ depending on the number of days in the month and the billing cycle.
-
-:::
-
-- **Static Usage:**
-Using Rancher to manage 10 nodes for 1 month (730 hours) with no additional nodes added in the month.
-- **Bursting Model:**
-Using Rancher to manage 10 nodes for 3 weeks (562 hours) in the month and bursting to 30 nodes for 1 week (168 hours).
-- **Transient Cluster:**
-A temporary deployment of Rancher on 20 nodes for 2 weeks (336 hours).
-
-| | Hours Active (Hours Rancher is active in the month) | Nodes (Managed Nodes counted at each check-in) | Usage total (Sum of nodes reported at each check-in) | Average Node Count (Usage total / hours active) | Note |
-| ----------------- | :--: | :------------------------: | :----: | :--: | :------------------------------: |
-| **Static Usage** | 730 | 10 | 7300 | 10 | 10 @ Tier 1 |
-| **Bursting Model** | 730 | 10 (562 hrs), 30 (168 hrs) | 10660 | 15 | 15 @ Tier 1 (rounded from 14.6) |
-| **Transient Cluster** | 336 | 20 | 6720 | 20 | 20 @ Tier 2 |
-
-#### Are special commercial terms available?
-
-Depending on the deployment, securing special commercial terms (e.g., an annual subscription) may be possible. This will be handled via an Azure private offer. Please contact SUSE for more information.
-
-#### Can my spend on Rancher Prime count towards my MACC Program?
-
-Yes. Contact your Azure Sales Team for more details.
-
-#### How do I purchase Rancher for additional nodes?
-
-Once Rancher Prime has been deployed from the Azure Marketplace and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes Rancher is managing. Just deploy or onboard additional clusters to Rancher as needed.
-
-#### Is this an annual commitment, will it auto-renew?
-
-By default, the Rancher Prime listing is billed on a monthly cycle, based on usage. Billing is ongoing for as long as Rancher Prime is deployed.
-
-It is possible to set up an annual commitment via an Azure Private Offer; these will need to be reviewed and renewed at the end of the term, or the deployment will drop back to the default monthly billing cycle.
-
-### Technical
-
-#### Do I need a Kubernetes cluster running in Azure to install Rancher and be billed via the Azure Marketplace?
-
-Yes. To benefit from monthly billing via Azure, the primary Rancher cluster must be an Azure Kubernetes Service (AKS) cluster running in your Azure account.
-
-#### Which Kubernetes distributions can the Rancher Prime Azure Marketplace listing be deployed on?
-
-The Rancher Prime marketplace listing must be deployed on Azure Kubernetes Service (AKS). Downstream/managed clusters can run any supported Kubernetes platform: RKE, RKE2, EKS, GKE, vanilla Kubernetes, OpenShift, Mirantis Kubernetes Engine, etc. See Supported Platforms for more details.
-
-#### What is the deployment mechanism?
-
-The Rancher Prime marketplace listing is deployed using Azure’s CNAB (with Helm inside).
-
-#### What is the easiest way to get started?
-
-One of the easiest ways to get started is to deploy the Rancher Prime marketplace listing to an existing AKS cluster. Follow the instructions in the usage section of the listing. A Helm chart takes care of installation and billing setup.
-
-#### What is the minimum version of Rancher required to support Azure Marketplace billing?
-
-The minimum version supporting marketplace billing is Rancher 2.7.9.
-
-#### What version of Rancher is installed when using the marketplace listing?
-
-The Rancher Prime marketplace listing is tied to a specific version of Rancher, typically the latest version available at the time of the listing update. Check the listing for further information.
-
-#### I need a prior version of Rancher; can I still use the listing?
-
-No. There is no choice over the Rancher version when deploying using the Azure Marketplace listing. If a prior version of Rancher is required, this must be installed manually using the standard documentation.
-
-:::note
-
-Billing through the Azure Marketplace may not be supported with earlier versions.
-
-:::
-
-#### How often is the listing updated (including the version of Rancher, etc.)?
-
-The marketplace listing is tied to a specific version of Rancher, usually it is the latest version available at the time the listing was last updated. Typically, the marketplace listing is updated quarterly, or more frequently to address any new security issues.
-
-#### I have many Kubernetes clusters across multiple Azure accounts; does the Rancher Prime billing still work and enable tiered pricing?
-
-Yes. Downstream/managed clusters can be deployed across single or multiple Azure accounts, on-premises, and in other public clouds. Downstream/managed nodes report up to Rancher Prime, enabling tiered pricing with billing routed to the Azure account in which the managing Rancher Prime cluster is running.
-
-#### I have multiple independent clusters, each running a separate installation of the Rancher Prime Azure Marketplace listing. How is this billed?
-
-As the Rancher Prime deployments are independent, each deployment is billed separately from the others. It is not possible to benefit from tiered pricing. If managing multiple independent Rancher Prime clusters, consider custom terms from SUSE.
-
-#### How can I benefit from tiered pricing across all Rancher deployments?
-
-The primary Rancher Prime cluster must be running on AKS in Microsoft Azure, deployed through the marketplace listing. To benefit from tiered pricing, downstream/managed clusters should be imported into the primary Rancher Prime cluster.
-
-#### I have purchased multiple SUSE products from the Azure Marketplace (e.g., SUSE Manager, NeuVector Prime, Rancher Prime). Does the Azure Marketplace billing method still work?
-
-Yes. The billing mechanisms for the deployments are independent and are billed separately via the Azure Marketplace.
-
-#### I already have an existing AKS cluster in place and want to add Rancher Prime to it and be billed through the Azure Marketplace. Is this possible?
-
-Yes. Simply deploy the Rancher Prime to the cluster with the Azure Marketplace listing.
-
-#### I already deployed Rancher to an existing AKS cluster. Can I just install the marketplace version to enable Azure Marketplace billing?
-
-No. You need to deploy Rancher Prime with the Azure Marketplace listing and migrate the existing Rancher configuration to this new deployment. Be sure that you back up your existing Rancher configuration.
-
-### Technical (Product)
-
-#### How do I get support?
-
-It is very simple to [open a support case](https://scc.suse.com/cloudsupport) with SUSE for Rancher Prime. Create a ‘supportconfig’ via the Rancher UI (click Get Support under the hamburger menu and follow instructions), then upload the ‘supportconfig’ output to the SUSE Customer Center. If the billing mechanism is active, a support case will be opened. See Supportconfig bundle in the Rancher [documentation](../supportconfig.md) for more details.
-
-:::note
-
-For deployments where Rancher Prime is managing multiple downstream clusters, be sure to export the ‘supportconfig’ bundle from the primary cluster only.
-
-:::
-
-#### What are the resource requirements for installing Rancher on AKS?
-
-Check the documentation for [best practices](../../../getting-started/installation-and-upgrade/installation-requirements/installation-requirements.md#hosted-kubernetes).
-
-#### Is there any difference between Rancher Prime from Azure Marketplace and the versions I can run in my own data center?
-
-Rancher Prime available in the Azure Marketplace is the same product, with the same functionality that you would install manually in the cloud or on-premises. The only difference between deploying manually and deploying via the marketplace listing is the billing route.
-
-#### Does the primary cluster (responsible for billing) need to run 24/7?
-
-To ensure continuity of support, it is recommended that the primary Rancher Prime cluster always remain active.
-
-#### What if the primary cluster responsible for billing is unable to connect to the Azure billing framework?
-
-There may be multiple reasons why the primary cluster is unable to connect to the Azure billing framework, but it is the customer’s responsibility to ensure that the primary cluster is active and connected. While the cluster is not connected to the billing framework, it is not possible to raise a support request.
-
-#### My primary cluster has been offline. What will happen with billing when reconnected?
-
-If the Racher Prime cluster is offline or disconnected from the Azure billing framework for a period of time, when it reconnects, the stored usage data will be uploaded to Azure and will appear on your next Azure bill. Depending on the month when the primary cluster gets reconnected you may have several months of usage on your next billing cycle.
-
-#### How do I get fixes and updates for Rancher?
-
-To update to the latest version of the Rancher Prime PAYG offering supported in the marketplace listing, please see [upgrading Rancher Prime PAYG cluster in Azure](upgrading-rancher-payg-cluster.md).