Merge pull request #262020 from ElazarK/WI195353-qualys-notice

ttorble · web-flow · commit a103b327e50c · 2024-01-09T11:56:52.000Z
WI19553-qualys
diff --git a/articles/defender-for-cloud/TOC.yml b/articles/defender-for-cloud/TOC.yml
@@ -517,22 +517,22 @@
               displayName: mde, tvm, vulnerability, va, arc, hybrid, defender vulnerability
                 management
               href: deploy-vulnerability-assessment-defender-vulnerability-management.md
-            - name: Enable vulnerability scanning with the integrated Qualys scanner
-              displayName: qualys, va, vulnerability, arc, hybrid
-              href: deploy-vulnerability-assessment-vm.md
             - name: Enable vulnerability scanning with a Bring Your Own License (BYOL)
                 solution
               displayName: qualys, rapid7, vulnerability
               href: deploy-vulnerability-assessment-byol-vm.md
             - name: Automatically enable a vulnerability assessment solution
               displayName: qualys, rapid7, vulnerability, auto provision
               href: auto-deploy-vulnerability-assessment.md
-            - name: Transition to the integrated Microsoft Defender Vulnerability Management vulnerability assessment solution
+            - name: Transition to Microsoft Defender Vulnerability Management for servers
               displayName: qualys, rapid7, vulnerability, migrate, transition, Microsoft Defender Vulnerability Management, mdvm
               href: how-to-transition-to-built-in.md
             - name: Common questions 
               displayName: questions, common, MDVM, Qualys, BYOL, bring your own license, agent, consolidated, vulnerability, management, faq, frequently asked questions
               href: faq-scanner-detection.yml
+            - name: Enable vulnerability scanning with the integrated Qualys scanner (deprecated)
+              displayName: qualys, va, vulnerability, arc, hybrid
+              href: deploy-vulnerability-assessment-vm.md
         - name: Enable just-in-time access on VMs
           displayName: jit, management, ports
           href: just-in-time-access-usage.md
diff --git a/articles/defender-for-cloud/deploy-vulnerability-assessment-defender-vulnerability-management.md b/articles/defender-for-cloud/deploy-vulnerability-assessment-defender-vulnerability-management.md
@@ -3,13 +3,22 @@ title: Enable vulnerability scanning with Microsoft Defender Vulnerability Manag
 description: Enable, deploy, and use Microsoft Defender Vulnerability Management with Microsoft Defender for Cloud to discover weaknesses in your Azure and hybrid machines
 ms.topic: how-to
 ms.custom: ignite-2022
-ms.date: 06/29/2023
+ms.date: 01/08/2024
 ms.author: dacurwin
 author: dcurwin
 ---
 
 # Enable vulnerability scanning with Microsoft Defender Vulnerability Management
 
