So, what do you do when a user's browser is not on the corporate network? You can either use a tunnel connection or a reverse proxy.
Both of these solutions will work if your organization wants to expose some of your data to users outside of your corporate network, without giving users VPN rights. For example, your company wants to expand a segment of their business, so they hire a consulting team to do market research for them. Your company wants to provide the consultants access to their data but wants to safeguard this data inside their own firewall. They don't want to give the consultants VPN access to their network, so they create a tunnel connection, allowing them to access the data, without compromising your network.
In this lesson, we will explore tunnel live connections.

When using tunnel connections, the data flows from the on-premise data source to the SAP Analytics Cloud system via the SAP BTP cloud connector, but is not stored in SAP Analytics Cloud. Let's take a closer look at using tunnel connections, when creating direct live data connections to on-premise data sources.
A few additional things to keep in mind regarding tunnel connections to on-premise data sources:
- There is no need to configure CORS in the on-premise system. Instead, tunnel connections require that the on-premise data source is configured as an accessible resource in the SAP BTP cloud connector setup.
- SSO can be used with tunnel connections. SAML trust is established between SAP Analytics Cloud and the on-premise data source for connections created with SSO.
- For SAP HANA, app to app SAML SSO is used.
- For SAP BW/4HANA and SAP S/4HANA, trust is established through the exchange of certificates between the ABAP system and the SAP BTP cloud connector.
- For SSO, it's not necessary to configure SAP Analytics Cloud to use a custom SAML IdP.
- They are slower than direct live connections because the data has to flow to SAP Analytics Cloud.
- It is not possible to use an SAP Universe when creating a tunnel connection.