210
Pages Scanned
31
Pages Flagged
210
Changed Pages
14.8%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-04 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 210
Files Completed: 210
Problematic Pages
31 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
powershell_heavy
missing_linux_example
windows_tools
Summary
The tutorial is heavily oriented toward Windows users, with all instructions and screenshots based on Visual Studio for Windows. Steps for publishing, managing, and configuring the ASP.NET app and Azure SQL Database rely exclusively on Visual Studio (Windows), and PowerShell/Package Manager Console commands are used without Linux/macOS alternatives. There are no examples or guidance for Linux/macOS users, such as using VS Code, CLI tools, or cross-platform workflows.
Recommendations
- Add instructions and screenshots for VS Code or Visual Studio for Mac, or clarify that only Visual Studio for Windows is supported for this workflow.
- Provide Azure CLI or cross-platform alternatives for tasks such as publishing, configuring managed identity, and database migrations.
- Include guidance for Linux/macOS users on how to run, develop, and deploy the sample ASP.NET app (e.g., using dotnet CLI, Azure CLI, or GitHub Actions).
- Mention any limitations or required adaptations for Linux/macOS users explicitly in the prerequisites section.
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_tools
missing_linux_example
windows_first
Summary
The documentation provides only Windows/PowerShell-based instructions for creating and exporting a self-signed certificate, and for installing IIS on backend VMs. There are no Linux/macOS equivalents for certificate creation or backend setup, and the examples and VM creation steps are Windows-centric, making it difficult for Linux/macOS users to follow the tutorial end-to-end.
Recommendations
- Add instructions for creating a self-signed certificate on Linux/macOS using OpenSSL, including exporting to PFX format.
- Mention and provide examples for using Linux VMs as backend servers, including installation of a simple web server (e.g., Nginx or Apache) for testing.
- Where PowerShell is used, provide equivalent Bash/CLI commands where possible, or link to official guides for non-Windows users.
- Clarify that the backend can be any supported OS, and provide parity in examples for both Windows and Linux.
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 before CLI and REST examples. While Azure CLI and REST API examples are also included, the prominence and depth of PowerShell coverage may create friction for Linux/macOS users, as PowerShell is primarily associated with Windows environments. However, the presence of CLI and REST options ensures Linux parity is possible.
Recommendations
- Present CLI and REST examples before or alongside PowerShell examples to avoid Windows-first impression.
- Explicitly note that Azure PowerShell is cross-platform and provide installation guidance for Linux/macOS users.
- Expand CLI examples to cover managed identity scenarios, matching the depth of PowerShell coverage.
- Add a short section clarifying tool parity and recommending CLI/REST for Linux/macOS users.
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 notable Windows bias. Azure PowerShell is the only CLI method shown for preview registration and IIS installation, with no equivalent Bash/Azure CLI or Linux examples. The VM creation example uses Windows Server exclusively, and IIS is used for backend testing, omitting Linux VM or web server alternatives. This creates friction for Linux/macOS users, though the portal-based steps are cross-platform.
Recommendations
- Provide Azure CLI (bash) examples for preview registration and unregistration alongside PowerShell.
- Include instructions for creating Linux VMs (e.g., Ubuntu) as backend targets, not just Windows Server.
- Offer Linux web server setup (e.g., Apache or Nginx) for backend testing, with sample install commands.
- Clarify that backend pools can use Linux VMs and provide parity in examples.
- Ensure that CLI instructions are presented for both PowerShell and Bash/Azure CLI, or link to equivalent Linux/macOS guidance.
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
missing_linux_example
Summary
The documentation provides examples for 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. No explicit Linux/macOS shell examples (e.g., Bash) are provided, and PowerShell is mentioned in prerequisites alongside Azure CLI. The ordering of examples (portal, CLI, PowerShell) is neutral, but the inclusion of PowerShell-specific instructions without Linux/macOS-specific alternatives may create friction for non-Windows users.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider adding Bash shell examples or notes for Linux/macOS users where relevant.
- Mention that Azure PowerShell is available cross-platform, but highlight CLI as the preferred tool for Linux/macOS users.
- Add explicit guidance for Linux/macOS users in the prerequisites section.
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 portal instructions are platform-neutral, but the CLI guidance is Windows-centric.
Recommendations
- Add Azure CLI examples for uploading CA certificates, if supported.
- If Azure CLI does not support this operation, clarify this limitation and suggest PowerShell Core (cross-platform) usage.
- Mention that PowerShell Core is available on Linux/macOS and provide installation guidance or links.
- Consider including Bash or REST API examples for certificate upload to improve 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_first
Summary
The documentation provides step-by-step instructions for using managed identities in Azure API Management via the Azure portal, Azure PowerShell, and ARM templates. However, all CLI examples are exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. PowerShell is Windows-centric, and Linux/macOS users are not given parity guidance. Additionally, PowerShell instructions are presented before ARM template examples, reinforcing Windows-first bias.
Recommendations
- Add Azure CLI examples for all operations currently shown in PowerShell (creating resource groups, API Management instances, assigning managed identities, updating instances).
- Explicitly mention that Azure CLI is cross-platform and provide links to Azure CLI documentation.
- Consider including Bash scripts or generic REST API examples for broader platform coverage.
- Where PowerShell is referenced, clarify that Azure CLI is an alternative for Linux/macOS 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 demonstrates a moderate Windows bias. Windows-specific approaches and code samples (especially for certificate store access) are presented first and in greater detail, with C# and Java examples for Windows but only C# examples for Linux. Instructions for non-Windows platforms and languages (Node.js, PHP, Python, Java) are deferred to external documentation. Windows tools and patterns (certificate store, environment variables, user profile loading) are described in detail, while Linux equivalents are less thoroughly covered.
Recommendations
- Provide equivalent code samples for Linux for all languages shown for Windows (e.g., Java, not just C#).
- Include explicit Linux examples earlier in the document, not only in container-specific sections.
- Offer direct code snippets or guidance for popular non-Windows languages (Node.js, Python, PHP) on both Windows and Linux, rather than referring users to external documentation.
- Balance the order of presentation so Linux and Windows approaches are shown side-by-side or in parallel sections/tabs.
- Clarify when a feature or approach is Windows-only, and provide clear Linux alternatives where possible.
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 managing Key Vault permissions, but PowerShell is given equal or slightly more prominence in some sections. There are references to Windows-specific tools (IIS, Certreq.exe) for exporting certificates, and links to Windows Server documentation for certificate export. In the automation FAQ, both Azure CLI and PowerShell are mentioned, but PowerShell is listed second. There are no Linux-specific certificate management examples (e.g., OpenSSL is mentioned, but not with Linux-specific context), and Windows tools are referenced for certificate export.
Recommendations
- Add explicit Linux/macOS examples for certificate export and management, especially for common tasks like exporting to .pfx (e.g., using OpenSSL on Linux/macOS).
- When referencing Windows tools (IIS, Certreq.exe), provide equivalent Linux/macOS instructions or links.
- In automation sections, ensure Azure CLI examples are shown first, as it is cross-platform, and clarify when PowerShell is Windows-only.
- Where possible, provide bash scripts or command-line examples for Linux/macOS users.
- Review links to ensure they do not point only to Windows Server documentation when cross-platform alternatives exist.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and describes Azure App Service networking features without explicit Windows bias. However, the 'Hybrid Connections' section requires installing Hybrid Connection Manager on a Windows Server 2012 or newer host, with no mention of Linux/macOS support or alternatives. This omission creates friction for Linux users who may need to use Hybrid Connections but cannot install the required agent on their preferred OS.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS hosts. If not, explicitly state the Windows-only requirement and suggest alternative approaches for Linux users.
- If possible, provide or link to Linux/macOS-compatible relay agents or tools for Hybrid Connections.
- For all examples and tool references, ensure parity by mentioning Linux/macOS equivalents or limitations where relevant.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, ARM templates, and the Azure portal. While Azure CLI and ARM templates are cross-platform, PowerShell examples are prominent and sometimes shown before CLI examples. In some sections, PowerShell is used for both CLI and PowerShell tabs (e.g., 'az identity create' is labeled as 'azurepowershell-interactive'), which may confuse Linux/macOS users. Additionally, PowerShell is given its own code tab for token retrieval, but there is no equivalent Bash or shell script example. The documentation does not mention Windows-specific tools, but the ordering and prominence of PowerShell can create friction for non-Windows users.
Recommendations
- Ensure that Azure CLI examples are always shown before PowerShell examples, as CLI is more cross-platform.
- Add Bash or shell script examples for token retrieval from the REST endpoint, especially in the 'Connect to Azure services in app code' section.
- Clarify labeling in code blocks to distinguish between Azure CLI and PowerShell, avoiding confusion (e.g., do not use 'azurepowershell-interactive' for Azure CLI commands).
- Consider adding explicit notes or examples for Linux/macOS users where PowerShell is not supported or less common.
- Where possible, provide parity in scripting examples (e.g., Bash, Python) alongside PowerShell.
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 environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths, tools (such as Web Deploy/MSDeploy, IIS, and site extensions), and examples are often mentioned first or exclusively, with Linux equivalents sometimes missing or appearing later. Some settings and explanations reference Windows conventions (e.g., `D:\home`, `%HOME%`, `.dll` extensions, Windows-specific build automation with Kudu) before Linux paths or tools. In several sections, Windows-centric terminology and features (such as site extensions, msbuild, and IIS logging) are prioritized or lack Linux parity in explanation or examples.
Recommendations
- Ensure Linux paths and conventions (e.g., `/home`, `/tmp`) are mentioned alongside Windows paths in all relevant settings.
- Provide Linux-specific examples and explanations for deployment, build automation, logging, and language runtimes where only Windows tools or patterns are described.
- Clarify which settings are Windows-only and which are cross-platform, ideally with clear labeling or tabbed sections.
- Add Linux equivalents for Windows tools (e.g., Web Deploy/MSDeploy) or explicitly state when no equivalent exists.
- Review all examples and ensure Linux/macOS users can follow them without ambiguity or missing information.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides explicit instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent CLI (az), Bash, or Linux/macOS examples. The only command-line example is a PowerShell cmdlet, which is Windows-centric. Additionally, references to log conversion tools are tied to Visual Studio and C#, which are more commonly associated with Windows environments. There is no mention of Linux/macOS-friendly alternatives or parity in command-line instructions.
Recommendations
- Add Azure CLI (az) examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples where relevant.
- Mention or link to log conversion tools that can be used on Linux/macOS, such as Python scripts or open-source alternatives.
- When referencing PowerShell, clarify that PowerShell Core is available cross-platform, but provide CLI alternatives for users who may not wish to install PowerShell.
- Ensure that examples and screenshots are not exclusively Windows-centric, and consider including Linux/macOS UI screenshots if relevant.
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 (az), Bash, or Cloud Shell examples, nor does it mention Linux/macOS tooling. This may create friction for users who do not use PowerShell or Windows environments.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for configuration tasks, especially for enabling HTTP/2 support.
- Explicitly mention that configuration can be performed from any OS using the Azure portal or Azure CLI.
- Where PowerShell is shown, provide Bash/CLI equivalents or link to cross-platform instructions.
- Clarify that PowerShell Core is available cross-platform if relevant, or recommend the Azure Cloud Shell for OS-agnostic scripting.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides PowerShell-centric examples and references, particularly for custom probe configuration and advanced parameters (e.g., MinServers, probe match criteria). Linux equivalents (Azure CLI, ARM templates) are mentioned but not demonstrated, and PowerShell is presented as the primary method for advanced configuration. Additionally, PowerShell cmdlets are shown before any mention of other tools, creating a Windows-first impression.
Recommendations
- Add Azure CLI examples for probe configuration and match criteria, especially for custom probes and advanced settings like MinServers.
- Include ARM template snippets for relevant configuration tasks.
- Explicitly state parity between PowerShell and Azure CLI/ARM for all probe-related operations.
- Where PowerShell is used, provide equivalent CLI commands or links to CLI documentation.
- Consider showing CLI examples before PowerShell or side-by-side for cross-platform clarity.
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_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for configuring an internal load balancer endpoint on Azure Application Gateway Standard v1, but it exhibits notable Windows bias. All virtual machine examples use Windows Server images, and IIS installation is demonstrated exclusively via PowerShell in Azure Cloud Shell. There are no Linux VM examples, nor are Linux-based backend server setup instructions provided. The PowerShell Cloud Shell is used by default, with no mention of Bash or Linux alternatives.
Recommendations
- Include examples for creating Linux-based backend VMs (e.g., Ubuntu) alongside Windows Server.
- Provide instructions for installing a web server (such as Apache or Nginx) on Linux VMs, using Bash in Azure Cloud Shell.
- Show how to use Bash Cloud Shell for relevant steps, or at least mention that Bash is an option.
- Ensure backend pool addition steps reference both Windows and Linux VMs.
- Add a note clarifying that backend pools can contain both Windows and Linux servers, and provide parity in examples.
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
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation demonstrates a notable Windows bias. All backend VM examples use Windows Server, and IIS is installed using PowerShell commands. The hosts file editing instructions and command-line examples are exclusively for Windows (e.g., referencing c:\Windows\System32\drivers\etc, using ipconfig). There are no Linux VM or web server examples, nor are there instructions for editing /etc/hosts or using Linux command-line tools.
Recommendations
- Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Include examples for installing a Linux web server (e.g., Apache or Nginx) and verifying connectivity.
- Add guidance for editing the /etc/hosts file on Linux/macOS, including appropriate commands (e.g., using sudo nano /etc/hosts and sudo systemctl restart networking or equivalent).
- Mention Linux/macOS equivalents for commands like ipconfig (e.g., systemd-resolve --flush-caches or sudo service network-manager restart).
- Clarify that the Application Gateway supports both Windows and Linux backend servers, and that the choice of OS is flexible.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements. However, in the 'Related content' section, the link 'Connect virtual networks from different deployment models using PowerShell' references PowerShell specifically, which is a Windows-centric tool. No Linux/bash equivalents are mentioned alongside this link, and PowerShell is listed before other general resources.
Recommendations
- Add links or references to equivalent Linux/bash CLI documentation for connecting virtual networks (e.g., Azure CLI examples).
- When mentioning PowerShell-specific guidance, also mention or link to Linux/macOS-compatible tools and instructions (such as Azure CLI or ARM templates).
- Ensure parity in example scripts and tooling references throughout the documentation, especially in 'Related content' sections.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given immediately after Bash, and the PowerShell formatting is explicitly called out, which may indicate a slight Windows bias. There are no Linux-specific tools or patterns mentioned, but Bash is presented first, which is positive for Linux parity. No critical Linux functionality is missing.
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 clarity.
- Add a brief note explaining which shell to use on each platform to reduce confusion.
- Ensure parity in explanations for both shells, not just formatting.
API Center
Perform API Linting and Analysis
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both bash and PowerShell examples for Azure CLI commands, but PowerShell syntax is consistently shown after bash. Visual Studio Code is recommended as the editor, which is cross-platform, and all tooling (Azure CLI, Azure Developer CLI, Azure Functions Core Tools, Node.js, npm) is available for Linux/macOS. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks. However, minor bias exists in the order of examples and some output paths referencing Windows directories.
Recommendations
- Ensure all CLI examples are shown for both bash and PowerShell, with clear labeling.
- Consider alternating the order of bash and PowerShell examples or grouping them together to avoid implicit prioritization.
- Where possible, use generic output paths or note that output locations may differ by OS.
- Explicitly state that all steps are supported on Linux/macOS and Windows.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given alongside Bash for every step, and in some cases, PowerShell syntax is shown first or equally, which may indicate a slight Windows bias. There are no missing Linux examples, but the presence of PowerShell throughout may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clearly label Bash and PowerShell examples, and consider showing Bash (Linux/macOS) examples first, as Bash is the default shell for most non-Windows environments.
- Provide brief guidance for macOS users if any commands differ or require additional setup.
- If PowerShell is not required for Linux/macOS, clarify that Bash is the recommended shell for those platforms.
- Consider grouping PowerShell examples in a separate tab or section to reduce clutter for Linux/macOS readers.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions Azure PowerShell and Azure CLI as tools for reviewing deployed resources, but lists Azure PowerShell before Azure CLI. This ordering may subtly prioritize Windows tooling, as PowerShell is most commonly associated with Windows environments, even though it is cross-platform. No explicit Linux/macOS examples or tools are provided, and no command-line examples are shown.
Recommendations
- List Azure CLI before Azure PowerShell, as Azure CLI is more commonly used on Linux/macOS.
- Explicitly mention that both Azure CLI and Azure PowerShell are cross-platform.
- Provide example commands for both Azure CLI and Azure PowerShell, ensuring Linux/macOS users see parity.
- Consider referencing Bash or shell scripting where relevant for Linux/macOS users.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is mentioned alongside CLI throughout and receives equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the prerequisites section includes Azure PowerShell requirements. However, Azure CLI (cross-platform) is also fully supported and shown first in the deployment example tabs. No Windows-only tools or patterns are exclusively mentioned, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider mentioning Bash or shell scripting as alternatives for Linux/macOS users where appropriate.
- Ensure that any references to uploading files (e.g., in Cloud Shell) include instructions for Linux/macOS users, such as using SCP or drag-and-drop.
- If possible, add a note that Azure PowerShell is available cross-platform, but CLI is generally preferred for Linux/macOS.
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 is generally cross-platform, focusing on Azure portal and Azure CLI, which are available on Windows, Linux, and macOS. However, there is mild Windows bias in the 'Disable routing to a regional gateway' section, where the Azure PowerShell cmdlet (set-azapimanagement) is mentioned alongside Azure CLI and REST API, but no equivalent Linux/macOS-specific tooling is highlighted. Additionally, PowerShell is mentioned before REST API and Azure CLI in the tools list, which may subtly prioritize Windows patterns.
Recommendations
- Explicitly state that Azure CLI and REST API are fully supported on Linux/macOS.
- When listing tools, mention cross-platform options (Azure CLI, REST API) before Windows-specific ones (PowerShell).
- If PowerShell is referenced, clarify its cross-platform availability or provide Bash/shell script equivalents where relevant.
- Add a note that all Azure CLI examples work on Linux/macOS terminals.
- Consider including sample Bash scripts for common operations, if relevant.
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 provides links for creating an Azure Kubernetes cluster using Azure CLI, Azure PowerShell, and Azure Portal. The PowerShell (Windows-centric) option is mentioned second, after Azure CLI, and before Azure Portal. All command examples use kubectl, which is cross-platform, and no Windows-specific tools or patterns are prioritized or exclusively mentioned. There are no missing Linux/macOS examples, and no Windows-only tools are used.
Recommendations
- Consider listing Azure CLI and Azure Portal options before Azure PowerShell, as CLI is more cross-platform and PowerShell is Windows-centric.
- Explicitly note that all kubectl commands work on Linux, macOS, and Windows.
- If possible, provide brief guidance for Linux/macOS users on installing kubectl and Azure CLI, or link to relevant documentation.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is presented as an equal option throughout, which can create friction for Linux/macOS users since PowerShell is less commonly used outside Windows. In some sections, PowerShell is mentioned alongside CLI, but not after CLI, and the prerequisites list PowerShell requirements separately. However, Azure CLI examples are always present, and there are no Windows-specific tools or patterns.
Recommendations
- Clarify that Azure CLI is cross-platform and generally preferred for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell in all sections to reinforce CLI as the default for non-Windows users.
- Add a brief note in the prerequisites indicating that PowerShell is optional and primarily for users who prefer it, especially on Windows.
- Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
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/general sections, Windows/PowerShell examples are often shown before Linux/Bash equivalents. PowerShell commands are consistently included alongside Bash, and some sections (like persistent storage and environment variables) mention Windows paths or behaviors first. There is also a tendency to reference Windows-specific tools and concepts (e.g., C:\home, IIS, .NET Framework) before their Linux counterparts, even in general guidance. However, Linux content is present and substantial, and Linux-specific instructions (e.g., for SSH, Docker Compose) are included where relevant.
Recommendations
- In shared/general sections, alternate the order of Bash and PowerShell examples, or present Bash (Linux/macOS) first to avoid implicit prioritization of Windows.
- Where possible, use neutral language and paths (e.g., '/home' and 'C:\home') together, or clarify platform-specific differences up front.
- Ensure that Linux-specific tools and workflows are mentioned with equal prominence and detail as Windows tools.
- Consider adding a summary table or section at the top that clearly distinguishes which instructions are for Windows and which are for Linux, to help users quickly find relevant content.
- Review for any subtle language that assumes a Windows-first audience (e.g., referencing Windows paths or features before Linux) and balance with Linux equivalents.
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 example commands for Azure portal, Azure CLI, and Azure PowerShell in all procedural sections. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is presented alongside CLI examples. In several sections, PowerShell examples are shown after CLI but are always present, which may reinforce Windows-centric workflows. There is no evidence of missing Linux/macOS examples, and the documentation does not reference Windows-specific tools or patterns outside PowerShell. The overall structure is platform-neutral, but the inclusion of PowerShell in every example may create a subtle Windows bias.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Consider explicitly mentioning that Azure CLI is recommended for Linux/macOS users.
- If possible, add brief notes or links for Bash scripting or automation for Linux users.
- Ensure that CLI examples are shown first or highlighted as the default for cross-platform scenarios.
- Review whether PowerShell examples are necessary in every section, or if they can be grouped in a dedicated appendix.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
minor_windows_path_patterns
Summary
The documentation provides both Azure portal and Azure CLI instructions, which are cross-platform. However, there are several subtle Windows biases: Windows path patterns (e.g., `%HOME%`, `D:\home\site\wwwroot\`), references to Kudu DebugConsole (which is more familiar to Windows users), and the use of Windows-style paths in backup filter examples. PowerShell is mentioned alongside Azure CLI for scripting, but no Bash or Linux shell scripting samples are linked. Windows path conventions and terminology are often presented first or exclusively, with Linux equivalents only briefly mentioned.
Recommendations
- Add explicit Linux/macOS path examples (e.g., `/home/site/wwwroot/`) alongside Windows paths.
- Provide Bash/Linux shell scripting samples in the 'Automate with scripts' section, not just PowerShell.
- Clarify that Kudu DebugConsole is available for both Windows and Linux App Service apps.
- Where `%HOME%` is referenced, add a note that Linux apps use `/home`.
- In backup filter examples, show both Windows and Linux path formats.
- Ensure that instructions for uploading files (e.g., via FTP) mention Linux-compatible tools and paths.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service Plans, explicitly noting both Windows and Linux support. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (e.g., PowerShell, RDP, IIS customization, .NET Framework) are described first and in detail, while Linux is only mentioned as unsupported for this feature. The main content otherwise avoids Windows bias, but the Windows-focused Managed Instance section appears before any Linux equivalent (which does not exist), potentially giving Windows users more visibility.
Recommendations
- Clearly label Windows-only features (such as Managed Instance) as Windows-specific, and consider grouping them in a dedicated section to avoid confusion.
- If Linux equivalents exist (e.g., Linux containers, custom OS features), provide links or brief descriptions for Linux users.
- Ensure parity in examples and guidance for both Windows and Linux App Service plans throughout the documentation.
- Add a short note in the Managed Instance section clarifying that Linux users should use standard App Service plans or containers for OS customization.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is largely 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 references to Windows documentation (Kerberos, IIS Windows Authentication) are mentioned without Linux equivalents or guidance for non-Windows backends. Additionally, Windows authentication is discussed before any mention of cross-platform alternatives, creating a mild 'windows_first' bias.
Recommendations
- Add guidance for troubleshooting authentication issues with Linux-based backends, such as using SPNEGO or other Kerberos implementations.
- Include references or links to documentation for configuring Kerberos/NTLM on Linux (e.g., Samba, MIT Kerberos, mod_auth_kerb for Apache).
- Clarify that NTLM and Kerberos are Windows-centric protocols, and provide information about supported authentication methods for Linux-based backend servers.
- If possible, add troubleshooting steps for common Linux web servers (Apache, Nginx) when used as Application Gateway backends.