SPP M365 Backup via Proxy

Several clients are enforcing the usage of a client provided HTTP/HTTPS proxy server to grant systems access to the Internet. In such case the IP network traffic is not routed through the default gateway. That is the reason why a client proxy needs to
be configured on the system that requires internet access. That may be achieved on the Linux operating system level or in a application itself like the SPP cloudAgent component.

The usecase in focus is the backup of Microsoft 365 workloads with Spectrum Protect Plus. Therefore the SPP "Proxy Host server" needs access to the internet to the endpoint https://graph.microsoft.com:443

Client HTTPS proxy settings can for example be exported by variables (http_proxy, https_proxy, no_proxy) in Linux shell scripts like: /etc/environment, /etc/profile.d/http_proxy.csh, /etc/profile.d/http_proxy.sh


Unfortunately, the SPP cloudAgent component does not pick up Linux (shell) system-wide settings so it may be required to pass additional parameters to the components that are actually communicating through the Internet.
It is important to note, that clients typically implement granular ACLs in the proxy and limiting the access to specific ports and target addresses, e.g. the host called "SPP_cloud_proxy_host" can only access https://graph.microsoft.com:443

One clients will enforce authorization against the proxy with username and password against the HTTPS proxy while other clients do not enforce the authentication against their HTTPS proxies.


example1: export https_proxy=https://USERNAME:PASSWORD@proxy:8080
example2: export http_proxy=http://proxy:8080


As a side note the following more generic use case would require the usage od HTTPS Proxies as well. it needs to be mentioned that the usage of a HTTP/HTTP proxy is not only
important for SPP cloud proxy host communication to the MS365 backup but also in case a SPP server is located on-prem and
communicating over a HTTP/HTTPS proxy to off-prem components like "SPP cloud proxy host and vsnap in Azuew" and other use cases. In this case the SPP server itself must be able to communicate to the
Internet target addresses using a HTTPS proxy.