250
Pages Scanned
51
Pages Flagged
250
Changed Pages
20.4%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-02-20 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 250
Files Completed: 250
Problematic Pages
51 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 heavily focuses on Windows-specific tools and workflows, particularly SignTool and PowerShell, with detailed setup instructions and examples exclusively for Windows environments. There are no equivalent Linux/macOS instructions or examples for Artifact Signing integration, and Windows tools (SignTool, MSI installer, winget) are mentioned first and exclusively. Other integrations (GitHub Actions, Azure DevOps, SDK) are referenced but not explained in detail, and no Linux/macOS signing tool guidance is provided.
Recommendations
- Add explicit instructions and examples for integrating Artifact Signing with Linux/macOS signing tools (e.g., OpenSSL, GPG, codesign for macOS).
- Provide parity in setup steps for Linux/macOS, including how to install required SDKs and dependencies.
- Include sample scripts or commands for Linux/macOS environments alongside PowerShell/Windows examples.
- Clarify which integrations are cross-platform and provide links or guidance for Linux/macOS users.
- Consider restructuring the page so that cross-platform integrations (GitHub Actions, SDK) are presented before Windows-only tools.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and does not focus on Windows-specific features. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. This omission may create friction for Linux users who wish to use Hybrid Connections.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux users.
- Where possible, provide parity or guidance for Linux/macOS users in sections that reference tools or agents.
- Review other sections for implicit Windows assumptions and ensure Linux/macOS users are not excluded from critical workflows.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides detailed instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is a PowerShell cmdlet, and there is no mention of Azure CLI or Bash scripting alternatives. Additionally, the 'log converter tools' tip references a C#/Visual Studio-based tool, which is more accessible to Windows users. This creates friction for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Where PowerShell is shown, provide Bash or CLI alternatives side-by-side or in tabs.
- For log conversion, mention or link to cross-platform tools or scripts (e.g., Python-based converters) if available, or clarify if the provided tool can be used on Linux/macOS via .NET Core.
- Review the 'Next steps' section to include links to cross-platform visualization tools or instructions, not just Power BI/Excel.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page frequently references Azure PowerShell scripts as the primary method for migrating Application Gateway V1 to V2, without mentioning or providing equivalent examples for Azure CLI or other cross-platform tools. There are no Linux/macOS-specific instructions or alternatives, and PowerShell is presented as the default migration tool, which may create friction for users on non-Windows platforms.
Recommendations
- Add Azure CLI examples or scripts for migration tasks, especially for configuration and public IP retention.
- Explicitly mention that PowerShell scripts can be run on Linux/macOS via PowerShell Core, or provide guidance for cross-platform usage.
- Where possible, provide Bash or Azure CLI alternatives alongside PowerShell instructions.
- Clarify any limitations or prerequisites for running PowerShell scripts on non-Windows systems.
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 CLI examples for Linux/macOS users (e.g., Azure CLI). PowerShell is presented as the primary scripting tool, and its examples appear before ARM template instructions. There are no references to Linux-specific tools or workflows, and no parity in scripting guidance for non-Windows platforms.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (creating, updating, and assigning managed identities).
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
- Where PowerShell is referenced, clarify its cross-platform availability, but also provide CLI alternatives for users who prefer native Linux/macOS tools.
- Consider including Bash shell scripting samples for ARM template deployments.
- Ensure that portal instructions are platform-neutral and clarify any OS-specific requirements.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides three main workflows for importing an OpenAPI specification: Azure portal, Azure CLI, and Azure PowerShell. Azure PowerShell is featured equally alongside Azure CLI, despite PowerShell being primarily a Windows-centric tool. The CLI example is cross-platform, but PowerShell is Windows-first. The order of presentation (CLI before PowerShell) is reasonable, but PowerShell is given full example parity, which may create friction for Linux/macOS users who do not use PowerShell. No Linux/macOS-specific tools or workflows (such as Bash scripts or REST API examples) are provided.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding REST API or Bash script examples for importing OpenAPI specifications, to further support Linux/macOS users.
- Explicitly note PowerShell's platform limitations and recommend CLI for non-Windows environments.
- Mention that Azure PowerShell is available on Linux/macOS via PowerShell Core, but CLI is generally easier for cross-platform use.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. The PowerShell example is given equal prominence to the CLI example, but there are no Linux/macOS-specific shell examples (e.g., Bash or zsh), nor is there guidance for Linux users beyond the CLI. The prerequisites list both Azure CLI and Azure PowerShell, but does not clarify that PowerShell is primarily for Windows users, nor does it mention cross-platform alternatives or note PowerShell Core's cross-platform support. The ordering of examples (CLI first, then PowerShell) is neutral, but the presence of PowerShell as a primary example without Linux/macOS shell alternatives creates friction for non-Windows users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and mention PowerShell Core's cross-platform support if relevant.
- Provide Bash/zsh shell examples for Linux/macOS users, or explicitly state that Azure CLI is the recommended cross-platform tool.
- Add a note in the prerequisites section indicating which tools are best suited for each platform.
- Consider linking to guidance for using Azure CLI on Linux/macOS, or to PowerShell Core installation instructions for those platforms.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for certificate-related tasks, but PowerShell is mentioned prominently and sometimes before CLI. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and links to Windows documentation are provided. Linux tools (OpenSSL) are included, but Windows methods are described in detail and referenced first in some sections. The FAQ and automation sections list PowerShell before CLI, and Windows export methods are given more prominence.
Recommendations
- Ensure Linux/CLI examples are always provided alongside PowerShell, and shown first where possible.
- Expand instructions for Linux/macOS users, including OpenSSL usage and troubleshooting.
- Add links to Linux/macOS certificate export documentation, not just Windows.
- Clarify when Windows tools are optional, and provide parity for Linux/macOS users.
- In automation/FAQ sections, list CLI and Linux-native methods before PowerShell/Windows tools.
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 platforms. However, there is evidence of Windows bias: Windows-specific paths (e.g., D:\home) and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS, site extensions) are often mentioned first or exclusively. Windows terminology and examples (such as referencing Windows time zones, Windows-specific logging, and legacy Windows deployment tools) appear before Linux equivalents, even in sections that apply to both platforms. Some settings and explanations are more detailed for Windows, while Linux-specific guidance is less prominent or deferred to external links (e.g., Oryx configuration).
Recommendations
- Ensure Linux examples and paths (e.g., /home) are presented alongside Windows ones, not only as afterthoughts.
- When describing settings, clarify applicability for Windows, Linux, and containers, and provide parity in explanations and examples.
- Add Linux-specific deployment and build automation examples (e.g., Oryx usage, Linux container paths, relevant shell commands).
- Avoid referencing Windows tools (e.g., msbuild, Web Deploy) without also mentioning Linux alternatives or noting their platform specificity.
- Where Windows terminology is used (e.g., time zones, logging paths), provide equivalent Linux information or links.
- Consider restructuring sections so that Linux and Windows are treated equally, or use clear pivots/tabs for each platform.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure PowerShell links for restarting Application Gateway instances, but does not offer equivalent Azure CLI or Linux/macOS command examples. PowerShell is mentioned first and exclusively, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. No Windows-specific tools or patterns are otherwise referenced, and the rest of the documentation is platform-neutral.
Recommendations
- Add Azure CLI examples alongside PowerShell commands for operations such as restarting Application Gateway instances.
- When referencing command-line tools, mention both PowerShell and Azure CLI, or provide links to both.
- Ensure that any procedural instructions are not phrased in a way that assumes Windows/PowerShell as the default or only option.
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 demonstrates a moderate Windows bias: Windows-specific instructions and code samples (especially for certificate loading) are presented first and in greater detail, with C# and Java examples for the Windows certificate store. Linux guidance is present but less detailed, and non-Windows language/platform examples (Node.js, PHP, Python, Java) are deferred to external documentation. The use of Windows certificate store and related APIs is emphasized, while Linux users are directed to file-based approaches with less explanation.
Recommendations
- Provide Linux-specific code samples (not just C#) for common languages supported on App Service, such as Node.js, Python, Java, and PHP, showing how to load certificates from the injected file paths.
- Present Linux and Windows instructions/examples in parallel or with equal prominence, rather than Windows-first.
- Expand the Linux section to explain best practices for certificate handling, including environment variable usage for certificate paths.
- Include explicit examples for loading certificates in Java on Linux, as well as for other popular stacks.
- Clarify any differences in certificate formats or permissions between Windows and Linux containers.
- Where external documentation is referenced, provide direct links to relevant sections for each language/platform.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides examples and instructions for both Windows and Linux platforms, but there are several areas where Windows patterns, terminology, and tools are presented first or exclusively. For instance, file paths and directory references use Windows-style paths (e.g., `%HOME%`, `D:\home\site\wwwroot`), and the use of Kudu DebugConsole is described with Windows-centric paths. The 'Automate with scripts' section references Azure PowerShell alongside Azure CLI, but does not provide parity for Linux shell scripting. Additionally, FTP upload instructions and screenshots are Windows-oriented. Linux equivalents are mentioned but often after Windows, and some instructions (such as file upload locations) are not clearly mapped for Linux users.
Recommendations
- Provide Linux-specific examples and file paths (e.g., `/home/site/wwwroot`) alongside Windows paths wherever file operations are described.
- Clarify how to access Kudu DebugConsole and upload files for Linux-based App Service apps, including screenshots or instructions for Linux environments.
- Ensure that CLI and scripting examples are not biased toward PowerShell; include Bash shell script examples for Linux users.
- When referencing environment variables or directories, note the Linux equivalents and differences explicitly.
- Where screenshots or instructions are Windows-centric, add Linux/macOS alternatives or clarify any differences.
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 notable Windows bias. It exclusively uses Windows Server as the SQL backend VM, and the SQL client connection example relies on SQL Server Management Studio (SSMS), a Windows-only tool. There are no Linux or macOS alternatives mentioned for either the SQL backend or client connection. The instructions and screenshots are all based on Windows environments, and Linux-compatible SQL Server images, tools, or connection methods are not referenced.
Recommendations
- Include instructions for deploying SQL Server on Linux (e.g., Ubuntu-based SQL Server VM) as an alternative backend.
- Provide examples of connecting to SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible clients.
- Mention Linux/macOS compatibility in relevant sections and clarify any limitations.
- Add screenshots or CLI instructions for Linux users where appropriate.
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_first
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias. Key migration and creation tutorials are linked as PowerShell-based, and the only migration script mentioned is a PowerShell script. Azure CLI commands are shown, but the examples use PowerShell cmdlets (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature) rather than cross-platform Azure CLI commands. There is no explicit mention of Linux/macOS-specific instructions or parity for migration scripts or tutorials.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for migration and creation tasks, ensuring cross-platform compatibility.
- Clearly indicate whether migration scripts are usable on Linux/macOS (e.g., if PowerShell Core is supported, specify this).
- Add links to tutorials or guides using Azure CLI or ARM templates for Application Gateway v2 creation and migration.
- Where PowerShell is used, note if the commands are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
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_first
missing_linux_example
Summary
The documentation page provides a conceptual overview of enabling end-to-end TLS on Azure Application Gateway, which is a cross-platform Azure service. However, the 'Next steps' section exclusively links to a PowerShell-based guide for configuration, with no mention of Azure CLI, Bash, or Linux/macOS-compatible instructions. Additionally, certificate format references (PFX) and links to Windows API documentation (PFXImportCertStore) are given without Linux equivalents or guidance. This creates friction for Linux/macOS users who may prefer or require non-Windows tooling.
Recommendations
- Add links to Azure CLI and/or ARM template guides for configuring end-to-end TLS on Application Gateway, ensuring Linux/macOS users have parity.
- Provide examples or references for certificate management and conversion on Linux/macOS (e.g., using OpenSSL to create PFX files).
- When referencing certificate formats or APIs, include cross-platform guidance or note that PFX files can be generated on any OS.
- In 'Next steps', offer multiple paths (PowerShell, Azure CLI, Portal, ARM templates) for configuration.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but in several sections, Windows/PowerShell tools are mentioned first or exclusively. Examples for exporting runbooks and DSC configurations reference only PowerShell cmdlets, with no equivalent CLI or Linux-native instructions. Some asset management and deletion tasks are described only with PowerShell cmdlets, and Linux alternatives are not provided.
Recommendations
- Provide Azure CLI or REST API examples alongside PowerShell cmdlets for tasks like exporting runbooks, DSC configurations, and managing assets.
- When referencing platform-specific instructions, present Linux and Windows guidance in parallel, or clarify when a feature is Windows-only.
- Include Linux-native methods (e.g., Bash scripts, az CLI commands) for backup and management operations where possible.
- In tables and lists, avoid consistently listing Windows before Linux unless there is a technical reason.
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 biased toward Windows/PowerShell environments. All migration scripts, examples, and instructions are provided exclusively for Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible alternatives. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all code samples are PowerShell-based. There is no parity for Linux/macOS users who may prefer or require Azure CLI or Bash scripting.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning, certificate handling, and IP migration.
- Include Bash shell examples for script execution and parameter handling.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both PowerShell and Bash), and provide guidance for Linux/macOS users.
- Add a section explicitly addressing Linux/macOS environments, listing any limitations or workarounds.
- Where possible, link to cross-platform tools or documentation, and avoid assuming PowerShell as the default shell.
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 next steps primarily using Azure PowerShell, with CLI examples included but less detailed. The 'Next steps' section directs users to a PowerShell-specific guide, and PowerShell is consistently mentioned before CLI. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux-native tools for certificate management or validation.
Recommendations
- Provide equal depth of examples for Azure CLI alongside PowerShell, including full configuration flows.
- In the 'Next steps' section, include links to both PowerShell and Azure CLI guides for mutual authentication setup.
- When referencing certificate extraction or management, include Linux/macOS command-line examples (e.g., using OpenSSL) for extracting and preparing certificate chains.
- Alternate the order of PowerShell and CLI examples, or present them in parallel tabs, to avoid Windows-first bias.
- Explicitly state that all configuration steps can be performed from Linux/macOS using Azure CLI where 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_tools
Summary
The documentation page for disaster recovery in Azure Automation is heavily focused on PowerShell scripts and workflows for migration tasks, with no mention of Bash, CLI, or Python alternatives. All migration examples and instructions are PowerShell-based, and there are no Linux-native scripting options or examples. While the page states applicability to both Linux and Windows VMs, the tooling and examples are Windows-centric, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for asset migration between Automation accounts.
- Include Python runbook examples for migration, as Azure Automation supports Python runbooks.
- Clarify if PowerShell scripts can be executed from Linux/macOS environments, and provide guidance for cross-platform usage.
- Add explicit instructions or links for Linux/macOS users on how to perform migration tasks without relying on Windows tools.
- Mention and demonstrate the use of Azure CLI for relevant operations (e.g., account creation, asset replication).
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 provides extensive PowerShell-based examples for configuring encryption of secure assets in Azure Automation, with REST API alternatives. There are no Azure CLI (cross-platform) examples, and PowerShell is referenced as the primary scripting interface, which may create friction for Linux/macOS users who prefer or require CLI/bash-based workflows.
Recommendations
- Add Azure CLI examples for all major operations (assigning managed identity, configuring Key Vault access policy, updating Automation account encryption).
- Explicitly mention that PowerShell examples work cross-platform with PowerShell Core, and clarify any Windows-only limitations.
- Reorder sections to present REST API or CLI examples before or alongside PowerShell to avoid the impression of Windows-first bias.
- Reference Azure CLI documentation in the prerequisites, not just PowerShell.
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 and module references are PowerShell-specific, with no mention of Bash, Azure CLI, or cross-platform scripting. The phrase 'Windows PowerShell' is used, and there are no Linux/macOS equivalents or guidance for users who may want to use Python runbooks or other cross-platform approaches in Azure Automation.
Recommendations
- Add Azure CLI examples for credential management and authentication, showing how to achieve similar tasks using Bash or cross-platform tools.
- Clarify that PowerShell in Azure Automation is cross-platform, but also provide explicit guidance for Linux/macOS users running scripts locally or authoring runbooks.
- Include references to Python runbooks or other supported languages in Azure Automation, with links or examples for authenticating to Azure using Microsoft Entra ID.
- Avoid using 'Windows PowerShell' unless the instructions are truly Windows-only; otherwise, use 'PowerShell' to reflect cross-platform support.
- Add a section or note explaining how Linux/macOS users can install required modules and interact with Azure Automation.
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 equivalent CLI or scripting examples for Linux/macOS users. Additionally, PowerShell is mentioned before any cross-platform alternatives, creating friction for non-Windows users. However, the rest of the documentation is largely platform-neutral, and Azure Automation features discussed (Hybrid Runbook Worker, Update Management, DSC) are available for both Windows and Linux machines.
Recommendations
- Add Azure CLI and/or REST API examples for configuring public network access flags, alongside the PowerShell example.
- Explicitly mention that the PowerShell example is for Windows users, and provide guidance for Linux/macOS users.
- Where possible, present cross-platform commands (e.g., Azure CLI) before or alongside PowerShell examples.
- Clarify that both Windows and Linux Hybrid Runbook Workers are supported, and provide links to relevant Linux documentation if available.
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_tools
windows_first
Summary
The documentation page heavily focuses on PowerShell and Windows-centric tools and patterns. Most examples, parameter types, and workflows are presented using PowerShell, PowerShell Workflow, and graphical runbooks (which are also PowerShell-based). Windows/PowerShell terminology and tooling are referenced throughout, with only brief mention of Python runbooks. The examples for starting runbooks, passing parameters, and working with JSON objects are almost exclusively PowerShell-based, and Windows PowerShell features are discussed. There is little to no coverage of Linux/macOS-specific workflows or CLI tools (e.g., Bash, Azure CLI), and PowerShell examples are shown first and most frequently.
Recommendations
- Add equivalent examples using Azure CLI (bash) for assigning parameters and starting runbooks, especially for Linux/macOS users.
- Clarify that PowerShell examples can be run cross-platform (PowerShell Core), and note any Windows-specific limitations.
- Expand Python runbook examples to show parameter passing and invocation from Linux/macOS environments.
- Mention and demonstrate how to use REST API and SDKs from Linux/macOS, including sample shell commands (curl, jq) for REST calls.
- Balance the order of examples so that PowerShell and non-Windows approaches are presented equally or in parallel.
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
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows for Azure Automation. Most examples, tools, and instructions reference PowerShell, Windows PowerShell versions, and Windows-specific cmdlets. Internal cmdlets and modules are noted as unavailable on Linux Hybrid Runbook Workers, but Linux alternatives or parity are not discussed. Python modules are briefly mentioned, but no Linux-specific guidance or examples are provided.
Recommendations
- Add explicit guidance and examples for Linux Hybrid Runbook Workers, including module management and limitations.
- Provide parity for module import, update, and deletion using Linux tools or CLI (e.g., Azure CLI, Bash) where possible.
- Clarify which features are Windows-only and which are cross-platform, and offer Linux/macOS alternatives or workarounds.
- Expand documentation on Python modules and other cross-platform scripting options, including examples.
- Include a comparison table or section outlining feature support differences between Windows and Linux Hybrid Runbook Workers.
Azure Cache For Redis
Scale an Azure Cache for Redis instance
...n/articles/azure-cache-for-redis/cache-how-to-scale.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides scaling instructions for Azure Cache for Redis using the Azure portal, Azure PowerShell, and Azure CLI. PowerShell examples are consistently given alongside CLI, and PowerShell is mentioned before CLI in most sections. There are no Linux/macOS-specific examples or explicit references to Linux tooling, but Azure CLI is cross-platform. The documentation does not provide Linux/macOS shell examples (e.g., Bash), nor does it clarify CLI usage on non-Windows platforms. PowerShell is a Windows-centric tool, though it is available cross-platform, but its usage is more common among Windows users.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be used on Linux/macOS as well as Windows.
- Consider providing Bash shell examples for Azure CLI usage, especially for Linux/macOS users.
- Mention that PowerShell is available cross-platform, but highlight CLI as the primary tool for Linux/macOS users.
- Reorder examples to show Azure CLI first, or provide both CLI and PowerShell examples equally.
- Add a note for Linux/macOS users about installing and using Azure CLI.
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, upload, retrieval) shown exclusively using PowerShell. There are no Bash, CLI, or Linux-native examples for certificate management, and PowerShell is presented first and most prominently. Python examples are provided for runbook access, but not for certificate creation or upload. The page assumes PowerShell as the primary tool, which may create friction for Linux/macOS users who prefer Bash or Azure CLI.
Recommendations
- Add Azure CLI examples for certificate creation, upload, and management tasks.
- Include Bash shell scripts or commands for Linux/macOS users where possible.
- Document any limitations or parity gaps between PowerShell and CLI for certificate management in Azure Automation.
- Present CLI or Bash examples alongside PowerShell, not only after or instead of.
- Clarify if PowerShell is required for certain tasks, and provide guidance for Linux/macOS users (e.g., using PowerShell Core, or alternatives).
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on Windows PowerShell tools and patterns. All CLI examples are PowerShell-based, and cmdlet tables exclusively reference PowerShell/Az modules. Windows PowerShell is mentioned as the primary method for creating credential assets, with no equivalent Bash, Linux CLI, or cross-platform scripting examples. While Python runbook examples are provided, there is no guidance for Linux-native shell scripting or non-PowerShell automation. The structure and ordering of the page consistently present Windows/PowerShell approaches first and in greater detail.
Recommendations
- Add examples for managing credentials using Azure CLI (az) commands, which are cross-platform.
- Include guidance or examples for Bash or shell scripting where applicable, especially for Linux/macOS users.
- Clarify that PowerShell Core (pwsh) is cross-platform and indicate if the cmdlets work on Linux/macOS, or note any limitations.
- Provide parity in documentation structure by presenting Python and CLI examples alongside PowerShell, not only after.
- Explicitly state if certain features are Windows-only, or if PowerShell cmdlets are supported on Linux/macOS.
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 presents Azure Change Tracking and Inventory as a cross-platform feature, supporting both Windows and Linux. However, there is a notable bias in the 'Track registry keys' section, which exclusively discusses Windows registry keys and provides no equivalent Linux example (such as tracking changes to Linux configuration files or directories). Additionally, the registry section is placed before any Linux-specific tracking examples, and no Linux-specific tools or patterns are mentioned in detail.
Recommendations
- Add a section detailing Linux-specific change tracking capabilities, such as monitoring changes to important configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) or directories.
- Provide examples or tables for Linux daemons and configuration files that can be tracked, similar to the Windows registry key table.
- Clarify in the registry section that this feature is Windows-specific, and provide a parallel section for Linux users.
- Ensure screenshots and examples alternate between Windows and Linux, or show both platforms equally.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation generally aims for cross-platform parity, but there are several areas where Windows and Windows tooling are mentioned first or exclusively, and Linux-specific guidance is less prominent or missing. Windows/PowerShell commands are sometimes shown before their Linux equivalents, and some instructions (such as for ReadyToRun, checking process bitness, and certain deployment steps) focus on Windows scenarios or tools, with Linux alternatives only mentioned later or not at all. Azure PowerShell is listed as a primary resource creation method, while Bash/Azure CLI is not always given equal prominence. Some minor friction exists for Linux/macOS users, though most tasks are still possible.
Recommendations
- When listing resource creation or deployment methods, always mention cross-platform tools (Azure CLI, Bash) before or alongside Windows-specific tools (PowerShell, Visual Studio).
- For all CLI commands, provide both Windows (PowerShell/CMD) and Linux/macOS (Bash) syntax/examples where differences exist.
- In sections like ReadyToRun, ensure Linux build and deployment instructions are as detailed and prominent as Windows instructions.
- Where PowerShell is referenced, add equivalent Bash/Azure CLI examples and clarify platform applicability.
- In troubleshooting and configuration, explicitly call out any platform-specific differences and provide guidance for both Windows and Linux/macOS users.
- Review the order of presentation in tables and lists to avoid always listing Windows/PowerShell/Visual Studio first unless there is a technical reason.
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 provides PowerShell-based examples for setting up a local SQL Server instance in Docker, with no equivalent Bash or Linux/macOS shell examples. The instructions and troubleshooting steps reference Windows tools and patterns first, and do not offer explicit guidance for Linux/macOS users, despite Docker and PowerShell being cross-platform. This creates friction for non-Windows users, especially those unfamiliar with PowerShell or who prefer Bash.
Recommendations
- Add Bash shell examples alongside PowerShell for Docker-based SQL Server setup, including database creation and validation commands.
- Explicitly note that all PowerShell commands can be run on Linux/macOS if PowerShell is installed, but provide native Bash alternatives for users who do not wish to install PowerShell.
- Clarify any OS-specific nuances, such as file paths or Docker networking, for Linux/macOS users.
- Ensure troubleshooting steps reference both Windows and Linux/macOS environments, including how to browse container files without Docker Desktop.
- Consider listing Linux/macOS tools (e.g., sqlcmd, Azure CLI) and their installation instructions in the prerequisites section.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI command examples for both Bash and PowerShell throughout, with Bash examples shown first and PowerShell examples following. There are no Windows-specific tools or patterns, and Linux parity is maintained in all examples. The only minor bias is that Bash (Linux/macOS) examples are presented before PowerShell (Windows), but both are equally supported.
Recommendations
- No significant changes needed. Both Bash and PowerShell examples are provided, ensuring parity.
- If desired, clarify at the start that all CLI commands work on Windows, Linux, and macOS, and that examples for both shells are included.
- Consider alternating the order of Bash and PowerShell examples in future documentation for absolute neutrality.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation for Azure App Service Plans is generally neutral, describing both Windows and Linux support. However, the 'Managed Instance on Azure App Service' section is Windows-only and is presented prominently, with Windows-specific features (PowerShell, RDP, IIS, .NET Framework) listed before any mention of Linux limitations. The main content does not provide platform-specific examples or tools, but the Windows-only Managed Instance section is not clearly separated as a Windows-specific feature, which could cause confusion.
Recommendations
- Clearly label the 'Managed Instance on Azure App Service' section as Windows-only at the start of the section.
- Add a brief note or comparison for Linux users, explaining the equivalent options or limitations for Linux App Service plans.
- Ensure links and feature tables consistently indicate OS support (Windows/Linux) where relevant.
- Consider adding Linux-specific examples or clarifications in sections that discuss features available on both platforms.
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), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and complete. The rest of the tutorial is cross-platform, with Maven and Java instructions applicable to all OSes. The only minor bias is Windows examples appearing first and PowerShell being called out separately.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows examples, or group all OS instructions together for parity.
- Clarify that all steps are cross-platform unless otherwise noted.
- Consider providing a table or collapsible sections for environment variable setup to avoid Windows-first ordering.
- Ensure that any tool recommendations (e.g., Visual Studio Code) continue to highlight cross-platform compatibility.
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, and includes detailed Windows-specific commands (setx, PowerShell syntax). Linux/macOS instructions are present but shown last and less prominently. The rest of the tutorial uses cross-platform tools (Azure CLI, Maven, curl) and is generally platform-neutral.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Use a table or side-by-side layout for environment variable setup commands to equally highlight all platforms.
- Clarify that Azure CLI, Maven, and curl commands are cross-platform and can be run on any OS.
- Consider mentioning Linux/macOS terminal restart requirements explicitly, as is done for Windows.
- Ensure screenshots and portal instructions do not assume Windows UI conventions.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but the PowerShell versions are always shown immediately after the Bash ones, and are labeled as 'Formatted for PowerShell.' This gives slight preference to Windows/PowerShell users, but Linux/macOS users are not blocked. All commands are cross-platform Azure CLI commands.
Recommendations
- Consider using tabbed code blocks for Bash and PowerShell to make it easier for users to select their preferred shell.
- Explicitly mention that Bash examples work on Linux/macOS and Windows (with WSL or Git Bash), and that PowerShell examples are for Windows or PowerShell Core.
- If possible, default to Bash examples first, as Bash is available on all platforms, or clarify that both are equally supported.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific tools or workflows (such as Bash scripting or references to Linux/macOS environments). The instructions reference uploading files to Azure Cloud Shell, which is cross-platform, but do not explicitly provide guidance for Linux/macOS users. The order of examples does not strongly favor Windows, but the inclusion of PowerShell as a primary method may create mild friction for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works natively on Linux/macOS and is recommended for cross-platform use.
- Add brief instructions or links for Linux/macOS users on saving/uploading files (e.g., using Bash or SCP).
- Consider providing Bash shell examples or clarifying that PowerShell is optional for Linux/macOS users.
- Highlight that Azure Cloud Shell supports both Bash and PowerShell, and users can choose their preferred shell.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page is generally platform-neutral, focusing on Azure networking concepts. However, there is a minor bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks, and no equivalent Linux/CLI example is provided or mentioned. Additionally, PowerShell is mentioned before any Linux alternatives, which may create friction for Linux/macOS users.
Recommendations
- Add links or references to Azure CLI or Bash-based guides for connecting virtual networks, alongside the PowerShell example.
- Ensure that Linux/macOS-friendly tools and examples are mentioned wherever PowerShell is referenced.
- Consider listing cross-platform solutions (Azure CLI, REST API, Portal) before or alongside Windows-specific tools in related content sections.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are given immediately after Bash for every step, indicating a Windows-first approach. The PowerShell formatting is prominent, and there is no explicit mention of Linux/macOS environments or their nuances. However, Bash examples are present, so Linux users can complete the task.
Recommendations
- Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider showing Bash examples first, or clarify that Bash is the default for cross-platform usage.
- Add a note about any differences in environment setup or command syntax between platforms.
- Provide guidance for macOS users if any step differs.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files. However, PowerShell is mentioned alongside CLI throughout, and the page includes a custom tag 'devx-track-azurepowershell'. PowerShell examples are given equal prominence to CLI, but there is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, which may create friction for Linux/macOS users who typically use CLI or Bash. There are no Windows-only tools or patterns, and Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Consider mentioning Azure CLI first, as it is cross-platform and more widely used on Linux/macOS.
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Add a note that all steps can be completed on Linux/macOS using Azure CLI and Bicep.
- Ensure that any references to PowerShell do not imply it is required or preferred over CLI.
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, which are cross-platform. However, in the section about disabling routing to a regional gateway, Azure PowerShell is mentioned alongside Azure CLI and REST API, but no Linux-specific tools or shell scripts are referenced. Azure PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (like Bash scripts or REST API via curl) may create minor friction for Linux/macOS users. The overall guidance and examples are not Windows-exclusive, but there is a slight tendency to mention Windows tools (PowerShell) without Linux equivalents.
Recommendations
- When referencing Azure PowerShell, also mention Bash or shell scripting alternatives for Linux/macOS users, such as using curl with the REST API.
- Provide explicit examples using Azure CLI (already present) and REST API via curl for disabling gateways, to ensure parity.
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Avoid listing PowerShell before CLI or REST API unless the feature is truly Windows-only.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance via pivot sections, but in several areas, Windows-specific examples, tools, and terminology are presented first or more prominently. PowerShell commands are frequently included alongside Bash/Azure CLI, and Windows tools (like Kudu, IIS, .NET Framework, and Windows directory paths) are referenced in detail. Linux equivalents are present but sometimes less detailed or appear after Windows content.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with clear pivots.
- Where PowerShell commands are shown, always provide Bash/Azure CLI equivalents and clarify OS applicability.
- Expand Linux-specific guidance to match the depth of Windows sections (e.g., troubleshooting, diagnostic logs, persistent storage details).
- Avoid referencing Windows tools or patterns (like Kudu, C:\home, IIS) in Linux pivots unless Linux equivalents are also provided.
- Review ordering of sections/examples to avoid consistently presenting Windows content first.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity for Azure portal, Azure CLI, ARM templates, and programming languages (Python, Java, JavaScript, .NET), but PowerShell examples are prominent and often shown alongside or before CLI equivalents. PowerShell is a Windows-centric tool, and its heavy inclusion (especially with detailed scripts) may create friction for Linux/macOS users. However, Azure CLI and ARM template instructions are present throughout, and most critical tasks can be completed on Linux/macOS. Some sections (e.g., assigning user-assigned identities for App Service) note PowerShell limitations, but do not provide Linux-specific workarounds or alternatives.
Recommendations
- Ensure Azure CLI examples are always present and shown before PowerShell examples, as CLI is cross-platform.
- Where PowerShell is used, clarify its OS requirements and provide equivalent Bash or shell script examples for Linux/macOS users.
- Highlight that Azure CLI and ARM templates are fully supported on Linux/macOS, and recommend them as the primary automation tools.
- Add explicit notes or links for Linux/macOS users when PowerShell functionality is limited or unavailable.
- Consider including Bash shell script examples for token retrieval, especially in sections where only PowerShell is shown.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is largely platform-neutral, focusing on Azure Application Gateway backend settings. However, in the troubleshooting section for Dedicated Backend Connections, Windows authentication mechanisms (NTLM and Kerberos) and IIS configuration are referenced, with links to Windows and IIS documentation. These references are presented without mentioning Linux equivalents or alternatives, and Windows tools are mentioned first and exclusively in this context.
Recommendations
- When discussing authentication mechanisms, clarify whether NTLM/Kerberos and IIS are required or if Linux-based alternatives (such as SPNEGO for Kerberos, Apache/Nginx for web server authentication) are supported.
- If Application Gateway supports Linux backend servers for authentication, provide links or examples for configuring Kerberos/NTLM on Linux (e.g., Samba, mod_auth_kerb for Apache).
- Explicitly state if certain troubleshooting steps or authentication mechanisms are Windows-only, so Linux users are not misled.
- Where possible, provide parity by mentioning Linux/macOS tools and documentation alongside Windows references.
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, but consistently presents PowerShell examples immediately after CLI, and offers a Windows-specific Helm installation example before the Linux equivalent. Windows tools (winget) are mentioned for Helm installation, while Linux installation is referenced but not as prominently. There is no missing Linux example for any critical step, but Windows is often presented first or with more detail.
Recommendations
- Alternate the order of CLI and PowerShell examples, or present CLI (cross-platform) first throughout.
- For Helm installation, present Linux instructions before Windows, or equally highlight both.
- Mention macOS installation for Helm, as it is also a common platform for Kubernetes administrators.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and encourage use of Azure Cloud Shell for cross-platform parity.
- Where possible, avoid referencing Windows-specific tools (like winget) without mentioning Linux/macOS equivalents (e.g., Homebrew for macOS).
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 troubleshooting steps for Application Gateway for Containers with a clear focus on cross-platform Kubernetes commands. However, in the section 'Collect ALB Controller logs', Windows and Linux are separated into tabs, but the Windows example (using 'findstr') is shown after the Linux example (using 'grep'). Both platforms are covered, but the Linux example is given first, minimizing Windows bias. There are no PowerShell-specific commands, Windows tools, or patterns mentioned exclusively or before Linux equivalents. All other examples and instructions use standard Kubernetes CLI commands, which are platform-agnostic.
Recommendations
- Maintain parity by continuing to provide both Linux and Windows command examples where output filtering is required.
- Consider clarifying that all kubectl commands work on both platforms, and only output filtering differs.
- If possible, provide macOS-specific notes where relevant, though macOS users typically use Linux commands.
- Ensure future troubleshooting steps do not assume Windows tools or shell environments by default.
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 examples are consistently included alongside CLI, and are presented in a way that may suggest parity. However, PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. Additionally, in some sections (e.g., resource group deletion), PowerShell examples are given immediately after CLI, which could be perceived as 'windows_first' bias. No Linux-specific tools or patterns (such as Bash scripting or references to Linux package managers) are mentioned, but the CLI examples are cross-platform.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly state that PowerShell examples are optional and primarily for Windows users.
- Consider providing Bash shell scripting examples for common tasks (e.g., environment variable usage, loops) where relevant.
- Add notes indicating that all CLI commands work on Linux/macOS, and highlight any platform-specific caveats if present.
- If PowerShell is included, ensure it is not presented as the default or primary method for Linux/macOS users.
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, PowerShell instructions are presented as a separate tab and explicitly reference Windows PowerShell. Additionally, in the CLI section, Windows PowerShell is mentioned as an example of a command console application before alternatives, suggesting a Windows-first perspective. There are no Linux-specific examples or explicit mentions of Linux/macOS shell environments, and screenshots are all from the Azure portal (which is platform-agnostic).
Recommendations
- In the Azure CLI section, clarify that the CLI can be used from any terminal on Linux, macOS, or Windows, and provide examples for Bash or other common Linux/macOS shells.
- Avoid mentioning Windows PowerShell as the default CLI environment; instead, refer to 'a command console application such as Bash, Terminal, or PowerShell'.
- Add explicit instructions or notes for Linux/macOS users, such as how to install and use Azure CLI in their environments.
- Consider including sample shell commands for Bash or Zsh where relevant.
- Ensure parity in troubleshooting or environment setup notes for all platforms.
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
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash). All other instructions, code, and tooling are cross-platform (Java, Maven, Spring Boot). No Windows-specific tools or patterns are mentioned, and Linux/macOS instructions are present and correct.
Recommendations
- Present environment variable instructions for Linux/macOS (bash) before Windows (cmd/PowerShell), or group them equally.
- Explicitly state that all steps are cross-platform except for OS-specific environment variable commands.
- Consider adding a note that Maven and Java instructions work identically on Linux/macOS and Windows.
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 (export), and uses 'cmd' syntax highlighting for build/run/curl commands, but does include Linux/macOS equivalents. No critical steps are Windows-only, and all major tasks can be completed on Linux/macOS.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group them equally.
- Use generic shell syntax highlighting (e.g., 'bash' or no language) for cross-platform commands like Maven build/run and curl.
- Explicitly mention that all steps are cross-platform, and clarify any OS-specific differences.
- Add a note that Maven and Java are cross-platform, and that the instructions apply to Linux/macOS as well as Windows.
Azure Functions
Durable Functions best practices and diagnostic tools
...s/durable/durable-functions-best-practice-reference.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Durable Functions best practices and diagnostic tools, with examples and guidance for multiple languages. However, in the section on Azure Functions performance settings, PowerShell is listed before Python, which may subtly suggest Windows-first bias. No critical diagnostic tools or examples are Windows-only, and Linux/macOS users are not blocked from completing any tasks.
Recommendations
- When listing language-specific guidance, alternate the order or list languages alphabetically to avoid subtle Windows-first bias.
- Ensure that examples and tool recommendations include Linux/macOS equivalents where relevant.
- Explicitly mention cross-platform compatibility for diagnostic tools and extensions (e.g., Application Insights, VS Code extension).
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
windows_tools
Summary
The documentation is generally cross-platform and provides parity for both Windows and Linux users. However, there are minor instances of Windows bias: Windows-specific syntax (e.g., %HOME% in AzureWebJobs_TypeScriptPath) is shown without a Linux equivalent, and Azure CLI and Azure PowerShell are recommended for programmatic management of settings, with no mention of Linux-native tools. In the WEBSITE_TIME_ZONE section, Windows and Linux examples are both given, but Windows is listed first. The WEBSITE_NODE_DEFAULT_VERSION setting is clearly marked as Windows-only, which is appropriate. Overall, Linux/macOS users can complete all tasks, but minor friction exists due to Windows-first ordering and tool recommendations.
Recommendations
- Where Windows-specific syntax is shown (e.g., %HOME%), add the Linux equivalent (e.g., $HOME).
- When recommending Azure CLI and Azure PowerShell, clarify that Azure CLI is fully cross-platform and PowerShell Core is available on Linux/macOS.
- Consider listing Linux examples before or alongside Windows examples in sections where both are relevant.
- Explicitly mention cross-platform alternatives or note when a setting/tool is Windows-only.