+> [!IMPORTANT]
+> Defender for Server's vulnerability assessment solution powered by Qualys, is on a retirement path that set to complete on **May 1st, 2024**. If you are a currently using the built-in vulnerability assessment powered by Qualys, you should plan to [transition to the Microsoft Defender Vulnerability Management vulnerability scanning solution](how-to-transition-to-built-in.md). 
+>
+> For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, see [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
+>
+> Check out the [common questions](faq-scanner-detection.yml) regarding the transition to Microsoft Defender Vulnerability Management.
+>
+> Customers who want to continue using Qualys, can do so with the [Bring Your Own License (BYOL) method](deploy-vulnerability-assessment-byol-vm.md).
+
 [Microsoft Defender Vulnerability Management](/microsoft-365/security/defender-vulnerability-management/defender-vulnerability-management) is included with Microsoft Defender for Servers and uses built-in and agentless scanners to:
 
 - Discover vulnerabilities and misconfigurations in near real time
diff --git a/articles/defender-for-cloud/deploy-vulnerability-assessment-vm.md b/articles/defender-for-cloud/deploy-vulnerability-assessment-vm.md
@@ -1,14 +1,23 @@
 ---
-title: Enable vulnerability scanning with the integrated Qualys scanner
+title: Enable vulnerability scanning with the integrated Qualys scanner (deprecated)
 description: Install a vulnerability assessment solution on your Azure machines to get recommendations in Microsoft Defender for Cloud that can help you protect your Azure and hybrid machines
 author: dcurwin
 ms.author: dacurwin
 ms.topic: how-to
 ms.custom: ignite-2022
-ms.date: 12/18/2023
+ms.date: 01/08/2024
 ---
 
-# Enable vulnerability scanning with the integrated Qualys scanner
+# Enable vulnerability scanning with the integrated Qualys scanner (deprecated)
+
+> [!IMPORTANT]
+> Defender for Server's vulnerability assessment solution powered by Qualys, is on a retirement path that set to complete on **May 1st, 2024**. If you are a currently using the built-in vulnerability assessment powered by Qualys, you should plan to [transition to the Microsoft Defender Vulnerability Management vulnerability scanning solution](how-to-transition-to-built-in.md). 
+>
+> For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, see [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
+>
+> Check out the [common questions](faq-scanner-detection.yml) regarding the transition to Microsoft Defender Vulnerability Management.
+>
+> Customers who want to continue using Qualys, can do so with the [Bring Your Own License (BYOL) method](deploy-vulnerability-assessment-byol-vm.md).
 
 A core component of every cyber risk and security program is the identification and analysis of vulnerabilities. Defender for Cloud regularly checks your connected machines to ensure they're running vulnerability assessment tools.
 
diff --git a/articles/defender-for-cloud/faq-scanner-detection.yml b/articles/defender-for-cloud/faq-scanner-detection.yml
@@ -1,13 +1,13 @@
 ### YamlMime:FAQ
 metadata:
-  title: Common questions - the built-in Microsoft Defender Vulnerability Management solution
+  title: Common questions about the built-in Microsoft Defender Vulnerability Management solution
   description: Frequently asked general questions about the built-in Microsoft Defender Vulnerability Management solution
   services: defender-for-cloud
   author: elkrieger
   ms.author: elkrieger
   manager: raynew
   ms.topic: faq
-  ms.date: 12/03/2023
+  ms.date: 01/08/2024
 title: Common questions about the built-in Microsoft Defender Vulnerability Management solution
 summary: |
 
diff --git a/articles/defender-for-cloud/how-to-transition-to-built-in.md b/articles/defender-for-cloud/how-to-transition-to-built-in.md
@@ -1,13 +1,22 @@
 ---
-title: Transition to the integrated Microsoft Defender Vulnerability Management vulnerability assessment solution
+title: Transition to Microsoft Defender Vulnerability Management for servers
 description: Learn how to transition to the Microsoft Defender Vulnerability Management solution in Microsoft Defender for Cloud
 services: defender-for-cloud
 ms.service: defender-for-cloud
 ms.topic: how-to
-ms.date: 12/18/2023
+ms.date: 01/09/2024
 ---
 
-# Transition to the integrated Microsoft Defender Vulnerability Management vulnerability assessment solution
+# Transition to Microsoft Defender Vulnerability Management for servers
+
+> [!IMPORTANT]
+> Defender for Server's vulnerability assessment solution powered by Qualys, is on a retirement path that is set to complete on **May 1st, 2024**. If you are a currently using the built-in vulnerability assessment powered by Qualys, you should plan to transition to the Microsoft Defender Vulnerability Management vulnerability scanning using the steps on this page. 
+>
+> For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, see [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
+>
+> Check out the [common questions](faq-scanner-detection.yml) regarding the transition to Microsoft Defender Vulnerability Management.
+>
+> Customers who want to continue using Qualys, can do so with the [Bring Your Own License (BYOL) method](deploy-vulnerability-assessment-byol-vm.md).
 
 With the Defender for Servers plan in Microsoft Defender for Cloud, you can scan compute assets for vulnerabilities. If you're currently using a vulnerability assessment solution other than the Microsoft Defender Vulnerability Management vulnerability assessment solution, this article provides instructions on transitioning to the integrated Defender Vulnerability Management solution.
 
diff --git a/articles/defender-for-cloud/upcoming-changes.md b/articles/defender-for-cloud/upcoming-changes.md
@@ -2,7 +2,7 @@
 title: Important upcoming changes
 description: Upcoming changes to Microsoft Defender for Cloud that you might need to be aware of and for which you might need to plan 
 ms.topic: overview
-ms.date: 01/03/2024
+ms.date: 01/09/2024
 ---
 
 # Important upcoming changes to Microsoft Defender for Cloud
@@ -25,6 +25,7 @@ If you're looking for the latest release notes, you can find them in the [What's
 
 | Planned change | Announcement date | Estimated date for change |
 |--|--|--|
+| [Defender for Servers built-in vulnerability assessment (Qualys) retirement path](#defender-for-servers-built-in-vulnerability-assessment-qualys-retirement-path) | January 9, 2024 | May 2024 |
 | [Retirement of the Defender for Cloud Containers Vulnerability Assessment powered by Qualys](#retirement-of-the-defender-for-cloud-containers-vulnerability-assessment-powered-by-qualys) | January 9, 2023 | March 2024 |
 | [New version of Defender Agent for Defender for Containers](#new-version-of-defender-agent-for-defender-for-containers) | January 4, 2024 | February 2024 |
 | [Upcoming change for the Defender for Cloud’s multicloud network requirements](#upcoming-change-for-the-defender-for-clouds-multicloud-network-requirements) | January 3, 2024 | May 2024 |
@@ -39,6 +40,18 @@ If you're looking for the latest release notes, you can find them in the [What's
 | [Deprecating two security incidents](#deprecating-two-security-incidents) |  | November 2023 |
 | [Defender for Cloud plan and strategy for the Log Analytics agent deprecation](#defender-for-cloud-plan-and-strategy-for-the-log-analytics-agent-deprecation) |  | August 2024 |
 
+## Defender for Servers built-in vulnerability assessment (Qualys) retirement path
+
+**Announcement date: January 9, 2024**
+
+**Estimated date for change: May 2024**
+
+The Defender for Servers built-in vulnerability assessment solution powered by Qualys is on a retirement path which is estimated to complete on **May 1st, 2024**. If you are currently using the vulnerability assessment solution powered by Qualys, you should plan your [transition to the integrated Microsoft defender vulnerability management solution](how-to-transition-to-built-in.md).
+ 
+For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, you can read [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
+
+You can also check out the [common questions about the transition to Microsoft Defender Vulnerability Management solution](faq-scanner-detection.yml).
+
 ## Retirement of the Defender for Cloud Containers Vulnerability Assessment powered by Qualys
 
 **Announcement date: January 9, 2023**
