Skip to content

Commit efb0ff0

Browse files
committed
fixed typo
1 parent 652b9d6 commit efb0ff0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/defender-for-cloud/upcoming-changes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Important upcoming changes
33
description: Upcoming changes to Microsoft Defender for Cloud that you might need to be aware of and for which you might need to plan
44
ms.topic: overview
5-
ms.date: 01/08/2024
5+
ms.date: 01/09/2024
66
---
77

88
# Important upcoming changes to Microsoft Defender for Cloud
@@ -47,7 +47,7 @@ If you're looking for the latest release notes, you can find them in the [What's
4747

4848
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).
4949

50-
For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, you can ead [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
50+
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).
5151

5252
You can also check out the [common questions about the transition to Microsoft Defender Vulnerability Management solution](faq-scanner-detection.yml).
5353

0 commit comments

Comments
 (0)