Docs: Recommend Defender for Servers Plan 2 as preferred server onboarding option#505
Open
jongABCDsudo-rm-rf wants to merge 1 commit into
Conversation
Contributor
|
Learn Build status updates of commit 20c7e45: ✅ Validation status: passed
For more details, please refer to the build report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an explicit recommendation in the "Server plans" section of
defender-endpoint/onboard-server.mdidentifying Microsoft Defender for Servers Plan 2 as the preferred onboarding option for server workloadsToday the article lists three valid licensing options without indicating which one Microsoft recommends for typical scenarios:
Customers and partners frequently default to the standalone "Microsoft Defender for Endpoint for servers" SKU on the assumption it is functionally equivalent to Defender for Servers Plan 2, missing capabilities that are specific to Plan 2.
This guidance is already implied across
azure/defender-for-cloud/defender-for-servers-overview.mdandazure/defender-for-cloud/plan-defender-for-servers-select-plan.md, but it is not surfaced on the Defender for Endpoint server onboarding entry-point article that most readers land on first.Related