251
Pages Scanned
49
Pages Flagged
251
Changed Pages
19.5%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:09
Scan Information
Started At: 2026-02-17 00:00:09
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 251
Files Completed: 251
Problematic Pages
50 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page heavily focuses on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows SDK dependencies. All setup instructions, examples, and installation steps are Windows-centric, with no mention of Linux/macOS equivalents or cross-platform alternatives for Artifact Signing. The only integrations with potential cross-platform support (GitHub Actions, Azure DevOps, SDK) are referenced briefly and externally, without detailed parity instructions.
Recommendations
- Provide explicit guidance for Linux/macOS users, including supported signing tools, installation steps, and examples.
- Clarify whether Artifact Signing supports non-Windows signing workflows and, if so, document them with equal detail.
- Add examples for using Artifact Signing SDK on Linux/macOS, including sample commands and environment setup.
- If SignTool is Windows-only, highlight alternative cross-platform signing tools (e.g., OpenSSL, GPG, or platform-agnostic SDK usage) and how they can integrate with Artifact Signing.
- Ensure that GitHub Actions and Azure DevOps instructions include Linux/macOS runners and relevant configuration details.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Windows/PowerShell tools and cmdlets are consistently mentioned first or exclusively for several management and backup tasks (e.g., unregistering DSC nodes, exporting runbooks/configurations). Linux equivalents (such as Azure CLI, REST API, or bash examples) are not provided for these operations. In the TLS upgrade section, both Windows and Linux guidance are present, but Windows instructions are more detailed and linked, while Linux is limited to a Python script without broader context or alternative methods.
Recommendations
- Provide Azure CLI, REST API, or bash examples alongside or in place of PowerShell cmdlets for tasks such as unregistering DSC nodes, exporting runbooks, and exporting DSC configurations.
- List Linux and cross-platform methods before or alongside Windows/PowerShell approaches in tables and instructions.
- Link to Linux-specific documentation or official Azure CLI references where available.
- Clarify when a feature or cmdlet is Windows-only, and suggest alternatives for Linux/macOS users if possible.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page is heavily focused on PowerShell cmdlets and Windows-centric patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, and there is no mention of Bash, Azure CLI, or Linux-native credential management approaches. The 'Create a new credential asset' section only provides a Windows PowerShell example, with no Linux or cross-platform CLI equivalent. The documentation assumes familiarity with PowerShell concepts and tools, which may create friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for creating and managing credential assets, if supported.
- Explicitly state if credential asset management is only possible via PowerShell, or clarify cross-platform alternatives.
- Provide guidance for Linux/macOS users, including how to install and use PowerShell Core (pwsh) if required.
- Mention any limitations or platform requirements for credential management in Azure Automation.
- Consider including Bash or shell script examples if relevant APIs exist.
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 detailed instructions and code samples for using Azure PowerShell to create and manage managed identities in Azure API Management, but does not offer equivalent examples for Azure CLI or Bash scripting. PowerShell is presented as the primary scripting option, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or parity for command-line tasks, and PowerShell examples are shown before ARM template examples.
Recommendations
- Add Azure CLI examples for all PowerShell sample sections, including creation, updating, and removal of managed identities.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
- Consider showing Azure CLI and PowerShell examples side-by-side, or at least alternating which is presented first.
- Clarify that ARM templates are cross-platform and can be deployed from any OS, and provide guidance for deploying them using Azure CLI.
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 CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. PowerShell examples are given equal prominence to Azure CLI, but there is no explicit mention of Linux/macOS alternatives for PowerShell. The CLI example is cross-platform, but the PowerShell section may create friction for Linux/macOS users. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not clarify PowerShell Core compatibility or provide guidance for Linux users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Indicate whether the PowerShell example is compatible with PowerShell Core on Linux/macOS, or provide a note about PowerShell Core support.
- Consider adding a Bash shell example for Azure CLI usage to reinforce Linux parity.
- Explicitly mention that PowerShell is primarily for Windows users, and suggest CLI 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 presents Windows examples and concepts first, with detailed C# and Java code for accessing certificates via the Windows certificate store. Linux guidance is limited, mostly referencing file-based access and deferring language-specific examples to external documentation. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are emphasized, while Linux and non-Windows language examples are sparse or missing.
Recommendations
- Provide code examples for loading certificates in popular Linux-hosted languages (Node.js, Python, PHP, Java) directly in the documentation, not just C#.
- Present Linux and Windows guidance in parallel sections or tabs, rather than Windows-first.
- Expand Linux-specific instructions beyond file paths, including sample code for common certificate operations.
- Clarify any differences in certificate handling between Windows and Linux containers, including environment variable usage.
- Add explicit guidance for macOS scenarios if relevant.
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
missing_linux_example
Summary
The documentation provides some Windows-specific guidance and examples, such as referencing IIS and Certreq.exe for certificate export, and links to a Windows Server 2008 guide for exporting certificates. PowerShell and Azure CLI are both presented for RBAC, but in the FAQ and automation sections, PowerShell is mentioned before CLI. There are no explicit Linux/macOS certificate export instructions or references to Linux tools (other than OpenSSL), and the Windows export path is more detailed. This may create friction for Linux/macOS users, especially those unfamiliar with Windows certificate tooling.
Recommendations
- Add explicit Linux/macOS instructions for exporting certificates (e.g., using OpenSSL for .pfx export when the certificate was generated on Linux).
- When referencing certificate export, provide parity between Windows (IIS/Certreq.exe) and Linux/macOS (OpenSSL) methods, with links to relevant documentation for both.
- In automation and FAQ sections, list Azure CLI and PowerShell examples in parallel or in a neutral order, or clarify that both are supported equally.
- Where possible, avoid linking only to Windows-specific documentation for common tasks (e.g., exporting .pfx files), and include cross-platform alternatives.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths, tools, and terminology (such as 'D:\home', 'applicationHost.config', IIS, and Web Deploy/MSDeploy) are frequently mentioned first or exclusively, while Linux equivalents are sometimes missing or only referenced later. Some sections (e.g., build automation, logging, caching) provide more detail for Windows scenarios and tools, with Linux alternatives referenced but not always explained equally. Examples and explanations often default to Windows conventions, even when Linux is supported.
Recommendations
- Where Windows paths or tools are mentioned (e.g., 'D:\home', 'applicationHost.config', IIS, Web Deploy/MSDeploy'), add equivalent Linux paths or tools (e.g., '/home', Nginx/Apache, Oryx build, ZIP deploy) and explain differences.
- Ensure Linux-specific environment variables and behaviors are documented with equal detail and clarity as Windows.
- When listing environment variables, avoid defaulting to Windows-first order; consider grouping by OS or providing parallel tables/examples for Windows and Linux.
- Add explicit Linux/macOS examples where only Windows examples are given (e.g., for deployment, logging, caching, build automation).
- Clarify which settings are Windows-only and which are cross-platform, to reduce confusion for Linux users.
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 example for Azure CLI, Bash, or other cross-platform tools. The only command-line automation guidance is Windows-centric, and there is no mention of Linux/macOS-friendly alternatives. Additionally, the log conversion tool referenced is a C#/.NET-based solution, which is more familiar to Windows users.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but clarify if the example requires Windows PowerShell or works on all platforms.
- Provide example scripts or commands for downloading and converting logs using common Linux/macOS tools (e.g., jq for JSON parsing, csvkit for CSV conversion).
- Reference or link to log conversion tools or scripts that do not require Visual Studio or C#/.NET, or provide instructions for using open-source, platform-agnostic alternatives.
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 exclusively demonstrates deploying a SQL Server VM using Windows Server and connecting via SQL Server Management Studio (SSMS), which is a Windows-only tool. There are no examples or guidance for Linux-based SQL Server VMs, nor for connecting from Linux/macOS clients. The instructions and screenshots focus solely on Windows environments, creating friction for Linux users.
Recommendations
- Add instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) in Azure, including relevant screenshots and settings.
- Provide examples for connecting to the SQL Server backend using cross-platform SQL clients (such as Azure Data Studio, sqlcmd, or DBeaver) that work on Linux/macOS.
- Explicitly mention that SQL Server can be deployed on Linux and provide links to relevant documentation.
- Where possible, clarify that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends.
- Include troubleshooting tips or notes relevant to Linux-based SQL Server deployments.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples and instructions using PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions provided. The guidance assumes the reader is using PowerShell (locally or via Azure Cloud Shell), and script installation and usage steps are PowerShell-centric. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for configuration and traffic migration, or explicitly state if PowerShell is required.
- Add Bash script examples or instructions for Linux/macOS users, especially for certificate handling and resource management.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both Bash and PowerShell), and provide guidance for Bash users.
- Include a section comparing PowerShell and Azure CLI approaches, and link to Azure CLI documentation where relevant.
- Mention prerequisites for Linux/macOS users (e.g., installing PowerShell Core, if required), and provide installation guidance.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides configuration examples and references for Azure PowerShell first, with more detailed PowerShell guidance and command breakdowns than for Azure CLI. Azure CLI is included, but with less detail and no Linux/macOS-specific guidance. There are no explicit Linux/macOS shell examples for certificate extraction or management, and the 'Next steps' section directs users to a PowerShell-focused guide, omitting Linux-first or cross-platform alternatives.
Recommendations
- Provide equal depth of examples for Azure CLI as for PowerShell, including step-by-step breakdowns.
- Include Linux/macOS shell commands (e.g., OpenSSL) for certificate extraction, chain creation, and file management where relevant.
- In 'Next steps', link to both PowerShell and Azure CLI guides, or a cross-platform guide, not just PowerShell.
- Explicitly mention that all Azure CLI commands can be run on Linux/macOS, and provide troubleshooting or environment notes for non-Windows users.
- Where PowerShell is referenced, clarify if Azure Cloud Shell can be used cross-platform, or suggest alternatives for Linux/macOS users.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for Azure Application Gateway v2 shows evidence of Windows bias. The migration section references an Azure PowerShell script as the primary migration tool, and the registration/unregistration examples use Azure CLI commands with PowerShell syntax (e.g., Set-AzContext), which are Windows-centric. Additionally, the 'Next steps' section links first to a PowerShell-based tutorial. There are no explicit Linux/bash examples or instructions, and Windows tools/patterns are mentioned before any Linux equivalents.
Recommendations
- Provide equivalent bash/Linux shell examples for Azure CLI commands (e.g., using az instead of Set-AzContext).
- Clarify that Azure CLI is cross-platform and show examples in both PowerShell and bash syntax.
- Offer migration scripts or guidance for Linux/macOS users, or note if the PowerShell script can be run via Azure Cloud Shell (which is platform-agnostic).
- In 'Next steps', include links to tutorials using Azure CLI in bash or via the Azure Portal, not just PowerShell.
- Explicitly state platform compatibility for tools/scripts where relevant.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page repeatedly references Azure PowerShell scripts as the primary migration tooling, without mentioning or providing alternatives for Linux/macOS users (such as Azure CLI or ARM templates). There are no Linux/macOS-specific examples or guidance, and PowerShell is presented as the default approach for migration tasks.
Recommendations
- Provide equivalent Azure CLI commands or scripts for migration tasks, especially for public IP retention and configuration migration.
- Mention that Azure PowerShell can be run cross-platform (on Linux/macOS), but also clarify any prerequisites or limitations.
- Add examples or links for ARM template-based migration, if available.
- Explicitly state if certain scripts are Windows-only, and offer guidance for Linux/macOS users.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tools, such as New-SelfSignedCertificate and Export-PfxCertificate, with all examples and instructions provided only for Windows/PowerShell environments. There are no Bash, Azure CLI, or Linux/macOS alternatives, and Windows-centric commands (e.g., certificate creation, file paths) are used throughout. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows certificate tools.
Recommendations
- Add equivalent Azure CLI (bash) instructions and examples for all steps, especially resource creation and configuration.
- Provide Linux/macOS-compatible methods for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
- Use platform-neutral file paths or clarify how to adapt them for Linux/macOS.
- Mention that Azure PowerShell can be installed on Linux/macOS, or provide links to cross-platform installation guides.
- Consider including a note about cross-platform compatibility and alternative tooling for non-Windows users.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page exhibits Windows bias primarily through the exclusive mention of PowerShell and Windows-specific certificate tooling. The 'Next steps' section directs users only to a PowerShell-based configuration guide, and certificate format references link to Windows APIs. There are no Linux/macOS CLI or tooling examples, and Windows tools are mentioned before any cross-platform alternatives.
Recommendations
- Add equivalent Linux/macOS configuration guides using Azure CLI or ARM templates.
- Provide examples for certificate creation and management using OpenSSL or cross-platform tools, not just referencing Windows APIs.
- Include links to cross-platform documentation in the 'Next steps' section alongside PowerShell.
- Mention Azure Portal and REST API options for configuration, which are platform-agnostic.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell-based examples for configuring secure asset encryption in Azure Automation, with REST API alternatives but no Azure CLI or Linux/macOS-specific guidance. PowerShell is presented as the primary scripting method, and Linux-friendly approaches (such as Azure CLI or Bash) are either missing or only briefly mentioned. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer CLI/Bash workflows.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks, including assigning managed identities, configuring Key Vault access policies, and updating encryption settings.
- Explicitly mention cross-platform options (e.g., Azure CLI, Bash) and their compatibility with Linux/macOS.
- Reorder sections to present REST API and CLI examples before or alongside PowerShell, rather than after.
- Clarify that PowerShell examples are cross-platform (if using Az PowerShell Core), or provide guidance for Linux/macOS users if not.
- Link to Azure CLI documentation for relevant commands.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples use PowerShell, and references to credential management, module installation, and runbook scripting are exclusively in the context of PowerShell. There are no examples or guidance for users who may wish to use Python, Bash, or other cross-platform scripting languages supported by Azure Automation. The phrase 'Windows PowerShell' is used, and no mention is made of PowerShell Core (pwsh) or cross-platform compatibility. Linux/macOS users may find it unclear whether these instructions apply to them or how to adapt them.
Recommendations
- Clarify whether the PowerShell examples are compatible with PowerShell Core (pwsh) on Linux/macOS, or if they require Windows PowerShell.
- Add equivalent examples or guidance for using Python runbooks, which are supported in Azure Automation and widely used on Linux/macOS.
- If PowerShell is required, explicitly state that PowerShell Core is supported on all platforms, and provide installation instructions for Linux/macOS.
- Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, use 'PowerShell' to indicate cross-platform compatibility.
- Mention or link to documentation for Bash or other cross-platform scripting options in Azure Automation, if applicable.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation page for 'Disaster recovery for Azure Automation' is notably PowerShell-centric, with all migration scripts and runbook examples provided exclusively in PowerShell and PowerShell Workflow. There are no equivalent examples or guidance for Linux-native scripting tools (such as Bash or Python), nor are cross-platform alternatives discussed. Additionally, links and instructions often default to Windows tabs or terminology, and Windows is mentioned first in several hybrid worker scenarios. This creates friction for Linux/macOS users, especially those who prefer or require non-PowerShell solutions.
Recommendations
- Provide Bash or Python script examples for migrating Automation account assets, or clarify if PowerShell Core (pwsh) is fully supported cross-platform.
- Explicitly state PowerShell Core compatibility and provide instructions for Linux/macOS users, including installation and execution steps.
- Add guidance or links for using Azure CLI or REST API for asset migration where possible.
- Ensure hybrid worker instructions and links are balanced, showing both Windows and Linux tabs equally.
- Mention cross-platform considerations in prerequisites and limitations, such as PowerShell module support on Linux/macOS.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...in/articles/automation/how-to/private-link-security.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for configuring public network access flags, without offering an equivalent CLI or Linux-friendly example. While the article mentions both Windows and Linux in the context of Hybrid Runbook Workers and Update Management, the scripting guidance is Windows-centric. The PowerShell example is presented as the primary method for automation, and no Azure CLI, REST API, or ARM template alternatives are given. Additionally, PowerShell is mentioned before any Linux tools or cross-platform options.
Recommendations
- Add Azure CLI and/or REST API examples for configuring public network access flags, ensuring Linux/macOS users can follow along without PowerShell.
- Explicitly mention that PowerShell is available cross-platform, but provide guidance for Linux users on installing and using it if PowerShell is required.
- Where possible, provide ARM template snippets or portal instructions alongside scripting examples.
- Review other scripting sections for Windows-centric language or assumptions, and clarify cross-platform applicability.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily features PowerShell cmdlets and examples for certificate management in Azure Automation, with no mention of Linux/macOS shell equivalents or cross-platform CLI usage. All detailed examples for creating and managing certificates use PowerShell, and PowerShell is presented first and most prominently. There are Python examples for runbooks, but no guidance for Linux users on certificate creation or management outside of PowerShell.
Recommendations
- Add Azure CLI examples for certificate management tasks, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Clarify whether PowerShell examples are usable on PowerShell Core (pwsh) on Linux/macOS, or if Windows PowerShell is required.
- Provide guidance for Linux/macOS users on preparing .pfx/.cer files and uploading them via the Azure portal or CLI.
- Mention any limitations or differences for Linux/macOS users, especially if certain cmdlets or features are Windows-only.
- Ensure that introductory sections acknowledge cross-platform usage and link to relevant Linux/macOS documentation where applicable.
Automation
Manage modules in Azure Automation
...b/main/articles/automation/shared-resources/modules.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page is heavily focused on PowerShell modules and Windows-centric workflows, with almost all examples, instructions, and tooling based on PowerShell and Windows Automation environments. Linux Hybrid Runbook Worker support is mentioned only to highlight limitations (e.g., internal cmdlets not available), and there are no Linux-specific or cross-platform module management examples. Python module support is referenced, but not detailed. The guidance, examples, and screenshots are almost exclusively Windows/PowerShell-oriented, creating friction for Linux/macOS users.
Recommendations
- Add explicit guidance and examples for managing modules on Linux Hybrid Runbook Workers, including any differences in workflow or limitations.
- Provide parity in examples for module import, update, and deletion using cross-platform tools (e.g., Azure CLI, REST API), not just PowerShell.
- Clarify which features are Windows-only and which are available cross-platform, ideally with a comparison table.
- Expand the Python module section with more details and examples, especially for Linux environments.
- Include at least one end-to-end Linux Hybrid Runbook Worker scenario for module management.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes PowerShell and Windows-centric tooling and patterns throughout, with most examples, screenshots, and workflows using PowerShell cmdlets or referencing Windows concepts. Linux/macOS equivalents (such as Bash, CLI, or Python) are minimally covered, and PowerShell is presented as the primary interface for parameter assignment and runbook invocation. There are no examples showing how to start runbooks or pass parameters from Linux/macOS environments using Azure CLI or Bash, nor is there guidance for non-Windows users beyond Python runbooks.
Recommendations
- Add Azure CLI examples for starting runbooks and passing parameters, including JSON input, to demonstrate cross-platform usage.
- Include Bash shell examples for parameter assignment and runbook invocation.
- Clarify that PowerShell examples work on PowerShell Core (pwsh) on Linux/macOS, and provide explicit instructions for those environments.
- Expand Python runbook parameter examples to show invocation from Linux/macOS.
- Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell examples.
- Add notes or links for Linux/macOS users about installing and using PowerShell Core, if PowerShell is required.
Azure Change Tracking Inventory
Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent
...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation describes Azure Change Tracking and Inventory as supporting both Windows and Linux, with features like file and software change tracking applicable to both. However, the section on registry key tracking is exclusively Windows-focused, with no mention of Linux equivalents (such as tracking changes to configuration files or systemd unit files). Additionally, Windows registry examples are provided in detail, while Linux-specific examples (e.g., tracking changes to /etc, systemd, or package managers) are missing. The order of presentation also tends to highlight Windows-specific features first.
Recommendations
- Add Linux-specific examples for change tracking, such as monitoring changes to /etc, systemd unit files, or package manager logs.
- Clarify which features are Windows-only and which are cross-platform, especially in sections like registry tracking.
- Provide parity in examples and screenshots, showing both Windows and Linux scenarios.
- Consider including a table or section listing Linux-specific tracked items (e.g., configuration files, daemons) alongside the Windows registry keys.
Azure Functions
Quickstart: Create a Durable Functions app that uses the MSSQL storage provider
...n/articles/azure-functions/durable/quickstart-mssql.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section on setting up a local SQL Server instance with Docker. PowerShell commands are used exclusively for database setup, and Windows-specific patterns (such as referencing SQL Server Express on Windows) are mentioned before Linux alternatives. No explicit Bash or Linux/macOS shell examples are provided for Docker setup, and troubleshooting steps reference Windows tools and folder structures. While Docker and PowerShell are cross-platform, the lack of Bash/Linux-specific instructions may create friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash shell commands for Docker-based SQL Server setup, including database creation and validation.
- Mention Linux/macOS installation and usage patterns for SQL Server Express and Docker more explicitly.
- Add troubleshooting guidance for Linux/macOS users, such as file path differences and permissions.
- Where PowerShell is used, clarify that Bash alternatives exist and link to relevant resources.
- Ensure screenshots and instructions in Visual Studio Code are not Windows-centric (e.g., keyboard shortcuts, UI differences).
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented after the Linux example (using grep). All other troubleshooting steps and commands are platform-neutral (kubectl, helm), and no Windows-specific tools or patterns are mentioned. The only evidence of bias is the explicit separation of Linux and Windows log filtering commands, with Linux shown first.
Recommendations
- Ensure both Linux and Windows examples are presented equally, perhaps side-by-side or in a tabbed interface.
- Explicitly mention macOS compatibility where relevant, as macOS users will use the Linux commands.
- Consider clarifying that all kubectl and helm commands are cross-platform unless otherwise noted.
- If possible, provide a brief note that Windows users can install GNU grep via WSL or Git Bash as an alternative.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_powershell_mentions
Summary
The documentation provides a balanced approach for both Windows and Linux users, with explicit sections and examples for Linux deployment and configuration. However, there are minor instances where Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before their Linux equivalents (Visual Studio Code, Azure CLI), and Windows examples (such as ReadyToRun and deployment commands) are sometimes presented first. Azure PowerShell is referenced as a deployment option, but Azure CLI is also covered. No critical functionality is Windows-only, and Linux/macOS users can complete all tasks with the information provided.
Recommendations
- Ensure Linux and Azure CLI examples are presented alongside or before Windows/PowerShell examples where possible.
- Where Windows-specific instructions are given, provide equivalent Linux/macOS commands and clarify cross-platform applicability.
- Highlight Visual Studio Code and Azure CLI as primary cross-platform tools in 'Getting Started' and deployment sections.
- Consider grouping deployment instructions by platform or tool rather than by Windows-first ordering.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but PowerShell (Windows) examples are shown immediately after Bash in every step, and PowerShell-specific formatting is highlighted. There is no explicit Linux/macOS bias, but the presence of PowerShell examples throughout and their prominence may signal a slight Windows-first approach.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider grouping Bash and PowerShell examples under explicit OS headings (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Ensure Bash examples are shown first to emphasize cross-platform parity.
- Add a note that Azure CLI works identically on all platforms, and users should use the shell appropriate for their OS.
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, and in some cases, PowerShell syntax is shown first or equally, which may indicate a mild Windows bias. There is no exclusive use of Windows tools or missing Linux examples, but the presence of PowerShell-specific formatting can create friction for Linux/macOS users.
Recommendations
- Clearly label Bash and PowerShell sections, and ensure Bash (Linux/macOS) examples are shown first.
- Consider separating Bash and PowerShell examples into distinct tabs for clarity.
- Review variable usage and ensure Bash syntax is correct and prioritized for cross-platform parity.
- Add notes clarifying that Bash examples are for Linux/macOS and PowerShell for Windows.
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 mentioned prominently in metadata and examples. Azure PowerShell is a Windows-centric tool, though it is available cross-platform. The CLI example is present and shown first, but PowerShell requirements are listed in the prerequisites and metadata, which may suggest a Windows bias.
Recommendations
- Ensure Azure CLI examples are equally prominent and not secondary to PowerShell.
- Clarify that Azure PowerShell is available cross-platform, not only on Windows.
- Add explicit instructions for Linux/macOS users where relevant, such as file upload steps in Azure Cloud Shell.
- Remove or balance metadata tags (e.g., devx-track-azurepowershell) to avoid implying PowerShell is preferred.
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 cross-platform, while Azure PowerShell is more commonly associated with Windows, though it is available on Linux/macOS. The CLI example is presented first, followed by PowerShell. There is no evidence of Windows-only tools or patterns, nor are Linux/macOS equivalents missing. The documentation does not exhibit significant Windows bias.
Recommendations
- Maintain the current order, showing Azure CLI (cross-platform) examples first.
- Clarify that both Azure CLI and Azure PowerShell are available on Windows, Linux, and macOS.
- Optionally, add a note for Linux/macOS users about using Azure CLI in their native terminal environments.
- Ensure any referenced prerequisites or included content (e.g., 'azure-powershell-requirements-no-header.md') do not assume Windows-only environments.
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 primarily uses Azure Portal and Azure CLI examples, but when mentioning programmatic options for disabling routing to a regional gateway, it lists Azure PowerShell cmdlets alongside REST API and Azure CLI, with PowerShell mentioned before Linux-native tools. There are no explicit Linux/macOS examples or references to Bash scripting, and PowerShell is referenced without Linux parity guidance. However, the main workflow is portal- and CLI-based, which are cross-platform.
Recommendations
- When listing programmatic options, mention Azure CLI first, as it is cross-platform, and clarify that PowerShell is available on Linux/macOS as well.
- Add explicit Bash or shell scripting examples where relevant, or clarify that Azure CLI commands work equally on Linux/macOS.
- Avoid listing PowerShell before CLI unless the task is Windows-specific.
- Add a note that Azure PowerShell is available cross-platform, or link to Linux/macOS installation guides.
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
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is featured equally alongside CLI and is presented as a primary workflow. PowerShell is a Windows-centric tool, and its inclusion as a main example may create friction for Linux/macOS users. However, Azure CLI examples are present and fully functional for cross-platform users. The order of examples (Portal, CLI, then PowerShell) does not prioritize Windows, but the presence of PowerShell as a main tab could be seen as minor Windows bias.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider adding Bash or shell script examples for Linux users, or explicitly state that Azure CLI is cross-platform.
- Add a note indicating that PowerShell Core is available on Linux/macOS, if relevant.
- Ensure all CLI instructions are verified to work on Linux/macOS.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions using Azure CLI and PowerShell, and uses pivot sections to separate Windows and Linux-specific guidance. However, in several cross-platform sections, Windows/PowerShell examples are consistently presented before Linux/Bash equivalents. Some sections (e.g., persistent storage, environment variables, port configuration) show PowerShell commands immediately after Bash, and the Windows path (C:\home) is sometimes mentioned before the Linux path (/home). There are also several references to Windows-specific tools and patterns (e.g., IIS, .NET Framework, System.ConfigurationManager) in the main flow, with Linux equivalents only in pivoted sections or as afterthoughts.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them under clear OS-specific headings to avoid implicit prioritization.
- When referencing file paths, mention Linux and Windows equivalents together, or clarify which applies to which OS.
- Ensure that Linux-specific tools and patterns (e.g., OpenSSH, Linux environment variable conventions) are given equal prominence and not relegated to notes or after Windows sections.
- Where possible, provide Linux examples first in sections that are not inherently Windows-centric.
- Review pivoted content to ensure parity in depth and clarity between Windows and Linux sections.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_only_feature
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is for gateway-required virtual network integration, which is explicitly stated to be a Windows-only feature. All examples and troubleshooting steps reference Windows tools (e.g., PowerShell's Test-NetConnection, netstat -aon), and there are no Linux/macOS equivalents or guidance. Linux users are excluded from using this feature, and the documentation does not provide parity or alternative instructions for Linux environments.
Recommendations
- Clearly highlight at the top that this feature is Windows-only and not available for Linux apps.
- Where troubleshooting steps reference Windows tools (e.g., PowerShell, netstat), add notes that these are only applicable for Windows environments.
- For general networking troubleshooting, consider providing Linux/macOS equivalents (e.g., nc, netcat, ss, lsof) in sections that are not strictly tied to Windows-only features.
- Link to documentation for regional virtual network integration, which supports Linux apps, and provide migration guidance for Linux users.
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 signs of Windows bias: Windows paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used as primary examples, and references to Kudu DebugConsole and FTP upload methods are described using Windows-style paths. PowerShell is mentioned as an automation option alongside Azure CLI, but no Bash or Linux shell scripting examples are provided. The documentation does mention Linux app backup locations, but Windows patterns are presented first and more frequently.
Recommendations
- Provide Linux/macOS path examples (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections.
- Clarify that Kudu DebugConsole and FTP methods work for both Windows and Linux apps, and show Linux directory structures where appropriate.
- Add Bash or Linux shell scripting samples for automation, not just Azure CLI and PowerShell.
- When referencing environment variables, include both Windows (%HOME%) and Linux ($HOME) formats.
- Ensure that instructions for uploading files (e.g., _backup.filter) are clear for Linux users, including directory paths and tools.
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 relevant sections. However, PowerShell examples are consistently included alongside CLI, and the PowerShell examples are presented immediately after the CLI examples, which may subtly prioritize Windows tooling. There is no evidence of missing Linux examples, as Azure CLI is fully cross-platform and all CLI commands are present. No Windows-only tools or patterns are mentioned, and the content is not Windows-specific. However, the use of PowerShell as a primary scripting example may create minor friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Consider explicitly noting that Azure CLI is cross-platform and preferred for Linux/macOS users.
- If possible, provide Bash shell script examples for common migration steps, especially for tasks that may require scripting beyond Azure CLI.
- Clarify that PowerShell examples are optional and primarily for Windows users.
- Ensure that CLI examples are always shown before PowerShell, or provide a clear tabbed interface so users can easily select their preferred environment.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for configuring managed identities. However, PowerShell examples are prominent and often shown alongside or before CLI examples. In several sections, PowerShell is presented as a primary scripting option, which is most commonly used on Windows. Additionally, PowerShell is referenced for tasks where Azure CLI (cross-platform) is also available, but PowerShell is sometimes given more detailed coverage (e.g., for Functions). There is no explicit mention of Linux/macOS-specific tools or shell patterns, and the CLI examples do not reference Bash or other Linux shells. However, Azure CLI is included throughout, mitigating most friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell examples, especially for cross-platform tasks.
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and consider adding Bash shell context or notes for Linux/macOS users.
- Where PowerShell is used for scripting, add equivalent Bash or shell script examples for token retrieval and automation.
- Explicitly mention that Azure CLI and ARM templates are fully cross-platform.
- Review PowerShell-heavy sections for opportunities to add or prioritize CLI or Bash alternatives.
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 generally platform-neutral, focusing on Azure Application Gateway backend settings. However, in the troubleshooting section for Dedicated Backend Connections, references are made to Windows-specific authentication mechanisms (NTLM, Kerberos) and backend server logs, with links to Windows and IIS documentation. These Windows tools and patterns are mentioned first and exclusively, with no equivalent guidance for Linux-based authentication or backend logging. This creates a mild bias, as Linux users may need additional guidance for troubleshooting or configuring equivalent authentication mechanisms.
Recommendations
- Add troubleshooting guidance for Linux-based backend servers, including how to review logs and configure authentication mechanisms such as SPNEGO or other Kerberos implementations.
- Include links to Linux documentation for Kerberos authentication and backend logging (e.g., Apache, NGINX).
- Clarify that NTLM and IIS Windows Authentication are Windows-specific, and provide alternatives or notes for Linux users.
- Ensure examples and troubleshooting steps are platform-agnostic or provide parity for Linux/macOS where possible.
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 is featured alongside CLI in nearly every section, and is often presented immediately after CLI. There are no Linux-specific instructions or notes, and PowerShell is a Windows-centric tool. The use of PowerShell may create friction for Linux/macOS users, as they must rely solely on Azure CLI or REST examples. However, Azure CLI is featured first in most cases, and all critical tasks can be completed using CLI, which is cross-platform.
Recommendations
- Clearly indicate that Azure PowerShell examples are for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider grouping PowerShell examples in a dedicated section or tab labeled 'Windows/PowerShell', and Azure CLI as 'Linux/macOS/CLI'.
- Add explicit notes stating that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Remove PowerShell examples from main flow or relegate them to a secondary position, ensuring CLI is the default.
- If possible, provide Bash shell script examples for common tasks, or clarify that all CLI commands work on Linux/macOS.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, ensuring parity for users on Windows and Linux. However, in the Helm installation section, Windows installation instructions (using winget) are presented before Linux instructions, and PowerShell examples are consistently shown alongside CLI examples, which may slightly favor Windows users. All critical tasks are achievable on Linux/macOS, and Linux-specific instructions (e.g., Helm install via curl) are included.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel or in a neutral order, rather than Windows first.
- Explicitly mention macOS support and provide a macOS Helm installation example.
- Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
- Consider grouping CLI and PowerShell examples together, or defaulting to CLI as the primary example, since it is cross-platform.
- Add notes or links for Linux/macOS users regarding Azure CLI and Helm installation best practices.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and uses Windows terminology ('command prompt') first. However, Linux/macOS equivalents are present and the build/run/test instructions are cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Use neutral terminology such as 'terminal' instead of 'command prompt' when referring to the shell.
- Clarify that Maven and curl commands work on all platforms, not just Windows.
- Consider grouping all OS-specific instructions together for clarity.
Azure App Configuration
Quickstart for adding feature flags to Spring Boot with Azure App Configuration
...p-configuration/quickstart-feature-flag-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). Windows-specific tools (setx, PowerShell) are mentioned first in each section, with Linux/macOS instructions following. All other instructions, code, and tooling are cross-platform (Java, Maven), and no Windows-only tools or patterns are used elsewhere.
Recommendations
- Present environment variable instructions for Linux/macOS (bash) before Windows, or group them together in a table for parity.
- Clarify that Maven and Java commands are cross-platform.
- Consider adding a note that all steps are applicable to Linux/macOS unless otherwise stated.
- Avoid phrasing that implies Windows is the default or primary platform.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). Windows command prompt and PowerShell commands are listed first, with Linux/macOS bash commands following. The use of 'setx' and PowerShell is emphasized, but Linux/macOS equivalents are present. The rest of the tutorial is platform-neutral, and explicitly mentions Visual Studio Code as cross-platform. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
- Present environment variable instructions for Linux/macOS before Windows, or side-by-side, to avoid Windows-first bias.
- Add explicit notes that all steps are cross-platform unless otherwise stated.
- Where possible, use generic shell commands or highlight cross-platform tools.
- Consider grouping all OS-specific instructions in a table or tabbed format for parity.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides monitoring instructions for Azure App Configuration using the Azure portal, Azure CLI, and PowerShell. While the Azure CLI section is cross-platform, the PowerShell section is Windows-specific and is presented as a main option. Additionally, the CLI instructions mention Windows PowerShell as an example of a command console application before mentioning alternatives, which subtly prioritizes Windows. There are no Linux/macOS-specific examples or explicit mentions of their usage, and screenshots are portal-based (platform-neutral).
Recommendations
- Clarify that Azure CLI works on Linux/macOS and provide explicit examples or notes for Linux/macOS users.
- In CLI instructions, mention 'terminal' or 'command prompt' generically, rather than 'Windows PowerShell' first.
- Consider adding Bash or shell script examples for common log collection tasks.
- If PowerShell is included, note that PowerShell Core is cross-platform and provide guidance for Linux/macOS users where relevant.
Azure App Configuration
Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs
...-configuration/use-key-vault-references-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (export), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and the overall tutorial is cross-platform, with Java, Maven, and Azure CLI used throughout.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Use neutral language to indicate all platforms are equally supported (e.g., 'On Windows, use... On Linux/macOS, use...').
- Consider grouping environment variable setup instructions in a table or side-by-side format for clarity.
- Ensure screenshots and portal instructions do not assume Windows-only UI conventions.
Azure Cache For Redis
Scale an Azure Cache for Redis instance
...n/articles/azure-cache-for-redis/cache-how-to-scale.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for scaling Azure Cache for Redis using the Azure portal, Azure PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, and are presented before CLI examples in each section. There is no explicit mention of Linux/macOS-specific tools or shell usage, and PowerShell is a Windows-centric tool, though it is technically cross-platform. The CLI examples are generic and applicable to all platforms, but the ordering and emphasis on PowerShell may create a perception of Windows bias.
Recommendations
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform option.
- Consider presenting Azure CLI examples before PowerShell examples, or at least clarify their parity.
- Add a short note that PowerShell is available on Linux/macOS, but Azure CLI is often preferred for cross-platform scripting.
- If possible, include Bash shell scripting examples for common operations, or link to CLI usage guides for Linux/macOS users.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but the PowerShell section appears first and is more detailed, which may create a perception of Windows bias. The portal instructions are platform-neutral, but scripting examples prioritize Windows tools before Linux-friendly alternatives. No Linux/macOS-specific issues or missing examples are present, but the ordering and emphasis favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused.
- Add brief notes clarifying that all portal steps are platform-agnostic.
- Consider including Bash or shell script snippets for DNS verification (e.g., `nslookup`) to reinforce Linux parity.
Azure Cache For Redis
Deploy Azure Cache for Redis using Bicep
...s/azure-cache-for-redis/redis-cache-bicep-provision.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 and managing Azure Cache for Redis using Bicep. However, PowerShell examples are presented alongside CLI examples throughout, and PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash), but the Azure CLI commands are cross-platform and suitable for Linux/macOS users. The documentation does not mention Linux tools or shell patterns, nor does it clarify that PowerShell can be used on Linux/macOS, which may cause confusion.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Mention that Azure PowerShell is available on Linux/macOS, or clarify its Windows origins.
- Consider adding Bash shell examples for file operations (e.g., saving the Bicep file) to improve Linux parity.
- Ensure that CLI examples are shown first, or clarify their cross-platform nature in the prerequisites.
Azure Functions
App settings reference for Azure Functions
...ain/articles/azure-functions/functions-app-settings.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides comprehensive coverage of Azure Functions app settings for both Windows and Linux. However, there are minor signs of Windows bias: Windows-specific examples (e.g., environment variable delimiters, paths) are sometimes mentioned first or exclusively, PowerShell settings are detailed, and Windows tools (Azure PowerShell) are recommended alongside Azure CLI. Some settings are marked as Windows-only, but Linux equivalents are generally provided. Overall, Linux parity is strong, but minor friction remains.
Recommendations
- Ensure Linux examples (e.g., environment variable delimiters, file paths) are shown alongside Windows examples, not just mentioned second.
- Where PowerShell is referenced, also provide equivalent Azure CLI or Bash commands for Linux/macOS users.
- When recommending tools for programmatic management (e.g., Azure CLI or Azure PowerShell), clarify Linux support and provide CLI-first guidance.
- Review sample values (e.g., paths like '%HOME%\typescript') and provide Linux equivalents (e.g., '/home/typescript').
- Continue to highlight OS-specific behaviors (e.g., colon delimiter differences) and provide clear guidance for Linux users.