Remove plug-in docs from checker page

Author: JesseParsons

powerapps-docs/maker/data-platform/use-powerapps-checker.md

@@ -19,11 +19,7 @@ search.app:
 
 To deliver on complex business requirements, model-driven app makers often can end up with highly advanced solutions that customize and extend the Microsoft Dataverse platform. With advanced implementations comes an increased risk where performance, stability, and reliability issues become introduced, which can negatively impact the user experience. Identifying and understanding how to resolve these issues can be complicated and time consuming. With the solution checker feature, you can perform a rich static analysis check on your solutions against a set of best practice rules and quickly identify these problematic patterns. After the check completes, you receive a detailed report that lists the issues identified, the components and code affected, and links to documentation that describes how to resolve each issue.
 
-> [!Important]
-> Starting March 2022, solution checker won’t analyze plugins in solutions. Plugin validations are being modernized and will eventually focus on the native plugin authoring time, which will help you detect and fix issues earlier.
-
 The solution checker analyzes these solution components: 
-- Dataverse plug-ins
 - Dataverse custom workflow activities 
 - Dataverse web resources (HTML and JavaScript)
 - Dataverse configurations, such as SDK message steps 
@@ -121,9 +117,9 @@ Here's a summary of each column in the report.
 |Component     |  The solution component where the issue was identified.        |   All      |
 |Location     |  The ___location and/or source file of the component where the issue that was identified occurred, such as the assembly or JavaScript file name.        |  All       |
 |Line  #     |  The line number reference of the issue in the impacted web resource component.       |  Web resources       |
-|Module     | Module name where the issue identified in the assembly was detected.     |   Plug-in or custom workflow activity      |
-|Type     | Type of the issue identified in the assembly.        | Plug-in or custom workflow activity        |
-|Member     |  Member of the issue identified in the assembly.      | Plug-in or custom workflow activity        |
+|Module     | Module name where the issue identified in the assembly was detected.     |   Custom workflow activity      |
+|Type     | Type of the issue identified in the assembly.        | Custom workflow activity        |
+|Member     |  Member of the issue identified in the assembly.      | Custom workflow activity        |
 |Statement     | The code statement or configuration that resulted in the issue.        |  All       |
 |Comments     | Details about the issue that include high-level resolution steps.         |  All       |
 
@@ -132,21 +128,6 @@ Here's a summary of each column in the report.
 
 |Solution component  |Rule name  |Rule description  |
 |---------|---------|---------|
