Merge pull request #10981 from MicrosoftDocs/main

[AutoPublish] main to live - 07/08 10:33 PDT | 07/08 23:03 IST

windows/deployment/do/mcc-ent-deploy-to-linux.md

@@ -19,6 +19,8 @@ This article describes how to deploy Microsoft Connected Cache for Enterprise an
 
 Before deploying Connected Cache to a Linux host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your Connected Cache Azure resource and cache node](mcc-ent-create-resource-and-cache.md).
 
+For Connected Cache deployment to succeed, you must allow direct calls to the Delivery Optimization service from your devices. When using a TLS-inspecting proxy, you must configure your proxy/host machine to allow calls to and from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
+
 ## Steps to deploy Connected Cache cache node to Linux
 
 # [Azure portal](#tab/portal)

windows/deployment/do/mcc-ent-deploy-to-windows.md

@@ -21,6 +21,8 @@ Deploying Connected Cache to a Windows host machine requires designating a [Grou
 
 Before deploying Connected Cache to a Windows host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your Connected Cache Azure resource](mcc-ent-create-resource-and-cache.md).
 
+For Connected Cache deployment to succeed, you must allow direct calls to the Delivery Optimization service from your devices. When using a TLS-inspecting proxy, you must configure your proxy/host machine to allow calls to and from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
+
 ## Steps to deploy Connected Cache node to Windows
 
 # [Azure portal](#tab/portal)
@@ -29,7 +31,7 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
 1. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the archive onto the host machine.
 
    >[!Note]
-   >* The provisioning package should be extracted to a directory that isn't synced to OneDrive, as the sychronization process will interfere with the installation. It is recommended to extract the provisioning package to the root directory of the host machine (e.g. C:\mccInstaller)
+   >* The provisioning package should be extracted to a directory that isn't synced to OneDrive, as the synchronization process will interfere with the installation. It is recommended to extract the provisioning package to the root directory of the host machine (e.g. C:\mccInstaller)
 
 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 

windows/deployment/do/mcc-ent-faq.yml

@@ -23,7 +23,7 @@ summary: |
 sections:
   - name: Ignored
     questions:
-      - question: What are the licesning requirement?
+      - question: What are the licensing requirement?
         answer: Microsoft Connected Cache for Enterprise and Education is available to all Windows E3, E5 and F3 and Education A3 and A5 customers.
       - question: Is there a charge to create Connected Cache resources and cache node on Azure?
         answer: No. You won't be charged to create Connected Cache resource and cache nodes on Azure. However, you need an Azure pay-as-you-go subscription to create the resources but there is no charge for the resource itself.

windows/deployment/do/mcc-ent-release-notes.md

@@ -46,7 +46,7 @@ This release contains improvements that can only be applied by redeploying your
 ### Improvements to Linux-hosted cache nodes
 
 - **Connected Cache container now uses Ubuntu 24.04 Docker environment**: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features.
-- **TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation**: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation.
+- **TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation**: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation. Added an intermediate certificate verification step to the installation process on both Windows-hosted and Linux-hosted cache nodes. Calls to *.prod.do.dsp must be enabled for installation to succeed.
 - **Security improvements**: Kept intentionally vague to protect previous versions of Connected Cache.
 
 ## Windows-hosted install script v2.0.0.2

windows/deployment/do/mcc-ent-troubleshooting.md

@@ -23,11 +23,17 @@ This article contains instructions on how to troubleshoot different issues you m
 
 This section describes known issues with the latest release of Microsoft Connected Cache for Enterprise and Education. See the [Release Notes page](mcc-ent-release-notes.md) for more details on the fixes included in the latest release.
 
+### Connected Cache Azure resource is missing from Scope selection under the "Metrics" tab
+
+You can create custom charts on the Connected Cache Azure portal by selecting the **Metrics** tab under the **Monitoring** section of the Connected Cache Azure resource. The Connected Cache Azure resource is correctly selected as the Scope by default, but if you change the selected Scope you're unable to reselect the Connected Cache Azure resource, preventing subsequent creation of custom charts.
+
+As a temporary workaround, you can navigate away from the **Metrics** tab and then return to it. The Connected Cache Azure resource is once again correctly selected as the Scope.
+
 ### Script provisionmcconwsl.ps1 fails when executed on a Windows 11 host machine configured to use Japanese language
 
 In the Connected Cache installation script (provisionmcconwsl.ps1), the check processing is executed until the value of the last execution code (Last Result) of the installation task becomes 0 in the following processing. However, in Japanese OS, the return value is null because "Last Result" is displayed, and an exception occurs.
 
-As a temporary workaround, the above error doesn't occur by changing the language setting of the local administrator user from Japanese to English and then executing the script.
+As a temporary workaround, you can change the language setting of the local administrator user from Japanese to English and then execute the script.
 
 ## Steps to obtain an Azure subscription ID
 
@@ -48,7 +54,7 @@ If you're encountering a validation error, check that you have filled out all re
 
 If your configuration doesn't appear to be taking effect, check that you have selected the **Save** option at the top of the configuration page in the Azure portal user interface.
 
-If you have changed the proxy configuration, you'll need to re-provision the Connected Cache software on the host machine for the proxy configuration to take effect.
+If you have changed the proxy configuration, you'll need to reprovision the Connected Cache software on the host machine for the proxy configuration to take effect.
 
 ## Troubleshooting cache nodes created during early preview