Azure Patterns and Practices contributions

Azure Patterns and Practices content helps customers design, build, and operate solutions on Azure. The content comprises three content portfolios listed below. Contributions are encouraged through GitHub pull requests.

Portfolio	Summary	Repository
Azure Architecture Center	Guidance for architecting solutions on Azure using established patterns and practices, incorporating the five pillars of architectural excellence. Use the technology choices and guides to determine the services that are right for your workload's requirements.	https://github.com/MicrosoftDocs/architecture-center
Azure Well-Architected Framework	A set of guiding tenets to improve the quality of a workload. The framework consists of five pillars of architectural excellence to help produce a high-quality, stable, and efficient cloud architecture: reliability, security, cost optimization, operational excellence, and performance efficiency.	https://github.com/MicrosoftDocs/well-architected
Cloud Adoption Framework for Azure	A full lifecycle framework that enables cloud architects, IT professionals, and business decision-makers to achieve their cloud-adoption goals. Best practices, documentation, and tools help you create and implement business and technology strategies for the cloud.	https://github.com/MicrosoftDocs/cloud-adoption-framework

Propose changes to an article

You can propose small changes to content if you want to correct a typo or error, add a link, or add more details. Ensure that your contribution is technically accurate and provides helpful or valuable information in the context of the article. To get started, select the "Edit this document" pencil icon in the upper-right corner of the page you'd like to contribute to. See Edit Microsoft Learn documentation for more details.

If you can't directly propose changes through GitHub, you can also use the feedback experience at the bottom of the article you'd like to see improved. Please leave a detailed description of the change you'd like to see and why.