-|Plug-in or workflow activity   | [il-specify-column](../../developer/data-platform/best-practices/work-with-metadata/retrieve-specific-columns-entity-via-query-apis.md?client=PAChecker&error=il-specify-column&source=featuredocs)  | Avoid selecting all columns via Dataverse query APIs.     |
-|Plug-in or workflow activity   | [meta-remove-dup-reg](../../developer/data-platform/best-practices/business-logic/do-not-duplicate-plugin-step-registration.md?client=PAChecker&error=meta-remove-dup-reg&source=featuredocs)     | Avoid duplicate Dataverse plug-in registrations.     |
-|Plug-in or workflow activity   | [il-turn-off-keepalive](../../developer/data-platform/best-practices/business-logic/set-keepalive-false-interacting-external-hosts-plugin.md?client=PAChecker&error=il-turn-off-keepalive&source=featuredocs)   | Set KeepAlive to false when interacting with external hosts in a Dataverse plug-in.     |
-|Plug-in or workflow activity   | [il-avoid-unpub-metadata](../../developer/data-platform/best-practices/work-with-metadata/retrieve-published-metadata.md?client=PAChecker&error=il-avoid-unpub-metadata&source=featuredocs)   | Avoid retrieving unpublished Dataverse metadata.     |
-|Plug-in or workflow activity   | [il-avoid-batch-plugin](../../developer/data-platform/best-practices/business-logic/avoid-batch-requests-plugin.md?client=PAChecker&error=il-avoid-batch-plugin&source=featuredocs)   | Avoid using batch request types in Dataverse plug-ins and workflow activities.    |
-|Plug-in or workflow activity   | [meta-avoid-reg-no-attribute](../../developer/data-platform/best-practices/business-logic/include-filtering-attributes-plugin-registration.md?client=PAChecker&error=meta-avoid-reg-no-attribute&source=featuredocs)  | Include filtering attributes with Dataverse plug-in registrations.    |
-|Plug-in or workflow activity   | [meta-avoid-reg-retrieve](../../developer/data-platform/best-practices/business-logic/limit-registration-plugins-retrieve-retrievemultiple.md?client=PAChecker&error=meta-avoid-reg-retrieve&source=featuredocs)  | Use caution with Dataverse plug-ins registered for Retrieve and RetrieveMultiple messages.    |
-|Plug-in or workflow activity   | [meta-remove-inactive](../../developer/model-driven-apps/best-practices/business-logic/remove-deactivated-disabled-configurations.md?client=PAChecker&error=meta-remove-inactive&source=featuredocs)    | Remove inactive configurations in Dataverse.    |
-|Plug-in or workflow activity   | [il-meta-avoid-crm2011-depr-message](/previous-versions/dynamics-crm2011/developers-guide/gg509038(v=crm.5)?client=PAChecker&error=il-avoid-crm2011-depr-message&source=featuredocs)  | Don't use Microsoft Dynamics CRM 2011 deprecated messages.     |
-|Plug-in or workflow activity   | [meta-avoid-crm4-event](../../developer/model-driven-apps/best-practices/index.md?client=PAChecker&error=meta-avoid-crm4-event&source=featuredocs) | Don't use Microsoft Dynamics CRM 4.0 plug-in registration stage.    |
-|Plug-in or workflow activity   | [il-avoid-specialized-update-ops](/previous-versions/dynamicscrm-2016/developers-guide/dn932124(v=crm.8)?client=PAChecker&error=il-avoid-specialized-update-ops&source=featuredocs)  | Don't use specialized update operation requests in Dataverse.    | 
-| Plug-in or workflow activity |  [il-use-autonumber-feature](../../developer/data-platform/best-practices/index.md?client=PAChecker&error=il-use-autonumber-feature)  |Use the auto number feature instead of a custom auto numbering solution. | 
-| Plug-in or workflow activity  | [il-avoid-parallel-plugin](../../developer/data-platform/best-practices/business-logic/do-not-use-parallel-execution-in-plug-ins.md?client=PAChecker&error=il-avoid-parallel-plugin)  | The usage of parallel patterns should be avoided within plug-ins.  |
-| Plug-in or workflow activity  | [il-avoid-lock-plugin](../../developer/data-platform/best-practices/index.md?client=PAChecker&error=il-avoid-lock-plugin)  | Avoid lock of static members in plug-ins.  |
-| Plug-in or workflow activity  | [meta-avoid-retrievemultiple-annotation](../../developer/data-platform/best-practices/index.md?client=PAChecker&error=meta-avoid-retrievemultiple-annotation)  | Avoid registering a plugin on RetrieveMultiple of annotation.  |
 |Web Resources  | [web-use-async](../../developer/model-driven-apps/best-practices/business-logic/interact-http-https-resources-asynchronously.md?client=PAChecker&error=web-use-async&source=featuredocs)  |  Interact with HTTP and HTTPS resources asynchronously.   |
 |Web Resources  | [web-avoid-modals](../../developer/model-driven-apps/clientapi/reference/xrm-navigation.md?client=PAChecker&error=web-avoid-modals&source=featuredocs)  | Avoid using modal dialogs.   |
 |Web Resources  | [web-avoid-crm2011-service-odata](../../developer/model-driven-apps/best-practices/business-logic/do-not-use-odata-v2-endpoint.md?client=PAChecker&error=web-avoid-crm2011-service-odata&source=featuredocs) | Don't target the Microsoft Dynamics CRM 2011 OData 2.0 endpoint.     |