diff --git a/tidb-cloud/scale-tidb-cluster.md b/tidb-cloud/scale-tidb-cluster.md
index 9143756307b72..0dd4f29ac2e05 100644
--- a/tidb-cloud/scale-tidb-cluster.md
+++ b/tidb-cloud/scale-tidb-cluster.md
@@ -55,9 +55,6 @@ You can increase or decrease vCPU and RAM of TiDB, TiKV, or TiFlash nodes.
 
 > **Note:**
 >
-> - Changing vCPU and RAM is only available to the following clusters:
->     - Hosted on AWS and created after 2022/12/31.
->     - Hosted on Google Cloud and created after 2023/04/26.
 > - AWS has a cooldown period of vCPU and RAM changes. If your TiDB cluster is hosted on AWS, after changing the storage or vCPU and RAM of TiKV or TiFlash, you must wait at least six hours before you can change it again.
 
 To change the vCPU and RAM of TiDB, TiKV, or TiFlash nodes, take the following steps:
@@ -81,8 +78,8 @@ You can increase the storage of TiKV or TiFlash.
 
 > **Warning:**
 >
-> - For a running cluster, AWS and Google Cloud do not allow in-place storage capacity downgrade.
-> - AWS has a cooldown period of storage changes. If your TiDB cluster is hosted on AWS, after changing the storage or vCPU and RAM of TiKV or TiFlash, you must wait at least six hours before you can change it again.
+> - For a running cluster, TiDB Cloud do not allow in-place storage capacity downgrade.
+> - AWS and Azure has a cooldown period of storage changes. If your TiDB cluster is hosted on AWS or Azure, after changing the storage or vCPU and RAM of TiKV or TiFlash, you must wait at least six hours before you can change it again.
 
 To change the storage of TiKV or TiFlash, take the following steps: