235
Pages Scanned
37
Pages Flagged
235
Changed Pages
15.7%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:39
Scan Information
Started At: 2026-02-28 00:00:39
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 235
Files Completed: 235
Problematic Pages
38 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. PowerShell and Package Manager Console commands are used exclusively, and no cross-platform CLI or editor options are provided. Linux/macOS users are left without guidance for completing the tutorial.
Recommendations
- Add instructions for using Visual Studio Code or JetBrains Rider, which are cross-platform IDEs.
- Provide equivalent steps using the .NET CLI (dotnet) for project creation, running, and publishing.
- Include Azure CLI commands for resource creation and deployment, instead of relying solely on Visual Studio wizards.
- Offer examples for connecting to Azure SQL Database using sqlcmd or Azure Data Studio on Linux/macOS.
- Mention how to configure managed identity and permissions using Azure CLI or PowerShell Core (which is cross-platform).
- Add screenshots and guidance for Linux/macOS environments where applicable.
Create Pull Request
Application Gateway
Configure an internal load balancer (ILB) endpoint
...configure-application-gateway-with-private-frontend-ip.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily biased toward Windows environments. All examples for backend VMs use Windows Server images, and IIS is installed using PowerShell commands. There are no instructions or examples for deploying Linux VMs or using Linux-native tools (e.g., Apache, NGINX). The only provided script for backend configuration is a PowerShell command, and the Cloud Shell is explicitly set to PowerShell. This excludes Linux users from easily following the guide, especially for backend pool configuration and health testing.
Recommendations
- Provide parallel instructions for deploying Linux VMs (e.g., Ubuntu) as backend servers.
- Include Linux-native web server setup (e.g., install Apache or NGINX) with Bash/Cloud Shell commands.
- Show how to use Bash in Azure Cloud Shell for Linux VM configuration.
- When presenting VM creation steps, offer both Windows and Linux image options.
- Ensure that all critical configuration and validation steps have Linux equivalents.
Application Gateway
Tutorial: Configure an Application Gateway with TLS termination using the Azure portal
...main/articles/application-gateway/create-ssl-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial demonstrates significant Windows bias. All certificate creation and export steps use Windows PowerShell cmdlets (New-SelfSignedCertificate, Export-PfxCertificate) with no mention of Linux/macOS alternatives. The backend VM creation is exclusively for Windows Server, and IIS installation is shown only for Windows. There are no Linux/macOS instructions or examples for certificate generation, VM setup, or web server configuration.
Recommendations
- Add instructions for creating a self-signed certificate and exporting a PFX file using OpenSSL on Linux/macOS.
- Provide an example of deploying a Linux VM (e.g., Ubuntu) as a backend server, including web server installation (such as Apache or Nginx).
- Include Linux/macOS command-line examples alongside PowerShell for relevant steps.
- Clarify that Application Gateway supports both Windows and Linux backend servers, and link to documentation for Linux setup.
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 examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools. The rest of the instructions are portal-based and platform-agnostic.
Recommendations
- Add Azure CLI example(s) for uploading a CA certificate, if supported.
- If Azure CLI does not support this operation, clarify this explicitly and suggest PowerShell Core as a cross-platform alternative.
- Mention that PowerShell Core is available on Linux/macOS, and provide installation guidance or links.
- Consider including REST API or ARM template examples for certificate upload, which are platform-neutral.
Application Gateway
Deploy Application Gateway Basic (Preview)
...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All CLI examples for registering/unregistering the preview and installing IIS are provided exclusively in Azure PowerShell, with no Bash, Azure CLI, or Linux shell equivalents. The VM creation walkthrough uses Windows Server as the default example, and IIS (a Windows web server) is used for backend testing, with no mention of Linux VMs or Apache/Nginx alternatives. Linux users are left to infer their own steps, creating friction.
Recommendations
- Provide Azure CLI (Bash) equivalents for preview registration/unregistration steps.
- Include Linux VM creation instructions alongside Windows, or clarify that any OS can be used.
- Offer examples for installing a Linux web server (e.g., Apache or Nginx) for backend testing.
- Explicitly state that backend VMs can run any OS and provide links to Linux quickstarts.
- Balance screenshots and walkthroughs to show both Windows and Linux scenarios.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium 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 suggests a Windows/PowerShell bias, as no equivalent Linux/bash/CLI example is referenced or linked. Additionally, PowerShell is mentioned before any cross-platform tools, which may create friction for Linux/macOS users.
Recommendations
- Add links to equivalent Azure CLI tutorials for autoscaling and zone redundancy, or explicitly state if PowerShell is required.
- Ensure that conceptual and procedural examples are provided for both PowerShell and Azure CLI, with clear guidance for Linux/macOS users.
- In the 'Next steps' section, list cross-platform tools (Azure CLI, ARM templates) before or alongside PowerShell to avoid Windows-first bias.
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_tools
windows_first
Summary
The documentation provides step-by-step instructions for enabling and using managed identities in Azure API Management via the Azure Portal, Azure PowerShell, and ARM templates. However, all CLI/scripted examples are exclusively in Azure PowerShell, with no mention of Azure CLI (cross-platform) or Bash scripting. PowerShell is a Windows-native tool (though available cross-platform, it is less common on Linux/macOS), and the documentation does not provide parity for Linux/macOS users who may prefer Azure CLI. The PowerShell sections are also presented before ARM template examples, and there are no explicit Linux/macOS-specific notes or alternatives.
Recommendations
- Add Azure CLI examples for all tasks currently demonstrated with Azure PowerShell, such as creating resource groups, managed identities, and API Management instances.
- Explicitly mention that Azure PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Where possible, provide Bash scripting examples or reference Azure CLI documentation.
- Consider reordering sections so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
- Add a short note for Linux/macOS users on how to perform equivalent actions if only PowerShell is shown.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC assignment, but PowerShell is given equal prominence and is referenced in automation FAQs. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. Windows-specific tooling is mentioned first or equally, and links to Windows documentation are provided for certificate export. There is no explicit Linux/macOS example for exporting certificates from non-Windows sources, and PowerShell is referenced in automation guidance.
Recommendations
- Add explicit Linux/macOS guidance for certificate export, such as detailed OpenSSL instructions, and clarify the process for users who do not use IIS or Certreq.exe.
- Provide Linux/macOS-specific automation examples (e.g., Bash scripts) alongside PowerShell, especially in the FAQ section.
- When referencing tools, list cross-platform options first or equally, and avoid linking only to Windows documentation for certificate export.
- Clarify that Azure CLI is cross-platform and encourage its use for automation when possible.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides examples and instructions for both Windows and Linux platforms in several places, but there are notable Windows-centric patterns. Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used as defaults, and Windows tools like PowerShell are mentioned alongside Azure CLI. The Kudu DebugConsole example is Windows-oriented, and FTP upload instructions reference Windows paths. Linux equivalents are mentioned but often after Windows, and Linux-specific instructions are less detailed.
Recommendations
- Provide Linux/macOS-specific file path examples (e.g., /home/site/wwwroot) alongside Windows paths wherever file operations are described.
- Ensure parity in tool recommendations: mention Bash and Linux-native scripting alongside PowerShell, and provide sample scripts for both.
- Clarify that Kudu DebugConsole and FTP can be used from any OS, and show Linux/macOS screenshots or terminal commands where appropriate.
- Where environment variables are referenced, show both Windows (%HOME%) and Linux ($HOME) conventions.
- In sections describing file uploads or directory navigation, include Linux/macOS instructions and paths.
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
missing_linux_example
Summary
The documentation page covers both Windows and Linux environment variables for Azure App Service, but there is a notable Windows-first and Windows-tools bias. Windows paths, tools, and concepts (such as D:\home, Web Deploy/MSDeploy, IIS, and .bat files) are mentioned first or exclusively in many places, and examples often use Windows syntax. Linux equivalents are sometimes mentioned, but often as an afterthought or in a secondary position. Some sections, like build automation, are split into Windows (Kudu) and Linux (Oryx) tabs, but the Windows tab appears first. There are also variables and explanations that reference Windows-only features without always clarifying Linux alternatives. In some cases, Linux-specific examples or explanations are missing or less detailed.
Recommendations
- Ensure that for every Windows-specific example, an equivalent Linux/macOS example is provided, with equal detail and prominence.
- When referencing file paths, always show both Windows and Linux paths (e.g., D:\home and /home) together.
- Avoid using Windows tools (e.g., .bat files, MSDeploy) as the default or only example; mention Linux tools and workflows with equal weight.
- Where tabs are used for Windows and Linux, consider making Linux the first tab or randomize the order to avoid implicit prioritization.
- Add explicit notes when a feature or variable is Windows-only, and provide Linux alternatives or workarounds where possible.
- Audit the documentation for variables or features that are only described in Windows terms (e.g., IIS, applicationHost.config) and clarify their applicability or alternatives for Linux.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is primarily focused on gateway-required virtual network integration, which is explicitly stated to be a Windows-only feature. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat usage) are Windows-centric, and Linux/macOS equivalents are not provided. Windows tools and patterns are mentioned first and exclusively in command examples, creating friction for Linux/macOS users who may need to perform similar troubleshooting tasks.
Recommendations
- Clearly state early in the document that gateway-required virtual network integration is Windows-only, and highlight alternatives for Linux apps (such as regional virtual network integration).
- Where troubleshooting steps involve Windows tools (e.g., Test-NetConnection, netstat -aon), provide Linux/macOS equivalents (e.g., nc, curl, netstat, ss) or mention that these steps are for Windows VMs and suggest alternatives for Linux VMs.
- Add explicit guidance or links for Linux users on how to test connectivity and debug networking issues in Azure environments.
- Ensure that any portal instructions or UI references clarify if they are Windows-specific or applicable to all platforms.
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 provides detailed, step-by-step code examples for accessing certificates in Windows apps and Windows containers, including C# and Java code for the Windows certificate store. Linux examples are limited to C# file-based loading and lack parity for other languages (Node.js, PHP, Python, Java). Windows-specific tools and patterns (certificate store, environment variables, user profile settings) are described in depth, while Linux guidance is brief and often refers users to external language/platform documentation.
Recommendations
- Add Linux-specific code examples for Node.js, PHP, Python, and Java, showing how to load certificates from the injected file paths.
- Provide more detailed guidance on Linux certificate handling, including environment variable usage and best practices for certificate file permissions.
- Ensure that Linux instructions and examples are presented alongside Windows examples, rather than referring users to external documentation.
- Clarify any differences in certificate handling between Windows and Linux containers, especially for popular frameworks and languages.
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 the relay agent (Hybrid Connection Manager) on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. There are no PowerShell-heavy examples or Windows-first ordering, but the lack of Linux guidance for Hybrid Connections is a notable gap.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connections is Windows-only, explicitly state this limitation to inform Linux users.
- Where possible, provide Linux/macOS equivalents or note feature parity for tools and agents.
- Review other sections for potential platform-specific instructions and ensure parity in examples and guidance.
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 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 Linux authentication examples or guidance, and the troubleshooting steps assume Windows-based backend servers.
Recommendations
- Add guidance for Linux-based backend authentication scenarios, such as using Kerberos on Linux (e.g., Apache, NGINX, or other web servers) and how to configure SPNs and review logs in those environments.
- Include troubleshooting steps and links for common Linux web server authentication issues when using Dedicated Backend Connections.
- When referencing backend server logs, mention both Windows (IIS) and Linux (Apache, NGINX) log locations and formats.
- Clarify that NTLM is Windows-specific, and provide alternatives or note limitations for Linux backends.
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 example for enabling HTTP/2 support but does not offer equivalent CLI or Linux-native examples (e.g., Azure CLI or ARM template). This creates friction for users on Linux/macOS who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI examples alongside PowerShell for configuration tasks, especially for enabling HTTP/2 support.
- Where possible, provide ARM/Bicep template snippets for configuration to support infrastructure-as-code users on all platforms.
- Clearly indicate that PowerShell is just one option and link to cross-platform alternatives.
- Consider adding a table or section summarizing commands for PowerShell, Azure CLI, and portal UI for parity.
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 Azure CLI, Bash, or cross-platform scripting example. It also references Excel and Visual Studio-based tools for log analysis and conversion, which are primarily Windows-centric. There are no Linux/macOS-specific instructions or parity in command-line examples.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples where appropriate.
- Mention and provide examples for using jq, awk, or other common Linux tools to process and analyze JSON logs.
- Reference open-source or cross-platform log conversion tools, or provide instructions for converting logs using Python or other platform-agnostic languages.
- When suggesting tools like Excel or Visual Studio, also mention alternatives available on Linux/macOS (e.g., LibreOffice Calc, VS Code, or Python pandas).
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 conceptual information applicable to all platforms, but it demonstrates bias by exclusively using Azure PowerShell cmdlets for custom probe configuration examples and mentioning PowerShell as a primary method for advanced settings (e.g., MinServers). There are no Azure CLI or ARM template examples, and PowerShell is referenced before other methods. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for custom probe configuration and health response matching.
- Mention ARM template syntax for advanced settings such as MinServers.
- Where possible, provide cross-platform guidance and clarify which methods are available on all OSes.
- Ensure that references to PowerShell are balanced with Azure CLI or REST API options, especially in sections describing configuration steps.
Application Gateway
Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal
...es/application-gateway/create-multiple-sites-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial demonstrates notable Windows bias: it exclusively uses Windows Server VMs as backend targets, provides only PowerShell commands for IIS installation, and gives instructions for editing the hosts file and DNS cache using Windows-specific paths and tools. No Linux/macOS equivalents are mentioned, and Linux scenarios (e.g., using Apache/Nginx, Linux VMs, or Bash) are absent. Windows tools and patterns are referenced throughout, creating friction for Linux/macOS users.
Recommendations
- Include Linux VM creation steps alongside Windows, e.g., Ubuntu or CentOS.
- Provide Linux/macOS instructions for editing the hosts file (e.g., /etc/hosts), including appropriate commands for DNS cache flushing (e.g., 'sudo systemctl restart network-manager' or 'sudo dscacheutil -flushcache').
- Offer Bash/Azure CLI alternatives for IIS installation, such as installing Apache or Nginx on Linux VMs.
- Clarify that Application Gateway supports both Windows and Linux backend servers, and provide parity in examples.
- Add notes or links for macOS users regarding hosts file editing and DNS cache management.
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
windows_tools
Summary
The documentation is notably Windows-centric: it exclusively demonstrates deploying a SQL Server VM using a Windows Server image, and the SQL client connection example relies solely on SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM or for connecting using cross-platform SQL clients. This may create friction for Linux/macOS users wishing to follow the guide.
Recommendations
- Add instructions for deploying a SQL Server on Linux VM (e.g., Ubuntu with SQL Server 2019/2022) as an alternative to the Windows-based deployment.
- Include examples of connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other open-source SQL clients.
- Explicitly mention that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, if applicable.
- Where screenshots or steps are OS-specific, provide parallel guidance for Linux/macOS users or clarify any limitations.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions Azure PowerShell alongside Azure CLI as tools to review deployed resources, but does not provide explicit Linux/macOS examples or clarify cross-platform usage. Azure PowerShell is primarily associated with Windows, and its mention before Linux-native tools may suggest a Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Provide example commands for both Azure CLI and Azure PowerShell, or clarify that both are available on all major OSes.
- If referencing PowerShell, note that PowerShell Core is available on Linux/macOS, or link to installation instructions for those platforms.
- Consider listing Azure CLI first, as it is the default cross-platform tool.
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 both Bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown directly after Bash, and the note about CLI usage references PowerShell before Bash. There are no Windows-only tools or patterns, but the ordering and explicit inclusion of PowerShell syntax throughout the CLI sections creates a mild Windows bias. All instructions are cross-platform, and Linux/macOS users can complete the tasks without friction.
Recommendations
- Alternate the order of Bash and PowerShell examples, or show Bash first in some sections to avoid implicit Windows prioritization.
- Clarify that all Azure CLI commands are cross-platform and can be run in any shell, not just PowerShell or Bash.
- Consider providing a single CLI example with a note about variable syntax differences, rather than duplicating for PowerShell unless necessary.
- Explicitly mention Linux/macOS compatibility in the prerequisites or intro.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but the PowerShell examples are given equal prominence and are formatted specifically for Windows users. Bash examples are shown first, but the inclusion of PowerShell-specific syntax and comments indicates a moderate Windows bias. No Linux-specific tools or patterns are missing, but the PowerShell formatting may create friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell examples, and consider grouping them under OS-specific tabs (e.g., 'Linux/macOS' and 'Windows').
- Provide a brief note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows.
- Ensure Bash examples are always shown first, and PowerShell examples are secondary.
- Avoid PowerShell-specific comments unless necessary, and provide parity in explanation for Bash users.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash (Linux/macOS) and PowerShell (Windows), but the PowerShell examples are formatted and presented immediately after the Bash examples in each step. The PowerShell formatting is explicitly called out, and variable assignment syntax is shown for both shells. However, the PowerShell examples are labeled as 'Formatted for PowerShell', which may subtly prioritize Windows users. There is no missing Linux example, but the documentation could be more explicit about shell/platform parity.
Recommendations
- Clarify that Bash examples are for Linux/macOS and PowerShell examples are for Windows.
- Present Bash and PowerShell examples side-by-side or in clearly separated tabs to avoid implicit prioritization.
- Ensure variable names and assignment patterns are consistent and correct for each shell.
- Add a brief note at the start of the CLI section explaining which shell/platform each example targets.
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 a Windows-centric tool and is presented alongside Azure CLI without explicit mention of Linux/macOS alternatives (such as Bash or shell scripting). The Azure PowerShell example may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms, even though it is technically cross-platform. The CLI example is shown first, which helps mitigate bias, but there is no explicit guidance for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- Add a note that Azure PowerShell is available cross-platform, but CLI is preferred for Linux/macOS users.
- Consider including Bash shell script examples or instructions for Linux/macOS users, if relevant.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
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, Azure PowerShell is highlighted alongside Azure CLI throughout, and PowerShell examples are given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the prerequisites section explicitly tracks Azure PowerShell. The CLI example is shown first, but both are presented in parallel, and Linux users can complete the task using Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS.
- Add a note in the prerequisites section to guide Linux/macOS users toward Azure CLI.
- Consider including a Bash script example for further Linux parity, if relevant.
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 using the Azure portal and Azure CLI, with a brief mention of Azure PowerShell in the section about disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI and REST API, but no Linux-specific tools or shell examples are given. However, the Azure CLI is cross-platform and the portal is OS-agnostic, so the bias is minimal. There are no Windows-only tools or patterns, and no exclusive PowerShell-heavy sections.
Recommendations
- Ensure parity by including Bash or shell script examples where relevant, especially for automation.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- If mentioning PowerShell, also mention Bash or other scripting options for Linux users.
- Consider linking to documentation about using Azure CLI on Linux/macOS.
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 comprehensive instructions for backing up and restoring Azure API Management instances using PowerShell, Azure CLI (Bash), and REST API. However, PowerShell examples are presented first in each section, and the documentation assumes familiarity with PowerShell cmdlets and patterns, which are more common on Windows. While Azure CLI (Bash) and REST API examples are included, the prominence and ordering of PowerShell may create a perception of Windows-first bias.
Recommendations
- Present Azure CLI (Bash) examples before PowerShell, or at least alternate the order in different sections to avoid Windows-first impression.
- Explicitly note that PowerShell cmdlets can be used cross-platform (Windows, macOS, Linux) if true, or clarify any platform limitations.
- Where possible, provide additional context or links for users on Linux/macOS who may not have PowerShell installed by default.
- Ensure that all features and steps described are equally achievable via Azure CLI and REST API, and highlight any gaps or differences.
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/PowerShell (Azure PowerShell) as a method for creating an AKS cluster before Linux-centric alternatives (Azure CLI), but otherwise provides cross-platform instructions using kubectl and YAML files. No exclusive Windows tools or examples are present, and Linux users can follow all steps without friction.
Recommendations
- List Azure CLI as the first option for creating an AKS cluster, as it is more universally available and preferred in cross-platform scenarios.
- Explicitly note that all kubectl commands and YAML files are cross-platform and can be run from Linux, macOS, or Windows terminals.
- Consider providing example commands for both Bash (Linux/macOS) and PowerShell (Windows) if scripting is involved, though in this case kubectl commands are universal.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and management steps. However, PowerShell is a Windows-centric tool, and its inclusion alongside CLI may subtly favor Windows users. In some sections, PowerShell examples are presented immediately after CLI, but not before. There are no Linux-specific tools (e.g., Bash, shell scripts) or explicit Linux/macOS guidance, but Azure CLI is cross-platform and is presented first in all cases.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding brief notes or links for Linux/macOS users, such as installation instructions for Azure CLI on those platforms.
- Explicitly state that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
- If relevant, mention that Bicep can be used from Bash or other shells, not just PowerShell.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance using pivot sections, but in shared sections, Windows/PowerShell examples are often shown before Linux/Bash equivalents. There is a notable emphasis on PowerShell commands alongside Azure CLI, and some sections (e.g., persistent storage, environment variables, port configuration) consistently present Windows/PowerShell commands first. Additionally, Windows-specific tools and patterns (like references to C:\home, IIS, and .NET Framework) are described in detail, sometimes before or with more context than their Linux counterparts.
Recommendations
- In shared sections, alternate the order of Bash and PowerShell examples, or present Bash/Linux examples first to balance the experience.
- Where possible, group platform-specific instructions under clear subheadings or tabs, so users can easily find their relevant OS guidance.
- Ensure Linux-specific details (such as /home directory usage, Linux logging, and SSH setup) are as comprehensive and visible as Windows details.
- Reduce the prominence of PowerShell examples in general sections, or clearly mark them as optional/alternative to Bash/Azure CLI.
- Review for any subtle prioritization of Windows tools/patterns in introductory or summary paragraphs and ensure parity in Linux coverage.
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 CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. Both tools are cross-platform, but PowerShell is still more commonly associated with Windows. The documentation does not provide Linux/macOS-specific guidance or examples (e.g., Bash scripts, shell usage), and PowerShell is presented equally alongside CLI, which may create friction for Linux/macOS users. However, Azure CLI is cross-platform and the examples are generic, so Linux users can complete the task.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is more commonly used on Windows.
- Add explicit Bash or shell script examples for Linux/macOS users, or note that Azure CLI commands work identically across platforms.
- Consider mentioning that Azure CLI is the recommended tool for Linux/macOS users.
- Add a short section or note about using Azure CLI and PowerShell on Linux/macOS, including installation links.
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 does not mention Bash or other Linux-native tools. The PowerShell example is not marked as Windows-only, and both CLI and PowerShell are presented as equivalent options. The portal instructions are platform-neutral. There is minor bias in listing PowerShell as a primary tool, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes about cross-platform compatibility for Azure CLI and PowerShell.
- Consider providing Bash shell script examples for Linux users, or clarify that Azure CLI commands are suitable for Bash/zsh environments.
- Mention that Azure PowerShell can be installed on Linux/macOS, but Azure CLI is the default cross-platform tool.
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
windows_first
powershell_heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell examples for all procedural steps. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is presented alongside CLI in all code sections. In several places, PowerShell examples are given equal prominence to CLI, which may subtly reinforce Windows-centric workflows. However, Linux/macOS users can fully complete all tasks using the Azure portal or CLI, and there are no Windows-only tools or patterns required.
Recommendations
- Consider listing Azure CLI examples before PowerShell in all code sections to reinforce CLI as the cross-platform default.
- Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional for those on Windows.
- If possible, clarify that all migration steps can be completed on any OS using Azure CLI or portal.
- Add a brief section or note about using Bash or other shells for scripting on Linux/macOS, if relevant.
App Service
Authentication and Authorization
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service authentication and authorization features for both Windows and Linux/container deployments. However, in the 'Feature architecture' section, the Windows (IIS module) implementation is described first, followed by the Linux/container implementation. There are no Windows-only examples, tools, or PowerShell-heavy instructions. All CLI examples use Azure CLI, which is cross-platform. No Linux/macOS equivalents are missing, and Linux/container scenarios are explicitly addressed.
Recommendations
- Consider describing the Linux/container architecture before or alongside the Windows architecture to avoid subtle ordering bias.
- Continue to ensure all CLI instructions use Azure CLI and avoid Windows-only tooling.
- Where relevant, provide explicit examples for Linux/container deployments, especially for configuration or troubleshooting steps.
- Maintain parity in troubleshooting/logging guidance for both Windows (IIS) and Linux/container environments.
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 sometimes shown before CLI, and PowerShell is referenced heavily for certain operations (e.g., assigning identities to Azure Functions). Azure CLI examples are present and generally cross-platform, but PowerShell is still emphasized, which may create friction for Linux/macOS users. No Windows-only tools or patterns are mentioned, and there are no missing Linux examples, but PowerShell's prominence and occasional first placement indicate a mild Windows bias.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell, as CLI is fully cross-platform.
- Clarify in sections where PowerShell is used that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Where PowerShell is not supported (e.g., assigning user-assigned identity in App Service), explicitly state alternatives for Linux/macOS users.
- Consider adding Bash shell scripting examples for common tasks, especially in sections where PowerShell scripts are provided.
- Review and balance the order of examples so that cross-platform tools (CLI, ARM templates) are not secondary to PowerShell.
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 shell examples (e.g., Bash), and PowerShell is not clearly marked as Windows-only. The use of PowerShell tabs and commands may create friction for Linux/macOS users, although all critical operations are also available via Azure CLI, which is cross-platform.
Recommendations
- Clearly indicate that Azure PowerShell examples are intended for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider showing Azure CLI examples first, as CLI is cross-platform and more widely used in Linux/macOS environments.
- Add notes or guidance for Linux/macOS users, such as confirming that Azure CLI and kubectl commands work natively on their platforms.
- Remove or de-emphasize PowerShell examples unless there is a Windows-specific requirement.
- Where possible, provide Bash shell script examples for common tasks, especially for verification steps.
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) is mentioned for Helm installation, and Windows is referenced explicitly in Helm install instructions. However, Linux parity is generally maintained, with Bash and Azure CLI examples provided, and Linux-specific Helm install instructions included. The bias is mostly in ordering and explicit Windows tool mentions.
Recommendations
- Ensure Linux instructions are presented before or alongside Windows instructions, not after.
- For Helm installation, mention Linux package managers (apt, yum, snap) as alternatives, not just curl script.
- Add explicit macOS instructions for Helm installation (e.g., Homebrew).
- Clarify that Azure CLI and Bash commands are cross-platform, and PowerShell is optional for Windows users.
- Where possible, avoid referencing Windows-specific tools (like winget) before Linux equivalents.
- Consider grouping CLI and PowerShell examples together, or using tabs with clear OS labels.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
linux_first
windows_tools
Summary
The documentation provides both Linux and Windows examples for filtering logs, with Linux (using grep) shown first and Windows (using findstr) second. All other examples are cross-platform (kubectl, helm) and do not show bias toward Windows. No sections are Windows-only, and Linux users are fully supported.
Recommendations
- Maintain parity by continuing to provide both Linux and Windows examples where OS-specific commands differ.
- Consider adding macOS as a tab or note if there are any differences, though in this context, the Linux commands generally apply.
- Explicitly state that all examples are valid for both Linux and macOS where applicable.