Add Azure security documentation and best practices for .NET Aspire deployments #4051
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.
This PR adds comprehensive Azure security documentation for .NET Aspire deployments as requested in the issue. The new article covers:
What's included
New documentation:
docs/deployment/azure/azure-security-best-practices.md
Default security posture
Additional security hardening
Production considerations
Security monitoring and incident response
Changes made
docs/deployment/azure/azure-security-best-practices.md
(203 lines)docs/toc.yml
to include the new article in the Deploy > Azure sectionThe documentation follows the Microsoft Writing Style Guide and matches the existing documentation patterns, including proper front matter, code examples, and cross-references to related articles.
Fixes #1766.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Internal previews