Skip to content

Commit beab5f0

Browse files
committed
Add content type to code block and expected note style
1 parent b6b2d88 commit beab5f0

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

defender-endpoint/linux-static-proxy-configuration.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,23 +61,26 @@ During installation, the `HTTPS_PROXY` environment variable must be passed to th
6161
6262
The `HTTPS_PROXY` environment variable may similarly be defined during uninstallation.
6363

64-
Note that installation and uninstallation will not necessarily fail if a proxy is required but not configured. However, telemetry won't be submitted, and the operation could take longer due to network timeouts.
64+
> [!NOTE]
65+
> Installation and uninstallation will not necessarily fail if a proxy is required but not configured. However, telemetry won't be submitted, and the operation could take longer due to network timeouts.
6566
6667
## Post installation configuration
6768

6869
After installation, configure Defender for Endpoint with a static proxy. This can be done in two ways:
6970

7071
### 1. Using mdatp command-line tool
7172

72-
Run the following command on the endpoint to configure proxy for Defender for Endpoint
73+
Run the following command on the endpoint to configure proxy for Defender for Endpoint.
74+
7375
```bash
7476
mdatp config proxy set --value http://address:port
7577
```
7678

7779
### 2. Using managed configuration
7880

7981
Set the proxy in the managed configuration at `/etc/opt/microsoft/mdatp/managed/mdatp_managed.json`. This is an example of the json schema:
80-
```
82+
83+
```json
8184
{
8285
"cloudService":{
8386
"proxy": "http://proxy.server:port/"

0 commit comments

Comments
 (0)