Skip to content

Update faq-defender-for-servers.yml - #553

Open
pixel559 wants to merge 1 commit into
MicrosoftDocs:publicfrom
pixel559:patch-1
Open

Update faq-defender-for-servers.yml#553
pixel559 wants to merge 1 commit into
MicrosoftDocs:publicfrom
pixel559:patch-1

Conversation

@pixel559

Copy link
Copy Markdown

Information received from Support MDfC support team and MDfC EEE

Information received from Support MDfC support team and MDfC EEE
@prmerger-automator

Copy link
Copy Markdown
Contributor

@pixel559 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 1f36823:

✅ Validation status: passed

File Status Preview URL Details
defender-for-cloud/faq-defender-for-servers.yml ✅Succeeded

For more details, please refer to the build report.

@prmerger-automator

Copy link
Copy Markdown
Contributor

PRMerger Results

Issue Description
Yaml File(s) This PR includes changes to .yml file(s) owned by another author.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@pixel559 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-dirichards
v-dirichards requested a review from Copilot July 29, 2026 15:58
@v-dirichards

Copy link
Copy Markdown
Contributor

@ElazarK

Could you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding an approval and a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator

Copy link
Copy Markdown
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @ElazarK

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged Tracking label for the vendor PR Review team label Jul 29, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Defender for Servers FAQ to clarify how the Microsoft Defender for Endpoint license-based discount behaves on license renewal/extension, based on input from the support team.

Changes:

  • Adds a new clarification statement about discount continuation when the underlying license is renewed/extended.


The discount becomes effective starting on the approval date. It isn't retroactive.

The discount is not automatically continued when the licensed that served as basis for discount is being extended/renewed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants