Merge branch 'main' into release-intune-2207

Author: v-alje

memdocs/configmgr/core/get-started/azure-template.md

@@ -16,7 +16,7 @@ ms.localizationpriority: medium
 
 *Applies to: Configuration Manager (current branch, technical preview branch)*
 
-<!--3556017-->
+<!--3556017
 > [!Important]
 > As of June 20, 2022, there is a known issue with the Azure templates for lab environments. We are working on resolving the issue and we will update this message when it's resolved. For more information, see [known issues](#known-issues). <!--icm 314312504-->
 
@@ -154,9 +154,9 @@ The prefix that you specified in the deployment template is the VM name prefix.
 - Windows 10
 - Configuration Manager client
 
-
+<!--icm 314312504
 ## Known issues
-<!--icm 314312504-->
+<!--icm 314312504
 As of June 20, 2022, there is a known issue with the Azure templates for lab environments. We are working on resolving the issue and we will update this message when it's resolved. This issue occurs during deployment of the template and the following error message is displayed:
 
 ```text
@@ -169,3 +169,4 @@ As of June 20, 2022, there is a known issue with the Azure templates for lab env
 }
 
 ```
+-->

memdocs/configmgr/core/get-started/technical-preview.md

@@ -97,7 +97,7 @@ Install a baseline version for up to one year after its release. When you instal
 
 - **Technical preview version 2206**
 
-Download a baseline version from the [Evaluation Center](https://www.microsoft.com/evalcenter/download-microsoft-endpoint-configuration-manager-technical-preview).
+Download a baseline version from the [Evaluation Center](https://www.microsoft.com/en-in/evalcenter/evaluate-microsoft-endpoint-configuration-manager-technical-preview).
 
 <!--
 > [!NOTE]
@@ -156,7 +156,7 @@ The following features were released with previous versions of the Configuration
 
 - [Default site boundary group behavior to support cloud source selection](2022/technical-preview-2206.md#bkmk_dbgmp) <!--10674394-->
 - [PowerShell release notes preview](2022/technical-preview-2206.md#bkmk_powershell) <!--14431761-->
-- 
+
 ### Technical preview version 2205
 
 - [Offset for reoccurring monthly maintenance window schedules](2022/technical-preview-2205.md#bkmk_offset) <!--3601127-->

memdocs/configmgr/sum/deploy-use/third-party-software-updates.md

@@ -238,7 +238,7 @@ To help you find custom catalogs that you can import for third-party software up
 - Configuration Manager has a new version for the catalog cab file format. The new version includes the certificates for the vendor's binary files. These certificates are added to the **Certificates** node under **Security** in the **Administration** workspace once you approve and trust the catalog.
      - You can still use the older catalog cab file version as long as the download URL is https and the updates are signed. The content will fail to publish because the certificates for the binaries aren't in the cab file and already approved. You can work around this issue by finding the certificate in the **Certificates** node, unblocking it, then publish the update again. If you're publishing multiple updates signed with different certificates, you'll need to unblock each certificate that is used.
      - For more information, see status messages 11523 and 11524 in the below status message table.
-- When the third-party software update synchronization service on the top-level software update point requires a proxy server for internet access, digital signature checks may fail. To mitigate this issue, configure the WinHTTP proxy settings on the site system. For more information, see [Netsh commands for WinHTTP](/windows-server/networking/technologies/netsh/netsh-http.md).
+- When the third-party software update synchronization service on the top-level software update point requires a proxy server for internet access, digital signature checks may fail. To mitigate this issue, configure the WinHTTP proxy settings on the site system. For more information, see [Netsh commands for WinHTTP](/windows-server/networking/technologies/netsh/netsh-http).
 - When using a CMG for content storage, the content for third-party updates won't download to clients if the **Download delta content when available** [client setting](../../core/clients/deploy/about-client-settings.md#allow-clients-to-download-delta-content-when-available) is enabled. <!--6598587-->
 - If the catalog provider has changed the catalog's signing certificate since you last approved it or subscribed, the catalog sync will fail until the certification is approved in the **Certificates** node. For more information, see MessageID 11508 in [status messages](#status-messages) table.