DOC-919 enable Kafka Connect in Azure Dedicated (#167)

* DOC-919 enable Kafka Connect in Azure Dedicated

* style edit

* returning Next steps section

* add link for Kafka Connect in overview & note in KC page

modules/develop/pages/managed-connectors/index.adoc

@@ -10,6 +10,8 @@ your data than manually creating a solution with the Kafka API. You can set up
 and manage these connectors in Redpanda Console. All connectors are managed by
 Redpanda.
 
+include::shared:partial$kafka-connect.adoc[]
+
 Each connector is either a source or a sink:
 
 * A source connector imports data from a source system into a Redpanda cluster.

modules/get-started/pages/cloud-overview.adoc

@@ -1,5 +1,6 @@
 = Redpanda Cloud Overview
 :description: Learn about Redpanda Serverless, Dedicated, and Bring Your Own Cloud (BYOC) clusters.
+:tag-pipeline-service: api:ROOT:cloud-api.adoc#tag--PipelineService
 :page-aliases: cloud:dedicated-byoc.adoc, deploy:deployment-option/cloud/dedicated-byoc.adoc, deploy:deployment-option/cloud/cloud-overview.adoc
 
 
@@ -174,6 +175,12 @@ BYOVPC::
 --
 =====
 
+== Redpanda Connect and Kafka Connect
+
+xref:develop:connect/about.adoc[Redpanda Connect] is integrated into Redpanda Cloud and available as a fully-managed service. Choose from a range of connectors, processors, and other components to quickly build and deploy streaming data pipelines or AI applications from the Cloud UI or using the pass:a,m[xref:{tag-pipeline-service}[Data Plane API\]]. Comprehensive metrics, monitoring, and per pipeline scaling are also available. To start using Redpanda Connect, xref:develop:connect/connect-quickstart.adoc[try this quickstart].
+
+xref:develop:managed-connectors/index.adoc[Kafka Connect] is automatically enabled on AWS and GCP clusters. With this, there is a node running for Kafka Connect even if connectors are not used. To enable Kafka Connect on Azure clusters, see xref:get-started:cluster-types/byoc/azure/create-byoc-cluster-azure.adoc#enable-kafka-connect[Enable Kafka Connect].
+
 == Maintenance windows
 
 Redpanda runs maintenance and upgrade operations on clusters in a rolling fashion, accompanied by a series of health checks, so there is no disruption to the availability of your service. As part of the Kafka protocol, recycling nodes cause client connections to be restarted. All mainstream client libraries support automatic reconnections for this.

modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc

@@ -124,7 +124,7 @@ As part of agent deployment, Redpanda assigns the permissions required to run th
 
 == Enable Kafka Connect
 
-To enable xref:develop:managed-connectors/index.adoc[Kafka Connect] on your BYOC cluster:
+To enable xref:develop:managed-connectors/index.adoc[Kafka Connect] for clusters on Azure:
 
 . Authenticate to the Redpanda Cloud API. Follow the steps in xref:manage:api/cloud-api-authentication.adoc[].
 

modules/get-started/pages/cluster-types/dedicated/create-dedicated-cloud-cluster.adoc

@@ -27,8 +27,10 @@ To unlock this feature for Azure, contact https://support.redpanda.com/hc/en-us/
 ** Your network name is used to identify this network.
 ** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.
 +
-NOTE: Private networks require either a VPC peering connection or a private connectivity service, such as xref:networking:configure-privatelink-in-cloud-ui.adoc[AWS PrivateLink], xref:networking:configure-private-service-connect-in-cloud-ui.adoc[GCP Private Service Connect], or xref:networking:azure-private-link.adoc[Azure Private Link]. 
+Private networks require either a VPC peering connection or a private connectivity service, such as xref:networking:configure-privatelink-in-cloud-ui.adoc[AWS PrivateLink], xref:networking:configure-private-service-connect-in-cloud-ui.adoc[GCP Private Service Connect], or xref:networking:azure-private-link.adoc[Azure Private Link]. 
 
 . Click *Create*.
 
 After the cluster is created, you can click the cluster name on the *Clusters* page to see the overview for it.
+
+include::shared:partial$kafka-connect.adoc[]

modules/shared/partials/kafka-connect.adoc

@@ -0,0 +1 @@
+NOTE: Kafka Connect is automatically enabled on AWS and GCP clusters, which means there is a node running for Kafka Connect even if connectors are not used. To enable Kafka Connect on Azure clusters, see xref:get-started:cluster-types/byoc/azure/create-byoc-cluster-azure.adoc#enable-kafka-connect[Enable Kafka Connect].