Merge pull request #231810 from niklarin/startstop

Compute start stop update

Author: v-dirichards

articles/cosmos-db/postgresql/TOC.yml

@@ -105,6 +105,8 @@
           href: concepts-maintenance.md
         - name: Burstable compute
           href: concepts-burstable-compute.md
+        - name: Start and stop cluster compute
+          href: concepts-compute-start-stop.md
         - name: Upgrade
           href: concepts-upgrade.md
     - name: Business continuity
@@ -145,6 +147,8 @@
           href: howto-create-users.md
         - name: Schedule maintenance
           href: howto-maintenance.md
+        - name: Start and stop cluster compute
+          href: how-to-start-stop-cluster.md
         - name: Restart cluster
           href: howto-restart.md
         - name: Upgrade cluster

articles/cosmos-db/postgresql/concepts-compute-start-stop.md

@@ -0,0 +1,32 @@
+---
+title: Start and stop cluster compute - Azure Cosmos DB for PostgreSQL
+description: Learn about how to start and stop compute on the cluster nodes
+ms.author: nlarin
+author: niklarin
+ms.service: cosmos-db
+ms.subservice: postgresql
+ms.topic: conceptual
+ms.date: 3/22/2023
+---
+# Start and stop compute on cluster nodes
+
+[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
+
+Azure Cosmos DB for PostgreSQL allows you to stop compute on all nodes in a cluster. Compute billing is paused when cluster is stopped and continues when computer is started again.
+
+> [!NOTE]
+> Billing for provisioned storage on all cluster nodes continues when cluster's compute is stopped.
+
+## Managing compute state on cluster nodes
+
+You can stop compute on a cluster for as long as you need.
+
+You can perform management operations such as compute or storage scaling, adding a worker node, or updating networking settings only on clusters with started compute. 
+
+If cluster has [high availability (HA)](./concepts-high-availability.md) enabled, compute start and stop operations would start and stop compute on all primary and standby nodes in the cluster. You can start and stop compute on the primary cluster and any of its [read replicas](./concepts-read-replicas.md) independently.
+
+## Next steps
+
+- Learn how to start and stop [cluster compute in Azure Cosmos DB for PostgreSQL](./how-to-start-stop-cluster.md)
+- Learn about [pricing options in Azure Cosmos DB for PostgreSQL](./resources-pricing.md) 
+

articles/cosmos-db/postgresql/how-to-start-stop-cluster.md

@@ -0,0 +1,39 @@
+---
+title: Start and stop cluster - Azure Cosmos DB for PostgreSQL
+description: How to start and stop compute on the cluster nodes
+ms.author: nlarin
+author: niklarin
+ms.service: cosmos-db
+ms.subservice: postgresql
+ms.topic: how-to
+ms.date: 3/03/2023
+---
+# Start and stop compute on a cluster
+
+[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
+
+Azure Cosmos DB for PostgreSQL allows you to stop and start compute on all nodes in a cluster. 
+
+## Stop a running cluster
+
+1.  In the [Azure portal](https://portal.azure.com/), choose the Azure Cosmos DB for PostgreSQL cluster that you want to stop.
+
+2.  From the **Overview** page, click the **Stop** button in the toolbar.
+
+> [!NOTE]
+> Once the cluster is stopped, other management operations are not available for the cluster.
+
+
+## Start a stopped cluster
+
+1.  In the [Azure portal](https://portal.azure.com/), choose the Azure Cosmos DB for PostgreSQL cluster that you want to start.
+
+2.  From the **Overview** page, click the **Start** button in the toolbar.
+
+> [!NOTE]
+> Once the cluster is started, all management operations are now available for the cluster.
+
+## Next steps
+
+- Learn more about [compute start and stop in Azure Cosmos DB for PostgreSQL](./concepts-compute-start-stop.md).
+

articles/cosmos-db/postgresql/product-updates.md

@@ -1,13 +1,13 @@
 ---
 title: Product updates for Azure Cosmos DB for PostgreSQL
-description: New features and features in preview
+description: Release notes, new features and features in preview
 ms.author: jonels
 author: jonels-msft
 ms.custom: mvc
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: conceptual
-ms.date: 02/25/2023
+ms.date: 03/23/2023
 ---
 
 # Product updates for Azure Cosmos DB for PostgreSQL
@@ -22,14 +22,14 @@ Updates that don’t directly affect the internals of a cluster are rolled out g
 
 Updates that change cluster internals, such as installing a [new minor PostgreSQL version](https://www.postgresql.org/developer/roadmap/), are delivered to existing clusters as part of the next [scheduled maintenance](concepts-maintenance.md) event. Such updates are available immediately to newly created clusters.
 
+### March 2023
+
+* General availability: Cluster compute [start / stop functionality](./concepts-compute-start-stop.md) is now supported across all configurations.
+	
 ### February 2023
 
 * General availability: 4 TiB, 8 TiB, and 16 TiB storage per node is now supported for [multi-node configurations](resources-compute.md#multi-node-cluster) in addition to previously supported 0.5 TiB, 1 TiB, and 2 TiB storage sizes.
 	* See cost details for your region in 'Multi-node' section of [the Azure Cosmos DB for PostgreSQL pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/postgresql/).
-* General availability: [Latest minor PostgreSQL version updates](reference-versions.md#postgresql-versions) (11.19, 12.14, 13.10, 14.7, and 15.2) are now available in all supported regions.
-	* Existing clusters will get minor Postgres version update with [the next maintenance](concepts-maintenance.md)
-	* Major Postgres and minor Citus [version upgrades](concepts-upgrade.md) can be performed in-place.
-
 
 ### January 2023