resolved conflicts#128541
Open
tanvishinde017 wants to merge 29 commits into
Open
Conversation
Corrected grammar and formatting in migration documentation.
Revised customer intent statement for clarity and completeness.
Improve App Service plan documentation readability and formatting consistency
Updated summaries and titles for clarity and consistency. Revised descriptions and links for better understanding of Azure App Testing features.
Improve Azure App Testing landing page readability and content organization
Updated the FAQ article for WordPress on Azure App Service to enhance descriptions, correct terminology, and improve clarity on various topics including security, performance, and configuration.
## Summary Enhanced the WordPress on Azure App Service FAQ documentation by improving content structure, refining technical explanations, and expanding operational guidance for deployment, security, monitoring, scaling, and troubleshooting scenarios. ## Key improvements ### Documentation quality and readability * Refined article introduction and FAQ flow for improved discoverability * Standardized formatting, capitalization, and terminology across all sections * Improved readability of technical explanations and operational guidance * Simplified complex configuration workflows into clearer step-based guidance ### Security and identity enhancements * Expanded security recommendations for App Service, MySQL Flexible Server, and Microsoft Entra integrations * Clarified managed identity authentication and phpMyAdmin access workflows * Improved guidance for HTTPS, VNet integration, Key Vault, and Defender for Cloud scenarios * Enhanced explanations for enterprise authentication and access management ### Performance and scalability guidance * Improved recommendations for scaling, caching, and enterprise-grade deployments * Enhanced guidance for Azure Front Door, Blob Storage, Redis Cache, and dynamic caching integrations * Clarified App Service plan sizing considerations and hosting capacity recommendations * Added more actionable performance optimization references ### Troubleshooting and monitoring improvements * Reorganized debugging and monitoring sections for easier navigation * Improved troubleshooting guidance for common WordPress deployment issues * Enhanced log access, Kudu, SSH, and diagnostic workflow explanations * Refined phpMyAdmin and database access documentation for clarity and operational accuracy ### Developer and deployment experience * Improved CI/CD, startup script, and configuration guidance * Enhanced documentation for custom domains, multisite deployments, and headless WordPress architectures * Updated enterprise deployment recommendations and production readiness guidance * Improved consistency across external references and Azure service integrations ## Files updated * `articles/app-service/wordpress-faq.md` ## Impact These updates improve the overall developer and administrator experience by making the FAQ easier to navigate, more technically accurate, and more actionable for enterprise WordPress deployments on Azure App Service. The revised structure and guidance help users better understand operational best practices, troubleshoot issues more efficiently, and deploy scalable, secure, production-ready WordPress environments on Azure.
Updated the article to clarify the usage of Azure Key Vault references in app settings and connection strings, including access permissions and troubleshooting.
## Summary Added comprehensive Markdown documentation for using Azure Key Vault references as application settings in: - Azure App Service - Azure Functions - Azure Logic Apps (Standard) ## Changes Included - Added managed identity configuration guidance - Documented Key Vault access setup and RBAC permissions - Added support details for user-assigned identities - Included network-restricted vault configuration - Added secret rotation and refresh behavior documentation - Documented Key Vault reference formats with examples - Added Azure Files mounting considerations - Included Application Insights integration notes - Added ARM template deployment examples - Improved troubleshooting guidance and diagnostics steps - Added security and deployment best practices ## Benefits - Improves readability and maintainability of documentation - Provides end-to-end guidance for secure secret management - Helps developers implement production-ready Key Vault integration - Simplifies onboarding for App Service and Functions users
Updated the agent registry overview to enhance clarity and detail, including improved descriptions and structured sections for key features, registration, management, and dependency tracking.
Fix formatting of link in agent overview documentation
Updated the access tokens documentation for clarity and accuracy, including changes to the customer intent, access token descriptions, and scope explanations.
Revise access tokens documentation for clarity
Update overview-what-is-azure-app-testing.md
Contributor
|
Learn Build status updates of commit 99cf52f: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
Contributor
|
Learn Build status updates of commit a51cfa8:
|
Expanded the README file to provide detailed guidance on contributing to Microsoft Azure documentation, including sections on prerequisites, contribution workflow, documentation standards, and additional resources.
Strengthen contributor onboarding by enhancing Azure documentation README
prmerger-automator
Bot
assigned
cephalin,
dlepow,
kengaderdus,
msangapu-msft and
NandiniMurali
prmerger-automator
Bot
requested review from
NandiniMurali,
cephalin,
dlepow,
kengaderdus and
msangapu-msft
Contributor
|
@tanvishinde017 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
Bot
added
azure-app-testing/svc
B2C/subsvc
Change sent to author
labels
Strengthen contributor onboarding by enhancing Azure documentation README
Contributor
|
Learn Build status updates of commit a6b51a9:
|
Contributor
|
Learn Build status updates of commit 992ae1f:
|
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
6 participants
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.
No description provided.