Remove BreakingPoint Cloud as approved DDoS simulation partner

[ofirsar]

BreakingPoint Cloud is no longer an approved Azure DDoS Protection simulation testing partner. This PR removes all references to it from the simulation testing tutorial:

• Removed the BreakingPoint Cloud entry from the approved testing partners list.
• Updated the Public cloud availability note to reference only Red Button.
• Removed the BreakingPoint Cloud configuration subsection (intro, offerings, account note, example attack values table, screenshot, and blog/video note).

Remaining approved partners (MazeBolt, Red Button, RedWolf) are unchanged.

[learn-build-service-prod]

Learn Build status updates of commit 9ffeb48:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/ddos-protection/test-through-simulations.md	✅Succeeded

For more details, please refer to the build report.

[ofirsar]

@microsoft-github-policy-service agree company=Microsoft

[prmerger-automator]

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

[ofirsar]

I'm the product manager for Azure DDoS Protection. BreakingPoint Cloud is no longer an approved DDoS simulation testing partner, so this PR removes it from the approved partners list, the Public cloud availability note, and its configuration section. The remaining approved partners (MazeBolt, Red Button, RedWolf) are unchanged.

[ofirsar]

#sign-off

[prmerger-automator]

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

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Removes BreakingPoint Cloud from the Azure DDoS simulation testing tutorial to align with the updated list of approved DDoS simulation partners.

Changes:

• Removed BreakingPoint Cloud from the “approved testing partners” list.
• Updated the Public cloud availability note to reference only Red Button.
• Deleted the dedicated BreakingPoint Cloud configuration subsection (including links, example values, and media references).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Court72]

@duongau

Can you review the proposed changes?

Important: When the changes are ready for publication, adding 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