---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Proxy server configuration for MID Servers used for Cloud Discovery and Cloud Provisioning and Governance

# Proxy server configuration for MID Servers used for Cloud Discovery and Cloud Provisioning and Governance {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can configure the MID Server for Cloud Provisioning and Governance to use a proxy server. Using a proxy server supports all cloud-based activities such as running Discovery, billing downloads, provisioning virtual machines, and running life-cycle operations on virtual machines.{#mid-server-proxy__mid-proxy-cloud-mgt}

## Proxy server limitations {#mid-server-proxy__section_flc_vty_hdb}

* VMware Cloud is not supported.
* Windows or Linux platforms only are supported.
* The Google Cloud Console integration does not support downloading billing data.
* Remote PowerShell scripts cannot be executed.
* Custom APIs may not work.
{#mid-server-proxy__ul_jgf_vvq_vcb} Note:  

SSH calls should not be routed through a proxy server, when using a private cloud environment that is on the same side of the proxy as the MID Server.

Set mid.capi.skip_proxy_for_ssh to true to skip it. See [MID Server properties used by Service Mapping](https://servicenow-prod.fluidtopics.net/DUWVt444iEnqsdqRHH3JlQ "Service Mapping uses the MID Server parameters during discovery and mapping. Do not change default values for these parameters unless you are troubleshooting the discovery process.") for more information.  
mid.capi.skip_proxy_for_ssh:

* Determines whether the MID Server skips the proxy server when routing SSH calls.
* Type: true \| false
* Default value: false
{#mid-server-proxy__ul_lbh_byw_gyb}

## Supported proxy server authentication for Cloud Provisioning and Governance {#mid-server-proxy__section_tns_sty_hdb}

{#mid-server-proxy__table_vkk_lgy_vcb__entry__2}

| Proxy Server type | Authentication type |
|-|-|
| HTTP/HTTPS | No authentication |
| SOCKS5 | No authentication |
| HTTP/HTTPS | Basic authentication |
| SOCKS5 | Basic authentication |
| HTTP/HTTPS | NTLM |
[ ]

{#mid-server-proxy__table_vkk_lgy_vcb}

## Supported proxy server configurations for Cloud Provisioning and Governance {#mid-server-proxy__section_ecs_t5y_hdb}

{#mid-server-proxy__table_vkj_hdl_1db__entry__4}

| Configuration | Operating system | Proxy server | Authentication mode |
|-|-|-|-|
| Configuration 1 | Linux | None | Not Applicable |
| Configuration 2 | Windows | Squid (HTTPS) | None |
| Configuration 3 | Linux | Squid (HTTPS) | Local |
| Configuration 4 | Windows | Squid (HTTPS) | Active Directory |
[Table 1. Supported configuration settings]

{#mid-server-proxy__table_vkj_hdl_1db} {#mid-server-proxy__table_ddy_12l_1db__entry__6}

| Cloud provider | Functionality | Configuration 1 | Configuration 2 | Configuration 3 | Configuration 4 |
|-|-|-|-|-|-|
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | Cloud Discovery | Yes | Yes | Yes | Yes |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | VM Provisioning | Yes | Yes | Yes | Yes |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | VM life cycle | Yes | Yes | Yes | Yes |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | CFT provisioning | Yes | Yes | Yes | Yes |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | Billing download | Yes | Yes | Yes | Yes |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | Scripts using SSH | Yes | Yes | Yes | Yes |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | Scripts using PowerShell | Not Applicable | Not Applicable | Not Applicable | Not Applicable |
| Amazon AWS Cloud, Microsoft Azure Cloud, and IBM Cloud Platform | Cloud events | Not Applicable | Not Applicable | Not Applicable | Not Applicable |
| Google Cloud Platform | Cloud Discovery | Yes | Yes | Yes | Yes |
| Google Cloud Platform | VM Provisioning | Yes | Yes | Yes | Yes |
| Google Cloud Platform | VM life cycle | Yes | Yes | Yes | Yes |
| Google Cloud Platform | CFT provisioning | Yes | Yes | Yes | Yes |
| Google Cloud Platform | Billing download | No | No | No | No |
| Google Cloud Platform | Scripts using SSH | Yes | Yes | Yes | Yes |
| Google Cloud Platform | Scripts using PowerShell | Not Applicable | Not Applicable | Not Applicable | Not Applicable |
| Google Cloud Platform | Cloud events | Not Applicable | Not Applicable | Not Applicable | Not Applicable |
| VMware Cloud | Not Applicable |||||
[Table 2. Supported configurations]

{#mid-server-proxy__table_ddy_12l_1db}
**Related topics**   

* [Install a MID Server on Windows](https://www.servicenow.com/docs/access?context=mid-server-install-prereqs&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [Install a MID Server on Linux](https://www.servicenow.com/docs/access?context=t_InstallAMIDServerOnLinux&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)
* [MID Server parameters](https://www.servicenow.com/docs/access?context=mid-server-parameters&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)