Update from SAP DITA CMS (squashed):

commit bfe843f86040a2dff9f4d17242fb971b61362211
Author: REDACTED
Date:   Thu Jul 10 16:03:09 2025 +0000

    Update from SAP DITA CMS 2025-07-10 16:03:09

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

commit d03aded1c7f9922d8925b4fec1ea7f57e79f976d
Author: REDACTED
Date:   Thu Jul 10 15:39:25 2025 +0000

    Update from SAP DITA CMS 2025-07-10 15:39:25

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

commit bff3ead33ea67c4a20fe7f6ea0c936df95992b04
Author: REDACTED
Date:   Thu Jul 10 15:14:48 2025 +0000

    Update from SAP DITA CMS 2025-07-10 15:14:48

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/1-connectivity-documentation/cloud-connector-e6c7616.md

@@ -103,19 +103,27 @@ Back to [Content](cloud-connector-e6c7616.md#loioe6c7616abb5710148cfcf3e75d96d59
 
 **Connecting On-Premises Database Tools to SAP HANA Databases**
 
+> ### Restriction:  
+> This scenario is only available for the Neo environment.
+
 ![](images/SCC_Intro_2_ded00cb.png)
 
-1.  Install and configure the Cloud Connector: [Installation](installation-57ae3d6.md), [Initial Configuration](initial-configuration-db9170a.md), [Adding and Managing Subaccounts](adding-and-managing-subaccounts-f16df12.md)
+1.  Install and configure the Cloud Connector: [Installation](https://help.sap.com/docs/connectivity/sap-btp-connectivity-neo/installation?version=Cloud), [Initial Configuration](https://help.sap.com/docs/connectivity/sap-btp-connectivity-neo/cloud-connector-initial-configuration?version=Cloud), [Adding and Managing Subaccounts](https://help.sap.com/docs/connectivity/sap-btp-connectivity-neo/managing-subaccounts?version=Cloud)
 2.  Access HANA databases on SAP BTP: [Configure a Service Channel for an SAP HANA Database](https://help.sap.com/viewer/b865ed651e414196b39f8922db2122c7/Cloud/en-US/3dc28b456bb64fad89084d2d10af602c.html "Using Cloud Connector service channels, you can establish a connection to an SAP HANA database in SAP BTP that is not directly exposed to external access.") :arrow_upper_right:
 3.  Connect on-premises database or BI tools to a HANA database on SAP BTP: [Connect DB Tools to SAP HANA via Service Channels](https://help.sap.com/viewer/b865ed651e414196b39f8922db2122c7/Cloud/en-US/64d6a510e98941d28dbff2fc8179f175.html "") :arrow_upper_right:
 
 > ### Note:  
 > You can use service channels also for other purposes:
 > 
-> -   Connect to a virtual machine on SAP BTP.
-> -   Configure an RFC connection from your on-premises system to S/4HANA Cloud.
+> -   Connect to a virtual machine on SAP BTP \(**Neo** environment only\).
+> -   Configure an RFC connection from your on-premises system to S/4HANA Cloud \(**Neo** and **Multi-Cloud** environment\).
+> -   Connect to a service in a Kubernetes cluster \(**Multi-Cloud** environment only\)
+> 
+> See also:
+> 
+> [Using Service Channels](using-service-channels-16f6342.md) \(**Multi-Cloud** environment\)
 > 
-> See [Using Service Channels](using-service-channels-16f6342.md).
+> [Using Service Channels](https://help.sap.com/docs/connectivity/sap-btp-connectivity-neo/using-service-channels?version=Cloud) \(**Neo** environment\)
 
 Back to [Basic Scenarios](cloud-connector-e6c7616.md#loioe6c7616abb5710148cfcf3e75d96d596__scenarios) 
 

docs/1-connectivity-documentation/frequently-asked-questions-f8d6f9a.md

@@ -660,9 +660,26 @@ You can use the TCP channel of the Cloud Connector, if the client supports a SOC
 
 ### **Can I use the Cloud Connector from on-premises to cloud for any protocol?**
 
-This is possible only for a limited set of protocols. You can use the Cloud Connector as a JDBC or ODBC proxy to access the HANA DB instance within your SAP BTP Neo subaccount \(service channel\). This is sometimes referred to as “HANA protocol”. Also, there are service channels for SSH access to SAP BTP Neo virtual machines, and for RFC access to ABAP cloud systems. All of these service channels provide access to endpoints that are not visible in the Internet.
+This is possible only for a limited set of protocols, using Cloud Connector *service channels*:
 
-For HTTP, the endpoints that could be addressed are visible in the Internet. Therefore, you can simply use your normal network infrastructure that is prepared for accessing HTTPS endpoints in the Internet anyway.
+**Neo** environment:
+
+-   You can use the Cloud Connector as a JDBC or ODBC proxy to access the HANA DB instance within your SAP BTP Neo subaccount \(service channel\). This is sometimes referred to as “HANA protocol”.
+-   Also, there are service channels for SSH access to SAP BTP Neo virtual machines.
+
+**Neo** and **Multi-Cloud** environment:
+
+-   RFC access to ABAP cloud systems.
+
+All of these service channels provide access to endpoints that are not visible in the Internet.
+
+See also:
+
+[Using Service Channels](using-service-channels-16f6342.md) \(**Multi-Cloud** environment\)
+
+[Using Service Channels](https://help.sap.com/docs/connectivity/sap-btp-connectivity-neo/using-service-channels?version=Cloud) \(**Neo** environment\)
+
+For HTTP \(**Neo** and **Multi-Cloud**\), the endpoints that can be addressed are visible in the Internet. Therefore, you can simply use your normal network infrastructure that is prepared for accessing HTTPS endpoints in the Internet anyway.