timescale · atovpeko · Oct 1, 2025 · Oct 2, 2025 · Oct 2, 2025 · Oct 5, 2025
diff --git a/_partials/_not-supported-for-azure.md b/_partials/_not-supported-for-azure.md
@@ -0,0 +1 @@
+This feature is on our roadmap for $CLOUD_LONG on Microsoft Azure. Stay tuned! 
diff --git a/integrations/aws.md b/integrations/aws.md
@@ -8,9 +8,14 @@ keywords: [AWS, integrations]
 
 import IntegrationPrereqsCloud from "versionContent/_partials/_integration-prereqs-cloud-only.mdx";
 import TransitGateway from "versionContent/_partials/_transit-gateway.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Integrate Amazon Web Services with $CLOUD_LONG
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 [Amazon Web Services (AWS)][aws] is a comprehensive cloud computing platform that provides on-demand infrastructure, storage, databases, AI, analytics, and security services to help businesses build, deploy, and scale applications in the cloud.
 
 This page explains how to integrate your AWS infrastructure with $CLOUD_LONG using [AWS Transit Gateway][aws-transit-gateway].
@@ -33,6 +38,17 @@ To connect to $CLOUD_LONG:
 
 You have successfully integrated your AWS infrastructure with $CLOUD_LONG. 
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
+
 [aws]: https://aws.amazon.com/
 [aws-transit-gateway]: https://aws.amazon.com/transit-gateway/
 [gtw-setup]: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html
diff --git a/integrations/cloudwatch.md b/integrations/cloudwatch.md
@@ -6,12 +6,18 @@ price_plans: [scale, enterprise]
 keywords: [integrate]
 ---
 
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 import IntegrationPrereqsCloud from "versionContent/_partials/_integration-prereqs-cloud-only.mdx";
 import CloudWatchExporter from "versionContent/_partials/_cloudwatch-data-exporter.mdx";
 import ManageDataExporter from "versionContent/_partials/_manage-a-data-exporter.mdx";
 
 # Integrate Amazon CloudWatch with $CLOUD_LONG
 
+
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 [Amazon CloudWatch][cloudwatch] is a monitoring and observability service designed to help collect, analyze, and act on data from applications, infrastructure, and services running in AWS and on-premises environments.
 
 You can export telemetry data from your $SERVICE_LONGs with the time-series and analytics capability enabled to CloudWatch. The available metrics include CPU usage, RAM usage, and storage. This integration is available for [Scale and Enterprise][pricing-plan-features] pricing tiers.
