233
Pages Scanned
35
Pages Flagged
233
Changed Pages
15.0%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06
Scan Information
Started At: 2026-02-27 00:00:06
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 233
Files Completed: 233
Problematic Pages
36 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
powershell_heavy
windows_tools
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 (Windows), with no mention of Linux/macOS alternatives. CLI steps use PowerShell and Package Manager Console, and database access is described via Visual Studio SQL Server Object Explorer. There are no examples or guidance for Linux/macOS users, such as using VS Code, Azure CLI, or cross-platform .NET tooling.
Recommendations
- Add instructions and screenshots for VS Code or cross-platform .NET CLI workflows.
- Include Azure CLI or Bash examples for database setup and migrations, alongside PowerShell.
- Mention and link to Linux/macOS-compatible tools for publishing and managing ASP.NET apps (e.g., dotnet CLI, Azure CLI).
- Provide guidance for connecting to Azure SQL Database from Linux/macOS (e.g., using sqlcmd, Azure Data Studio).
- Clarify which steps are Windows-only and offer alternatives for other platforms where possible.
Create Pull Request
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 Bash commands. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not always available or preferred on other platforms.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention if PowerShell Core (cross-platform) is supported, and provide installation guidance if relevant.
- Where possible, provide Bash or shell script examples for certificate management tasks.
- Clarify whether all certificate upload operations can be performed via the Azure portal or REST API, and link to those methods for platform neutrality.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway v2 shows moderate Windows bias. Migration instructions and tutorials are focused on Azure PowerShell scripts, with no mention of Azure CLI or ARM templates for Linux/macOS users. The 'Next steps' section links only to a PowerShell-based tutorial, and the migration script is described as a PowerShell Gallery resource. While the Azure CLI is referenced for preview registration, the commands shown are actually PowerShell cmdlets, not true Azure CLI commands. There are no Linux/macOS-specific examples or parity guidance.
Recommendations
- Add Azure CLI and/or ARM template examples for migration and deployment tasks, especially in the 'Migrate from v1 to v2' and 'Next steps' sections.
- Ensure that registration/unregistration instructions use actual Azure CLI syntax, not PowerShell cmdlets.
- Provide links to tutorials or guides that use cross-platform tools (Azure CLI, Bicep, ARM templates) for creating and managing Application Gateway v2.
- Explicitly mention that PowerShell instructions are Windows-centric and offer alternatives for Linux/macOS users.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides configuration examples for mutual authentication on Azure Application Gateway with a strong emphasis on PowerShell, listing PowerShell instructions and references first, followed by Azure CLI. There are no explicit Linux/macOS-specific examples (e.g., Bash scripting, OpenSSL usage), and the 'Next steps' section directs users to a PowerShell-focused guide, potentially creating friction for Linux/macOS users.
Recommendations
- Provide Linux/macOS-friendly examples, such as Bash/Cloud Shell commands, especially for certificate extraction and management.
- Ensure CLI examples are as detailed as PowerShell ones, and consider listing Azure CLI before PowerShell to avoid a 'Windows-first' impression.
- Add references or links to cross-platform tools (e.g., OpenSSL) for certificate manipulation.
- Include a 'Next steps' link to an Azure CLI or ARM/Bicep template guide, not just PowerShell.
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, it exclusively uses Azure PowerShell for CLI-based examples, with no mention of Azure CLI (az), Bash, or Linux/macOS shell equivalents. The PowerShell instructions are presented before ARM templates, and there is no guidance for Linux/macOS users who may prefer Azure CLI or Bash scripting. This creates friction for non-Windows users, as PowerShell is not native to Linux/macOS environments.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all tasks, including creating API Management instances, assigning managed identities, and updating instances.
- Explicitly mention that PowerShell examples can be run cross-platform, but provide CLI alternatives for Linux/macOS users.
- Consider including Bash scripting examples or references to Azure CLI documentation for parity.
- Present CLI examples (PowerShell and Azure CLI) together, or alternate their order, rather than always showing PowerShell first.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. The PowerShell example is given equal prominence to the CLI example, but there is no mention of Bash or Linux-specific workflows. The prerequisites list both Azure CLI and Azure PowerShell, but does not clarify that PowerShell is cross-platform or provide Linux/macOS-specific guidance. The CLI example is generic and works cross-platform, but the PowerShell example may create friction for Linux/macOS users who are less familiar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, and provide installation guidance for Linux/macOS users.
- Add Bash or shell script examples for importing SOAP APIs using Azure CLI, highlighting Linux workflows.
- Explicitly state that all CLI commands are cross-platform and provide links to Linux/macOS-specific setup guides.
- Consider mentioning alternative tools (e.g., REST API, SDKs) for users who prefer not to use PowerShell.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and neutral, but the 'Hybrid Connections' section requires installing Hybrid Connection Manager on Windows Server, with no mention of Linux/macOS support or alternatives. This creates friction for Linux users wishing to use Hybrid Connections. No PowerShell-heavy or Windows-first ordering is observed elsewhere, and most features are described generically.
Recommendations
- Clarify whether Hybrid Connection Manager supports Linux/macOS, and provide installation instructions or alternatives if available.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative outbound connectivity methods for Linux-hosted apps.
- Review other sections for potential OS-specific tool mentions and ensure parity in examples and guidance.
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 presents Windows examples and patterns first, especially for certificate loading in app code. Windows certificate store usage is explained in detail, with C# and Java code samples for Windows, while Linux examples are limited to C# file-based loading. Other languages (Node.js, PHP, Python, Java) are mentioned only as 'see external docs,' with no Linux-specific code samples. Windows tools and concepts (certificate store, thumbprint, environment variables) are emphasized, and Linux parity is lacking in practical examples and guidance.
Recommendations
- Add Linux-specific code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from file paths in Linux containers.
- Provide more detailed guidance for Linux users, including how to handle certificate permissions, file formats, and environment variables.
- Present Linux and Windows approaches side-by-side, or use tabs to avoid Windows-first bias.
- Clarify differences in certificate handling between Windows and Linux, especially for non-.NET workloads.
- Link to or create documentation for Linux-specific certificate management in App Service.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page provides backup and restore guidance for Azure App Service apps. While it covers both Windows and Linux app scenarios, there are several areas where Windows patterns, terminology, and tooling are prioritized or presented first. Examples and instructions often reference Windows paths (e.g., `%HOME%`, `D:\home\site\wwwroot`), Windows-centric tools (Kudu DebugConsole, FTP), and PowerShell samples are mentioned alongside Azure CLI. Linux equivalents are sometimes present but less emphasized, and Windows-specific terminology appears first in explanations.
Recommendations
- Provide Linux/macOS-specific examples and paths (e.g., `/home/site/wwwroot`) alongside Windows paths in all relevant sections.
- Clarify that Kudu DebugConsole and FTP are cross-platform, or offer alternatives for Linux users (such as SSH or SCP where applicable).
- Ensure that Azure CLI instructions are equally emphasized for Linux/macOS users, and avoid presenting PowerShell as the primary scripting option.
- Where file paths or environment variables are referenced, show both Windows and Linux formats.
- Review screenshots and UI references to ensure they are not Windows-only unless the feature is exclusive to Windows.
- Explicitly state when instructions apply to both Windows and Linux apps, and highlight any OS-specific differences.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI (az), Bash, or ARM template example. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. The only automation example is Windows-centric, and the log conversion tool is referenced as a C#/.NET solution, which is also more common in Windows environments.
Recommendations
- Add equivalent examples using Azure CLI (az) for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention or provide ARM/Bicep template snippets for enabling diagnostic logging for users who prefer infrastructure-as-code approaches.
- If referencing log conversion tools, also mention cross-platform alternatives (e.g., Python scripts, jq for JSON processing) or clarify that the .NET tool can be run on Linux/macOS with .NET Core.
- When showing automation examples, present Azure CLI first or alongside PowerShell to avoid Windows-first bias.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides PowerShell-centric examples and references, particularly for configuring advanced probe features (e.g., MinServers, probe match criteria). It mentions PowerShell cmdlets and operators exclusively for custom probe configuration, without equivalent Azure CLI or ARM template examples. Additionally, PowerShell is referenced before other methods in the 'Next steps' section, suggesting a Windows-first approach.
Recommendations
- Add Azure CLI and ARM template examples for custom probe configuration, especially for features like MinServers and probe match criteria.
- Explicitly mention that these configurations can be performed on Linux/macOS using Azure CLI or ARM templates, not just PowerShell.
- Provide CLI syntax alongside PowerShell in all code example sections.
- In the 'Next steps' section, list Azure CLI and ARM template options before or alongside PowerShell to avoid Windows-first ordering.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, specifically linking to IIS and Windows authentication configuration; (2) Windows tools and terminology (e.g., Service Principal Name, IIS, Windows Authentication) are mentioned before any Linux equivalents, with no Linux-specific troubleshooting or guidance provided for backend authentication scenarios.
Recommendations
- Add troubleshooting guidance for Linux-based backend servers, such as Apache, NGINX, or other common Linux web servers, including links to relevant documentation for configuring Kerberos/NTLM or other authentication mechanisms on Linux.
- When referencing authentication protocols, clarify that NTLM and Kerberos are supported on both Windows and Linux, and provide links to Linux-focused resources (e.g., mod_auth_kerb for Apache, GSSAPI for NGINX).
- Include examples or notes for Linux backend log analysis and configuration, not just Windows/IIS.
- Ensure that troubleshooting steps and best practices are presented in a platform-neutral way, or with parity between Windows and Linux guidance.
Application Gateway
Azure Application Gateway listener configuration
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support on Application Gateway listeners, with no equivalent example for Azure CLI, Bash, or ARM/Bicep. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration snippets, especially for enabling HTTP/2 support.
- Where possible, provide ARM template or Bicep examples for infrastructure-as-code users.
- Explicitly mention that all features are available via Azure CLI and portal, and link to relevant CLI documentation.
- Consider including Bash shell examples or guidance for cross-platform users.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page exclusively demonstrates configuring Azure Application Gateway TCP/TLS proxy with a SQL Server VM running Windows Server. All examples and screenshots reference Windows-based SQL Server deployments, and the client connection instructions assume the use of SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for deploying SQL Server on Linux, connecting from Linux/macOS clients, or using cross-platform SQL tools.
Recommendations
- Add instructions and examples for deploying SQL Server on Linux (e.g., Ubuntu) as a backend VM.
- Include guidance for connecting to the SQL Server via Azure Application Gateway from Linux/macOS clients, using cross-platform tools such as sqlcmd, Azure Data Studio, or other open-source SQL clients.
- Mention alternative client tools and provide sample connection commands for Linux/macOS environments.
- Clarify that the procedure is also applicable to SQL Server on Linux, unless there are Azure-specific limitations.
Application Gateway
TLS termination with Azure Key Vault certificates
...b/main/articles/application-gateway/key-vault-certs.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides PowerShell-centric examples and instructions for integrating Azure Application Gateway with Key Vault certificates. While Azure CLI is mentioned, all detailed command-line examples are exclusively in PowerShell, and PowerShell is referenced before CLI or ARM/Bicep in several places. There are no explicit Linux/macOS CLI examples or guidance, and the 'Next steps' section links only to a PowerShell guide.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command sequences, especially for certificate referencing and managed identity configuration.
- Include explicit guidance or links for Linux/macOS users, clarifying how to perform tasks using Azure CLI or Bicep.
- Ensure 'Next steps' includes links to CLI and ARM/Bicep documentation, not just PowerShell.
- Where PowerShell is referenced, mention that Azure CLI is cross-platform and provide parity in instructions.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling centered around PowerShell. There are no references to Azure CLI, Bash, or Linux-native tooling, nor are there examples or guidance for users on Linux or macOS platforms. The script installation and execution instructions assume a Windows/PowerShell environment, which creates friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for configuration and traffic migration, alongside PowerShell examples.
- Add explicit guidance for Linux/macOS users, including how to run PowerShell Core (pwsh) cross-platform, or alternative approaches using Azure CLI.
- Mention and link to Azure Cloud Shell as a cross-platform option, clarifying that both PowerShell and Bash are available.
- Where possible, offer Bash script examples or instructions for downloading and running migration scripts from Linux/macOS.
- Clarify prerequisites for Linux/macOS users, such as installing PowerShell Core or using Azure CLI.
Application Gateway
Quickstart: Direct web traffic using the portal
...in/articles/application-gateway/quick-create-portal.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
Summary
The documentation provides only Windows Server VM examples and uses PowerShell commands for backend setup (IIS installation), with no Linux VM or Linux web server (e.g., Apache, Nginx) examples. The IIS installation is performed via PowerShell, and there are no equivalent instructions for Linux-based VMs or web servers. The documentation also refers to Windows Server as the default VM type in the backend pool creation steps.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server.
- Provide examples for installing a Linux web server (such as Apache or Nginx) using Bash/SSH or Azure CLI.
- Show how to test the application gateway with a Linux backend (e.g., by browsing to the public IP and seeing the Apache/Nginx default page).
- Include both Windows and Linux options in backend pool setup, making clear that Application Gateway supports both.
- If using PowerShell for Windows, provide Bash/SSH/CLI equivalents for Linux.
- Consider showing both Windows and Linux VM creation steps side-by-side or in separate sections.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_only_feature
Summary
The documentation is for 'gateway-required virtual network integration', which is explicitly a Windows-only feature. The page clearly states that this integration 'only works for Windows plans' and 'can't be used from a Linux app.' All instructions, examples, and troubleshooting steps are therefore Windows-focused by design.
Recommendations
- No changes needed. The documentation correctly identifies the Windows-only nature of the feature and does not mislead Linux/macOS users.
- Ensure that links to alternative (cross-platform) solutions, such as 'regional virtual network integration', are prominent for Linux users.
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell syntaxes. However, throughout the page, PowerShell examples are consistently shown after bash, and the documentation explicitly states that Azure CLI commands can run in either shell. There are no Windows-only tools or patterns, and Linux parity is maintained. The only minor bias is that PowerShell examples are always shown second, which may slightly favor Linux/bash users.
Recommendations
- Consider alternating the order of bash and PowerShell examples in sections, or explicitly state that both are equally supported.
- Add a brief note at the start of the CLI sections clarifying that all examples are cross-platform and that both bash and PowerShell are fully supported.
- Ensure screenshots and portal instructions are not Windows-centric (they currently are not).
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 for every step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may suggest a Windows-centric approach. There are no Linux-specific tools or patterns mentioned, but Bash is presented first, indicating some parity.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, possibly with explicit labels.
- Consider grouping Bash and PowerShell examples under clear OS headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Ensure that any OS-specific caveats or requirements are mentioned (e.g., prerequisites for PowerShell on Windows, Bash on Linux/macOS).
- If possible, provide a note about using Azure CLI in Cloud Shell, which is cross-platform.
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
windows_first
powershell_heavy
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, with PowerShell being presented alongside CLI. There is a slight Windows bias in the inclusion and prominence of PowerShell examples and requirements, which are primarily relevant for Windows users. However, Azure CLI examples are also provided, and no critical steps are Windows-only.
Recommendations
- Ensure that Azure CLI examples are presented first, as CLI is cross-platform and more accessible for Linux/macOS users.
- Explicitly mention that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI or Azure Cloud Shell.
- Consider including Bash shell scripting examples for Linux users where 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 given equal prominence and is referenced in the metadata and prerequisites. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) can create a perception of Windows bias, especially since PowerShell is not as commonly used on Linux/macOS. However, both CLI and PowerShell instructions are present, and the CLI is shown first in the deployment section.
Recommendations
- Ensure that Azure CLI examples are always shown first, as it is cross-platform.
- Clarify that Azure PowerShell is available on Linux/macOS, but Azure CLI is recommended for cross-platform users.
- Add explicit notes or links for Linux/macOS users about using Azure CLI and uploading files in Cloud Shell.
- Review metadata tags (e.g., devx-track-azurepowershell) to ensure they do not imply Windows preference.
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 consistently shown immediately after Bash, and the PowerShell formatting is explicitly highlighted. This creates a mild Windows bias, as Linux/macOS users may perceive the PowerShell examples as unnecessary or confusing. There are no missing Linux examples, and the CLI commands are cross-platform, but the presence and prominence of PowerShell formatting indicate a Windows-first approach.
Recommendations
- Clearly label Bash and PowerShell sections to reduce confusion.
- Consider grouping Bash and PowerShell examples in separate tabs or collapsible sections.
- Ensure Bash examples are presented first, as Bash is the default shell for most Linux/macOS users.
- Add a note clarifying that Azure CLI commands work in both environments, and users should use the syntax appropriate for their shell.
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
powershell_heavy
Summary
The documentation provides Azure CLI and PowerShell examples for disabling routing to a regional gateway, but lists the PowerShell cmdlet ('set-azapimanagement') before the Azure CLI command ('az apim update'). There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for the CLI commands. However, the main walkthrough and all critical steps are performed in the Azure portal, which is platform-agnostic. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is mentioned alongside it, potentially implying Windows-first bias.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be used on Linux/macOS.
- Provide Linux/macOS-specific guidance or examples where relevant, such as shell syntax or installation instructions for Azure CLI.
- List Azure CLI examples before PowerShell examples to avoid Windows-first ordering.
- Clarify that PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux/macOS users.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions Windows tools (Azure PowerShell) alongside Azure CLI and Azure Portal in the prerequisites, but does not provide Windows-specific examples or prioritize Windows tools elsewhere. All deployment steps use cross-platform tools (kubectl), and examples are generic. The only minor bias is listing Azure PowerShell before Linux equivalents in the prerequisites.
Recommendations
- Consider listing Azure CLI before Azure PowerShell in the prerequisites, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly mention that all kubectl commands work on Windows, Linux, and macOS.
- If possible, provide links to Linux/macOS-specific guidance for creating AKS clusters (if any exists).
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 both Azure PowerShell and Azure CLI examples for backup and restore operations, but PowerShell examples are presented first and in greater detail. PowerShell is primarily a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI and REST API examples are also included, supporting cross-platform usage.
Recommendations
- Present Azure CLI examples before PowerShell, or at least equally, to emphasize cross-platform support.
- Expand CLI examples to cover managed identity scenarios, matching the detail provided for PowerShell.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add notes clarifying that PowerShell Core is available on Linux/macOS, but Azure CLI is generally preferred for those platforms.
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
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) and the explicit PowerShell example may create a Windows bias. Additionally, PowerShell is mentioned after Azure CLI, but both are given equal prominence. No Linux/macOS-specific tools or workflows are mentioned, and there are no explicit Linux/macOS examples or notes about platform parity.
Recommendations
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
- Add explicit notes or examples showing Azure CLI usage on Linux/macOS, such as shell syntax differences (e.g., bash vs PowerShell variable assignment).
- Consider mentioning that Azure PowerShell is available on Linux/macOS (via PowerShell Core), or provide guidance for Linux users.
- If possible, add troubleshooting tips or environment setup instructions for Linux/macOS users.
- Ensure that CLI examples use syntax compatible with bash/zsh, not just PowerShell.
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 and does not provide command-line examples or tooling instructions that are specific to Windows or Linux. However, in the 'Related content' section, a link is provided to a PowerShell-based guide ('Connect virtual networks from different deployment models using PowerShell') without mentioning or linking to an equivalent Azure CLI or Linux-friendly approach. This subtly prioritizes Windows/PowerShell as the default automation method.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or ARM template documentation for connecting virtual networks, ensuring Linux/macOS users have clear, first-class guidance.
- Where PowerShell is referenced, clarify that Azure CLI and portal-based alternatives exist and provide links.
- Consider reviewing other cross-references throughout the documentation to ensure that automation and scripting guidance is not Windows/PowerShell-centric by default.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is structured to cover both Windows and Linux containers, with clear pivots for each platform. However, Windows-specific examples, tools, and explanations (such as PowerShell commands, Windows container base images, IIS/.NET Framework integration, and Windows directory paths) are often presented first or in greater detail. PowerShell commands are consistently provided alongside Bash/Azure CLI, but sometimes Windows-specific tooling (like System.ConfigurationManager, IIS, and Windows directory paths) is emphasized. Linux parity is generally good, but some Windows concepts are explained more thoroughly or appear before their Linux equivalents.
Recommendations
- Ensure Linux examples and explanations are as detailed as Windows ones, especially for persistent storage and environment variable injection.
- Where possible, present Linux and Windows examples side-by-side, rather than Windows first.
- Expand Linux-specific troubleshooting and advanced configuration sections to match Windows coverage (e.g., diagnostic logs, memory/cpu customization).
- Clarify differences in persistent storage paths and behaviors for Linux vs Windows, avoiding references to Windows paths in Linux sections.
- Add more Linux-specific examples for advanced scenarios (e.g., customizing container resources, health ping behavior, diagnostic log access).
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for assigning Key Vault permissions, but PowerShell is given equal prominence and is mentioned in headings and code tabs. There are also references to Windows-specific tools (IIS, Certreq.exe) for certificate export, and the PowerShell script is shown before any Linux-native scripting. However, the documentation does include OpenSSL-based instructions for certificate preparation, which is cross-platform and Linux-friendly. The FAQ and automation sections reference both Azure CLI and PowerShell, but the PowerShell example is called out explicitly in the FAQ link text.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
- Where Windows-specific tools (IIS, Certreq.exe) are mentioned, provide explicit Linux/macOS alternatives or clarify that OpenSSL is the recommended cross-platform approach.
- In automation/FAQ sections, reference Azure CLI as the primary example and PowerShell as an alternative for Windows users.
- Review all code tabs and ensure that Linux/macOS users are not required to use Windows tools at any step.
- Where possible, add bash scripting examples for common tasks (e.g., certificate binding) to further support Linux users.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for configuring managed identities. However, PowerShell examples are prominent and often appear before CLI examples, and PowerShell is referenced heavily, which may suggest a Windows-centric approach. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is still presented as a primary scripting option. There are no explicit Linux/macOS-only gaps, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but highlight Azure CLI as the default for scripting on Linux/macOS.
- Add explicit notes or links for Linux/macOS users where relevant, e.g., installation instructions for Azure CLI and PowerShell Core.
- Consider including Bash shell script examples for token retrieval, especially in the 'Connect to Azure services in app code' section.
- Review related tutorials and ensure they include non-Windows language examples (e.g., Python, Java, JavaScript) and CLI instructions.
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure App Service virtual network integration. However, there is a section ('Windows Containers specific limits') where Windows-specific guidance is provided before any Linux-specific guidance. Additionally, Windows terminology (e.g., 'Windows Containers') is mentioned first, and Linux-specific continuous deployment network dependencies are only briefly referenced later. There are no PowerShell-only examples, and CLI examples use Azure CLI, which is cross-platform. Linux/macOS users can complete all tasks, but Windows-specific information is presented first.
Recommendations
- Ensure Linux container limits and guidance are described with equal prominence and detail as Windows containers.
- Present Linux and Windows-specific sections in parallel, or clarify when information is Windows-only.
- Add more explicit Linux/macOS examples or references where relevant (e.g., for environment variables, troubleshooting, or container networking).
- Consider including a summary table comparing Windows and Linux container subnet/IP requirements.
Application Gateway
Application gateway components
.../application-gateway/application-gateway-components.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides conceptual information about Application Gateway components and is largely platform-neutral. However, in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, which may subtly prioritize Windows tooling. No examples or instructions are given that are Windows-specific, and Linux/macOS users are not excluded from any critical information.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and more accessible to Linux/macOS users.
- Ensure parity in future procedural guides by providing both PowerShell and CLI examples, or referencing Bash scripts where relevant.
- Consider mentioning that Azure CLI works on all platforms, while PowerShell is most common on Windows, to guide users appropriately.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - AKS Add-on
...pplication-gateway-for-containers-alb-controller-addon.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are given equal prominence and are sometimes shown before Linux-native alternatives. Azure PowerShell is primarily used on Windows, and its inclusion as a first-class option may create friction for Linux/macOS users. However, all critical steps are covered with Azure CLI (cross-platform) and kubectl (Linux-native) commands, so Linux users can complete the tasks without issue.
Recommendations
- Clearly indicate that Azure PowerShell is Windows-centric and recommend Azure CLI for Linux/macOS users.
- Where possible, show Azure CLI examples first, as it is cross-platform.
- Consider adding bash shell script examples for common tasks to further improve Linux parity.
- Ensure all PowerShell steps have equivalent Azure CLI commands.
- Add a note clarifying that Azure PowerShell is optional and not required for Linux/macOS users.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always present and often shown immediately after CLI. Windows-specific tooling (winget for Helm install) is mentioned before Linux equivalents, and Windows installation instructions are given first. While Linux/Bash is supported and examples are present, Windows tools and patterns (PowerShell, winget) are consistently prioritized or presented first.
Recommendations
- Alternate the order of Windows and Linux installation instructions so Linux is not always second.
- Provide Bash/Linux equivalents for all PowerShell/Windows-specific commands where possible.
- Mention Linux installation options for Helm before Windows-specific tools like winget.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS, not just Windows.
- Consider adding a macOS tab for Helm installation.
- Where PowerShell is used, explicitly note that Bash or other shells can be used for Azure CLI steps.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides troubleshooting guidance for Application Gateway for Containers and includes both Linux and Windows examples for filtering logs. However, the Windows example (using 'findstr') is presented immediately after the Linux example (using 'grep'), and both are given equal prominence. The rest of the documentation uses cross-platform tools (kubectl, helm) and does not reference Windows-specific tools or patterns. There is minor bias in the ordering and explicit inclusion of Windows CLI examples, but Linux parity is maintained throughout.
Recommendations
- Consider presenting Linux and Windows examples in parallel tabs or sections, rather than sequentially, to reinforce equal importance.
- Ensure that Linux examples are not always listed first or last; alternate ordering or use tabbed UI for clarity.
- Explicitly state that all commands are cross-platform except where noted, to reassure non-Windows users.
- Review future documentation for unnecessary Windows CLI examples if Linux commands suffice.