I’m submitting this enhancement idea on behalf of my strategic client Microsoft.
Overview
• Microsoft is requesting enhanced Quality Check functionality to improve validation of URLs embedded within project responses
• The primary use case focuses on identifying URLs that return error pages such as “We are sorry, the page you requested cannot be found.”
• This capability is critical as Microsoft URLs frequently change, and broken, invalid, or unreachable links are not always immediately identified by content owners
Current Challenge
• During testing, Microsoft observed that Quality Check does not reliably identify all unreachable URLs in responses marked as Answered
• URLs that can not be found are passing Quality Check without any invalid URL or quality issue being reported
• Example of an invalid URL not currently flagged: https://www.microsoft.com/en-u
Proposed Enhancement
• Enhance Quality Check URL validation logic to detect unreachable URLs
• Introduce content level validation to identify common error messages such as “We are sorry, the page you requested cannot be found” and flag these URLs
Expected Impact
• Improves trust in Quality Check by ensuring all broken or unreachable links are consistently identified
• Reduces manual QA effort for enterprise teams managing high volumes of dynamic and frequently changing content
• Increases operational efficiency by delivering more accurate and actionable validation results
Thank you to the Product Team for your time and consideration. Please reach out if any further clarification is needed.
