240
Pages Scanned
48
Pages Flagged
240
Changed Pages
20.0%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09
Scan Information
Started At: 2026-02-26 00:00:09
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 240
Files Completed: 240
Problematic Pages
49 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
powershell_heavy
windows_first
missing_linux_example
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. PowerShell and Package Manager Console commands are used exclusively, and tools like SQL Server Object Explorer and log streaming are described only in the context of Visual Studio on Windows. There are no examples or guidance for Linux/macOS users, such as using VS Code, Azure CLI, or cross-platform deployment methods.
Recommendations
- Add instructions for Linux/macOS users, including how to use VS Code or the .NET CLI for project creation, running, and publishing.
- Provide Azure CLI or cross-platform commands for database setup, managed identity configuration, and publishing, instead of relying solely on Visual Studio wizards.
- Include screenshots and workflow descriptions for VS Code and/or command-line approaches.
- Offer guidance on connecting to Azure SQL Database from Linux/macOS, such as using sqlcmd (cross-platform), Azure Data Studio, or other tools.
- Document log streaming and database migration steps using Azure CLI or other cross-platform tools.
Create Pull Request
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation heavily focuses on Windows-specific tools (SignTool, MSI installers, WinGet, PowerShell) and provides detailed setup instructions only for Windows environments. There are no equivalent Linux/macOS instructions or examples for Artifact Signing integration, and Windows tools are mentioned first and exclusively in critical setup sections.
Recommendations
- Add explicit instructions or examples for Linux/macOS users, such as using cross-platform .NET tools or SDKs.
- Document how to use Artifact Signing with open-source signing tools available on Linux (e.g., osslsigncode, gpg, or .NET CLI).
- Clarify which integrations (GitHub Actions, Azure DevOps, SDK) are cross-platform and provide sample workflows for Linux/macOS.
- Mention any limitations or Windows-only requirements up front, and provide alternatives or workarounds for non-Windows users.
- Include parity tables or sections comparing Windows and Linux/macOS setup steps for each integration.
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 using PowerShell and Azure CLI, with PowerShell examples and references consistently shown first. There are no explicit Linux/macOS-specific examples or guidance, and the 'Next steps' section directs users to a PowerShell-focused guide, potentially leaving Linux users with less clear guidance.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Include explicit notes or links for Linux/macOS users, especially in sections where PowerShell is referenced, clarifying that Azure CLI provides equivalent functionality.
- In the 'Next steps' section, add a link to a CLI-based mutual authentication configuration guide, or create such a guide if it does not exist.
- Wherever possible, ensure that all configuration steps are documented for both Azure CLI and PowerShell, and clarify any platform-specific limitations.
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
windows_first
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and tooling based on PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided. Installation and execution instructions assume a Windows/PowerShell environment, and PowerShell Gallery is the only script distribution method mentioned. This creates friction for Linux/macOS users who prefer Azure CLI or Bash scripting, and may not have PowerShell installed or configured.
Recommendations
- Provide Azure CLI equivalents for migration steps, or clearly state if PowerShell is required and offer guidance for Linux/macOS users to install PowerShell Core.
- Add Bash script examples or instructions for Linux/macOS environments.
- Mention cross-platform compatibility of PowerShell Core and clarify if scripts work on Linux/macOS, including any prerequisites.
- Include guidance for running PowerShell scripts in Azure Cloud Shell (which is cross-platform), and highlight this option for non-Windows users.
- If PowerShell is the only supported method, explicitly state this limitation and provide links to PowerShell Core installation guides for Linux/macOS.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell examples for configuring encryption of secure assets in Azure Automation, with no equivalent CLI or Linux/macOS shell examples. PowerShell is presented as the primary scripting method, and REST API examples are given as alternatives, but Azure CLI or bash examples are missing. The PowerShell module is referenced as a prerequisite, and PowerShell commands are used in all procedural sections before REST API alternatives. This creates friction for Linux/macOS users who may prefer Azure CLI or bash scripting.
Recommendations
- Add Azure CLI examples for all procedural steps, including assigning managed identities, configuring Key Vault access policies, and reconfiguring Automation accounts.
- Include bash scripting samples where relevant, especially for users on Linux/macOS.
- Mention that PowerShell examples can be run cross-platform with PowerShell Core, but also clarify CLI alternatives.
- List Azure CLI as a prerequisite alongside PowerShell.
- Ensure that REST API and CLI examples are given equal prominence to PowerShell.
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 instructions. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
- Add Azure CLI examples for uploading a CA certificate, as Azure CLI is cross-platform and widely used.
- Mention REST API options for certificate upload, with links to relevant documentation.
- Clarify that PowerShell is optional and provide guidance for Linux/macOS users on alternative methods.
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
Medium 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 example section. While Azure CLI and REST API examples are also included, the PowerShell examples are more extensive and use Windows-centric tools (e.g., PowerShell cmdlets, variable syntax). There is no explicit Linux/macOS bias, but the ordering and depth of PowerShell examples may create friction for non-Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, or alternate their order to avoid Windows-first bias.
- Expand Azure CLI examples to cover managed identity scenarios, matching the depth of PowerShell examples.
- Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
- Add notes clarifying that PowerShell Core is available on Linux/macOS, and provide guidance for those environments if relevant.
- Ensure all example variable names and scripts are compatible with Bash syntax for CLI users.
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
windows_first
missing_linux_example
Summary
The documentation page 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-based examples are exclusively in Azure PowerShell, with no mention of Azure CLI or Bash scripting. PowerShell is presented before ARM templates, and there are no Linux/macOS-specific instructions or parity for command-line operations. This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
- Add Azure CLI examples for all operations currently demonstrated with Azure PowerShell, including creating resource groups, managed identities, and API Management instances.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant Azure CLI documentation.
- Consider providing Bash script snippets alongside PowerShell for cross-platform parity.
- Clarify that PowerShell commands can be run on Linux/macOS if using PowerShell Core, but recommend Azure CLI as the default for cross-platform users.
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 concepts first, with detailed code samples for accessing certificates via the Windows certificate store in C# and Java. Linux-specific guidance is limited to a brief section with only C# examples for loading certificates from files, and other languages (Node.js, PHP, Python, Java) are referenced but not demonstrated. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are emphasized throughout, while Linux equivalents are less prominent and lack parity in language coverage.
Recommendations
- Provide code samples for Linux environments in languages other than C#, such as Node.js, PHP, Python, and Java.
- Reorganize sections so that Linux and Windows guidance are presented with equal prominence, possibly using tabs or parallel subsections.
- Expand explanations for Linux certificate handling, including common patterns and tools (e.g., OpenSSL, file permissions, environment variables).
- Add explicit examples for accessing certificates in Linux containers using popular frameworks and languages.
- Clarify when Windows-specific instructions are not applicable to Linux, and offer Linux alternatives where possible.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. Azure PowerShell is a Windows-centric tool, and its example is given equal prominence to Azure CLI. The CLI example is cross-platform, but PowerShell is presented as a primary workflow, which may create friction for Linux/macOS users. Additionally, PowerShell requirements are listed in the prerequisites, and the PowerShell example is not explicitly marked as Windows-only, potentially confusing non-Windows users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users and provide guidance for Linux/macOS users (e.g., using Azure CLI or PowerShell Core).
- Explicitly note that Azure CLI is cross-platform and recommend it for Linux/macOS users.
- If PowerShell Core is supported on Linux/macOS, add a note or example showing usage on those platforms.
- Consider listing Azure CLI before PowerShell in prerequisites and examples to emphasize cross-platform support.
- Add a short section or FAQ addressing platform compatibility for each tool.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, ARM templates, and portal usage. While Azure CLI is cross-platform, PowerShell examples are prominent and often shown alongside or before CLI examples. In some sections (e.g., assigning user-assigned identities for Functions), PowerShell is the only option, and it is explicitly stated that PowerShell is not supported for App Service. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is referenced in code blocks and explanations, which may create friction for Linux/macOS users. The documentation does not reference Windows-specific tools, but the prominence of PowerShell and lack of Linux/macOS-specific guidance or troubleshooting constitutes a mild bias.
Recommendations
- Add Bash or shell script examples for Linux/macOS users where possible, especially for token retrieval and identity assignment.
- Clarify that Azure CLI commands work equally well on Linux/macOS and Windows, and highlight cross-platform compatibility.
- Where PowerShell is used, provide equivalent Bash or shell alternatives, or explicitly state when only PowerShell is supported.
- Include troubleshooting or notes for Linux/macOS environments, especially when PowerShell is not supported.
- Consider reordering examples so that Azure CLI (cross-platform) is shown before PowerShell.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section exclusively mentions installing Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. No PowerShell or Windows command examples are present, but the lack of Linux/macOS guidance for Hybrid Connections creates friction for non-Windows users.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux/macOS users.
- Review other sections for any implicit Windows assumptions and ensure parity in examples and tool recommendations.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logging but does not offer equivalent CLI/Bash or Azure CLI examples. The only programmatic example is PowerShell, which is Windows-centric. References to data analysis tools focus on Excel and Visual Studio/C#, which are primarily Windows tools, with no mention of Linux/macOS-friendly alternatives. This creates friction for Linux/macOS users who may prefer or require Azure CLI, Bash, or cross-platform tools.
Recommendations
- Add equivalent Azure CLI (az) commands for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples where appropriate.
- When mentioning data analysis tools, include Linux/macOS-compatible options (e.g., jq for JSON processing, pandas in Python, or open-source log viewers).
- Reference Visual Studio Code (cross-platform) instead of or in addition to Visual Studio.
- Explicitly state that PowerShell Core is available cross-platform if PowerShell is to be used, and provide installation guidance or alternatives.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths, tools, and terminology (such as 'D:\home', 'w3wp.exe', IIS, Web Deploy/MSDeploy, and Windows-specific environment variables) are frequently mentioned, often before their Linux equivalents. Windows examples and settings are sometimes described first or in more detail, while Linux-specific information is less prominent or appears later. Some sections (e.g., build automation) default to Windows/Kudu and require switching tabs for Linux/Oryx. Windows tools and patterns (like Web Deploy, MSDeploy, and IIS logging) are referenced without always providing Linux alternatives or parity.
Recommendations
- Ensure Linux-specific paths and variables (e.g., '/home') are mentioned alongside Windows paths, not just as parentheticals.
- Where Windows tools (e.g., Web Deploy, MSDeploy, IIS) are referenced, provide equivalent Linux guidance or clarify if no equivalent exists.
- Present Linux and Windows information equally in tables and descriptions, avoiding Windows-first ordering.
- Expand Linux-specific examples and explanations, especially for build automation, logging, and deployment.
- Clarify which settings are Windows-only and which are cross-platform, ideally with clear labeling or pivots.
- Add more Linux/macOS-focused troubleshooting and usage notes where relevant.
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 page for Azure Application Gateway health monitoring provides configuration examples and instructions primarily using Azure PowerShell cmdlets, such as New-AzApplicationGatewayProbeHealthResponseMatch, and references PowerShell as the main CLI for advanced probe configuration. There is no equivalent Azure CLI (Linux/macOS-friendly) example or mention, and PowerShell is presented as the default scripting interface for probe customization. Additionally, the 'MinServers' property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but only PowerShell examples are shown, and PowerShell is mentioned first.
Recommendations
- Add equivalent Azure CLI examples for probe configuration and matching criteria, especially for tasks shown with PowerShell (e.g., probe health response match).
- Explicitly mention that all configuration tasks can be performed using Azure CLI or ARM templates, not just PowerShell.
- Provide links or references to Azure CLI documentation for Application Gateway probe management.
- Consider showing Azure CLI examples before or alongside PowerShell examples to improve parity.
- Clarify that PowerShell is cross-platform, but highlight Azure CLI as a Linux/macOS-friendly option.
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 an Application Gateway listener, without offering equivalent Azure CLI, ARM template, or REST API examples that are platform-agnostic or Linux/macOS-friendly. No Windows-specific tools or patterns are otherwise emphasized, but the lack of cross-platform command examples introduces friction for non-Windows users.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration snippets, especially for enabling HTTP/2 support.
- Where possible, provide ARM template or REST API examples for tasks that can be automated, ensuring parity for users on all platforms.
- Explicitly mention that all operations can be performed via the Azure portal, Azure CLI, PowerShell, and REST API, with links to relevant documentation.
- If PowerShell is shown first, consider showing Azure CLI first or side-by-side to avoid implicit Windows-first bias.
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 backend settings. However, in the troubleshooting section for Dedicated Backend Connections, Windows-specific authentication protocols (NTLM, Kerberos) and links to Windows/IIS documentation are referenced first and exclusively. There are no equivalent Linux authentication examples or links, and the troubleshooting guidance is tailored to Windows environments. Additionally, references to backend logs and authentication are Windows-centric, with no mention of Linux alternatives.
Recommendations
- Add troubleshooting guidance for Linux-based backend servers, including common authentication mechanisms (such as LDAP, OAuth, or Kerberos on Linux).
- Provide links to Linux documentation for Kerberos authentication and web server log analysis (e.g., Apache, NGINX).
- Clarify that NTLM and Windows Authentication are Windows-specific, and offer alternative guidance for Linux users.
- Include examples or notes for Linux-based backend applications where relevant.
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 primarily demonstrates the configuration of Azure Application Gateway TCP/TLS proxy using a SQL Server VM running Windows Server. All examples and screenshots reference Windows-based SQL Server and SQL Server Management Studio (SSMS), which is a Windows-only tool. There are no examples or guidance for Linux-based SQL Server VMs or Linux/macOS-compatible SQL clients, and Windows patterns are presented exclusively and first.
Recommendations
- Add instructions and screenshots for deploying SQL Server on a Linux VM in Azure, or clarify that Linux is supported.
- Include examples of connecting to the SQL Server backend using cross-platform SQL clients such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible tools.
- Mention any differences or considerations when using Linux-based SQL Server as a backend for Application Gateway.
- Explicitly state if the procedure is equally applicable to Linux SQL Server VMs, or clarify any limitations.
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 registration/unregistration examples are provided exclusively using Azure PowerShell commands, with no equivalent Bash or Linux CLI examples. Additionally, the 'Next steps' section links to a PowerShell tutorial first, suggesting Windows-centric workflows. No Linux/macOS-specific guidance or parity is offered for these tasks.
Recommendations
- Add Azure CLI (bash) examples alongside PowerShell for migration, registration, and unregistration tasks.
- Ensure tutorials and quickstarts are available and linked for both PowerShell and Azure CLI users.
- Explicitly mention that all commands can be run cross-platform if true, or clarify any Windows-only requirements.
- Consider linking to Linux/macOS-specific guidance where relevant.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation repeatedly references an Azure PowerShell script as the primary or sole migration tool, with no mention of Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific migration instructions or examples, and the PowerShell script is referenced as the main automation method for migration and public IP retention. This creates friction for users on Linux/macOS who may not have PowerShell installed or prefer native tools.
Recommendations
- Provide Azure CLI (az) equivalents for migration steps and scripts, or explicitly state if such alternatives are not available.
- Clarify whether the PowerShell script can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide installation guidance if so.
- Add Bash or shell script examples for common migration tasks, or reference any available cross-platform tools.
- Explicitly note any Windows-only requirements for the migration scripts, so Linux/macOS users can plan accordingly.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation, resource management, and cleanup. Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used without mention of Linux/macOS alternatives. No Bash, Azure CLI, or cross-platform scripting examples are provided, and instructions assume a Windows environment (e.g., certificate store paths, file paths).
Recommendations
- Add Azure CLI (az) examples for each step alongside PowerShell, as Azure CLI is cross-platform.
- For certificate creation, provide Linux/macOS alternatives (e.g., using OpenSSL) and explain how to export/import certificates.
- Clarify which steps are Windows-specific and offer guidance for Linux/macOS users where possible.
- Use generic file paths or note differences for Windows vs. Linux/macOS.
- Mention that Azure PowerShell can be used in Cloud Shell (which is cross-platform) and provide instructions for Cloud Shell usage.
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 for 'TLS termination with Azure Key Vault certificates' demonstrates a notable Windows/PowerShell bias. PowerShell is the only command-line example provided for configuring Application Gateway with Key Vault using RBAC, with no equivalent Azure CLI (cross-platform) or Bash examples. The documentation references PowerShell steps and links to a PowerShell-specific guide in the 'Next steps' section, while Linux/macOS users are left to infer or adapt the process themselves. Although Azure CLI is mentioned as a supported tool, no CLI or Linux-native examples are shown.
Recommendations
- Provide Azure CLI (az) command-line examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- Where PowerShell is referenced, add equivalent Bash/CLI snippets or clearly indicate cross-platform alternatives.
- In the 'Next steps' section, link to both PowerShell and Azure CLI guides, or create CLI documentation if it does not exist.
- Ensure that screenshots and UI instructions are platform-neutral or clarify when a step is platform-specific.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references the PFXImportCertStore function from the Windows API when describing supported certificate formats, and links 'Next steps' to a PowerShell-based configuration guide. There are no explicit Linux/macOS CLI examples or references to Linux-native certificate tooling, and Windows/PowerShell tools are mentioned first or exclusively in actionable sections.
Recommendations
- When referencing certificate formats, provide Linux/macOS equivalents (e.g., OpenSSL commands for creating and converting certificates to PFX).
- In 'Next steps', include links to Azure CLI, Azure Portal, or ARM template guides for configuring end-to-end TLS, not just PowerShell.
- Where Windows-specific APIs or tools are mentioned, add notes or links for cross-platform alternatives.
- Consider including example commands or workflows for Linux/macOS users, especially for certificate preparation and gateway configuration.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and PowerShell cmdlets are mentioned first and more frequently throughout. Many backup and retention examples reference Windows PowerShell cmdlets, with no equivalent Linux CLI or scripting examples. Windows registry settings and tools are linked, while Linux guidance is more generic (OpenSSL changelog, Python script).
Recommendations
- Add Azure CLI or Bash examples alongside PowerShell cmdlets for backup and retention tasks.
- Provide explicit Linux/macOS instructions for exporting runbooks, DSC configurations, and managing assets, not just referencing PowerShell.
- Ensure Linux guidance is as detailed as Windows guidance (e.g., specific commands/scripts for asset management, not just generic references).
- Where possible, mention Linux tools (such as az CLI, shell scripts) before or alongside Windows tools.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation heavily relies on PowerShell scripts and workflows for disaster recovery tasks, with no equivalent examples or guidance for Linux-native tools (such as Bash or Python). All migration scripts and runbook examples are PowerShell-based, and the instructions for Hybrid Runbook Worker installation link to Windows-focused tabs first. This creates friction for Linux users, especially those who prefer or require Bash or Python for automation.
Recommendations
- Provide Bash or Python script examples for migrating Automation account assets, or clarify if PowerShell Core (pwsh) is fully supported cross-platform.
- Explicitly mention PowerShell Core compatibility for Linux/macOS users, and provide instructions for installing and running PowerShell scripts on Linux.
- Add Linux/macOS-specific guidance for Hybrid Runbook Worker installation, ensuring links and instructions are not Windows-first.
- Include notes or alternative steps for users who do not have access to PowerShell or prefer other scripting languages.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively uses Windows PowerShell and PowerShell-based examples for authenticating to Azure via Microsoft Entra ID in Azure Automation. All code samples, module references, and credential handling instructions are PowerShell-centric, with no mention of Bash, CLI, or Linux/macOS alternatives. The page refers to 'Windows PowerShell' and does not clarify cross-platform support for PowerShell Core or Azure CLI, potentially creating friction for Linux/macOS users.
Recommendations
- Clarify whether PowerShell Core (pwsh) is supported for these tasks and provide examples if so.
- Add Azure CLI examples for credential asset creation and authentication, where possible.
- Explicitly state platform requirements and limitations (e.g., if only Windows PowerShell is supported, mention it up front).
- Provide guidance for Linux/macOS users on how to use Azure Automation and Microsoft Entra ID authentication, including any necessary prerequisites or workarounds.
- Mention whether the Az module and related cmdlets are available and supported on Linux/macOS runbooks.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page is heavily focused on PowerShell and Windows-centric workflows, with all code examples, parameter handling, and runbook invocation methods centered around PowerShell cmdlets and Windows tools. There are no Linux shell (bash) or cross-platform CLI examples for starting runbooks or passing parameters, and PowerShell is presented as the default or primary method throughout. Python runbooks are briefly mentioned, but only in the context of parameter handling, not invocation. The SDK and REST API sections are platform-neutral, but the practical invocation guidance is Windows-first and lacks Linux parity.
Recommendations
- Add Azure CLI (az automation runbook start) examples for starting runbooks and passing parameters, including JSON parameter handling.
- Include bash shell examples for invoking runbooks via REST API (using curl) and passing parameters.
- Clarify that PowerShell examples are cross-platform when applicable (e.g., PowerShell Core/7), and note any Windows-specific limitations.
- Provide guidance for Linux/macOS users on installing and using PowerShell Core, or alternatives via Azure CLI.
- Expand Python runbook section to include invocation examples from Linux/macOS environments.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...in/articles/automation/how-to/private-link-security.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, without offering an equivalent CLI or ARM template example for Linux/macOS users. Additionally, PowerShell is presented as the primary scripting method, which may create friction for non-Windows users. However, the overall content is largely platform-neutral, and Linux is mentioned in the context of Hybrid Runbook Workers and Update Management.
Recommendations
- Add Azure CLI and/or ARM template examples for configuring 'publicNetworkAccess' to complement the PowerShell script.
- Explicitly mention that the PowerShell example is for Windows users, and provide guidance for Linux/macOS users.
- Where possible, provide cross-platform scripting options (e.g., Bash, Azure CLI) alongside PowerShell.
- Ensure screenshots and portal instructions are not Windows-centric (they appear neutral here).
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation is heavily focused on PowerShell cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, with no Bash, Linux shell, or cross-platform CLI equivalents. The 'Create a new credential asset' section only provides a Windows PowerShell example, and the cmdlet tables exclusively reference PowerShell tools. While Python runbook examples are included, there are no Linux-native or cross-platform CLI instructions for credential asset management outside of the Azure portal.
Recommendations
- Add Azure CLI examples for creating, retrieving, and managing credential assets, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Clarify whether credential asset management is possible via REST API or Azure CLI, and provide those examples if available.
- Explicitly state if PowerShell is required for certain operations, and note any limitations for Linux/macOS users.
- Include guidance for Linux/macOS users on installing and using PowerShell Core if PowerShell is required.
- Consider providing Bash or shell script equivalents where possible, or at least link to cross-platform alternatives.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes PowerShell cmdlets and Windows-centric certificate management patterns, with all scripting examples and advanced workflows provided in PowerShell. There are no explicit Linux/macOS shell (bash, CLI) examples, and PowerShell is consistently presented first. While Python examples are included, they are limited to runbook usage and do not cover certificate creation or management outside the Azure portal/PowerShell context. There is no mention of Linux tools or cross-platform CLI equivalents for certificate management.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to provide parity for Linux/macOS users.
- Include bash or shell script snippets for uploading and managing certificates where possible.
- Present cross-platform options (Azure CLI, REST API) before or alongside PowerShell examples.
- Clarify which tasks require PowerShell and which can be accomplished with other tools.
- Add a section discussing certificate requirements and handling on Linux/macOS environments, including any limitations or differences.
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 both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific tools or workflows (e.g., Bash, shell scripting, or references to Linux/macOS environments). The instructions for uploading files reference Azure Cloud Shell generically, but do not clarify Linux/macOS workflows. PowerShell is a Windows-centric tool, though it is available cross-platform; its inclusion may create friction for Linux/macOS users who typically use Bash or CLI.
Recommendations
- Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash shell example commands where relevant.
- Clarify file upload instructions for Linux/macOS users (e.g., using SCP, curl, or native file managers).
- Consider including a Bash shell example for deploying the ARM template, or at least note that Azure CLI commands can be run in Bash.
- Ensure that PowerShell is not presented as the default or primary method, but as an alternative for users who prefer it.
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_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts. However, there is a minor bias in the 'Related content' section, where a link is provided to a guide for connecting virtual networks using PowerShell, which is a Windows-centric tool. There are no explicit Linux/macOS command-line examples or references to cross-platform tools (such as Azure CLI), and PowerShell is mentioned before any Linux-equivalent tooling.
Recommendations
- In the 'Related content' section, add or prioritize links to cross-platform guides, such as connecting virtual networks using Azure CLI or Azure Portal.
- Where PowerShell is referenced, also mention or link to equivalent Azure CLI documentation, ensuring Linux/macOS users have clear guidance.
- Review other linked articles (e.g., VPN gateway configuration) to ensure Linux/macOS parity is maintained in referenced workflows.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but the 'Next steps' section prominently features a PowerShell-based tutorial for creating an autoscaling, zone-redundant Application Gateway. This may signal a Windows/PowerShell bias, as Linux/macOS users typically use Azure CLI or ARM templates. No Linux-specific examples or equivalent CLI guidance are provided or referenced.
Recommendations
- Add links to equivalent Azure CLI tutorials for autoscaling and zone-redundant Application Gateway creation.
- Mention that Azure CLI and ARM templates can be used on Linux/macOS for the same tasks.
- Ensure that PowerShell and CLI examples are presented side-by-side or with equal prominence in 'Next steps'.
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
powershell_heavy
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell syntax is consistently shown immediately after Bash, sometimes with explicit 'PowerShell syntax' labels. There are no Windows-only tools or patterns, but the order and labeling may subtly favor Windows users. All CLI commands are cross-platform, and Visual Studio Code is recommended (which is available on Linux/macOS). No Linux-specific examples or tools are missing, but Windows/PowerShell syntax is always shown alongside Bash, sometimes first.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them so neither is consistently first.
- Explicitly mention that all Azure CLI commands work on Linux/macOS as well as Windows.
- Add a brief note clarifying that Visual Studio Code and Azure CLI are fully supported on Linux/macOS.
- Consider including screenshots or references to Linux/macOS environments in portal instructions.
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 shown immediately after Bash for every command, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), indicating a Windows-centric approach. There are no macOS-specific notes, and Linux/Bash examples are not given priority or additional context.
Recommendations
- Consider showing Bash (Linux/macOS) examples first, as Bash is the default shell on most non-Windows platforms.
- Add a note clarifying that Bash examples work on Linux and macOS, and PowerShell examples are for Windows users.
- If possible, provide parity in explanations for both shells, and mention any differences in behavior or prerequisites for Linux/macOS users.
- Explicitly state that Azure CLI commands can be run on any OS with the Azure CLI installed.
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 shown immediately after Bash in each step, and the PowerShell formatting is explicitly called out, which may indicate a slight Windows-first bias. There is no evidence of missing Linux examples, as Bash is included, and no exclusive mention of Windows tools or patterns.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to improve parity and reduce friction.
- Ensure that Bash examples are not presented as secondary or less complete than PowerShell examples.
- Add a brief note at the start of the CLI section indicating which shell is appropriate for each platform.
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. However, PowerShell is featured equally alongside CLI, and references to PowerShell are present in prerequisites and deployment instructions. Azure PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since PowerShell is listed in prerequisites and deployment steps. The CLI example is present and shown first, mitigating some bias. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Explicitly state that Azure PowerShell is available cross-platform (via PowerShell Core), but CLI is often simpler for Linux/macOS.
- Consider adding a note or section for Linux/macOS users, highlighting CLI usage and file handling (e.g., uploading files in Cloud Shell).
- Ensure that CLI examples are always shown first and that PowerShell is presented as an alternative, not a primary method.
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. There are no PowerShell-heavy sections, nor are Windows tools mentioned exclusively or before Linux equivalents. All CLI examples use Azure CLI, which is cross-platform. The only minor bias is listing PowerShell as an alternative tool, but this does not impact Linux/macOS users.
Recommendations
- Ensure that all command-line examples use Azure CLI (already done).
- If referencing PowerShell, clarify that Azure CLI is cross-platform and PowerShell is an alternative for Windows users.
- Consider adding explicit notes that all portal and CLI instructions are applicable to Linux/macOS users.
- If possible, provide Bash or shell script examples for automation alongside PowerShell examples.
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 the PowerShell example is given equal prominence and detail. The prerequisites list Azure CLI and Azure PowerShell together, but there are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is primarily a Windows-centric tool, though it is cross-platform. The ordering of examples (CLI before PowerShell) is neutral, but the presence of PowerShell-specific instructions may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add Bash shell examples for Azure CLI usage, demonstrating typical Linux/macOS workflows.
- Explicitly note that PowerShell is available cross-platform, but CLI is recommended for Linux/macOS users.
- Consider adding a section or callout for Linux/macOS users, highlighting any differences or best practices.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance via zone pivots, but Windows-specific examples, tools, and explanations are often presented first or in greater detail. PowerShell commands are included alongside Bash/Azure CLI, but Windows concepts (such as IIS, .NET Framework, and Windows Server images) receive more prominent coverage. Some sections (e.g., persistent storage, diagnostic logs, memory/core customization) default to Windows terminology and paths before Linux equivalents, and PowerShell is consistently shown as an alternative to Bash/CLI.
Recommendations
- Ensure Linux examples and terminology are presented with equal prominence and detail as Windows sections.
- Where possible, show Linux/Bash examples first or side-by-side with Windows/PowerShell to avoid implicit prioritization.
- Expand Linux-specific guidance (e.g., base images, troubleshooting, diagnostic logs) to match Windows coverage.
- Clarify when features or settings differ between Windows and Linux containers, and provide explicit Linux alternatives.
- Review for subtle language or ordering that may imply Windows is the default or preferred platform.
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 briefly mentions Azure PowerShell as an option for creating an AKS cluster before mentioning Linux-friendly alternatives (Azure CLI and Portal). However, all deployment and operational examples use cross-platform tools (kubectl), and there are no Windows-specific commands, tools, or patterns prioritized. No critical steps are Windows-only.
Recommendations
- List Azure CLI as the first option for creating AKS clusters, as it is more universally available and preferred on Linux/macOS.
- Explicitly state that all deployment steps use cross-platform tools (kubectl) and are compatible with Linux/macOS terminals.
- Add a note clarifying that Azure PowerShell is optional and not required for Linux/macOS users.
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
powershell_heavy
windows_tools
Summary
The documentation is for a feature (gateway-required virtual network integration) that is explicitly Windows-only. The page clearly states that this integration does not work with Linux apps or Windows containers. Additionally, troubleshooting sections and connectivity tests use Windows/PowerShell tools (e.g., Test-NetConnection, netstat -aon) and do not provide Linux/macOS equivalents.
Recommendations
- No Linux parity is required for this feature, as it is intentionally Windows-only. However, to improve clarity and user experience:
- 1. Prominently state at the top that this feature is Windows-only (already present, but could be highlighted further).
- 2. In troubleshooting sections, clarify that PowerShell/Windows tools are suggested because the feature is not available for Linux apps.
- 3. For general networking troubleshooting, optionally mention Linux/macOS equivalents (e.g., 'telnet', 'nc', 'ss', 'netstat') for users managing hybrid environments, but clarify these are not applicable for Linux App Service apps with this feature.
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 managing Key Vault permissions, but PowerShell is given equal prominence, and there are references to Windows-specific certificate tools (IIS, Certreq.exe) before Linux alternatives. Export instructions for certificates mention IIS and Certreq.exe for Windows, while OpenSSL is mentioned for Linux/macOS, but the Windows tools are listed first. The FAQ and automation sections also provide both CLI and PowerShell links, but PowerShell is listed second. Overall, there is a mild Windows-first and Windows tools bias, but Linux/macOS users are not blocked from completing any tasks.
Recommendations
- When listing certificate export options, present OpenSSL (cross-platform) instructions before Windows-specific tools like IIS or Certreq.exe.
- Explicitly mention that OpenSSL commands work on Linux/macOS and Windows (if OpenSSL is installed), and provide links to OpenSSL installation guides for Windows.
- Where PowerShell and CLI examples are given, consider listing Azure CLI (cross-platform) first.
- Add a brief note in relevant sections clarifying that all certificate management operations can be performed from Linux/macOS using Azure CLI and OpenSSL.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_patterns
Summary
The documentation is generally cross-platform, referencing both Windows and Linux app backup paths and Azure CLI usage (which is OS-agnostic). However, there are subtle Windows biases: Windows directory patterns (e.g., '%HOME%', 'D:\home\site\wwwroot') are mentioned first or exclusively in some places, and tools like Kudu DebugConsole and FTP are described using Windows-style paths. The instructions for creating the '_backup.filter' file use Windows directory notation and upload paths, with no explicit Linux path equivalents. The portal screenshots and instructions are platform-neutral, but the file system references and some terminology lean toward Windows conventions.
Recommendations
- Add explicit Linux path examples (e.g., '/home/site/wwwroot') alongside Windows paths when describing file locations and upload instructions.
- Clarify that Kudu DebugConsole and FTP can be used from any OS, and provide Linux/macOS command-line alternatives for file uploads (e.g., using SCP or Azure CLI).
- When referencing environment variables like '%HOME%', also mention the Linux equivalent ('$HOME').
- Ensure all directory/file instructions are given in both Windows and Linux formats.
- Consider showing Linux examples first or equally alongside Windows examples to reinforce parity.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides example commands for Azure portal, Azure CLI, and Azure PowerShell in all relevant sections. PowerShell examples are present throughout, and in some cases, PowerShell is listed before CLI in the metadata and custom tags. However, the CLI (which is cross-platform) is always present, and there are no steps that are Windows-only. There is a slight ordering bias in metadata and custom tags, and the inclusion of PowerShell in every example may signal a slight preference for Windows tooling, but Linux/macOS users are fully supported.
Recommendations
- Ensure that Azure CLI examples are always listed before or alongside PowerShell examples, especially in metadata and custom tags.
- Explicitly note that both Azure CLI and PowerShell are cross-platform, but CLI is often preferred for Linux/macOS users.
- Consider providing Bash shell scripting examples for common migration automation tasks to further improve Linux parity.
- In the documentation body, alternate the order of CLI and PowerShell tabs to avoid perceived preference.
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 both Linux and Windows examples for filtering logs, but the Windows example (using 'findstr') is given after the Linux example ('grep'). All other troubleshooting steps use cross-platform tools (kubectl, helm) and shell syntax, with no Windows-specific tools or patterns. The bias is minor, as Windows users are accommodated, but Linux examples are shown first and more prominently.
Recommendations
- Present Linux and Windows examples side-by-side, or use tabbed sections for parity.
- Explicitly mention that all commands are cross-platform unless otherwise noted.
- Ensure that Windows and Linux instructions are equally visible and accessible.
- Consider providing PowerShell-specific examples if Windows users are likely to use PowerShell rather than CMD.
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 (a Windows-centric tool) is given equal prominence and is sometimes shown before or alongside CLI examples. There are no Linux-specific instructions or explicit mentions of Linux/macOS environments, and PowerShell is not available natively on most Linux/macOS systems. However, the primary workflow is based on Azure CLI, which is cross-platform, and all critical tasks can be completed using CLI. The bias is mostly in the inclusion and prominence of PowerShell examples, which may create minor confusion or friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider moving Azure CLI examples before PowerShell examples in each section.
- Add explicit notes stating that PowerShell examples are for Windows users, and CLI is for Linux/macOS.
- Remove PowerShell examples from sections where they do not add value or are redundant.
- Add troubleshooting notes for Linux/macOS users if any step differs (e.g., SSH key generation, environment variables).
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all critical steps, ensuring parity for cross-platform users. However, PowerShell examples are given equal prominence to Azure CLI, and Windows-specific installation instructions for Helm (using winget) are presented before Linux instructions. There is a slight 'windows_first' bias in the ordering and explicit mention of Windows tools, but Linux users are not blocked from completing any task.
Recommendations
- Ensure Linux installation instructions for Helm are presented before or alongside Windows instructions, rather than after.
- Consider explicitly mentioning macOS installation steps for Helm, or clarify that Linux steps are applicable to macOS.
- Where possible, highlight Azure CLI as the default, since it is cross-platform, and present PowerShell as an alternative for Windows users.
- Add a brief note that Azure CLI commands are fully supported on Linux/macOS, reinforcing parity.
Application Gateway
HTTP response codes - Azure Application Gateway
...in/articles/application-gateway/http-response-codes.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is generally cross-platform, but there are minor instances of Windows bias. In the 401 Unauthorized section, NTLM authentication (a Windows-specific protocol) is discussed before more general solutions, and the link provided is to Windows documentation. In the 504 Gateway Time-out section, IIS (a Windows web server) is discussed before Nginx (a popular Linux web server), and more detail is provided for IIS. However, Linux alternatives are mentioned, and the documentation is not Windows-exclusive.
Recommendations
- When referencing NTLM authentication, clarify that it is a Windows-specific protocol and provide equal emphasis on non-Windows authentication scenarios if relevant.
- In the 504 Gateway Time-out section, present Nginx (Linux) and IIS (Windows) examples in parallel, or alternate the order in which they are presented.
- Where possible, provide links to Linux/Unix documentation (e.g., for Nginx) with the same level of detail as for IIS.
- If referencing Windows-specific tools or protocols (like NTLM or IIS), explicitly note their platform specificity and, where possible, provide Linux/macOS equivalents or alternatives.