220
Pages Scanned
32
Pages Flagged
220
Changed Pages
14.5%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-01 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 220
Files Completed: 220
Problematic Pages
32 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 2022, with no mention of cross-platform alternatives (e.g., Visual Studio Code, CLI tools, or Linux/macOS workflows). PowerShell and Package Manager Console commands are used exclusively, and Azure App Service (Windows) is selected by default. There are no Linux/macOS-specific instructions or examples, and the documentation assumes a Windows environment throughout.
Recommendations
- Add instructions and examples for deploying ASP.NET Core apps using Visual Studio Code, Azure CLI, or GitHub Actions, which are cross-platform.
- Include guidance for Linux/macOS users, such as using dotnet CLI for migrations and publishing, and connecting to Azure SQL Database via sqlcmd or Azure Data Studio.
- Provide alternative steps for creating and managing Azure resources using the Azure Portal and CLI, not just Visual Studio.
- Mention Azure App Service (Linux) as a deployment target, and show how to select it during publishing.
- Add screenshots and walkthroughs for Linux/macOS environments where applicable.
Create Pull Request
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 heavily relies on Windows-specific tools and examples, particularly for certificate creation (New-SelfSignedCertificate, Export-PfxCertificate) and backend VM setup (Windows Server, IIS, PowerShell). No Linux/macOS alternatives are provided for creating self-signed certificates or configuring backend servers, and Windows/PowerShell instructions are given exclusively and first.
Recommendations
- Add instructions for creating a self-signed certificate using OpenSSL on Linux/macOS, including exporting to PFX format.
- Provide examples for deploying Linux VMs as backend servers, such as Ubuntu with Apache or Nginx, and include relevant installation steps.
- Include Azure CLI/bash alternatives for steps currently shown only in PowerShell.
- Clarify that backend pools can use Linux VMs and show parity in examples.
- Where possible, show both Windows and Linux/macOS commands side-by-side.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
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 Linux/macOS users may prefer Azure CLI or ARM template examples, which are not mentioned or linked.
Recommendations
- Add links to equivalent tutorials using Azure CLI and ARM templates for creating autoscaling, zone redundant Application Gateway v2.
- Ensure that PowerShell examples are not the only option in 'Next steps'; provide parity for Linux/macOS users.
- Consider listing Azure CLI or ARM template options before or alongside PowerShell to avoid 'windows_first' bias.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS-specific instructions or notes, and PowerShell is presented as a main option alongside Azure CLI. The prerequisites list both Azure CLI and Azure PowerShell, but does not clarify that PowerShell is not native to Linux/macOS. The CLI example is cross-platform, but the PowerShell example may create confusion or friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users (e.g., using Azure CLI or installing PowerShell Core).
- Consider listing Azure CLI examples first, as it is cross-platform and more accessible to Linux/macOS users.
- Add a note about PowerShell Core availability on Linux/macOS, and link to installation instructions if relevant.
- Ensure that all steps and examples are clearly marked as cross-platform or Windows-specific, to avoid confusion.
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, Bash, or Linux/macOS-friendly alternatives. This creates friction for non-Windows users, as PowerShell is primarily a Windows tool and not always available or preferred on Linux/macOS.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention if PowerShell Core (pwsh) is supported on Linux/macOS, and provide instructions for installation if relevant.
- Include Bash or REST API examples for certificate upload, or link to relevant documentation.
- Clarify that the portal-based steps are platform-agnostic, but ensure all CLI/script examples have Linux/macOS parity.
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 detailed instructions and code samples for using Azure PowerShell to manage managed identities in Azure API Management, but does not include equivalent examples for Azure CLI (which is cross-platform and preferred by many Linux/macOS users). PowerShell is a Windows-native tool (though available cross-platform), and its exclusive use here may create friction for Linux/macOS users. The Azure portal and ARM template methods are platform-neutral, but the command-line automation focus is PowerShell-only.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, including creating resource groups, managed identities, and API Management instances.
- When referencing command-line tools, mention Azure CLI first or equally with PowerShell, as Azure CLI is more familiar to Linux/macOS users.
- Explicitly state that both Azure CLI and PowerShell are supported, and link to relevant Azure CLI documentation.
- Consider adding bash/zsh shell snippets where appropriate, especially for automation scenarios.
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 importing an OpenAPI specification using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its example is given equal prominence. The documentation does not provide Linux/macOS-specific guidance or mention any platform-specific considerations. The order of examples (portal, CLI, PowerShell) is neutral, but the inclusion of PowerShell as a main workflow may create friction for Linux/macOS users, as PowerShell is less common on those platforms.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the preferred method for Linux/macOS users.
- Add a note indicating that Azure PowerShell is available on Linux/macOS, but may require additional setup.
- Consider including Bash shell scripting examples for Azure CLI to demonstrate Linux-native workflows.
- Explicitly mention platform compatibility for each tool in the prerequisites section.
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 for gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, the troubleshooting section and connectivity testing examples use PowerShell commands (e.g., Test-NetConnection) and Windows tools (netstat -aon) without providing Linux/macOS equivalents. The examples and guidance are Windows-centric, and Linux users are not provided with alternative commands or approaches for equivalent tasks.
Recommendations
- Add Linux/macOS equivalent commands for network troubleshooting, such as using 'nc' (netcat), 'ss', or 'telnet' for TCP connectivity testing, and 'lsof' or 'netstat' for port/process mapping.
- Explicitly state that the troubleshooting steps are Windows-specific and provide parallel instructions for Linux users where applicable.
- Where PowerShell is used, offer Bash or shell alternatives for Linux/macOS environments.
- Clarify that gateway-required integration is Windows-only, but troubleshooting and network diagnostics may be relevant for Linux users in related scenarios.
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 automating certificate operations, but PowerShell is presented as a primary scripting option alongside CLI. Windows tools such as IIS and Certreq.exe are referenced for certificate export, with only a brief mention of OpenSSL for Linux/macOS users. Windows-specific tools are mentioned before Linux equivalents, and the PowerShell example is given equal prominence to Azure CLI, which may create friction for Linux/macOS users. However, most steps are portal-based and platform-agnostic, and OpenSSL is referenced for certificate creation/export.
Recommendations
- Expand Linux/macOS guidance for certificate export, including step-by-step OpenSSL instructions for common scenarios.
- Provide Bash shell scripting examples for automation alongside PowerShell.
- Mention OpenSSL and Linux/macOS tools before or alongside Windows tools such as IIS and Certreq.exe.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add links to Linux/macOS-specific certificate management documentation where relevant.
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 examples for accessing certificates in Windows apps (including C# and Java code for Windows certificate store), but gives only minimal guidance for Linux apps and containers. Linux examples are limited to C# file loading, and other languages (Node.js, PHP, Python, Java) are referenced only generically, with no concrete code samples. Windows-specific tools and patterns (certificate store, environment variables, user profile loading) are described in depth, while Linux equivalents are not explained or demonstrated. Windows content appears first and is more comprehensive.
Recommendations
- Add concrete code examples for loading certificates in Linux containers and apps for popular languages (Node.js, Python, Java, PHP), not just C#.
- Provide step-by-step instructions for accessing certificates in Linux environments, including how to use environment variables and file paths.
- Ensure Linux guidance is as detailed as Windows guidance, including troubleshooting and best practices.
- Consider presenting Linux and Windows sections in parallel or tabs, rather than Windows-first.
- Clarify any differences in certificate handling between Windows and Linux, and provide guidance for cross-platform scenarios.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section introduces Windows bias by requiring the installation of Hybrid Connection Manager only on Windows Server hosts, with no mention of Linux support or alternatives. No Linux-specific examples or guidance are provided for this feature, which may create friction for Linux users wishing to use Hybrid Connections.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux or 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 users (such as VPN, ExpressRoute, or other outbound connectivity features).
- Where possible, provide Linux/macOS equivalents or examples for any tooling or configuration steps.
- Review other sections for opportunities to add Linux-specific guidance, especially for outbound connectivity scenarios.
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 instructions. It also references tools like Excel and Visual Studio for log analysis, which are primarily Windows-centric, and does not mention Linux/macOS alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-specific tools.
Recommendations
- Add Azure CLI and/or Azure Cloud Shell examples for enabling diagnostic logging, as these are cross-platform and widely used by Linux/macOS users.
- Include references or examples for analyzing logs using Linux/macOS-friendly tools (e.g., jq for JSON processing, csvkit, or open-source visualization tools).
- When mentioning Excel or Visual Studio, also mention alternatives such as LibreOffice Calc, VS Code, or command-line tools.
- Clarify that PowerShell Core is available cross-platform, if relevant, and provide installation links or notes.
- Consider providing Bash or Python script examples for common log processing tasks.
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 provides extensive coverage of both Windows and Linux environment variables and app settings for Azure App Service. However, there are several instances where Windows-specific details, paths, and tools are mentioned first or exclusively, and Linux equivalents are only mentioned later or in less detail. Some examples and references (such as file paths, time zones, and logging) default to Windows conventions, and certain features/tools (e.g., Web Deploy/MSDeploy, Kudu) are described with a Windows-centric perspective. There are also a few cases where Linux examples or tools are missing or less emphasized.
Recommendations
- Ensure that all examples (such as file paths, environment variable values, and configuration snippets) are provided for both Windows and Linux, or clearly indicate when a setting is platform-specific.
- When describing features or tools that have both Windows and Linux implementations (e.g., deployment engines, logging paths), provide Linux information with equal prominence and detail.
- Avoid defaulting to Windows-first language (e.g., 'D:\home' before '/home'), or alternate the order to avoid implicit prioritization.
- Where Windows-only tools are mentioned (e.g., MSDeploy, Web Deploy), explicitly state their Linux equivalents or clarify if no equivalent exists.
- Add more Linux-specific troubleshooting tips and usage notes where applicable.
Application Gateway
Configure an internal load balancer (ILB) endpoint
...configure-application-gateway-with-private-frontend-ip.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation provides only Windows-based examples for backend VMs (Windows Server 2019) and uses PowerShell scripts to install IIS, with no mention of Linux alternatives. All instructions for backend setup and verification are Windows-centric, and the only automation example is a PowerShell command. There are no examples or guidance for deploying Linux VMs or using Bash/SSH for configuration.
Recommendations
- Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Provide Bash/Cloud Shell (Bash) examples for installing a web server (e.g., Apache or Nginx) on Linux VMs.
- Add notes or sections explaining how to use SSH to connect to Linux VMs for backend configuration.
- Ensure that automation examples (e.g., VM extensions) are shown for both Windows and Linux, or clarify if only Windows is supported.
- When listing VM image choices, mention both Windows and Linux options, or clarify that either is supported.
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 concepts and settings. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and (2) backend authentication troubleshooting links point to IIS and Windows-specific resources before mentioning general concepts. No PowerShell-heavy or missing Linux example bias is present, but Windows tools and patterns are referenced exclusively in troubleshooting sections.
Recommendations
- Add links or references to Linux-based authentication troubleshooting guides (e.g., Apache, NGINX, or generic Kerberos/SPN configuration on Linux).
- Clarify that backend authentication concepts (NTLM, Kerberos, SPN) may apply to both Windows and Linux backends, and provide platform-neutral guidance where possible.
- When referencing backend logs or authentication, mention that Linux-based web servers (such as Apache or NGINX) may require different log review steps and configuration.
- If possible, provide examples or troubleshooting steps for common Linux backend scenarios alongside Windows/IIS examples.
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 include equivalent Azure CLI, Bash, or ARM template examples. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool.
Recommendations
- Add Azure CLI examples alongside PowerShell for configuration tasks such as enabling HTTP/2 support.
- Where possible, provide Bash or cross-platform scripting examples.
- Consider including ARM/Bicep template snippets for infrastructure-as-code users.
- Explicitly state when a feature can only be configured via PowerShell, if that is the case.
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. All VM examples use Windows Server, IIS installation is shown only via Azure PowerShell (with Windows-specific commands), and hosts file editing is described exclusively for Windows (with DOS commands and Windows file paths). No Linux VM, Apache/Nginx, or Linux/macOS hosts file instructions are provided, and Windows tools (ipconfig) are used without Linux/macOS equivalents.
Recommendations
- Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Include examples for installing Apache or Nginx on Linux VMs, using Bash or Azure CLI.
- Add hosts file editing steps for Linux/macOS (e.g., /etc/hosts, using sudo nano or vi).
- Mention Linux/macOS commands for DNS cache refresh (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo dscacheutil -flushcache').
- Clarify that backend pools can use any OS and provide links to relevant Linux documentation.
- Show Azure CLI examples alongside PowerShell for cross-platform parity.
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
windows_tools
Summary
The documentation page demonstrates notable Windows bias. Azure PowerShell is used exclusively for preview registration and IIS installation, with no mention of Azure CLI or Bash alternatives. The VM creation example uses Windows Server 2019 Datacenter, and IIS (a Windows web server) is installed for testing, with no Linux VM or Apache/Nginx examples. All command-line instructions are Windows/PowerShell-centric, and Windows tools/patterns are referenced before any Linux equivalents (which are absent).
Recommendations
- Provide Azure CLI (bash) equivalents for preview registration and unregistration steps.
- Include Linux VM creation instructions alongside Windows, using Ubuntu or another common distribution.
- Offer guidance for installing Apache or Nginx on Linux VMs for backend testing, in addition to IIS.
- Add examples for Linux users in the backend pool configuration and testing sections.
- Mention that Application Gateway can work with both Windows and Linux backend servers, and link to relevant Linux documentation.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides Azure CLI and PowerShell examples for disabling routing to a regional gateway, but lists the Azure PowerShell cmdlet before the Azure CLI command in the tools list. There are no explicit Linux/macOS-specific examples or mentions, but the Azure CLI commands shown are cross-platform. The documentation does not reference Windows-only tools or patterns, but the ordering of PowerShell and CLI tools may subtly favor Windows users.
Recommendations
- List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) when describing options.
- Explicitly note that Azure CLI commands work on Linux/macOS as well as Windows.
- Where possible, provide Bash shell examples alongside Azure CLI commands to demonstrate Linux parity.
- Avoid referencing PowerShell as the primary tool unless the task is Windows-specific.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are given for every step and are labeled 'Formatted for PowerShell', which is a Windows-centric shell. Bash examples are present, but PowerShell examples are always shown immediately after, suggesting a slight Windows-first bias. No Linux-specific tools or patterns are missing, but the PowerShell emphasis may create friction for Linux/macOS users.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider grouping Bash and PowerShell examples under explicit OS tabs (e.g., 'Linux/macOS' and 'Windows') for clearer parity.
- Ensure Bash examples are shown first or equally, to avoid implicit Windows prioritization.
- Add a note explaining the equivalence of Bash and PowerShell commands for cross-platform users.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, but PowerShell is given equal prominence to CLI and is referenced in metadata and prerequisites. There is a mild bias in listing PowerShell alongside CLI, which can create friction for Linux/macOS users who typically use CLI or Bash. However, the CLI example is present and complete, and no Windows-only tools or patterns are required.
Recommendations
- Clarify that Azure PowerShell is cross-platform, but highlight Azure CLI as the primary method for Linux/macOS users.
- Add Bash shell example for deploying the ARM template, or explicitly mention that Azure CLI works natively on Linux/macOS.
- Ensure that prerequisites and environment setup instructions for Azure CLI are as detailed as those for PowerShell.
- Consider listing Azure CLI examples before PowerShell to better serve Linux/macOS users.
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 shown immediately after the Bash ones for every command. This creates a mild bias toward Windows users, as PowerShell is primarily a Windows shell, and its inclusion may suggest Windows as a primary platform. However, Bash examples are present and shown first, ensuring Linux parity.
Recommendations
- Clearly label Bash and PowerShell examples to help users quickly identify their platform.
- Consider grouping Bash and PowerShell examples under explicit headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- If possible, provide a brief note explaining which shell to use depending on the user's OS.
- Ensure that Bash examples remain first for cross-platform parity.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the Bicep file. Azure CLI is presented first, which is cross-platform, followed by Azure PowerShell, which is more Windows-centric. There are no exclusive Windows tools or missing Linux examples; both deployment methods are covered. The only minor bias is the ordering, with PowerShell mentioned second and tracked in metadata.
Recommendations
- Ensure that Azure CLI examples are emphasized as the default for cross-platform users.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, while Azure PowerShell is primarily Windows-focused.
- Consider adding a note for Linux/macOS users recommending Azure CLI for best compatibility.
- If possible, provide links to installation instructions for 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 detailed PowerShell examples first for both backup and restore operations, with Bash/Azure CLI examples presented after. The PowerShell focus may create friction for Linux/macOS users, as PowerShell is traditionally associated with Windows, even though cross-platform versions exist. However, the inclusion of Azure CLI (Bash) and REST API examples ensures Linux/macOS users can complete all tasks.
Recommendations
- Explicitly mention that Azure PowerShell is cross-platform and can be installed on Linux/macOS, linking to installation instructions for those platforms.
- Consider presenting Azure CLI (Bash) examples before PowerShell, or at least side-by-side, to better reflect cross-platform parity.
- Add a short note at the start of the examples section clarifying that all shown tools (PowerShell, CLI, REST) are supported on Windows, Linux, and macOS.
- Where possible, use neutral variable names and avoid assumptions about the user's shell environment.
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 lists Windows/PowerShell options before Linux equivalents in the prerequisites section, specifically when describing how to create an Azure Kubernetes cluster. However, all deployment steps and examples use cross-platform tools (kubectl) and are not Windows-specific. No PowerShell-heavy or Windows-only tools are used in the main workflow.
Recommendations
- List Linux (Azure CLI) and Windows (PowerShell) options in parallel or clarify that both are supported equally.
- Consider mentioning that Azure CLI works on Windows, Linux, and macOS, and is generally recommended for cross-platform scenarios.
- If possible, provide explicit examples for both Azure CLI and PowerShell commands, or link to documentation that does so.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides a generally cross-platform overview of Azure App Service backup and restore, but exhibits mild Windows bias. Windows-specific paths (e.g., %HOME%, D:\home\site\wwwroot), references to Windows tools (Kudu DebugConsole, FTP), and Windows examples (e.g., MySQL in-app for Web Apps (Windows)) are presented before or more prominently than their Linux equivalents. PowerShell is mentioned alongside Azure CLI, but Linux-specific scripting or shell examples are absent. Linux paths and behaviors are referenced, but less frequently and often after Windows examples.
Recommendations
- Provide Linux/macOS-specific examples and paths (e.g., /home/site/wwwroot) alongside Windows paths.
- Clarify that tools like Kudu DebugConsole and FTP are available for both Windows and Linux App Service apps.
- Add Linux/macOS shell scripting examples where PowerShell is referenced.
- Ensure that Linux app backup/restore workflows are equally detailed and illustrated.
- Mention Linux-specific nuances (e.g., file permissions, case sensitivity) where relevant.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux-specific sections using pivot blocks, ensuring parity in most areas. However, in shared/general sections, Windows examples (e.g., PowerShell commands) are often presented before Linux/Bash equivalents. Some advanced configuration and diagnostic instructions (such as memory and CPU limits, and Kudu/PowerShell-based diagnostics) are more detailed for Windows containers. PowerShell commands are consistently shown alongside Bash, but Bash is not always shown first. There is a slight preference for Windows tools and patterns in the ordering and depth of examples.
Recommendations
- In shared/general sections, present Bash/Linux commands before or alongside PowerShell/Windows commands to avoid implicit prioritization.
- Ensure that advanced configuration and diagnostic instructions are equally detailed for both Linux and Windows containers, or clearly indicate platform limitations.
- Where possible, provide Linux-native troubleshooting and diagnostic tool instructions (e.g., using Linux shell commands in Kudu/SSH for Linux containers).
- Review the order of platform-specific sections to alternate or balance Windows and Linux coverage.
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 command-line examples for Azure CLI and Azure PowerShell in all relevant sections. While both tools are cross-platform, PowerShell is historically associated with Windows and is listed after Azure CLI in each example. No Linux-specific tools or shell commands (such as Bash) are provided, but Azure CLI is available on Linux/macOS. The documentation does not show explicit Windows bias in content or features, but the inclusion of PowerShell examples may create a slight Windows-centric impression.
Recommendations
- Clarify that Azure CLI and PowerShell are both cross-platform and available on Linux/macOS.
- Consider adding Bash shell script examples for common tasks, or explicitly mention that Azure CLI commands can be run from Bash on Linux/macOS.
- If possible, provide brief notes about CLI usage on Linux/macOS (e.g., installation links, shell compatibility).
- Ensure parity in troubleshooting and post-migration steps for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for most tasks, but PowerShell examples are given their own sections and are sometimes more detailed. In some cases, PowerShell is referenced before CLI, and there are explicit notes about PowerShell limitations. However, the CLI examples are present and usable on Linux/macOS, and ARM template instructions are platform-neutral. There are no Windows-only tools or patterns, and the documentation does not assume Windows as the default platform.
Recommendations
- Ensure Azure CLI examples are always presented before or alongside PowerShell examples, especially in sections where PowerShell is currently given prominence.
- Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Where PowerShell is used for scripting, consider providing Bash equivalents for token retrieval or other scripting tasks.
- Add explicit notes or links for Linux/macOS users if any step is platform-specific or if there are known limitations.
- Review the 'PowerShell' tab in the 'Connect to Azure services in app code' section and consider adding Bash/cURL examples for token retrieval.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers Azure App Service Plans for both Windows and Linux, but certain sections (such as Managed Instance) are Windows-only. However, the main content does not show significant Windows bias: it mentions both OS options, does not prioritize Windows tools or patterns, and does not provide Windows/PowerShell examples exclusively. The only minor bias is that Windows is listed first in the 'Operating system' bullet, and the Managed Instance section is Windows-only (which is appropriate, as noted).
Recommendations
- Where OS options are listed, alternate the order (e.g., 'Linux, Windows') or clarify parity where possible.
- If future examples or CLI instructions are added, ensure both Windows and Linux (Bash) examples are provided.
- Add links to Linux-specific App Service documentation or highlight feature parity between Windows and Linux plans.
- Clarify that Managed Instance is intentionally Windows-only and provide a pointer to Linux/container alternatives if available.
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service virtual network integration, with most concepts and instructions applicable to both Windows and Linux. However, in the 'Windows Containers specific limits' section, Windows container scenarios are described first and in detail, while Linux container limits are not discussed. Additionally, the troubleshooting section includes Azure CLI (bash) examples, which are cross-platform, and Linux continuous deployment is explicitly mentioned. Overall, the bias is minor and limited to Windows container details being presented first and more thoroughly.
Recommendations
- Add a comparable section detailing subnet/IP requirements and networking unit calculations for Linux containers, if applicable.
- Ensure parity in container-specific guidance by clarifying any Linux container limitations or requirements.
- Where Windows-specific limits are discussed, provide a clear statement if Linux containers do not have similar constraints, or link to Linux container documentation.
- Consider presenting container-specific limits in a way that makes clear which guidance applies to Windows, Linux, or both.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway health monitoring provides detailed conceptual information applicable to all platforms. However, it demonstrates a mild Windows bias by referencing PowerShell cmdlets and examples for custom probe configuration and response matching, without offering equivalent Azure CLI or ARM template examples. Additionally, the 'MinServers' property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but only PowerShell is shown in examples. The 'Next steps' section lists PowerShell before Azure portal, and does not mention Azure CLI or ARM template guides.
Recommendations
- Add Azure CLI examples alongside PowerShell for configuring custom probes and response matching.
- Provide ARM template snippets for probe configuration and matching criteria.
- Explicitly mention Azure CLI and ARM template documentation in 'Next steps' and throughout the page where PowerShell is referenced.
- Ensure parity in example ordering, showing Azure CLI and PowerShell together or alternating their order.