185
Pages Scanned
19
Pages Flagged
185
Changed Pages
10.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-10 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 185
Files Completed: 185
Problematic Pages
19 issues found
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
powershell_heavy
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tooling references are for Visual Studio 2022 (Windows), with no mention of Linux/macOS alternatives. PowerShell and Package Manager Console commands are provided, but no equivalent CLI or cross-platform instructions. The publish workflow, database management, and log streaming are all described using Windows-centric tools and UI, creating friction for Linux/macOS users.
Recommendations
- Add instructions for using Visual Studio Code or the .NET CLI for cross-platform development, publishing, and database migrations.
- Provide Azure CLI or Bash equivalents for PowerShell commands, especially for database setup and managed identity configuration.
- Include screenshots and steps for deploying from Linux/macOS environments, or at least note the differences and limitations.
- Mention alternative tools for database management (such as Azure Data Studio or SQLCMD) usable on Linux/macOS.
- Clarify which steps are Windows-only and provide links or guidance for Linux/macOS users where possible.
Create Pull Request
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation references enabling DDoS IP Protection for a public IP address via a linked page that uses PowerShell, but does not mention or provide examples for Linux/macOS users (such as Azure CLI or Bash). The main instructions focus on the Azure Portal, which is platform-agnostic, but the PowerShell reference creates friction for non-Windows users.
Recommendations
- Add Azure CLI examples for enabling DDoS IP Protection, alongside PowerShell instructions.
- Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for equivalent tasks.
- Provide links to cross-platform command-line documentation where relevant.
API Management
Add a Custom CA Certificate - API Management | Microsoft Docs
...api-management/api-management-howto-ca-certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not universally available or preferred on other platforms.
Recommendations
- Add Azure CLI example(s) for uploading a CA certificate, as Azure CLI is cross-platform.
- Mention REST API options for certificate upload, with example requests.
- Clarify that PowerShell is one option, and provide parity for Linux/macOS users.
- Consider linking to documentation on using PowerShell Core on Linux/macOS if PowerShell must be used.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is primarily focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (such as Test-NetConnection and netstat -aon) are given using Windows/PowerShell tools, with no Linux/macOS equivalents provided. The use of Windows-specific commands and lack of Linux guidance creates friction for users who may need to debug from non-Windows environments, even if the feature itself is Windows-only.
Recommendations
- Clarify early and prominently that all operational steps and troubleshooting are Windows-specific due to the feature limitation.
- Where troubleshooting involves connecting to VMs or network endpoints, provide equivalent Linux/macOS commands (e.g., 'nc', 'telnet', 'ss', 'netstat', 'dig') alongside PowerShell examples.
- Explicitly state that Linux App Service plans cannot use this feature, and link to Linux-compatible alternatives (such as regional virtual network integration).
- Add a section summarizing Linux/macOS limitations and recommended approaches for similar tasks.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC permissions, but PowerShell is given equal prominence and referenced in multiple places. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned as options for exporting certificates, while Linux tools (OpenSSL) are referenced but not explained in as much detail. Windows tooling is mentioned before Linux equivalents in some sections, and links to Windows documentation are provided for certificate export. The FAQ and automation sections reference PowerShell scripts alongside CLI, but do not provide Bash or Linux-native scripting examples.
Recommendations
- Provide Linux/macOS-specific instructions and examples for certificate export, including detailed OpenSSL usage and troubleshooting.
- Add Bash scripting examples for automation alongside PowerShell and Azure CLI.
- When referencing certificate export tools, mention OpenSSL first, and provide links to Linux/macOS documentation.
- Ensure parity in screenshots and UI descriptions for Linux/macOS users where relevant.
- Clarify which steps are OS-agnostic and which are Windows-specific, to help users on non-Windows platforms.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides step-by-step instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI examples are exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell instructions are presented before ARM template examples, and there is no mention of Linux/macOS-specific workflows or tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
- Add Azure CLI examples for all PowerShell workflows, especially for creating and updating API Management instances with managed identities.
- Explicitly mention that Azure CLI is cross-platform and provide links to relevant Azure CLI documentation.
- Where possible, show both PowerShell and Azure CLI code blocks side-by-side or in tabs.
- Clarify any limitations or differences between PowerShell and Azure CLI for these operations.
- Consider referencing Bash scripting for ARM template deployment, which is common on Linux/macOS.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is structured with clear pivots for Windows and Linux containers, providing parity in most sections. However, Windows-specific examples, tools (PowerShell), and terminology (e.g., C:\home) are often presented first or in more detail. PowerShell commands are shown alongside Bash/Azure CLI, but Windows-centric explanations (such as IIS, .NET Framework, and Windows Server images) are more prominent. Some sections (like customizing memory and CPU cores) provide Windows-specific instructions and verification steps using PowerShell, with no Linux equivalent. The use of Windows terminology (e.g., C:\home) sometimes appears in Linux sections, which could confuse Linux users.
Recommendations
- Ensure Linux examples and terminology (e.g., /home instead of C:\home) are presented first or equally alongside Windows examples in all relevant sections.
- Provide Linux-specific verification steps (e.g., checking CPU cores or memory limits) using Bash or Linux tools, not just PowerShell.
- Clarify when instructions or settings differ between Windows and Linux containers, and avoid mixing Windows paths or concepts in Linux container guidance.
- Where PowerShell is used, ensure Bash/Linux equivalents are always present and equally detailed.
- Review sections for unnecessary Windows-centric language or assumptions, especially in Linux pivots.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific certificate store access is described in detail with C# and Java code samples, while Linux guidance is less prominent and mostly limited to file-based access. Windows examples and terminology (certificate store, thumbprint, environment variables) are presented first and in greater depth. For non-Windows languages (Node.js, PHP, Python), Linux-specific code samples are missing, and users are referred to external documentation. Windows tools and patterns (certificate store, environment variables) are emphasized, and Linux equivalents are not always provided.
Recommendations
- Add Linux-specific code samples for popular languages (Node.js, Python, PHP, Java) showing how to load certificates from the injected file paths.
- Present Linux and Windows guidance in parallel, rather than Windows-first, especially in introductory and critical sections.
- Expand explanations of Linux certificate handling, including environment variables and file permissions.
- Clarify any differences in certificate formats or handling between Windows and Linux containers.
- Provide links to relevant Linux documentation or official guides for certificate handling in various languages.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given immediately after Bash, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may indicate a slight preference for Windows environments. There are no Linux-specific tools or patterns mentioned, but Linux users are not missing any critical information.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with explicit labels.
- Consider showing Bash examples first, or providing a brief note about cross-platform compatibility.
- Add a short explanation for users on Linux/macOS about how to use Azure CLI in their environment, if relevant.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is mentioned alongside CLI in prerequisites and deployment sections. Azure PowerShell is a Windows-centric tool, and its inclusion may imply Windows preference. However, Azure CLI examples are present and shown first in the deployment section, ensuring Linux/macOS users can follow along. No Windows-only tools or patterns are used, and Linux parity is mostly maintained.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and is recommended for those platforms.
- Consider adding a note about using Azure Cloud Shell for cross-platform compatibility.
- Ensure that CLI examples are always shown first, as is done here.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides instructions primarily via the Azure portal and Azure CLI, with a brief mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI example, and no Windows-specific tools or patterns are prioritized. No PowerShell-heavy or Windows-only examples are present, and Linux parity is generally maintained. However, Azure PowerShell is mentioned before 'other Azure tools,' which could be considered a minor 'windows_first' bias.
Recommendations
- When listing tools for managing API Management instances, mention Azure CLI and PowerShell together, clarifying that both are cross-platform.
- Provide explicit examples for both Azure CLI and Azure PowerShell where relevant, and note that Azure CLI is available on Linux/macOS.
- If referencing 'other Azure tools,' consider linking to cross-platform options or clarifying their OS compatibility.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for Azure CLI commands. However, in each case, the PowerShell example is presented immediately after the Bash example, and the PowerShell code is explicitly labeled as 'Formatted for PowerShell.' This approach is inclusive, but the PowerShell examples are given equal prominence, which may be interpreted as a slight Windows bias. There are no missing Linux examples, and all tasks can be completed on Linux/macOS.
Recommendations
- Continue to provide both Bash and PowerShell examples for cross-platform parity.
- Consider clarifying in the documentation that Bash examples are for Linux/macOS and PowerShell for Windows, to help users quickly identify the relevant sections.
- Optionally, use tabbed code blocks labeled 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to further improve clarity and parity.
- Ensure that any future updates maintain parity between Linux/macOS and Windows examples.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but the presence of PowerShell examples and references (including devx-track-azurepowershell metadata) may indicate a slight Windows bias. However, Azure CLI examples are also present and shown first, which helps Linux/macOS parity. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the Azure CLI is cross-platform.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and Windows.
- Add a Bash shell example for Linux users, or clarify that Azure CLI commands can be run in Bash.
- Consider referencing Azure Cloud Shell as a cross-platform option.
- Ensure that any prerequisites or environment setup instructions are not Windows-centric.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples for backup and restore operations, with PowerShell shown first in each section. While Azure CLI and REST API examples are also included, the PowerShell examples are more prominent and detailed, which may create friction for Linux/macOS users who do not use PowerShell. There is no evidence of missing Linux examples, as Azure CLI (bash) and REST API methods are documented, but the ordering and depth of PowerShell coverage suggest a Windows bias.
Recommendations
- Present Azure CLI (bash) examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Ensure that Azure CLI examples are as detailed and comprehensive as PowerShell examples, including managed identity scenarios.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI and REST API, and clarify any limitations.
- Consider adding a summary table comparing PowerShell, Azure CLI, and REST API approaches for quick reference.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a first-class option alongside CLI. The prerequisites list Azure CLI and Azure PowerShell equally, and PowerShell examples are given their own section. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for CLI commands, but the CLI example is cross-platform. The documentation does not use Windows-only tools or patterns, but PowerShell is a Windows-centric shell, and its inclusion without Bash or Linux shell alternatives may create friction for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Consider adding Bash or shell script examples for Linux users, or clarify that Azure CLI commands are suitable for Linux/macOS.
- Mention PowerShell Core compatibility if relevant, since PowerShell Core runs on Linux/macOS.
- List Azure CLI as the preferred cross-platform tool in prerequisites and examples, with PowerShell as an optional Windows-centric alternative.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a standard workflow alongside CLI, which may create friction for Linux/macOS users. The CLI example is cross-platform, but the lack of explicit Linux/macOS context or examples (such as Bash or zsh) and the inclusion of PowerShell as a main tab suggest a mild Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider adding Bash/zsh shell examples for Linux/macOS users, or explicitly note that PowerShell is optional and CLI is cross-platform.
- Reorder examples to show Azure CLI first, and PowerShell as an alternative for Windows users.
- Add a note about how to install and use Azure CLI on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but most Linux/macOS users prefer Bash/zsh.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and resource management steps. Azure CLI is cross-platform, while PowerShell is primarily associated with Windows, though it is available on Linux/macOS. The CLI examples are always presented before PowerShell, and there are no Windows-specific tools or patterns prioritized. No Linux/macOS-specific examples or shell scripts are provided, but the CLI coverage ensures parity.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash shell script examples for Linux/macOS users, especially for automation.
- Clarify that PowerShell examples are for users who prefer PowerShell, which is now cross-platform.
- Add a note about Azure CLI installation on Linux/macOS for completeness.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements for API Management virtual network injection. However, there is a minor bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks from different deployment models, without mentioning equivalent CLI or Linux-friendly options. No Windows-specific tools, patterns, or examples are present in the main guidance.
Recommendations
- In the 'Related content' section, add links to equivalent guides using Azure CLI or ARM templates for connecting virtual networks, ensuring Linux/macOS users have clear, first-class options.
- Where PowerShell is referenced, clarify that Azure CLI and Portal options exist and provide links to those alternatives.
- Review other cross-referenced documentation to ensure Linux/macOS parity in examples and tooling.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_path_pattern
Summary
The documentation provides parity for both Windows and Linux App Service apps, mentioning both platforms in backup content tables and referencing persistent storage for custom containers. However, there are subtle Windows biases: Windows path patterns (e.g., `%HOME%`, `D:\home\site\wwwroot`) are shown first or exclusively in some file instructions, and the use of Kudu DebugConsole (which is more familiar to Windows users) is referenced without mentioning Linux alternatives. FTP upload instructions use Windows-style paths. PowerShell is mentioned as a scripting option, but Linux shell scripting is not referenced. Overall, Linux users can complete all tasks, but Windows patterns are prioritized or assumed in some examples.
Recommendations
- Provide Linux path examples (e.g., `/home/site/wwwroot`) alongside Windows paths in file instructions and upload steps.
- Clarify that Kudu DebugConsole is available for both Windows and Linux App Service apps, and mention Linux-native tools (e.g., SCP, SFTP) for file upload.
- When referencing scripting, mention Bash or shell scripting as alternatives to PowerShell.
- In tables and instructions, list Windows and Linux content equally (not Windows first).