Merge pull request #7942 from MicrosoftDocs/main

Release CM2207TP

Author: mestew

memdocs/configmgr/core/TOC.yml

@@ -285,6 +285,8 @@ items:
     items:
     - name: Technical Preview overview
       href: get-started/technical-preview.md
+    - name: 2207 features
+      href: get-started/2022/technical-preview-2207.md       
     - name: 2206 features
       href: get-started/2022/technical-preview-2206.md           
     - name: 2205 features

memdocs/configmgr/core/get-started/2022/includes/2207/10928371.md

@@ -0,0 +1,99 @@
+---
+author: paasin
+ms.author: paasin
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 07/04/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_dpconmig"></a> Distribution point content migration
+<!--10928371-->
+Distribution point content migration support is now available for migrating content from one distribution point to another distribution point using PowerShell cmdlets. You can also monitor the distribution point migration status using these PowerShell cmdlets. 
+
+There are multiple scenarios where the content of one distribution point needs to be migrated to another distribution point. 
+1) Cloud distribution points (CDP) hosted on Azure classic services are getting deprecated by mid of 2024. You need to migrate CDP content to another distribution point.
+2) Migration of cloud migration gateway v1 (CMGv1) hosted with *.cloudapp.net domain is also getting deprecated, hence you may need to migrate CMGv1 content to another distribution point.
+3) You may need to migrate local distribution point content to other local distribution point or CMG. 
+
+#### Prerequisites
+
+1) The user's security role permission should have "Copy to Distribution Point" enabled under Distribution Point.
+2) If you want to deprecate the source distribution point, make sure that the source and destination distribution points have the same boundary group.
+3) The destination distribution point should be installed already and able to receive the content. 
+
+> [!NOTE]
+> You can't currently configure this behavior from the Configuration Manager console. For more information on configuring this behavior with PowerShell, see the cmdlet details in the following section. 
+
+### Start-CMDistributionPointMigration 
+
+Use this cmdlet to initiate distribution point content migration. You can pass the desired parameters such as SourceDistributionPointName and DestinationDistributionPointName per your distribution point migration scenario. 
+You can also pass the LockSourceDistributionPoint parameter to lock the source distribution point. This parameter is used to deprecate the source distribution point scenarios (for example: CDP Migration). If the source distribution point is locked during distribution point migration, you won't be able to distribute the new content to the source distribution point, but the endpoints will be able to download the content that is already available in the source distribution point. 
+For deprecation scenarios, you can delete the source distribution point after the distribution content migration is completed.  
+
+#### Syntax
+
+```powershell
+Start-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> 
+```
+
+#### Examples
+
+```powershell
+Start-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> -LockSourceDistributionPoint  
+
+Start-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> 
+```
+
+#### Parameters
+
+- **SourceDistributionPointName**: Use this to specify the source distribution point from where content will be migrated.
+
+- **DestinationDistributionPointName**: Use this to specify the destination distribution point where you want the content to be copied.
+
+- **LockSourceDistributionPoint**: Use when you need to initiate distribution point migration with source distribution point locked. 
+
+
+### Get-CMDistributionPointMigrationStatus 
+
+Use this cmdlet to monitor the distribution point migration status.
+
+#### Syntax
+
+```powershell
+Get-CMDistributionPointMigrationStatus -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> 
+```
+
+### Get-CMDistributionPointContentMigrationStatus 
+
+Use this cmdlet to monitor the distribution point content migration status.
+
+#### Syntax
+
+```powershell
+Get-CMDistributionPointContentMigrationStatus -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point>
+```
+
+### Stop-CMDistributionPointMigration 
+
+Use this cmdlet to stop the distribution point migration. In case you have mistakenly locked the source distribution point, you can use this cmdlet to unlock the source distribution point. Unlocking the source distribution point will stop the distribution point migration. To restart the migration, use the Start-CMDistributionPointMigration cmdlet.
+
+#### Syntax
+
+```powershell
+Stop-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> 
+```
+
+#### Examples
+
+```powershell
+Stop-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> -LockSourceDistributionPoint  
+
+Stop-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> 
+```
+
+> [!NOTE]
+> You won't be able to perform multiple migrations at a shared time. Migration for one set of source and destination distribution points needs to be completed before starting another.
+
+

memdocs/configmgr/core/get-started/2022/includes/2207/14059872.md

@@ -0,0 +1,19 @@
+---
+author: baladell
+ms.author: baladell
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 07/01/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_app-guard"></a> Improvements to Configuration Manager policies for Microsoft Defender Application Guard
+<!-- 14059872 -->
+
+1. Windows Defender Application Guard has been renamed to [Microsoft Defender Application Guard](../../../../../protect/deploy-use/create-deploy-application-guard-policy.md) in the Configuration Manager console.
+1. The **General** settings page allows you to enable for isolated Windows environments and enable for Microsoft Edge and isolated Windows environments.
+1. The **Application Behavior** settings page allows you to enable or disable cameras and microphones, along with certificate matching the thumbprints to the isolated container.
+1. The following items were removed:
+   - The [Enterprise sites can load non-enterprise content, such as third-party plug-ins](../../../../../protect/deploy-use/create-deploy-application-guard-policy.md#bkmk_ABS) setting under the **Host interaction** page
+   - The file trust criteria policy in the **File Management** page