@@ -33,6 +39,16 @@ tool. You create an exporter on the [project level][projects], in the same AWS r
 
 <ManageDataExporter />
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
 [projects]: /use-timescale/:currentVersion:/security/members/
 [pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan
 [cloudwatch]: https://aws.amazon.com/cloudwatch/

diff --git a/integrations/corporate-data-center.md b/integrations/corporate-data-center.md
@@ -8,9 +8,14 @@ keywords: [on-premise, integrations]
 
 import IntegrationPrereqsCloud from "versionContent/_partials/_integration-prereqs-cloud-only.mdx";
 import TransitGateway from "versionContent/_partials/_transit-gateway.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Integrate your data center with $CLOUD_LONG
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 This page explains how to integrate your corporate on-premise infrastructure with $CLOUD_LONG using [AWS Transit Gateway][aws-transit-gateway].
 
 ## Prerequisites
@@ -33,7 +38,18 @@ To connect to $CLOUD_LONG:
 
 </Procedure>
 
-You have successfully integrated your Microsoft Azure infrastructure with $CLOUD_LONG.
+You have successfully integrated your corporate data center with $CLOUD_LONG.
+
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
 
 [aws-transit-gateway]: https://aws.amazon.com/transit-gateway/
 [gtw-setup]: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html

diff --git a/integrations/datadog.md b/integrations/datadog.md
@@ -9,9 +9,14 @@ keywords: [integrate]
 import IntegrationPrereqsCloud from "versionContent/_partials/_integration-prereqs-cloud-only.mdx";
 import DataDogExporter from "versionContent/_partials/_datadog-data-exporter.mdx";
 import ManageDataExporter from "versionContent/_partials/_manage-a-data-exporter.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Integrate Datadog with $CLOUD_LONG
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 [Datadog][datadog] is a cloud-based monitoring and analytics platform that provides comprehensive visibility into
 applications, infrastructure, and systems through real-time monitoring, logging, and analytics.
 
@@ -132,6 +137,16 @@ metrics about your $SERVICE_LONGs.
 Metrics for your $SERVICE_LONG are now visible in Datadog. Check the Datadog $PG integration documentation for a
 comprehensive list of [metrics][datadog-postgres-metrics] collected.
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
 [datadog]: https://www.datadoghq.com/
 [datadog-agent-install]: https://docs.datadoghq.com/getting_started/agent/#installation
 [datadog-postgres]: https://docs.datadoghq.com/integrations/postgres/

diff --git a/integrations/google-cloud.md b/integrations/google-cloud.md
@@ -8,9 +8,14 @@ keywords: [Google Cloud, integrations]
 
 import IntegrationPrereqsCloud from "versionContent/_partials/_integration-prereqs-cloud-only.mdx";
 import TransitGateway from "versionContent/_partials/_transit-gateway.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Integrate Google Cloud with $CLOUD_LONG
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 [Google Cloud][google-cloud] is a suite of cloud computing services, offering scalable infrastructure, AI, analytics, databases, security, and developer tools to help businesses build, deploy, and manage applications.
 
 This page explains how to integrate your Google Cloud infrastructure with $CLOUD_LONG using [AWS Transit Gateway][aws-transit-gateway].
@@ -37,6 +42,17 @@ To connect to $CLOUD_LONG:
 
 You have successfully integrated your Google Cloud infrastructure with $CLOUD_LONG.
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
+
 [google-cloud]: https://cloud.google.com/?hl=en
 [aws-transit-gateway]: https://aws.amazon.com/transit-gateway/
 [gtw-setup]: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html

diff --git a/integrations/microsoft-azure.md b/integrations/microsoft-azure.md
@@ -8,9 +8,14 @@ keywords: [Azure, integrations]
 
 import IntegrationPrereqsCloud from "versionContent/_partials/_integration-prereqs-cloud-only.mdx";
 import TransitGateway from "versionContent/_partials/_transit-gateway.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Integrate Microsoft Azure with $CLOUD_LONG
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 [Microsoft Azure][azure] is a cloud computing platform and services suite, offering infrastructure, AI, analytics, security, and developer tools to help businesses build, deploy, and manage applications.
 
 This page explains how to integrate your Microsoft Azure infrastructure with $CLOUD_LONG using [AWS Transit Gateway][aws-transit-gateway].
@@ -37,6 +42,16 @@ To connect to $CLOUD_LONG:
 
 You have successfully integrated your Microsoft Azure infrastructure with $CLOUD_LONG.
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
 [aws-transit-gateway]: https://aws.amazon.com/transit-gateway/
 [gtw-setup]: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html
 [azure]: https://azure.microsoft.com/en-gb/

diff --git a/integrations/prometheus.md b/integrations/prometheus.md
@@ -7,7 +7,22 @@ keywords: [integrate]
 ---
 
 import PrometheusIntegrate from "versionContent/_partials/_prometheus-integrate.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Integrate Prometheus with $CLOUD_LONG
 
-<PrometheusIntegrate />
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
+<PrometheusIntegrate />
+
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
diff --git a/use-timescale/data-tiering/about-data-tiering.md b/use-timescale/data-tiering/about-data-tiering.md
@@ -11,9 +11,14 @@ cloud_ui:
 ---
 
 import TieredStorageBilling from "versionContent/_partials/_tiered-storage-billing.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # About storage tiers
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 The tiered storage architecture in $CLOUD_LONG includes a high-performance storage tier and a low-cost object storage tier. You use the high-performance tier for data that requires quick access, and the object tier for rarely used historical data. Tiering policies move older data asynchronously and periodically from high-performance to low-cost storage, sparing you the need to do it manually. Chunks from a single hypertable, including compressed chunks, can stretch across these two storage tiers. 
 
 ## High-performance storage 
@@ -119,6 +124,17 @@ The low-cost storage tier comes with the following limitations:
     partitioned on more than one dimension. Make sure your hypertables are
     partitioned on time only, before you enable tiered storage.
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
+
 [blog-data-tiering]: https://www.timescale.com/blog/expanding-the-boundaries-of-postgresql-announcing-a-bottomless-consumption-based-object-storage-layer-built-on-amazon-s3/
 [querying-tiered-data]: /use-timescale/:currentVersion:/data-tiering/querying-tiered-data/
 [parquet]: https://parquet.apache.org/

diff --git a/use-timescale/data-tiering/enabling-data-tiering.md b/use-timescale/data-tiering/enabling-data-tiering.md
@@ -11,9 +11,14 @@ cloud_ui:
 ---
 
 import TieredStorageBilling from "versionContent/_partials/_tiered-storage-billing.mdx";
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
 
 # Manage storage and tiering
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 The tiered storage architecture in $CLOUD_LONG includes a high-performance storage tier and a low-cost object storage tier:
 
 - You use [high-performance storage][high-performance-storage] to store and query frequently accessed data. 
@@ -286,6 +291,17 @@ If you no longer want to use tiered storage for a particular hypertable, drop th
 
 </Procedure>
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
+
+
 [data-retention]: /use-timescale/:currentVersion:/data-retention/
 [console]: https://console.cloud.timescale.com/dashboard/services
 [hypertable]: /use-timescale/:currentVersion:/hypertables/

diff --git a/use-timescale/data-tiering/index.md b/use-timescale/data-tiering/index.md
@@ -1,13 +1,17 @@
 ---
-title: Tiered Storage
+title: Storage on Tiger Cloud
 excerpt: Save on storage costs by tiering older data to a low-cost bottomless object storage tier. Tiger Cloud tiered storage makes sure you cut costs while having data available for analytical queries
 products: [cloud]
 price_plans: [scale, enterprise]
 keywords: [tiered storage]
 tags: [storage, data management]
 ---
 
-# Tiered storage
+# Storage
+
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
 
 Tiered storage is a [hierarchical storage management architecture][hierarchical-storage] for 
 [time series and analytics][create-service] $SERVICE_SHORT you create in [$CLOUD_LONG](https://console.cloud.timescale.com/).
@@ -53,11 +57,26 @@ In this section, you:
 * [Learn about replicas and forks with tiered data][replicas-and-forks]: understand how tiered storage works
   with forks and replicas of your $SERVICE_SHORT.
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+$CLOUD_LONG stores your data in high-performance storage optimized for frequent querying. Based on [AWS EBS gp3][aws-gp3], the high-performance storage provides you with up to 16 TB and 16,000 IOPS. Its [$HYPERCORE row-columnar storage engine][hypercore], designed specifically for real-time analytics, enables you to compress your data by up to 98%, while improving performance. 
+
+Coupled with other optimizations, $CLOUD_LONG high-performance storage makes sure your data is always accessible and your queries run at lightning speed. 
+
+</Tab>
+
+</Tabs>
+
+
 [about-data-tiering]: /use-timescale/:currentVersion:/data-tiering/about-data-tiering/
 [enabling-data-tiering]: /use-timescale/:currentVersion:/data-tiering/enabling-data-tiering/
 [replicas-and-forks]: /use-timescale/:currentVersion:/data-tiering/tiered-data-replicas-forks/
 [creating-data-tiering-policy]: /use-timescale/:currentVersion:/data-tiering/enabling-data-tiering/#automate-tiering-with-policies
 [querying-tiered-data]: /use-timescale/:currentVersion:/data-tiering/querying-tiered-data/
 [add-retention-policies]: /api/:currentVersion:/continuous-aggregates/add_policies/
 [create-service]: /getting-started/:currentVersion:/services/
-[hierarchical-storage]: https://en.wikipedia.org/wiki/Hierarchical_storage_management
+[hierarchical-storage]: https://en.wikipedia.org/wiki/Hierarchical_storage_management
+[hypercore]: /use-timescale/:currentVersion:/hypercore
+[aws-gp3]: https://docs.aws.amazon.com/ebs/latest/userguide/general-purpose.html
diff --git a/use-timescale/data-tiering/querying-tiered-data.md b/use-timescale/data-tiering/querying-tiered-data.md
@@ -7,8 +7,14 @@ keywords: [ tiered storage, tiering ]
 tags: [ storage, data management ]
 ---
 
+import NotSupportedAzure from "versionContent/_partials/_not-supported-for-azure.mdx";
+
 # Querying tiered data
 
+<Tabs label="Tiger Cloud on AWS and Azure" persistKey="tiger-platform-clouds">
+
+<Tab title="Tiger Cloud on AWS" label="aws-cloud">
+
 Once rarely used data is tiered and migrated to the object storage tier, it can still be queried 
 with standard SQL by enabling the `timescaledb.enable_tiered_reads` GUC. 
 By default, the GUC is set to `false`, so that queries do not touch tiered data.
@@ -186,3 +192,12 @@ Queries over tiered data are expected to be slower than over local data. However
 
 * Text and non-native types (JSON, JSONB, GIS) filtering is slower when querying tiered data.
 
+</Tab>
+
+<Tab title="Tiger Cloud on Azure" label="azure-cloud">
+
+<NotSupportedAzure />
+
+</Tab>
+
+</Tabs>
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		This feature is on our roadmap for $CLOUD_LONG on Microsoft Azure. Stay tuned!