208
Pages Scanned
42
Pages Flagged
208
Changed Pages
20.2%
% Pages Flagged
Scan Information
Started At: 2026-02-08 00:00:07
Finished At: 2026-02-10 18:44:36
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 208
Files Completed: 208
Problematic Pages
42 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, especially SignTool, with all setup instructions, prerequisites, and examples tailored exclusively for Windows environments. PowerShell commands and Windows installers are provided, while Linux/macOS equivalents, alternative signing tools, or cross-platform guidance are absent. Other integrations (GitHub Actions, Azure DevOps, SDK) are only briefly mentioned without platform-specific instructions, leaving Linux/macOS users with unclear guidance.
Recommendations
- Add explicit instructions and examples for using Artifact Signing with Linux/macOS, including supported signing tools (e.g., OpenSSL, GPG, or cross-platform .NET tools) if available.
- Clarify which integrations (GitHub Actions, Azure DevOps, SDK) are cross-platform and provide Linux/macOS setup steps and sample workflows.
- If SignTool is Windows-only, highlight alternative signing approaches for Linux/macOS users, or state clearly that SignTool integration is not supported outside Windows.
- Provide parity in authentication and configuration examples for non-Windows environments.
- Include troubleshooting or limitations sections for Linux/macOS users.
Create Pull Request
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. It also references Excel and Visual Studio-based log converter tools, which are Windows-centric, without mentioning Linux/macOS alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-based tools.
Recommendations
- Add equivalent Azure CLI (az) commands for enabling diagnostic logging, as Azure CLI is cross-platform.
- Mention or provide Bash scripts or REST API examples for enabling diagnostic logging.
- When referencing log analysis, suggest cross-platform tools (e.g., jq, pandas, or open-source CSV viewers) in addition to Excel.
- If referencing log converter tools, note if they are cross-platform or provide alternatives for Linux/macOS users.
- Clarify that PowerShell Core is available cross-platform, if that is the intended usage, or link to installation instructions.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts as the primary or only migration tooling. There are no examples or guidance for using Azure CLI, Bash, or other cross-platform tools, nor is it clarified whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration tasks where possible.
- Clarify whether the referenced PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide installation guidance if so.
- Add explicit examples or links for Linux/macOS users, such as Bash scripts or instructions for running PowerShell scripts cross-platform.
- Mention Azure Portal or ARM template options for migration steps, if available, as these are platform-agnostic.
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 notable Windows bias. Windows-specific instructions, code samples, and certificate store usage are presented first and in greater detail, including C# and Java examples for accessing the Windows certificate store. Linux equivalents are either deferred, less detailed, or referenced generically (e.g., 'see the documentation for the respective language'). Linux-specific code samples are limited to C# file loading, with no Node.js, Python, PHP, or Java examples. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are emphasized, while Linux approaches are less thoroughly explained.
Recommendations
- Provide Linux examples for all major languages (Node.js, Python, PHP, Java), not just C#.
- Present Linux and Windows instructions/examples in parallel tabbed sections, rather than Windows-first.
- Expand Linux-specific guidance on certificate handling, including common pitfalls and best practices.
- Reference Linux tools and patterns (e.g., OpenSSL, file permissions) where relevant.
- Clarify when instructions are Windows-only and provide direct 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 Azure PowerShell examples for RBAC role assignment, but PowerShell is given equal prominence and referenced in several places. Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. The PowerShell example is shown directly after the CLI example, and Windows tools are mentioned before Linux equivalents in the certificate export section. There are no Linux/macOS-specific portal screenshots or explicit parity checks for non-Windows users.
Recommendations
- Expand the certificate export section with explicit Linux/macOS instructions, including OpenSSL commands and troubleshooting tips.
- Add more detailed examples for Linux/macOS users, such as using OpenSSL for certificate requests and exports, and clarify any differences in portal experience.
- Where PowerShell is referenced, ensure Azure CLI examples are equally prominent and provide Bash scripting examples for automation.
- Mention Linux/macOS tools before or alongside Windows tools when discussing certificate generation and export.
- Add notes or links for Linux/macOS users regarding certificate management best practices.
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 provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux scenarios. However, there are several instances where Windows-specific tools, paths, and conventions are mentioned first or exclusively, such as referencing Windows directory paths (e.g., D:\home), IIS, Web Deploy/MSDeploy, and legacy Windows build automation (Kudu) before Linux equivalents (Oryx). Some examples and explanations default to Windows terminology, and Windows-specific settings are often described in greater detail. Linux-specific settings are present but sometimes appear as afterthoughts or are less thoroughly documented.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows examples, especially for directory paths, deployment, and logging.
- Where possible, present Linux and Windows information in parallel, rather than defaulting to Windows-first descriptions.
- Expand Linux-specific documentation (e.g., Oryx build automation, Linux container settings) to match the detail provided for Windows/Kudu.
- Clarify which settings are platform-specific and provide clear guidance for Linux/macOS users.
- Avoid referencing Windows tools (e.g., IIS, MSDeploy) without mentioning Linux alternatives or noting their applicability.
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 page demonstrates a bias toward Windows by exclusively using Windows Server as the SQL backend, referencing SQL Server Management Studio (a Windows-only tool) for client connectivity, and omitting Linux-based alternatives or examples. There are no instructions for deploying a Linux SQL server or connecting from Linux/macOS clients, which may hinder users on those platforms.
Recommendations
- Provide examples for deploying SQL Server on Linux (e.g., Ubuntu VM with SQL Server 2022).
- Include instructions for connecting to the SQL server using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible clients.
- Mention that SQL Server is available on Linux and clarify any limitations or differences in configuration.
- Add screenshots or command-line examples relevant to Linux/macOS environments.
- Ensure that backend pool configuration steps are generic and not tied to Windows-specific VM images.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page includes a 'Next steps' section that links only to a PowerShell-based tutorial for creating an autoscaling, zone redundant application gateway. No equivalent Linux/macOS CLI (Azure CLI or ARM template) example is provided or referenced. This creates friction for users on non-Windows platforms, as PowerShell is not the default or preferred tool for many Linux/macOS administrators.
Recommendations
- Add links to tutorials or examples using Azure CLI (az) and/or ARM templates for creating autoscaling, zone redundant application gateways.
- Ensure that PowerShell and Azure CLI examples are presented together, or Azure CLI is mentioned first, to avoid Windows-first bias.
- Explicitly state that PowerShell is cross-platform, but provide CLI alternatives for Linux/macOS users.
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
Summary
The documentation is heavily focused on Azure PowerShell scripts for migration, with all examples, installation instructions, and script usage shown exclusively in PowerShell syntax. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The guidance assumes users are comfortable with PowerShell and Windows tooling, which creates friction for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, or explicitly state if PowerShell is required.
- Add Bash/Linux/macOS installation and execution instructions for the migration scripts, including how to use PowerShell Core (pwsh) on non-Windows platforms.
- Clarify script compatibility with PowerShell Core and cross-platform environments; if scripts are Windows-only, state this clearly.
- Offer downloadable scripts or containerized solutions that can be run from any OS, not just Windows.
- Include examples and guidance for running migration from Azure Cloud Shell (which supports Bash and PowerShell), highlighting cross-platform options.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS-compatible certificate creation methods. All code examples are PowerShell, and the prerequisites require an 'administrative Azure PowerShell session locally', which is typically Windows-centric. There are no Linux/macOS instructions or alternatives provided, creating friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI examples for all steps, as Azure CLI is cross-platform and works natively on Linux/macOS.
- Provide instructions for creating self-signed certificates using OpenSSL, which is available on Linux/macOS.
- Clarify that Azure PowerShell can be installed and run on Linux/macOS (via PowerShell Core), and provide installation guidance for those platforms.
- Consider including Bash shell examples alongside PowerShell, or link to Linux/macOS-specific tutorials.
- Mention any limitations or differences for Linux/macOS users explicitly in the prerequisites section.
Azure Functions
Migrate C# app from in-process to isolated worker model
...es/azure-functions/migrate-dotnet-to-isolated-model.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides only Azure PowerShell scripts for identifying function apps to migrate, with no mention of Azure CLI or Bash alternatives. PowerShell is primarily a Windows-centric tool, though it is available cross-platform. Additionally, PowerShell is presented first and exclusively, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. However, the rest of the guide is generally platform-agnostic, focusing on .NET and Azure Functions concepts.
Recommendations
- Add equivalent Azure CLI (az) commands and Bash script examples for identifying function apps to migrate, alongside the PowerShell example.
- Explicitly mention that PowerShell is available cross-platform, but provide links or instructions for installing it on Linux/macOS.
- Where scripting is required, offer both PowerShell and CLI/Bash options, or clarify which tools are supported on which platforms.
- Consider presenting Azure CLI examples first or in parallel with PowerShell to avoid Windows-first bias.
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
missing_linux_example
Summary
The documentation page for Azure Application Gateway v2 includes several references to Azure PowerShell scripts and cmdlets, especially for migration and preview registration/unregistration. While Azure CLI is mentioned, the examples provided use PowerShell cmdlets (e.g., Set-AzContext, Get-AzProviderFeature), which are not native to Linux/macOS and may require additional setup. There are no Bash or cross-platform CLI examples, and the 'Next steps' section links to a PowerShell-based tutorial. This creates friction for Linux/macOS users who may prefer or expect Azure CLI/Bash examples.
Recommendations
- Provide Azure CLI (az) command examples alongside or instead of Azure PowerShell cmdlets, especially for common tasks like migration and feature registration.
- Clearly indicate when a script or example is PowerShell-only, and offer Bash/CLI equivalents where possible.
- In the 'Next steps' section, include links to tutorials that use Azure CLI or ARM templates, not just PowerShell.
- Where possible, use cross-platform tools and patterns in examples to ensure parity for Linux/macOS users.
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_tools
Summary
The documentation heavily relies on PowerShell scripts and workflows for migration tasks, with no equivalent examples or guidance for Linux/macOS users (e.g., Bash, Python, or CLI). All migration instructions and runbook examples are PowerShell-centric, and there is no mention of cross-platform alternatives or Azure CLI usage. While the page acknowledges Linux VMs are supported, the practical guidance is Windows/PowerShell-focused.
Recommendations
- Provide equivalent migration scripts or runbook examples using Azure CLI, Bash, or Python for Linux/macOS users.
- Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS for the provided scripts, and clarify any limitations.
- Add guidance or links for Linux/macOS users on how to execute migration tasks without relying on Windows PowerShell.
- Include examples or references for using cross-platform tools (e.g., Azure CLI, REST API) to perform asset migration.
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 are made to Windows PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Python SDK, or bash scripting, even though Azure Automation and Microsoft Entra ID are cross-platform services. The documentation refers to 'Windows PowerShell' explicitly and does not mention alternatives for non-Windows environments.
Recommendations
- Add equivalent examples using Azure CLI and/or Python SDK for credential management and authentication, especially for Linux/macOS users.
- Clarify that PowerShell Core (pwsh) is cross-platform and can be used on Linux/macOS, and provide guidance for installing and using it.
- Avoid using 'Windows PowerShell' unless the feature is truly Windows-only; otherwise, refer to 'PowerShell' generically.
- Include notes or sections for Linux/macOS users, explaining any differences or limitations.
- Provide links to cross-platform tools and documentation, such as Azure CLI and Microsoft Graph SDKs for other languages.
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, with all certificate management tasks (creation, retrieval, deployment) demonstrated exclusively via PowerShell. No Linux shell (bash) or cross-platform CLI examples are provided, and PowerShell is presented first and most extensively. While Python examples are included for runbooks, there are no Linux-native instructions or parity for certificate management outside PowerShell.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deployment) to support Linux/macOS users.
- Include bash shell scripting examples where applicable, especially for uploading certificates or interacting with Azure Automation.
- Clarify whether PowerShell Core (pwsh), which is cross-platform, can be used for these tasks, and provide guidance for Linux/macOS environments.
- Ensure that instructions for uploading certificates via the Azure portal are platform-neutral and note any OS-specific limitations.
- Consider referencing or linking to Linux/macOS certificate management tools (e.g., openssl) for preparing .pfx/.cer files.
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 instructions and examples primarily using Azure PowerShell, with CLI examples present but less detailed. PowerShell is a Windows-centric tool, and the 'Next steps' section directs users to a PowerShell-specific guide, potentially creating friction for Linux/macOS users. There is no mention of Linux-native tools or workflows (e.g., Bash scripting, OpenSSL usage for certificate management), and PowerShell examples are shown before CLI equivalents.
Recommendations
- Ensure parity between Azure PowerShell and Azure CLI instructions, providing equally detailed CLI examples for all configuration steps.
- Include explicit Linux/macOS workflows for certificate extraction and management, such as using OpenSSL commands.
- In 'Next steps', provide links to both PowerShell and CLI-based configuration guides, or a cross-platform guide.
- When listing configuration options (Portal, PowerShell, CLI), avoid listing PowerShell first unless it is the most widely used option for the audience.
- Add notes clarifying that all CLI commands are cross-platform and provide troubleshooting tips for Linux/macOS users where relevant.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but Windows instructions and references (including PowerShell cmdlets and registry settings) are often presented first or more prominently. Several backup and retention examples rely on Windows PowerShell cmdlets, with no equivalent Linux CLI or scripting examples. Windows tools and terminology are referenced more frequently, creating friction for Linux users.
Recommendations
- Provide Linux CLI or scripting alternatives (e.g., Azure CLI, Bash) alongside PowerShell cmdlet examples for backup and retention tasks.
- Present Windows and Linux guidance in parallel or with equal prominence, rather than Windows-first ordering.
- Reference Linux-specific tools (such as Bash scripts, Azure CLI, or Python) for asset and runbook export/import, where possible.
- Clarify when a task is Windows-only, and offer Linux workarounds or note limitations if Linux parity is not possible.
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 is heavily focused on PowerShell and Windows-centric patterns, with all code examples and parameter assignment workflows using PowerShell or Windows tools. There are no Linux/bash examples for starting runbooks or passing parameters, and PowerShell is presented as the primary method for automation. Python runbooks are mentioned, but only briefly and without parity in example depth. The SDK and REST API sections are platform-neutral, but the practical guidance and walkthroughs are Windows-first.
Recommendations
- Add examples for starting runbooks and passing parameters using Azure CLI (bash) on Linux/macOS.
- Provide equivalent bash or shell scripts for JSON parameter passing and runbook invocation.
- Clarify that PowerShell can be used cross-platform, but also highlight Azure CLI as a Linux-friendly alternative.
- Expand Python runbook examples to match the depth of PowerShell walkthroughs.
- Explicitly mention any limitations or differences for Linux/macOS users when using Azure Automation.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns for managing credentials in Azure Automation. All CLI examples are in PowerShell, and references to 'Windows PowerShell' are explicit. There is no mention of Linux shell equivalents (e.g., Bash, Azure CLI), nor are there examples for Linux/macOS users outside of Python runbooks. The documentation assumes familiarity with PowerShell and Windows credential objects, which may create friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for credential management tasks, such as creating, retrieving, and deleting credentials.
- Clarify whether PowerShell cmdlets can be used cross-platform (PowerShell Core on Linux/macOS), and provide guidance for non-Windows environments.
- Explicitly mention limitations or alternatives for Linux/macOS users, especially if certain features are Windows-only.
- Provide Bash or shell script examples where possible, or link to relevant Azure CLI documentation.
- Reorder sections to present platform-neutral or cross-platform methods first, or clearly label Windows-specific instructions.
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 generally describes Azure Change Tracking and Inventory as supporting both Windows and Linux, and mentions Linux daemons and file tracking for both OSes. However, the registry tracking section is exclusively Windows-focused, with no mention of Linux equivalents (such as tracking changes to configuration files or systemd units). Additionally, all detailed examples (tables, explanations) are Windows registry keys, and no Linux-specific examples or patterns are provided. Windows terminology and features are presented first and in more detail.
Recommendations
- Add Linux-specific examples for change tracking, such as monitoring changes to /etc configuration files, systemd unit files, or installed packages.
- Include a section on Linux equivalents to registry tracking, such as tracking changes to critical configuration files or directories.
- Balance examples and screenshots to show both Windows and Linux scenarios, especially in sections where only Windows details are currently provided.
- Clarify which features are Windows-only and which are cross-platform, to help Linux users understand applicability.
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 provides PowerShell-based setup instructions for the local SQL Server Docker instance, with no equivalent Bash or Linux/macOS shell examples. The PowerShell commands are presented as the primary method, and troubleshooting assumes familiarity with Windows/Docker Desktop. While Docker and SQL Server are cross-platform, Linux/macOS users may face friction due to the lack of explicit Bash instructions and some Windows-centric terminology.
Recommendations
- Add Bash/zsh shell examples for setting up the SQL Server Docker container, including environment variable usage and database creation.
- Explicitly note that all Docker commands can be run on Linux/macOS, and provide any OS-specific caveats.
- Include troubleshooting steps relevant to Linux/macOS users (e.g., using 'docker ps', 'docker exec', and file browsing without Docker Desktop).
- Where PowerShell is used, provide equivalent Bash syntax or clarify that PowerShell is available cross-platform but Bash is more common on Linux/macOS.
- Ensure screenshots and instructions reference cross-platform tools (e.g., VS Code, SQLCMD) and avoid Windows-only terminology where possible.
Azure Functions
Migrate Consumption plan apps to Flex Consumption in Azure Functions
...unctions/migration/migrate-plan-consumption-to-flex.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux and Windows migration paths, but the Windows (platform-windows) sections are often presented first and in more detail, especially for manual migration steps. Windows/PowerShell/Azure CLI examples are more prominent and sometimes appear before Linux equivalents. Some sections (e.g., collecting app settings, configuring app settings, and other configurations) are more detailed for Windows, and the Windows migration path is more step-by-step, while the Linux path relies heavily on a single CLI command. There is also a heavier emphasis on Windows tools and patterns, such as Visual Studio and PowerShell, in some areas.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and detail, especially in manual migration steps.
- Where possible, provide Linux-native examples (e.g., bash scripts, Linux-specific CLI usage) alongside or before Windows/PowerShell equivalents.
- Avoid defaulting to Windows-first ordering in sections where both platforms are supported.
- Expand Linux migration guidance to include more granular/manual steps, not just the automated CLI command.
- Highlight cross-platform tools (e.g., Azure CLI, VS Code) before platform-specific ones (e.g., PowerShell, Visual Studio).
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
Summary
The documentation provides a generally cross-platform guide for running C# Azure Functions in an isolated worker process, but there are minor signs of Windows bias. Windows-specific tools (Visual Studio, Azure PowerShell) are mentioned before their Linux equivalents in some sections, and Windows deployment/configuration commands are sometimes presented first. However, Linux options (Azure CLI, Visual Studio Code, Linux containers) are also covered, and most examples and instructions are platform-agnostic. There are no critical sections that are Windows-only, and Linux/macOS users can complete all tasks described.
Recommendations
- Ensure Linux and macOS options (Azure CLI, Visual Studio Code) are presented before or alongside Windows tools in all sections, especially in 'Create Azure resources' and 'Publish your application'.
- Where possible, provide explicit Linux/macOS command-line examples alongside Windows ones, rather than referencing Windows tools first.
- Review ordering of deployment instructions and configuration commands to avoid defaulting to Windows-first presentation.
- Consider adding a short note at the top confirming full parity for Linux/macOS users, and linking to any platform-specific guides if available.
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
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI examples, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor is there guidance for Linux users on using CLI as the preferred cross-platform tool. Azure CLI is shown first in each example, but the presence of PowerShell throughout may create confusion or friction for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Consider grouping PowerShell examples in a separate section or as an optional tab for Windows users.
- Add links or guidance for installing Azure CLI on Linux/macOS.
- Ensure that all instructions are clear for Linux/macOS users, especially regarding file paths and shell usage.
API Center
Perform API linting and analysis - Azure API Center
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI command examples for both bash and PowerShell syntax throughout, but PowerShell examples are consistently shown after bash examples. There is a clear statement that Azure CLI commands can run in either shell, and separate examples are provided where syntax differs. No Windows-only tools or patterns are used, and Visual Studio Code is recommended as the editor, which is cross-platform. All deployment and configuration steps are accessible from Linux/macOS, and no critical functionality is Windows-only.
Recommendations
- Continue to provide both bash and PowerShell examples where syntax differs.
- Consider alternating the order of bash and PowerShell examples, or explicitly state that bash examples are shown first for consistency.
- Ensure that any screenshots or references to Visual Studio Code clarify its cross-platform support.
- If possible, include a brief note confirming Linux/macOS parity for all steps.
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 receives special formatting. There is a mild bias toward Windows/PowerShell users, but Linux users can complete all tasks using the Bash examples.
Recommendations
- Ensure Bash examples are shown first, as Bash is the default shell for Azure CLI and most cross-platform users.
- Clearly label Bash and PowerShell sections, and avoid implying PowerShell is required unless there is a Windows-specific need.
- Consider providing macOS-specific notes if there are any unique considerations.
- Review variable naming for consistency between Bash and PowerShell examples.
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 scripting tools for managing API Management instances, Azure PowerShell is referenced alongside Azure CLI. The PowerShell cmdlet is mentioned before other tools, and no Linux-specific shell or scripting examples (e.g., Bash) are provided. However, the Azure CLI is cross-platform and is used for the main command-line examples. There are no exclusive Windows tools or patterns, and the overall workflow is accessible to Linux/macOS users.
Recommendations
- When listing scripting tools, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is available on Linux/macOS as well.
- Add Bash shell script examples for disabling/enabling regional gateways using Azure CLI.
- Explicitly state that all Azure CLI commands can be run on Linux/macOS terminals.
- Consider linking to Azure CLI installation guides for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, but the PowerShell examples are presented immediately after each Bash example, indicating a slight Windows-first bias. The PowerShell formatting is explicitly called out, which may subtly prioritize Windows users. However, Linux users are not missing any information, and the Bash examples are present and correct.
Recommendations
- Consider explicitly labeling Bash examples as suitable for Linux/macOS and PowerShell examples for Windows, to clarify parity.
- If possible, present Bash (Linux/macOS) and PowerShell (Windows) examples side-by-side, rather than always Bash first then PowerShell.
- Add a brief note at the start of the CLI section explaining that both Bash and PowerShell are supported, and Linux/macOS users should use Bash examples.
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 the Bicep file, but PowerShell is mentioned alongside CLI throughout, and PowerShell examples are given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is presented as a primary option, which may create friction for Linux/macOS users unfamiliar with PowerShell. However, Azure CLI (cross-platform) is also fully supported and documented, and no Windows-only tools or patterns are used.
Recommendations
- Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell examples to reduce perceived Windows bias.
- Add a brief note clarifying that PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
- Ensure prerequisites sections for Azure CLI and PowerShell are equally detailed and clear about platform compatibility.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is more commonly used on Windows) as a primary example, and the explicit mention of PowerShell requirements in prerequisites, may signal a Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, which could be confusing for Linux/macOS users, as PowerShell is less common on those platforms. However, the CLI example is present and fully functional for Linux/macOS users, and no critical steps are Windows-only.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Mention that Azure PowerShell is available cross-platform, but is more commonly used on Windows.
- Consider providing Bash shell scripting examples alongside PowerShell, or explicitly state that Bash users should use Azure CLI.
- Reorder examples to show Azure CLI before PowerShell, or indicate platform recommendations for each tool.
- In prerequisites, clarify that Azure PowerShell is optional and not required for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service plans, explicitly mentioning both Windows and Linux options. However, the 'Managed Instance on Azure App Service' section is Windows-only and is presented before any Linux-specific features or equivalents, which could create a perception of Windows-first bias. No PowerShell-heavy examples, Windows tools, or missing Linux examples are found elsewhere in the document.
Recommendations
- Clearly label Windows-only preview features (such as Managed Instance) as such, and consider placing them in a dedicated section or appendix to avoid confusion.
- Add a brief statement clarifying Linux parity and limitations, especially for preview features.
- If Linux-specific advanced hosting options exist or are planned, mention them for parity.
- Ensure links to plan details and pricing cover both Windows and Linux options equally.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows section is presented first and includes a Windows-specific tool (winget) for installation. The Linux section is present and offers a standard installation command. All other examples and instructions use cross-platform tools (Azure CLI, Helm, kubectl) and are shown in Bash syntax, which is compatible with Linux/macOS and Windows (via Azure Cloud Shell or WSL). No critical steps are Windows-only, and Linux/macOS users can complete the quickstart without friction.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel or with Linux first, to avoid implicit prioritization.
- Explicitly mention macOS in the Helm installation section, as the Helm install instructions are also applicable to macOS.
- Clarify that Azure CLI, Helm, and kubectl commands are cross-platform and can be run in Bash, PowerShell, or Azure Cloud Shell.
- Consider linking to official Helm installation docs for all platforms, not just Windows.
- Where possible, use neutral language (e.g., 'On your local machine (Windows, Linux, or macOS)...') rather than 'local device running Windows or Linux'.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
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 console application before other alternatives, which subtly prioritizes Windows. There are no Linux-specific examples or explicit mentions of Linux/macOS shell environments, and screenshots are from the Azure portal (which is platform-agnostic).
Recommendations
- Clarify that Azure CLI commands can be run from any shell (Bash, Zsh, etc.) on Linux/macOS, not just Windows PowerShell.
- In CLI instructions, mention Bash or terminal applications on Linux/macOS as equally valid environments for running Azure CLI.
- Consider providing Bash shell examples or noting that PowerShell commands are Windows-specific, while Azure CLI is cross-platform.
- Add a note that PowerShell instructions are for Windows users, and Linux/macOS users should use Azure CLI.
- If possible, include screenshots or references to Linux/macOS environments to reinforce cross-platform support.
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 page primarily uses Azure Portal (GUI) instructions, which are platform-neutral, but when it introduces scripting, it presents Azure PowerShell examples first, followed by Azure CLI. The PowerShell section is more detailed, and PowerShell is a Windows-centric tool, though it is available cross-platform. There are no Linux/macOS-specific shell examples (e.g., Bash), but Azure CLI is cross-platform and included. No Windows-only tools or patterns are mentioned, and the documentation does not exclusively reference Windows tools.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more widely used across Linux/macOS.
- Add explicit Bash shell examples for DNS verification (e.g., `nslookup`) and other relevant tasks.
- Clarify that both PowerShell and CLI are available cross-platform, and link to installation guides for Linux/macOS users.
- Consider including a table or section comparing PowerShell and CLI usage for common tasks.
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 a comprehensive reference for Azure Functions app settings, covering both Windows and Linux scenarios. However, there are several minor instances of Windows bias: Windows-specific examples (such as environment variable delimiters and paths) are sometimes presented first or exclusively, PowerShell settings and references are prominent, and Windows tools (like Azure PowerShell) are mentioned as preferred options for programmatic management. Linux equivalents are generally present, but not always given equal prominence or example coverage.
Recommendations
- Where Windows-specific examples are given (e.g., environment variable delimiters, paths), ensure Linux equivalents are shown alongside or first.
- When referencing tools for programmatic management (Azure CLI vs Azure PowerShell), mention both equally and provide examples for each.
- For PowerShell-heavy sections, ensure equivalent guidance is provided for other languages and platforms, or clarify if the feature is Windows-specific.
- In tables or lists, alternate the order of Windows and Linux examples to avoid implicit prioritization.
- Add explicit notes where settings or behaviors differ between Windows and Linux, and link to relevant Linux documentation.
Azure Functions
host.json reference for Azure Functions 2.x
...b/main/articles/azure-functions/functions-host-json.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is generally cross-platform and avoids Windows-specific bias in examples and explanations. However, the 'managedDependency' feature is described as PowerShell-only, which is a Windows-centric shell, and PowerShell is referenced without mentioning Linux/macOS alternatives. Additionally, minor bias is present in the use of Windows environment variable syntax (e.g., %TEMP%) and the order of mentioning Windows-specific paths before Linux equivalents.
Recommendations
- Clarify that PowerShell-based functions and managedDependency are supported on both Windows and Linux (if true), or explicitly note any OS limitations.
- Where environment variables or paths are referenced (e.g., %TEMP%), add Linux/macOS equivalents (e.g., $TMPDIR or /tmp) for clarity.
- When referencing PowerShell, mention Bash or other shells for Linux/macOS users if relevant.
- Ensure examples and explanations are equally applicable to Linux/macOS, and add notes or examples for those platforms where appropriate.
Azure Functions
Azure Functions Core Tools reference
...cles/azure-functions/functions-core-tools-reference.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation for Azure Functions Core Tools is generally cross-platform, but there are several areas where Windows-specific tools, behaviors, or issues are mentioned first or exclusively. Notably, the documentation references Windows tooling (such as func.exe), highlights Windows-specific build issues for Python, and includes PowerShell as a supported worker runtime with managed dependencies. Some options and notes are presented with a Windows-first perspective, and Windows terminology (e.g., 'command prompt') is used. However, Linux/macOS equivalents are usually implied or supported, and most commands are platform-agnostic.
Recommendations
- When referencing func.exe, clarify that func is available as a cross-platform CLI, not just a Windows executable.
- Where Windows-specific issues are discussed (e.g., Python packaging), provide explicit Linux/macOS guidance or links to relevant troubleshooting.
- Avoid using Windows-centric terminology like 'command prompt'; use 'terminal' or 'shell' instead.
- When mentioning PowerShell managed dependencies, clarify if Bash/zsh equivalents exist or if this is truly Windows-only.
- Ensure that any references to Docker, .NET SDK, or other tools include installation instructions or notes for Linux/macOS users.
- Consider providing example commands for both Windows and Linux/macOS where differences exist (e.g., path separators, environment variable syntax).
Azure Functions
Azure Functions networking options
...ticles/azure-functions/functions-networking-options.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides Azure Functions networking options across hosting plans, but exhibits mild Windows bias in several areas. Hybrid Connections are Windows-only and this is clearly stated, which is appropriate. However, in the 'Virtual network triggers (non-HTTP)' section, CLI, PowerShell, and portal examples are given, but PowerShell is presented alongside CLI without explicit Linux shell (bash) examples. Additionally, PowerShell is referenced in automation and configuration steps, and Windows subnet sizing is mentioned before Linux. The troubleshooting section references Azure portal tools, which are cross-platform, but does not mention Linux-specific troubleshooting approaches. Overall, Linux parity is mostly present, but Windows tools and examples are more prominent.
Recommendations
- Add explicit bash/Azure CLI examples for configuration tasks, especially where PowerShell is shown.
- Clarify when PowerShell commands are Windows-only and provide equivalent Linux/macOS instructions where possible.
- Ensure subnet sizing recommendations for Linux are given equal prominence to Windows (e.g., in tables and explanations).
- In troubleshooting, mention CLI-based diagnostics or other Linux-friendly approaches.
- Where automation is discussed, highlight cross-platform tools (e.g., Azure CLI, Terraform) before Windows-specific tools.
Azure Functions
Migrate AWS Lambda workloads to Azure Functions
...ons/migration/migrate-aws-lambda-to-azure-functions.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page provides a comprehensive migration guide from AWS Lambda to Azure Functions, with a strong focus on cross-platform tools and approaches. However, there are minor signs of Windows bias: PowerShell is listed as a supported language for Azure Functions (even though AWS Lambda does not support it), and Windows-oriented development tools (Visual Studio, Visual Studio Code) are mentioned before CLI-based or Linux-native alternatives. The examples and instructions are generally platform-neutral, but Windows-centric tools and patterns are sometimes referenced first.
Recommendations
- When listing supported languages, clarify that PowerShell is Windows-centric and not available on AWS Lambda.
- When mentioning development tools, ensure parity by referencing CLI-based and Linux/macOS-native tools (such as Azure Functions Core Tools, Azure CLI, and Maven) before or alongside Visual Studio/VS Code.
- Provide explicit Linux/macOS instructions or examples for local development, deployment, and troubleshooting, especially for command-line workflows.
- Highlight that Azure Functions Core Tools and Azure CLI are fully cross-platform and can be used on Linux/macOS for all deployment and management tasks.
- Consider adding a section or callout for Linux/macOS users, summarizing recommended tools and workflows.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is generally cross-platform and provides guidance for both Windows and Linux users, especially in VM provisioning, disk encryption, and network isolation. However, there are several instances where Windows terminology, tools, and technologies (such as Hyper-V, Windows Firewall, BitLocker, and Windows Server references) are mentioned first or more extensively than their Linux equivalents. Windows-specific tools and patterns (e.g., Windows Firewall, BitLocker, Hyper-V) are often described in detail, while Linux alternatives (e.g., DM-Crypt, Linux disk encryption, Linux VM provisioning) are referenced but with less depth or after Windows. In some sections, Windows terminology is used as the default, and Windows examples or links are shown before Linux ones.
Recommendations
- Ensure Linux tools and technologies (e.g., DM-Crypt, iptables, SELinux, Linux VM images) are described with equal depth and clarity as Windows equivalents.
- When listing cross-platform features (e.g., disk encryption, VM provisioning), alternate the order or provide Linux examples first in some cases.
- Expand explanations of Linux-specific security features and patterns (e.g., Linux firewall, Linux kernel isolation, Linux audit/logging tools) where Windows tools are discussed.
- Include explicit Linux command-line examples (e.g., Azure CLI, SSH, DM-Crypt usage) alongside or before Windows/PowerShell examples.
- Review terminology to avoid defaulting to Windows-specific language when describing general Azure features.
Azure Functions
Troubleshoot Python function apps in Azure Functions
...n/articles/azure-functions/recover-python-functions.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux/macOS examples for troubleshooting Python function apps in Azure Functions. However, in several places, Windows/PowerShell commands are presented before their Unix/Linux equivalents, and PowerShell is used as the primary example for checking Python interpreter bitness. Cmd and PowerShell examples are given alongside Bash, but Windows commands often appear first. There are no critical sections that are Windows-only, and Linux parity is generally maintained.
Recommendations
- Present Linux/Bash examples before Windows/PowerShell/Cmd examples, or group them equally.
- Where possible, provide explicit macOS examples or clarify that Bash examples apply to both Linux and macOS.
- In sections where PowerShell is used as the primary example, ensure that Bash/Unix-like shell commands are given equal prominence.
- Review all troubleshooting steps to ensure Linux users are not required to translate Windows-specific instructions.
- Add notes clarifying cross-platform applicability for tools like Azure Functions Core Tools.
Azure Functions
Storage considerations for Azure Functions
...ain/articles/azure-functions/storage-considerations.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally maintains cross-platform parity, but there are minor signs of Windows bias. Windows plans and settings are often mentioned first, and PowerShell examples are provided alongside Azure CLI, sometimes without explicit Linux shell examples. However, Linux-specific guidance is present, especially in sections about mounting Azure Files, and there are clear notes when features are Windows-only.
Recommendations
- Ensure that Linux and macOS examples (e.g., Bash shell) are provided alongside PowerShell where relevant, especially for mounting file shares and configuring app settings.
- When describing settings or deployment options, avoid listing Windows plans/settings first unless there is a technical reason.
- Clarify when features are Windows-only and provide alternative Linux guidance where possible.
- Add explicit Linux/macOS command-line examples for common tasks (e.g., using az CLI with Bash).