From c528bc6ff72376ca9bdf9e1b2bd57e9fcf325a34 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 9 Apr 2025 14:04:12 -0700 Subject: [PATCH] Update windows/deployment/do/mcc-ent-deploy-to-linux.md --- windows/deployment/do/mcc-ent-deploy-to-linux.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md index 94d3b8e1ca..6325dc4017 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-linux.md +++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md @@ -48,7 +48,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package. > [!Note] - >* If + >* If you're deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and then add `proxytlscertificatepath="/path/to/pem/file"` to the provisioning command. 1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute. 1. Replace the values in the following provisioning command before running it on the host machine.