You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/linux-updates.md
+18-8Lines changed: 18 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 05/01/2024
18
+
ms.date: 07/10/2024
19
19
---
20
20
21
21
# Deploy updates for Microsoft Defender for Endpoint on Linux
@@ -34,17 +34,26 @@ ms.date: 05/01/2024
34
34
Microsoft regularly publishes software updates to improve performance, security, and to deliver new features.
35
35
36
36
> [!WARNING]
37
-
> Each version of Defender for Endpoint on Linux is set to expire automatically after 9 months. While expired versions continue to receive security intelligence updates, install the latest version to get all available fixes and enhancements. <br>
38
-
>To check the expiration date, run the following command:
37
+
> Each version of Defender for Endpoint on Linux is set to expire automatically after 9 months. While expired versions continue to receive security intelligence updates, install the latest version to get all available fixes and enhancements.
38
+
>To check the expiration date, run the following command:
39
39
> ```bash
40
40
> mdatp health --field product_expiration
41
41
>```
42
+
> Expired clients report a health issue and warning message when you run the following command:
43
+
>```bash
44
+
> mdatp health
45
+
>```
46
+
> Indicators of an expired client include the message, "**ATTENTION: No license found. Contact your administrator for help**." with the following attributes:
47
+
>```bash
48
+
> ATTENTION: No license found. Contact your administrator for help.
49
+
> healthy :false
50
+
> health_issues : ["missing license"]
51
+
> licensed :false
52
+
>```
42
53
54
+
Defender for Endpoint capabilities that are generally available are equivalent, regardless of which update channel is used for deployment (Beta (Insider), Preview (External), Current (Production)).
43
55
44
-
Generally available Microsoft Defender for Endpoint capabilities are equivalent regardless update channel used for a deployment (Beta (Insider), Preview (External), Current (Production)).
45
-
46
-
47
-
To update Defender for Endpoint on Linux manually, execute one of the following commands:
56
+
To update Defender for Endpoint on Linux manually, run one of the following commands:
> When Defender for Cloud is provisioning the Microsoft Defender for Endpoint agent to Linux servers, it will keep the client updated automatically.
77
+
> When Defender for Cloud is provisioning the Microsoft Defender for Endpoint agent to Linux servers, it keeps the client updated automatically.
69
78
70
79
To schedule an update of Microsoft Defender for Endpoint on Linux, see [Schedule an update of the Microsoft Defender for Endpoint (Linux)](linux-update-mde-linux.md)
80
+
71
81
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
Copy file name to clipboardExpand all lines: defender-xdr/pilot-deploy-defender-cloud-apps.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,7 +215,7 @@ You can begin to manage these apps with the following tasks:
215
215
216
216
For more information, including supported apps and clients, see [Protect apps with Microsoft Defender for Cloud Apps Conditional Access App Control](/cloud-app-security/proxy-intro-aad).
217
217
218
-
For example policies, see [Recommended Microsoft Defender for Cloud Apps policies for SaaS apps](/defender-office-365/zero-trust-identity-device-access-policies-mcas-saas). These policies build on a set of [common identity and device access policies](/defender-office-365/zero-trust-identity-device-access-policies-overview) that are recommended as a starting point for all customers.
218
+
For example policies, see [Recommended Microsoft Defender for Cloud Apps policies for SaaS apps](/security/zero-trust/zero-trust-identity-device-access-policies-mcas-saas). These policies build on a set of [common identity and device access policies](/security/zero-trust/zero-trust-identity-device-access-policies-overview) that are recommended as a starting point for all customers.
0 commit comments