Plan Defender For Servers Select Plan
In brief
The Plan 1 documentation now defines a server as a device running a server operating system and links to the Defender for Servers FAQ.
What Defender admins need to know
Administrators can use the added definition and FAQ link when determining which devices the guidance applies to. No action is required.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
| Enable for resource | Yes | No | | Disable for resource | Yes | Yes |
- Plan 1 can be enabled and disabled at resource level. A server is defined as a device running a server operating system. For information, refer to Common questions about Defender for Servers.
- Plan 2 can't be enabled at the resource level, but you can disable the plan at the resource level.
Here are some use case examples to help you decide on Defender for Servers deployment scope.
@@ -80,7 +80,7 @@ We recommend enabling Defender for Servers at the subscription level, but you ca | **Enable for resource** | Yes | No |
| **Disable for resource** | Yes | Yes |
-- Plan 1 can be enabled and disabled at resource level.
+- Plan 1 can be enabled and disabled at resource level. A server is defined as a device running a server operating system. For information, refer to [Common questions about Defender for Servers](faq-defender-for-servers).
- Plan 2 can't be enabled at the resource level, but you can disable the plan at the resource level.
Here are some use case examples to help you decide on Defender for Servers deployment scope.
