create new article

Author: aczechowski

memdocs/configmgr/protect/TOC.yml

@@ -25,6 +25,8 @@ items:
       href: plan-design/security-and-privacy-for-wifi-vpn-profiles.md
     - name: Certificate profiles
       href: plan-design/security-and-privacy-for-certificate-profiles.md
+  - name: Resource access deprecation FAQ
+    href: plan-design/resource-access-deprecation-faq.yml
 - name: Deploy and use
   items:
   - name: Endpoint Protection

memdocs/configmgr/protect/plan-design/resource-access-deprecation-faq.yml

@@ -0,0 +1,59 @@
+### YamlMime:FAQ
+metadata:
+  title: FAQ for resource access deprecation
+  titleSuffix: Configuration Manager
+  description: Frequently asked questions (FAQ) about the end of support for compliance settings for company resource access features.
+  author: aczechowski
+  ms.author: aaroncz
+  ms.reviewer: dannygu
+  manager: dougeby
+  ms.date: 02/17/2022
+  ms.topic: faq
+  ms.prod: configuration-manager
+  ms.technology: configmgr-protect
+  ms.localizationpriority: medium
+
+title: Frequently asked questions about resource access deprecation
+summary: |
+  *Applies to: Configuration Manager (current branch)* 
+
+  Starting in Configuration Manager version 2103, the following company resource access [features are deprecated](../../core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md):<!-- 9315387 -->
+
+  - Certificate profiles
+  - VPN profiles
+  - Wi-Fi profiles
+  - Windows Hello for Business settings
+  - Email profiles
+  - The co-management resource access workload
+
+  This article answers your frequently asked questions about these deprecated features.
+
+sections:
+  - name: Ignored
+    questions:
+      - question: |
+          Will these features be removed from Configuration Manager?
+        answer: |
+          Yes. In version 2203, these features will no longer be available. If you're actively using these features, don't upgrade to version 2203.
+
+      - question: |
+          What functionality is available to replace these features?
+        answer: |
+          Use Microsoft Intune to deploy resource access profiles. For more information, see [Apply features and settings on your devices using device profiles in Microsoft Intune](../../../intune/configuration/device-profiles.md).
+
+          Use [co-management](../../comanage/overview.md) to enroll Configuration Manager clients to Intune.
+
+      - question: |
+          What do I do if I'm deploying wi-fi profiles with Configuration Manager?
+        answer: |
+          Before you upgrade to Configuration Manager version 2203, [enable co-management](../../comanage/how-to-enable.md), and deploy the same wi-fi profiles with Intune. For more information, see [Add and use Wi-Fi settings on your devices in Microsoft Intune](../../../intune/configuration/wi-fi-settings-configure.md).
+
+      - question: |
+          What happens if I don't enable co-management?
+        answer: |
+          If you upgrade to version 2203, you can't deploy any wi-fi, VPN, Windows Hello for Business, or certificate (SCEP, PFX, or root CA) profiles to Configuration Manager clients. Any existing deployed profiles won't remove from devices. For example, existing wi-fi connections should still function, and certificates won't be removed from Windows.
+
+      - question: |
+          What happens if I've enabled co-management, but haven't switched the resource access workload?
+        answer: |
+          Starting in version 2203, the behavior is the same as the workload switched to Intune.