Connecting on-premises Universal Forwarders (UFs) or Heavy Forwarders (HFs) to Splunk Cloud relies on the Universal Forwarder Credentials Package (splunkclouduf.spl), downloaded from Splunk Web under Apps > Universal Forwarder > Download Universal Forwarder Credentials.
Installing splunkclouduf.spl drops a stack-named app (such as <stack>_splunkcloud) into $SPLUNK_HOME/etc/apps/ containing TLS certificates and default/outputs.conf pointing to inputs1.<stack>.splunkcloud.com:9997, inputs2.<stack>.splunkcloud.com:9997, and so on.
A classic troubleshooting trap occurs when an admin also runs ./splunk add forward-server or configures outputs during an MSI install. That writes $SPLUNK_HOME/etc/system/local/outputs.conf, which takes highest configuration precedence and silently overrides the Splunk Cloud app outputs.conf.
$SPLUNK_HOME/bin/splunk install app /tmp/splunkclouduf.spl -auth admin:changeme
$SPLUNK_HOME/bin/splunk restart
$SPLUNK_HOME/bin/splunk btool outputs list --debug | grep server