Merge pull request #116419 from memildin/asc-melvyn-vmva

No need for an upgrade procedure from 1.0.0.4 any more

Author: PRMerger20

articles/security-center/built-in-vulnerability-assessment.md

@@ -167,28 +167,6 @@ You'll need the following details:
 ### How does the extension get updated?
 Like the Azure Security Center agent itself and all other Azure extensions, minor updates of the Qualys scanner may automatically happen in the background. All agents and extensions are tested extensively before being automatically deployed.
 
-If you're running v1.0.0.4, you must manually update the vulnerability scanner extension using the steps below. This procedure also shows you how to check the version of the scanner currently deployed to your VMs.
-
-1. From the Azure portal, open **Virtual machines**.
-
-1. Select the VM on which the extension is installed.
-
-1. From the sidebar navigation, open **Extensions** and select the following extension:
-
-    Name: **WindowsAgent.AzureSecurityCenter** Type: **Qualys.WindowsAgent.AzureSecurityCenter**
-
-1. Review the version information of the extension.
-
-    ![Qualys agent extension version information](media/built-in-vulnerability-assessment/qualys-agent-extension-version.png)
-
-1. If the version is 1.0.0.4, click **Uninstall** and wait until the extension is no longer listed in the VM's extensions page.
-
-1. Restart the VM.
-    
-1. When the VM's status is "Running", deploy the extension as described above in [Deploying the Qualys built-in vulnerability scanner](#deploying-the-qualys-built-in-vulnerability-scanner).
-
-
-
 ### Why does my VM show as "not applicable" in the recommendation?
 The recommendation details page for the **"Enable the built-in vulnerability assessment solution on virtual machines (powered by Qualys)"** recommendation groups your VMs in one or more of the following lists: **Healthy resources**, **Unhealthy resources**, and **Not applicable resources**.