244
Pages Scanned
53
Pages Flagged
244
Changed Pages
21.7%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-02-22 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 244
Files Completed: 244
Problematic Pages
53 issues found
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 page presents Azure PowerShell examples first and in greater detail, with CLI examples following but less emphasized. References to PowerShell commands and links are more prominent, and the 'Next steps' section directs users to a PowerShell-specific guide. There are no explicit Linux/macOS-specific examples or guidance, and the use of PowerShell is implicitly prioritized, which may create friction for Linux/macOS users who prefer Azure CLI or other tools.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, ensuring equal detail and clarity.
- Add explicit guidance for Linux/macOS users, including notes about CLI usage and any platform-specific considerations.
- In the 'Next steps' section, include links to CLI-based configuration guides or ARM/Bicep template guides, not just PowerShell.
- Where possible, clarify that PowerShell is not required and that all configuration steps can be performed with Azure CLI or REST API.
- Ensure all referenced tools and commands are cross-platform, and avoid implying PowerShell is the default or preferred method.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 repeatedly references Azure PowerShell scripts as the primary migration tooling, without mentioning Azure CLI or Bash alternatives. PowerShell is a Windows-centric tool, and its exclusive mention creates friction for Linux/macOS users. There are no Linux/macOS-specific examples or guidance, and PowerShell is presented as the default solution for migration tasks.
Recommendations
- Add Azure CLI examples or scripts for migration tasks, especially for configuration and public IP retention.
- Explicitly mention whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide installation guidance if so.
- Provide Bash or shell script alternatives for common migration steps.
- Clarify if any migration steps are only possible with PowerShell, and offer workarounds or alternatives for Linux/macOS users.
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
Medium 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 is used for all command-line examples, and Windows tools (MSI, winget, Visual Studio Installer) are mentioned throughout. No Linux or macOS equivalents or instructions are provided for SignTool integration, and Linux/macOS users are not addressed in the main setup sections.
Recommendations
- Clearly indicate if SignTool integration is Windows-only, and provide guidance for Linux/macOS users on alternative signing tools or integrations.
- For cross-platform integrations (GitHub Actions, Azure DevOps, SDK), add explicit Linux/macOS setup instructions and examples.
- Where possible, provide parity for Linux/macOS users, such as using .NET CLI or cross-platform tools instead of Windows-only installers.
- Add a section summarizing which integrations are platform-specific and which are cross-platform, with links to relevant instructions.
- Include sample commands for Linux/macOS environments (e.g., bash, dotnet CLI, package managers like apt/yum/homebrew) where applicable.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides step-by-step instructions for using managed identities in Azure API Management via the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively offers PowerShell examples for CLI-based operations, omitting equivalent Azure CLI (cross-platform) examples. Additionally, PowerShell is presented before ARM templates, and there is no mention of Bash or Linux/macOS-specific workflows. This creates friction for Linux/macOS users who may prefer or require Azure CLI.
Recommendations
- Add Azure CLI examples alongside PowerShell for all operations (creating, updating, and removing managed identities).
- Explicitly mention that Azure CLI is supported and provide links to relevant Azure CLI documentation.
- Where possible, show Azure CLI examples before or alongside PowerShell to emphasize cross-platform parity.
- Include notes clarifying that PowerShell is not required and that all operations can be performed on Linux/macOS using Azure CLI.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. Azure PowerShell is a Windows-centric tool, and its example is given equal prominence to Azure CLI. The CLI example is cross-platform, but PowerShell is presented as a primary workflow, which may create friction for Linux/macOS users. Additionally, PowerShell requirements are listed alongside CLI in prerequisites, and the PowerShell example is not explicitly marked as Windows-only, potentially confusing non-Windows users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Consider adding Bash or shell script examples for Linux/macOS users, or explicitly state that Azure CLI is cross-platform.
- Reorder examples to show Azure CLI before PowerShell, or group PowerShell as an alternative for Windows users.
- Add notes in the PowerShell section indicating its Windows-centric nature and suggest CLI for Linux/macOS.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance using zone pivots, but Windows-specific examples, tools, and explanations are often presented first or in more detail. PowerShell commands are frequently shown alongside Bash, sometimes with Windows-specific explanations. Windows tools and patterns (such as IIS, .NET Framework, and Windows directory paths) are referenced more prominently, and some sections (like customizing memory and CPU) are Windows-only, with no Linux equivalent provided.
Recommendations
- Ensure Linux examples and explanations are given equal prominence and detail as Windows, especially for advanced configuration topics.
- Where PowerShell commands are shown, always provide Bash equivalents and clarify any OS-specific differences.
- For sections that are Windows-only (e.g., memory and CPU customization), explicitly state Linux limitations or alternatives, or link to Linux-specific documentation.
- Review the order of examples and explanations to avoid consistently presenting Windows first.
- Expand Linux-specific troubleshooting and advanced configuration guidance to match Windows coverage.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command) are Windows-centric, and Linux/macOS equivalents are not provided. The use of Windows tools and terminology appears first and exclusively, creating friction for Linux/macOS users who may need to troubleshoot or test connectivity from VMs.
Recommendations
- Clarify early and prominently that gateway-required virtual network integration is Windows-only, as already stated, to set expectations.
- Where troubleshooting steps involve Windows-specific tools (e.g., PowerShell Test-NetConnection), provide Linux/macOS equivalents such as 'nc' (netcat), 'telnet', or 'curl' for TCP connectivity testing.
- Add examples for Linux/macOS users in troubleshooting sections, especially for connectivity and DNS testing.
- Mention that Linux App Service plans must use regional virtual network integration, and link to relevant documentation.
- Consider reordering troubleshooting guidance to present cross-platform tools first or in parallel.
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
windows_tools
missing_linux_example
Summary
The documentation page presents Windows-specific certificate loading patterns and code examples first, with detailed C# and Java samples for Windows certificate stores. Linux guidance is less prominent, often deferred to external language/platform documentation, and Linux code samples are limited to C#. There is a notable emphasis on Windows tools and stores, with Linux equivalents mentioned later or less thoroughly.
Recommendations
- Provide Linux-specific code samples for popular languages (Node.js, Python, Java, PHP) directly in the documentation, not just C#.
- Ensure Linux guidance is presented alongside Windows guidance, not only after or as an afterthought.
- Add explicit instructions for accessing certificates in Linux App Service environments for each major language.
- Include examples of using Linux environment variables for certificate paths in code samples.
- Clarify when Windows-specific instructions are not applicable to Linux users, and offer Linux alternatives.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and neutral, but the 'Hybrid Connections' section introduces Windows bias by only mentioning installation of the Hybrid Connection Manager on Windows Server, with no mention of Linux support or alternatives. There are no explicit PowerShell-heavy examples or Windows-first ordering, but the omission of Linux guidance for Hybrid Connections is notable.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux hosts, and if so, provide installation instructions or links for Linux.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux users.
- Review other sections for tool references and ensure parity in examples and guidance for Linux/macOS where applicable.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across platforms, but there is a consistent pattern of Windows-first presentation and more detailed coverage of Windows-specific variables and tools. Windows paths, tools (such as msbuild, Web Deploy/MSDeploy), and configuration files (like applicationHost.config, Web.config) are referenced more frequently and often before Linux equivalents. Some sections, such as Build Automation, provide more detailed explanations for Windows (Kudu) than for Linux (Oryx), and Windows-specific deployment and logging variables are described in greater detail. Linux and container-specific settings are present, but often after Windows, and sometimes with less context or explanation.
Recommendations
- Ensure Linux and container examples are presented alongside Windows examples, not after.
- Where Windows tools (e.g., msbuild, Web Deploy) are mentioned, provide Linux equivalents or clarify when none exist.
- Balance the level of detail in descriptions for Linux (Oryx) and Windows (Kudu) build automation.
- When referencing file paths or configuration files, provide both Windows and Linux paths in all examples.
- Add more Linux/container-specific troubleshooting and usage notes where appropriate.
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 provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, but does not mention or link to equivalent instructions for Azure CLI or ARM templates, which are cross-platform. This creates a bias toward Windows/PowerShell users and may cause friction for Linux/macOS users.
Recommendations
- Add links to tutorials or instructions for creating autoscaling, zone-redundant Application Gateway using Azure CLI and ARM/Bicep templates.
- Mention Azure CLI and ARM/Bicep as alternative, cross-platform tools alongside PowerShell.
- Ensure examples and walkthroughs are provided for both PowerShell and CLI, or at least reference CLI documentation.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI or Bash example for Linux/macOS users. It also references Visual Studio and a .NET-based log converter tool, which are Windows-centric. There are no Linux-first or Linux-parity examples for command-line log configuration or log conversion.
Recommendations
- Add Azure CLI and/or Bash examples for enabling diagnostic logging, alongside the PowerShell example.
- Mention cross-platform log converter tools or provide instructions for converting logs using Python or other open-source tools.
- Reference alternative editors and tools (such as VS Code or command-line utilities) for log analysis, not just Visual Studio.
- Ensure that all critical workflows (log enabling, log conversion, log analysis) have Linux/macOS-friendly guidance.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, in the troubleshooting section for Dedicated Backend Connections, Windows-specific tools and patterns are referenced (Service Principal Name configuration and Windows Authentication/IIS documentation), and Windows authentication mechanisms (NTLM, Kerberos) are discussed without mentioning Linux equivalents or guidance. Additionally, Windows terminology and links are presented first and exclusively in this context.
Recommendations
- Add guidance for troubleshooting backend authentication issues on Linux-based servers (e.g., Apache, NGINX, Samba, MIT Kerberos).
- Include references or links to Linux authentication documentation and tools where relevant.
- Clarify that NTLM and Kerberos are cross-platform and provide examples or troubleshooting steps for Linux environments.
- Where backend server logs are referenced, mention both Windows (IIS) and Linux (Apache, NGINX) log locations/formats.
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 exclusively demonstrates the configuration of Azure Application Gateway TCP/TLS proxy using a SQL Server virtual machine running Windows Server. All examples and screenshots reference Windows-based SQL Server VMs, and the client connection step recommends SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for Linux-based SQL Server VMs or cross-platform SQL clients, which may create friction for Linux/macOS users.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as a backend, or clarify if only Windows SQL Server is supported.
- Provide examples of connecting to the SQL Server via cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd, DBeaver) in addition to SSMS.
- Add notes or guidance for Linux/macOS users regarding any platform-specific requirements or limitations.
- If the feature supports Linux SQL Server VMs, add screenshots and walkthroughs for those scenarios.
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 page for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling centered around PowerShell. There are no references to Azure CLI, Bash, or Linux/macOS-native tooling, nor are there alternative examples for non-Windows environments. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all script downloads and usage are PowerShell-specific. This creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
- Add Bash shell examples for certificate handling and script execution, especially for Linux/macOS users.
- Clearly state that PowerShell is required, and offer guidance for installing PowerShell Core on Linux/macOS if PowerShell-only scripts are unavoidable.
- Mention Azure Cloud Shell's Bash environment as an alternative, and clarify which steps can be performed there.
- Consider linking to cross-platform migration tools or documenting limitations for Linux/macOS users.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias, primarily through exclusive use of Azure PowerShell examples and references, and by linking to tutorials that use PowerShell as the primary method. While the core content is platform-agnostic, Linux/macOS users may encounter friction due to the lack of Azure CLI or ARM template examples and the prominence of PowerShell-based workflows.
Recommendations
- Add Azure CLI examples alongside PowerShell for registration, migration, and other operations.
- Provide ARM template or Terraform examples for deployment and migration tasks.
- Ensure tutorials and quickstarts offer both PowerShell and CLI options, or clearly indicate which platforms are supported.
- Explicitly mention that PowerShell commands can be run cross-platform (with Azure PowerShell Core), but also provide native CLI alternatives for Linux/macOS users.
Application Gateway
Enabling end to end TLS on Azure Application Gateway
...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides a conceptual overview of end-to-end TLS on Azure Application Gateway, but the only 'Next steps' link is to a PowerShell-based configuration guide. There are no Linux/macOS CLI (Azure CLI, Bash, etc.) examples or links, and Windows/PowerShell tooling is referenced first and exclusively for practical configuration. Additionally, the certificate format guidance references a Windows API (PFXImportCertStore) without mentioning cross-platform alternatives.
Recommendations
- Add links to equivalent Azure CLI and/or ARM template guides for configuring end-to-end TLS on Application Gateway.
- Provide Linux/macOS-friendly instructions and examples for certificate creation, conversion, and upload (e.g., using OpenSSL, Azure CLI).
- When referencing certificate formats and APIs, mention cross-platform tools (such as OpenSSL for PFX creation) alongside Windows-specific APIs.
- Ensure that practical configuration steps are available for all supported platforms, not just Windows/PowerShell.
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 for Azure Automation' demonstrates a notable Windows bias. All migration scripts and runbook examples are provided exclusively in PowerShell and PowerShell Workflow, with no equivalent Bash, Python, or cross-platform scripting options. The instructions for Hybrid Runbook Worker installation link to pages with Windows tabs by default, and the prerequisites and module requirements are focused on PowerShell modules. There is no guidance for Linux users on using alternative scripting languages or tools, nor are Linux-specific examples or considerations provided.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or clearly state if PowerShell is required regardless of OS.
- Include Linux/macOS-specific instructions or examples, especially for Hybrid Runbook Worker scenarios.
- Clarify whether PowerShell Core (pwsh) is supported and provide guidance for Linux users on installing and using PowerShell if it is required.
- Add links or tabs for Linux-specific documentation where Windows tabs are referenced.
- Mention any limitations or requirements for Linux users explicitly, such as module compatibility or script execution environments.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily features PowerShell examples for all procedural steps, with no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting interface, and REST API alternatives are provided, but Azure CLI or Bash examples are missing. The prerequisites and procedural sections reference PowerShell modules and cmdlets first and exclusively, creating friction for users on Linux/macOS platforms.
Recommendations
- Add Azure CLI examples for all procedural steps (e.g., assigning managed identity, configuring Key Vault access policy, switching encryption keys).
- Include Bash scripting examples where applicable, especially for automation scenarios.
- Mention cross-platform tools (Azure CLI, Bash) alongside PowerShell in prerequisites and procedural guidance.
- Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, but provide native CLI/Bash alternatives for parity.
- Reorganize sections so that REST API and CLI examples are not secondary to 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 page is heavily focused on Windows PowerShell usage, with all examples and instructions provided exclusively for PowerShell. There are no references to Bash, Linux CLI tools, or cross-platform scripting approaches. Windows-specific tools and patterns (e.g., PSCredential, Get-AutomationPSCredential, New-AzAutomationCredential) are mentioned without Linux/macOS alternatives or guidance. The PowerShell-centric approach creates friction for Linux/macOS users, especially since Azure Automation supports Python runbooks and cross-platform scripting.
Recommendations
- Add examples for Python runbooks, which are supported in Azure Automation and are cross-platform.
- Clarify which steps are PowerShell-specific and provide equivalent instructions for Bash/CLI where possible (e.g., using Azure CLI for credential management).
- Mention that PowerShell Core (pwsh) is cross-platform and provide guidance for Linux/macOS users on how to install and use it.
- Include links or references to Linux/macOS-specific documentation for Azure Automation authentication.
- Explicitly state any Windows-only limitations if present, or clarify that the steps are applicable to all platforms if using PowerShell Core.
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 (e.g., New-SelfSignedCertificate, Export-PfxCertificate) for all steps, including certificate creation. There are no Bash, Azure CLI, or Linux/macOS-compatible examples, and Windows tools are referenced without alternatives. This creates friction for Linux/macOS users, especially for certificate generation and local scripting.
Recommendations
- Add Azure CLI examples for all steps, especially resource creation and management.
- Provide Linux/macOS-compatible instructions for generating self-signed certificates (e.g., using OpenSSL).
- Mention that Azure PowerShell can be installed and used cross-platform, but highlight Azure CLI as a viable alternative.
- Include Bash shell examples alongside PowerShell, or link to equivalent tutorials for Linux/macOS users.
- Clarify which steps are Windows-specific and offer alternatives where possible.
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 tools (PowerShell cmdlets) are mentioned first and more frequently throughout the data retention and backup sections. Examples for exporting and managing resources rely heavily on Windows PowerShell cmdlets, with no equivalent Linux/CLI examples provided. Linux guidance is present for TLS, but less so for other management tasks.
Recommendations
- Provide Azure CLI or REST API examples alongside PowerShell cmdlets for resource management, backup, and retention tasks.
- Include Linux-specific instructions for exporting runbooks, DSC configurations, and retrieving asset details, where possible.
- Ensure Linux guidance is given equal prominence and order in tables and lists, not always after Windows.
- Clarify which tasks are cross-platform and which are Windows-only, and offer alternatives for Linux/macOS users.
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
missing_linux_example
Summary
The documentation is heavily focused on PowerShell-based runbooks and examples, with all code snippets and parameter-passing walkthroughs using PowerShell, PowerShell Workflow, or C# (for SDK usage). There are no examples or guidance for using Linux-native tools (e.g., Azure CLI, Bash) to start or interact with runbooks, nor are there examples for Python runbooks beyond a brief mention. The PowerShell-centric approach may create friction for Linux/macOS users who prefer or require non-PowerShell tooling.
Recommendations
- Add Azure CLI (az automation runbook) examples for starting runbooks and passing parameters, including JSON parameter input.
- Provide Bash and/or Python-based examples for interacting with runbooks, especially for Linux/macOS users.
- Include explicit guidance or code snippets for starting Python runbooks with parameters from non-PowerShell environments.
- Where possible, present cross-platform tooling (e.g., Azure CLI, REST API with curl) before or alongside PowerShell examples.
- Clarify in relevant sections that PowerShell examples are shown, and link to equivalent CLI or SDK documentation for other platforms.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily emphasizes Windows PowerShell and PowerShell-based cmdlets for managing credentials in Azure Automation. All CLI examples are PowerShell-based, and there are no Bash, Linux shell, or cross-platform CLI examples. The page refers to 'Windows PowerShell' specifically and does not mention Linux or macOS equivalents for credential management. Python examples are provided, but only for runbooks, not for asset management outside runbooks. The documentation assumes familiarity with PowerShell and Windows-centric tools, creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples for credential management tasks, where possible, to provide cross-platform guidance.
- Clarify whether credential asset management is possible via Azure CLI, REST API, or SDKs, and provide links or examples.
- Explicitly state if PowerShell is required for certain operations, and note any limitations for Linux/macOS users.
- If PowerShell Core (pwsh) is supported on Linux/macOS for these tasks, mention this and provide relevant examples.
- Include guidance or links for Linux/macOS users on installing and using PowerShell Core if it is needed.
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 script example for configuring the 'publicNetworkAccess' property, without offering a Linux/macOS equivalent (such as Azure CLI or REST API). While the page covers both Windows and Linux in the context of Hybrid Runbook Workers and Update Management, the scripting example is Windows-centric and may create friction for Linux/macOS users. Additionally, PowerShell is presented as the primary automation method, with no mention of cross-platform alternatives.
Recommendations
- Add Azure CLI and/or REST API examples for configuring 'publicNetworkAccess', alongside the PowerShell script.
- Explicitly mention that PowerShell examples are Windows-centric and provide guidance for Linux/macOS users.
- Ensure that scripting and automation instructions are presented in a cross-platform manner, or at least offer parity.
- Consider showing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
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 emphasizes PowerShell cmdlets and examples, which are primarily associated with Windows environments. All certificate management tasks (creation, retrieval, deployment) are shown using PowerShell, with no equivalent Bash, CLI, or Linux-native tooling examples. PowerShell is presented first and in greater detail than Python, and there are no explicit instructions or examples for Linux/macOS users to perform certificate operations outside of Python runbooks.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to provide parity for Linux/macOS users.
- Include Bash or shell script snippets where applicable, especially for uploading certificates or interacting with Azure Automation.
- Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only, and provide guidance for Linux/macOS users if PowerShell Core is supported.
- Consider referencing or linking to documentation for certificate management on Linux/macOS, such as using OpenSSL to generate .pfx/.cer files.
- Present Python and CLI examples alongside PowerShell, not after, to avoid 'windows_first' bias.
Automation
Manage modules in Azure Automation
...b/main/articles/automation/shared-resources/modules.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 modules and Windows-centric workflows, with nearly all examples, tools, and instructions assuming the use of PowerShell and Windows environments. There is minimal mention of Linux or cross-platform scenarios, and Linux-specific guidance is limited to brief notes about unsupported features. No Linux shell (e.g., Bash) or cross-platform scripting examples are provided, and the internal cmdlets and modules are often unavailable on Linux Hybrid Runbook Workers, with no Linux alternatives or workarounds described.
Recommendations
- Add explicit guidance and examples for Linux Hybrid Runbook Workers, including supported modules and any differences in workflow.
- Provide Linux/macOS shell (e.g., Bash, Python) examples where possible, especially for module management and automation tasks.
- Clearly indicate which features are Windows-only and suggest Linux alternatives or workarounds where feasible.
- Expand the Python modules section to include more parity with PowerShell guidance, and link to Linux-specific resources.
- When describing portal or PowerShell Gallery workflows, note any platform-specific limitations and provide Linux-compatible instructions if available.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally platform-neutral and focuses on Azure infrastructure concepts. However, in the section about DNS server changes, restart instructions reference Azure PowerShell cmdlets (Stop-AzApplicationGateway and Start-AzApplicationGateway) with direct links, but do not mention or provide Azure CLI equivalents. This is a minor bias, as Azure CLI is cross-platform and widely used on Linux/macOS. No other Windows-specific tools, patterns, or examples are present, and the page does not prioritize Windows tools or concepts elsewhere.
Recommendations
- Add Azure CLI examples alongside PowerShell cmdlets for restarting Application Gateway instances, e.g., az network application-gateway stop/start.
- Wherever Azure PowerShell is referenced, provide Azure CLI equivalents or clarify that both tools can be used.
- Ensure future procedural steps or examples are given in both Azure CLI and PowerShell, or reference the relevant documentation for both.
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
Summary
The documentation provides environment variable setup instructions for Windows (Command Prompt and PowerShell) before Linux/macOS (bash), and Windows command examples are consistently shown first. However, equivalent Linux/macOS instructions are present throughout, and no critical steps are Windows-only.
Recommendations
- Present Linux/macOS and Windows instructions in parallel tabs or sections, rather than always listing Windows first.
- Where possible, use cross-platform commands or highlight that all platforms are supported equally.
- Consider mentioning that all major steps can be performed on Linux/macOS, reinforcing parity.
- If showing multiple OS instructions inline, alternate the order or clarify that the order does not imply preference.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides Azure portal instructions (which are cross-platform), Azure PowerShell examples, and Azure CLI examples. However, PowerShell examples are presented first and in greater detail, which may create a subtle Windows bias. There are no Linux/macOS-specific shell or tool examples (e.g., Bash, REST, or Python), but Azure CLI is cross-platform and included. The FAQ and troubleshooting sections reference commands like nslookup, which are available on all platforms, and REST API usage, which is platform-neutral.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Add Bash shell script examples where appropriate, especially for tasks like DNS verification (e.g., using dig or nslookup).
- Explicitly mention that Azure CLI and REST API methods are suitable for Linux/macOS users.
- Consider including a short note clarifying that PowerShell is available on Linux/macOS, but Azure CLI is generally preferred for cross-platform scripting.
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
powershell_heavy
Summary
The documentation provides both Bash and PowerShell syntax for Azure CLI commands, but PowerShell examples are consistently shown immediately after Bash, and sometimes with explicit 'PowerShell syntax' labels. There are no Windows-only tools or patterns, but the examples do show Windows (PowerShell) syntax alongside Bash, which may create minor friction for Linux/macOS users. The documentation does not exclusively mention Windows tools, and Visual Studio Code is cross-platform. No critical steps are Windows-only.
Recommendations
- Consider showing Bash examples first, or grouping Bash and PowerShell examples together for parity.
- Clarify that PowerShell syntax is for Windows users, and Bash for Linux/macOS, to help readers quickly identify their relevant section.
- If possible, provide a single Bash example where syntax is identical, and only split when necessary.
- Explicitly mention that all steps can be performed on Linux/macOS unless otherwise noted.
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 formatted specifically for Windows users and are presented immediately after the Bash examples. There is no explicit Linux bias, but the inclusion of PowerShell examples and their prominence suggests a mild Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples as 'Linux/macOS' and 'Windows' respectively to help users identify which example is relevant to their platform.
- Consider providing Bash examples first, or at least alternate the order to avoid always showing Windows examples second.
- Add a brief note clarifying that Bash examples are intended for Linux/macOS terminals, and PowerShell for Windows.
- Ensure parity in explanations and troubleshooting tips for both environments.
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 PowerShell examples for deploying the ARM template. However, PowerShell is featured equally alongside CLI, and there is no explicit mention of Linux/macOS-specific tools or workflows. The instructions reference uploading files to Azure Cloud Shell, which is cross-platform, but do not mention Linux-native tools (e.g., Bash, shell scripting) or alternative deployment methods (such as using REST API or Terraform). The order of examples (CLI first, then PowerShell) is neutral, but the presence of PowerShell-specific requirements and examples may create minor friction for Linux/macOS users.
Recommendations
- Add explicit mention that Azure CLI works natively on Linux/macOS, and provide Bash shell example commands where relevant.
- Clarify that Azure PowerShell is cross-platform, but CLI is often preferred on Linux/macOS.
- Consider including a REST API example for ARM template deployment, which is platform-agnostic.
- Mention that Cloud Shell supports both Bash and PowerShell, and show how to use Bash for file uploads and deployments.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is mentioned alongside CLI throughout and is given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the documentation includes a custom tag 'devx-track-azurepowershell'. However, Linux/macOS users can fully complete the quickstart using Azure CLI, and no critical steps are Windows-only.
Recommendations
- Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Clarify that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Add a note highlighting that Azure CLI is recommended for cross-platform scenarios.
- Ensure that any referenced prerequisites or environment setup instructions for PowerShell include Linux/macOS guidance.
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 page primarily uses Azure Portal and Azure CLI examples, but when mentioning scripting or automation, it references Azure PowerShell cmdlets before or alongside Azure CLI, and does not provide Linux/macOS-specific guidance or examples. The PowerShell cmdlet is mentioned as an option for disabling a regional gateway, but no Bash or Linux shell equivalent is given. The ordering of tools (PowerShell before CLI) and lack of explicit Linux/macOS parity is a minor Windows bias.
Recommendations
- When referencing scripting tools, mention Azure CLI first, as it is cross-platform, and PowerShell second.
- Provide explicit Bash or shell script examples for Linux/macOS users where automation is discussed.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Where PowerShell is referenced, add a note that Azure CLI is recommended for cross-platform use.
- Add links to Azure CLI installation and usage guides for Linux/macOS.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples for backup and restore operations, with PowerShell presented before Azure CLI and REST API options. While Azure CLI and REST API examples are included, the PowerShell section is more extensive and appears first, which may create friction for Linux/macOS users who prefer Bash or CLI workflows. No Windows-specific tools or patterns are mentioned beyond PowerShell, and Linux parity is generally maintained via CLI and REST examples.
Recommendations
- Present Azure CLI examples before PowerShell, or at least in parallel, to avoid implying PowerShell is the preferred or default method.
- Expand Azure CLI examples to cover managed identity scenarios, matching the detail provided in PowerShell sections.
- Explicitly note that PowerShell can be run cross-platform, but highlight CLI as the native option for Linux/macOS users.
- Add a short section clarifying that all operations can be performed on Linux/macOS using Azure CLI and REST API, and link to relevant CLI installation guides.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a first-class option alongside CLI, and the PowerShell example is given equal prominence. There is minor Windows bias in that PowerShell is a Windows-centric tool (though now cross-platform), and the documentation does not mention Linux-specific shell options or tools. However, the Azure CLI example is fully functional and shown before PowerShell, and all steps can be completed on Linux/macOS using the CLI or portal.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Explicitly note that Azure CLI is fully supported on Linux/macOS and is the recommended tool for non-Windows environments.
- Consider adding a brief note for Linux/macOS users about installing and using Azure CLI, or linking to relevant installation guides.
- If possible, provide bash/zsh shell script examples for Azure CLI usage to reinforce Linux parity.
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 is generally platform-neutral, focusing on Azure concepts and resources. However, in the 'Related content' section, a link is provided to 'Connect virtual networks from different deployment models using PowerShell', which highlights a Windows-centric tool without mentioning cross-platform alternatives (such as Azure CLI or ARM templates). Additionally, PowerShell is referenced before any Linux-friendly options, which may subtly reinforce Windows-first patterns.
Recommendations
- Add links or examples for connecting virtual networks using Azure CLI, which is cross-platform, alongside the PowerShell example.
- Mention ARM template or Bicep-based approaches for resource deployment and configuration, which are platform-agnostic.
- Ensure that any scripting or tooling references include both Windows and Linux/macOS-friendly options, or clarify when a tool is Windows-only.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing Key Vault permissions, but PowerShell is given equal prominence and is sometimes listed before Linux-native alternatives. There are references to Windows-specific tools (IIS, Certreq.exe) for certificate export, and the automation FAQ links to both PowerShell and CLI, but PowerShell is mentioned first. However, Linux tools (OpenSSL) are also referenced, and Azure CLI examples are present. Overall, the documentation is mostly cross-platform, but there is a slight Windows-first and PowerShell-heavy bias in some sections.
Recommendations
- When listing automation options, consistently present Azure CLI examples before PowerShell, as CLI is cross-platform.
- Where Windows-specific tools like IIS or Certreq.exe are mentioned, provide explicit Linux/macOS alternatives (e.g., OpenSSL commands) in parallel.
- In FAQ and automation sections, clarify which tools are cross-platform and recommend Azure CLI as the default for non-Windows users.
- Ensure screenshots and UI instructions do not assume a Windows environment unless necessary.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_path_patterns
Summary
The documentation generally covers Azure App Service backup features in a cross-platform manner, with Azure portal and Azure CLI instructions that work for both Windows and Linux apps. However, there are subtle signs of Windows bias: Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are referenced before Linux equivalents, and the Kudu DebugConsole example uses Windows-style paths. The documentation mentions uploading files via FTP, which is a common Windows pattern, but does not reference SFTP or Linux-native tools. PowerShell is mentioned as an automation option, but not prioritized over CLI. Linux paths and behaviors are referenced, but often after Windows ones.
Recommendations
- When referencing file paths, always show both Windows and Linux equivalents (e.g., %HOME%/site/wwwroot and /home/site/wwwroot).
- In examples and instructions, alternate between Windows and Linux paths, or show both side-by-side.
- Mention SFTP and Linux-native file upload tools alongside FTP.
- In the 'Automate with scripts' section, clarify that both Azure CLI and PowerShell are cross-platform, and provide links to Bash shell samples if available.
- When discussing Kudu DebugConsole, note that it works for both Windows and Linux apps, and show Linux path examples.
- Ensure screenshots and examples are balanced between Windows and Linux environments.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service plans, explicitly supporting both Windows and Linux. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (such as PowerShell, RDP, IIS customization, and .NET Framework) are described first and in detail, while Linux is mentioned only as a limitation. The rest of the page does not show significant Windows bias, and examples/tools are generally OS-neutral.
Recommendations
- When describing Managed Instance, clarify that its Windows focus is intentional and provide a brief note about Linux alternatives or equivalent Linux hosting options in Azure App Service.
- Ensure that links and feature tables consistently mention Linux parity or limitations where relevant.
- Add references or links to Linux-specific documentation for App Service plans, especially for users seeking OS customization or advanced networking on Linux.
- If possible, provide examples or guidance for Linux App Service plan scenarios alongside Windows examples.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity for Azure portal, Azure CLI, ARM templates, and language SDKs, but PowerShell examples are prominent and often shown alongside or before CLI equivalents. PowerShell is a Windows-centric tool, and its heavy inclusion (especially in identity assignment/removal and token retrieval) may create friction for Linux/macOS users. However, Azure CLI and ARM template instructions are present for all critical tasks, and language SDK examples are cross-platform.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell examples, as CLI is cross-platform.
- Clearly indicate that PowerShell instructions are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Where PowerShell is not supported (e.g., user-assigned identity for App Service), highlight CLI as the preferred method.
- Consider adding Bash shell script examples for token retrieval, especially in sections where only PowerShell is shown.
- Review the 'Connect to Azure services in app code' section to ensure parity in scripting examples (e.g., show Bash/cURL alongside PowerShell).
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - AKS Add-on
...pplication-gateway-for-containers-alb-controller-addon.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is given equal prominence and is presented in many sections. In some cases, PowerShell is listed before CLI, and there are no explicit Linux/macOS-specific notes or parity checks. The PowerShell examples are Windows-centric, and while Azure CLI is cross-platform, the documentation does not clarify this or provide guidance for Linux/macOS users. There are no Linux-specific tools or shell patterns (e.g., Bash, zsh) mentioned, and the documentation assumes familiarity with PowerShell in several places.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add explicit notes or tabs indicating that PowerShell is Windows-only, and recommend Azure CLI for Linux/macOS.
- Consider listing Azure CLI examples first in each section to reduce Windows-first bias.
- Where PowerShell is used, provide Bash shell equivalents if there are any subtle differences (e.g., environment variable syntax).
- Add a brief section in prerequisites noting that Azure PowerShell is Windows-centric and that Linux/macOS users should use Azure CLI.
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
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but often presents PowerShell examples immediately after CLI, and includes Windows-specific tooling (e.g., winget for Helm installation). While Linux installation instructions for Helm are present, Windows-specific tools are mentioned first or exclusively (winget). The PowerShell examples are consistently present, which may create friction for Linux/macOS users who do not use PowerShell. However, all critical tasks are also covered with Azure CLI and Bash-compatible commands, so Linux users can complete the quickstart.
Recommendations
- When listing installation options for Helm, mention Linux/Bash methods before Windows-specific tools like winget, or present them side-by-side.
- Consider adding macOS-specific Helm installation instructions for parity.
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Where PowerShell is used, explicitly state that it is primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Avoid presenting Windows-specific tools (e.g., winget) before Linux equivalents unless Windows is the primary audience.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example is presented second and uses the Windows 'findstr' command. All other troubleshooting steps use cross-platform tools (kubectl, helm) and shell syntax, and there are no Windows-specific tools or patterns prioritized. The bias is minor and limited to the log filtering example.
Recommendations
- Ensure Linux and Windows examples are presented side-by-side or in tabs, with equal prominence.
- Clarify that all commands except the log filtering example are cross-platform.
- Consider providing macOS-specific notes if there are any differences.
- Explicitly state that the majority of commands are platform-agnostic and only the log filtering command differs.
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, PowerShell) before Linux/macOS (bash). All platforms are covered, but Windows commands are listed first. No other Windows-specific tools or patterns are present, and Linux/macOS parity is maintained throughout.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows commands, or group all OS instructions together in a table or tabbed interface.
- Explicitly state that the instructions are cross-platform and that all commands are available for Windows, Linux, and macOS.
- Consider adding a note that Maven and Java are cross-platform and provide links to installation instructions for Linux/macOS if not already present.
Azure App Configuration
Use variant feature flags in a Spring Boot application
...figuration/how-to-variant-feature-flags-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), but includes all major platforms. No other Windows-specific tools or patterns are used, and all code and build instructions are platform-neutral.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows (cmd/PowerShell), or group all OS instructions together for parity.
- Consider using tabbed instructions or a table for environment variable setup to avoid implicit prioritization.
- Explicitly state that the tutorial works equally on Windows, Linux, and macOS to reassure non-Windows 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 mentions Windows PowerShell as a possible console, the PowerShell section is explicitly Windows-focused and refers only to Windows PowerShell. The ordering of examples presents the portal first, then CLI, then PowerShell, with PowerShell instructions clearly marked as Windows-specific. No Linux/macOS-specific instructions or shell examples are provided, and the CLI section does not mention Bash or other Linux/macOS shells, potentially implying Windows as the default environment.
Recommendations
- In the Azure CLI section, explicitly mention Bash or other Linux/macOS shells as supported environments, and provide example commands for those shells if there are any differences.
- Clarify that Azure CLI commands work cross-platform and are not limited to Windows PowerShell.
- Consider adding a note in the PowerShell section that PowerShell Core (pwsh) is available on Linux/macOS, and provide instructions if applicable.
- Ensure screenshots and instructions are not overly Windows-centric (e.g., avoid only showing Windows UI elements if Linux/macOS have different experiences).
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, PowerShell) before Linux/macOS (bash), and uses Windows command prompt terminology ("restart the command prompt") first. However, Linux/macOS instructions are present and Maven/curl commands are cross-platform.
Recommendations
- Present environment variable setup instructions for Linux/macOS before Windows, or group them together for parity.
- Use neutral terminology such as 'terminal' instead of 'command prompt' when referring to cross-platform command-line usage.
- Clarify that Maven and curl commands are cross-platform and can be run on any supported OS.
- Consider adding a note that all steps are applicable to Linux/macOS unless otherwise specified.
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 cross-platform guidance for environment variable setup, but Windows-specific commands (setx, PowerShell) are presented before Linux/macOS equivalents. The Windows command prompt and PowerShell examples are given first, with the Linux/macOS export command appearing last. The rest of the tutorial uses cross-platform tools (Azure CLI, Maven, curl) and avoids Windows-only tooling.
Recommendations
- Present Linux/macOS environment variable commands before or alongside Windows examples, rather than after.
- Explicitly state that all commands (Azure CLI, Maven, curl) work on Windows, Linux, and macOS.
- Consider grouping environment variable setup instructions by OS, or using tabs for Windows, macOS, and Linux.
- Add a note clarifying that Visual Studio Code and other editors are cross-platform, and that the tutorial is not Windows-specific.
Azure Cache For Redis
Scale an Azure Cache for Redis instance
...n/articles/azure-cache-for-redis/cache-how-to-scale.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides scaling instructions for Azure Cache for Redis using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given equal prominence to Azure CLI, and PowerShell is mentioned before Azure CLI in several sections. There are no Linux-specific examples (such as Bash shell scripting), and PowerShell is a Windows-centric tool, though it is technically cross-platform. Azure CLI is cross-platform and is included, but Windows/PowerShell patterns are presented first. No Windows-only tools or commands are used, and all tasks can be completed with Azure CLI on Linux/macOS.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more widely used on Linux/macOS.
- Explicitly note that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
- Consider adding Bash shell scripting examples for automation scenarios.
- Clarify that PowerShell is available cross-platform, but Azure CLI is the recommended tool for Linux/macOS users.
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 deploying and managing Azure Cache for Redis using Bicep. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS shell environments or guidance for those users, but Azure CLI is cross-platform and shown first in each example section.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note indicating that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
- Consider including Bash or shell-specific instructions for Linux/macOS users, especially for prerequisites like saving files.
- Explicitly mention that all CLI commands can be run from Bash, Zsh, or other Linux/macOS shells.
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 included alongside Bash for every step, and PowerShell syntax is shown first in some cases. There is a slight bias toward Windows/PowerShell users, as Linux/macOS users may find the PowerShell examples unnecessary or confusing. However, Bash examples are present, so Linux parity is mostly maintained.
Recommendations
- Clearly label Bash and PowerShell examples to avoid confusion.
- Consider grouping Bash and PowerShell examples under separate tabs or sections, rather than showing both inline.
- Ensure Bash examples are shown first, as Bash is the default shell for Azure CLI and most cross-platform users.
- Add a note clarifying which examples are for Windows (PowerShell) and which are for Linux/macOS (Bash).