251
Pages Scanned
49
Pages Flagged
251
Changed Pages
19.5%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06
Scan Information
Started At: 2026-02-15 00:00:06
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 251
Files Completed: 251
Problematic Pages
49 issues found
Artifact Signing
Set up signing integrations to use Artifact Signing
...ticles/artifact-signing/how-to-signing-integrations.md
High Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page is heavily focused on Windows-specific tools and workflows, particularly SignTool, PowerShell, and Windows SDK components. All setup instructions, installation steps, and examples are exclusively for Windows environments, with no mention of Linux/macOS equivalents or cross-platform alternatives. The main integration described is SignTool, which is a Windows-only tool, and all installation commands are Windows-centric (MSI, Setup.exe, winget, PowerShell). Other integrations (GitHub Actions, Azure DevOps, SDK) are briefly referenced but lack detailed cross-platform guidance.
Recommendations
- Add explicit guidance and examples for Linux/macOS users, especially for integrations like GitHub Actions, Azure DevOps, and the Artifact Signing SDK.
- Clarify which integrations are cross-platform and provide step-by-step instructions for non-Windows environments.
- If SignTool is Windows-only, highlight alternative signing tools or workflows for Linux/macOS users, or state clearly that SignTool integration is Windows-specific.
- Include installation and usage examples for the Artifact Signing SDK on Linux/macOS, and describe how to use it for signing artifacts.
- Where PowerShell is used, offer Bash or shell script equivalents for Linux/macOS users where possible.
Create Pull Request
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 creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI-based examples exclusively use Azure PowerShell, with no mention of Azure CLI or Bash scripting. PowerShell is Windows-centric, and while it is available on Linux/macOS, Azure CLI is more commonly used in cross-platform environments. The documentation also presents PowerShell instructions before ARM templates, and does not offer Linux/macOS-specific guidance or parity.
Recommendations
- Add equivalent Azure CLI examples alongside PowerShell for all tasks (creating resource groups, API Management instances, assigning managed identities, updating instances).
- Explicitly mention that Azure PowerShell can be used cross-platform, but recommend Azure CLI for Linux/macOS users.
- Consider providing Bash scripting examples where appropriate.
- Ensure that references to installation guides include Azure CLI for Linux/macOS users.
- Present CLI options (PowerShell and Azure CLI) in parallel, rather than PowerShell-only or PowerShell-first.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific certificate store access is explained in detail with C# and Java examples, while Linux is only referenced later and with less detail. Windows tools and patterns (certificate store, thumbprint access, environment variables) are described first and most thoroughly. Linux examples are limited to C# file loading, and other languages (Node.js, PHP, Python, Java) are not shown for Linux, with users referred to external documentation. Windows-specific instructions and terminology dominate the initial sections.
Recommendations
- Provide explicit Linux examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the file paths provided.
- Reorganize sections so Linux and Windows approaches are presented in parallel, rather than Windows first.
- Expand Linux guidance to include common certificate handling patterns and troubleshooting tips.
- Clarify which instructions are Windows-only and which are cross-platform.
- Add sample code for accessing certificates in Linux containers for languages other than C#.
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_only_feature
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is for a feature (gateway-required virtual network integration) that is explicitly Windows-only. This is stated up front, and Linux apps are not supported. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, with no equivalent Linux/macOS commands or guidance provided. The use of Windows tools and PowerShell is exclusive, and Linux users are not given alternative instructions, even for general networking troubleshooting.
Recommendations
- Add explicit statements clarifying that gateway-required virtual network integration is Windows-only, and direct Linux users to regional virtual network integration.
- Where troubleshooting steps are generic (e.g., testing TCP connectivity, checking listening ports), provide Linux/macOS equivalents such as 'nc', 'ss', or 'netstat' commands.
- For PowerShell examples, add Bash/Linux command alternatives where applicable, even if only for VM troubleshooting.
- Link to regional virtual network integration documentation for Linux users throughout the page.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating certificate operations, but PowerShell is mentioned equally or slightly more prominently. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, while Linux tools (OpenSSL) are also covered. However, Windows tools are mentioned first in some sections and the PowerShell example is given alongside the CLI example, which may create friction for Linux/macOS users. There are no critical sections that are Windows-only, and Linux-friendly instructions (OpenSSL, Azure CLI) are present.
Recommendations
- Ensure Azure CLI examples are always given before PowerShell, as CLI is cross-platform.
- Where Windows tools (IIS, Certreq.exe) are mentioned, provide equivalent Linux/macOS instructions or clarify that OpenSSL is the preferred cross-platform method.
- Explicitly state which steps are platform-agnostic and which are Windows-specific.
- Add links or brief instructions for certificate export on Linux/macOS, if not already present.
- Consider grouping automation examples by platform, with Linux/macOS first, to improve parity.
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides Azure portal and Azure CLI instructions, which are cross-platform, but there are several subtle Windows biases. Windows file paths and environment variables (e.g., `%HOME%`, `D:\home\site\wwwroot\`) are used as primary examples, and the Kudu DebugConsole is referenced with Windows-style paths. FTP upload instructions reference Windows directories. The mention of Azure PowerShell is prominent, and PowerShell samples are linked alongside CLI samples, but no Bash or Linux shell samples are provided. Windows terminology and patterns (such as `%HOME%` and drive letters) appear before Linux equivalents, and screenshots and examples are Windows-centric.
Recommendations
- Provide Linux/macOS equivalents for file paths and environment variables (e.g., `/home/site/wwwroot` instead of `D:\home\site\wwwroot\`).
- Add Bash or Linux shell sample scripts alongside Azure PowerShell samples.
- Clarify that Kudu DebugConsole and FTP can be used from any OS, and show Linux/macOS examples for uploading files.
- When referencing environment variables or paths, mention both Windows and Linux formats.
- Ensure screenshots and instructions are not Windows-exclusive, or provide Linux screenshots where relevant.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there are several areas where Windows-specific tools, paths, and terminology are presented first or exclusively, such as references to Windows directory paths (e.g., D:\home), IIS, Web Deploy/MSDeploy, and legacy Windows build automation (Kudu) being described before Linux equivalents (Oryx). Some settings and examples use Windows conventions or tools without always providing Linux alternatives or parity. Linux-specific information is present but often secondary.
Recommendations
- Ensure Linux paths and conventions are presented alongside Windows examples, not as an afterthought.
- Where Windows tools (e.g., Web Deploy, MSDeploy, IIS) are mentioned, clarify their Linux equivalents or note if not applicable.
- Present Linux build automation (Oryx) and deployment options equally, and not only in secondary tabs.
- Add explicit Linux/macOS examples for environment variable usage, especially where Windows paths or tools are referenced.
- Review tables and descriptions to ensure Linux-specific settings are not buried or omitted.
- Where possible, use neutral language and examples that apply to both platforms, or clearly indicate platform-specificity.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides detailed instructions for enabling diagnostic logging on Azure Application Gateway, but the only CLI example given is for PowerShell. There are no equivalent examples for Azure CLI (cross-platform) or Bash, and PowerShell is a Windows-centric tool. Additionally, references to log conversion tools are focused on Visual Studio and C#, which are more common in Windows environments. The documentation does not mention or demonstrate Linux/macOS-compatible workflows for enabling logging or analyzing logs.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash script examples or note that Azure CLI commands can be run in Bash shells.
- Mention and link to log conversion tools or scripts that do not require Visual Studio or C#, such as Python or jq-based solutions.
- Ensure that references to analysis tools (e.g., Power BI, Excel) are balanced with alternatives available on Linux/macOS, such as Grafana or open-source visualization tools.
- Explicitly state that PowerShell examples are for Windows, and provide parity for Linux/macOS users.
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 backend settings. However, there are subtle Windows biases: troubleshooting guidance for Dedicated Backend Connections references Kerberos and NTLM authentication, with links to Windows-specific documentation and IIS configuration. Windows authentication mechanisms are mentioned without Linux equivalents (such as SPNEGO or GSSAPI). Additionally, Windows tools and patterns (IIS, Windows Authentication) are referenced first or exclusively in troubleshooting, creating friction for Linux users managing cross-platform backends.
Recommendations
- Include troubleshooting guidance for Linux-based authentication mechanisms (e.g., SPNEGO, GSSAPI, Samba, Apache mod_auth_kerb) alongside NTLM/Kerberos.
- Add links to Linux documentation for Kerberos configuration and authentication (e.g., MIT Kerberos, Samba, Apache).
- Clarify that backend authentication can be implemented on both Windows and Linux, and provide examples or references for both.
- When referencing backend server logs or authentication, mention common Linux web servers (Apache, Nginx) and their log locations/configuration.
- Avoid referencing IIS or Windows Authentication exclusively; provide parity for Linux environments.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always present and often shown immediately after CLI. Helm installation instructions are given for both Windows and Linux, but Windows is listed first. For Azure CLI, Linux-specific shell examples (e.g., Bash) are not explicitly shown, even though the CLI commands are cross-platform. There are no macOS-specific instructions or examples. Some steps (e.g., managed identity creation, AKS cluster setup) only show CLI and PowerShell, omitting Bash or Linux-native scripting. The use of PowerShell is heavy, and Windows is often mentioned or shown first.
Recommendations
- Provide explicit Bash/Linux shell examples for Azure CLI steps, especially where scripting or environment variables are used.
- Add macOS installation instructions for Helm, or clarify that Linux instructions apply to macOS.
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Where PowerShell is used, offer Bash equivalents for Linux users (e.g., for scripting resource setup).
- Clarify that Azure CLI commands can be run on Linux/macOS, and provide sample Bash scripts for complex steps.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exclusively demonstrates the scenario using a SQL Server VM running on Windows Server and instructs users to connect using SQL Server Management Studio (a Windows-only tool). There are no examples or guidance for deploying a Linux-based SQL Server VM, nor are cross-platform SQL client alternatives mentioned. The instructions and screenshots are Windows-centric, which may create friction for Linux/macOS users attempting similar configurations.
Recommendations
- Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as an alternative to Windows Server.
- Mention and provide examples for connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other open-source SQL clients.
- Where possible, clarify that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, and provide any Linux-specific configuration notes if applicable.
- Add screenshots or CLI instructions that are relevant for Linux/macOS users, or indicate when steps are identical across platforms.
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 migration instructions, examples, and tooling based on PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell examples provided, nor is there guidance for users who prefer or require non-PowerShell workflows. The script installation and usage instructions assume a Windows/PowerShell environment, and PowerShell is mentioned before any alternative tooling (which is not mentioned at all).
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, including configuration and IP retention.
- Add Bash shell examples for script execution and parameter handling, especially for Linux/macOS users.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (which supports both Bash and PowerShell), and provide instructions for both environments.
- Mention cross-platform compatibility of the scripts, or explicitly state any limitations for Linux/macOS users.
- Offer guidance for users who do not have PowerShell installed, including how to use Azure CLI or REST API for migration if possible.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for Azure Application Gateway v2 exhibits moderate Windows bias. Migration and registration/unregistration instructions rely exclusively on Azure PowerShell commands, with no Linux/macOS CLI or Bash equivalents. The 'Next steps' section links to a PowerShell-based tutorial as the primary onboarding path. Azure CLI commands are shown, but the syntax is PowerShell-centric (e.g., Set-AzContext), and no Bash or cross-platform CLI examples are provided. There is no mention of Linux tools or workflows, and Windows tools/patterns are referenced first and exclusively.
Recommendations
- Provide Azure CLI (bash) examples alongside PowerShell for registration, unregistration, and migration tasks.
- Ensure onboarding tutorials include both PowerShell and Azure CLI/Bash workflows.
- Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
- Add links or sections specifically for Linux/macOS users, ensuring parity in guidance.
- Review all command snippets and ensure they are not Windows-centric unless the feature is Windows-only.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation repeatedly references Azure PowerShell scripts as the primary or sole migration tooling, without mentioning Azure CLI or providing Bash/Linux/macOS-compatible examples. There are no Linux/macOS-specific instructions or parity for non-Windows users, and PowerShell is assumed as the default automation tool.
Recommendations
- Provide equivalent Azure CLI commands or scripts for migration tasks, or explicitly state if Azure CLI is not supported.
- Clarify whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide guidance for non-Windows users.
- Add Bash or shell script examples where appropriate, or link to documentation for Linux/macOS environments.
- Explicitly mention any limitations or requirements for running the migration scripts on non-Windows platforms.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides configuration examples for both Azure PowerShell and Azure CLI, but PowerShell is presented first and in more detail, with additional command references. The 'Next steps' section directs users to a PowerShell-specific guide, and there is no mention of Linux-native tools or OpenSSL for certificate management. There are no explicit Linux/macOS-specific examples or guidance, and the CLI section is less detailed.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Provide equal detail and command references for Azure CLI as for PowerShell.
- Include guidance or links for certificate extraction and management using cross-platform tools like OpenSSL.
- In the 'Next steps' section, link to both PowerShell and CLI-based configuration guides, or provide a unified guide with both sets of instructions.
- Explicitly state that all features are available via Azure CLI on Linux/macOS, and clarify any platform-specific limitations if they exist.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash/CLI alternatives or Linux/macOS-compatible workflows. All code samples and instructions assume a Windows environment, creating friction for Linux/macOS users who may not have access to PowerShell or the Windows certificate tools.
Recommendations
- Provide equivalent Azure CLI (az) commands for each step, especially for resource creation and management.
- Include instructions for generating self-signed certificates using cross-platform tools (e.g., OpenSSL) for Linux/macOS users.
- Mention that Azure PowerShell can be installed on Linux/macOS, and provide guidance for doing so.
- Where possible, offer Bash or shell script examples alongside PowerShell.
- Clarify which steps are Windows-specific and offer alternatives or links for Linux/macOS users.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for Azure Automation disaster recovery is heavily focused on PowerShell scripts and workflows for asset migration, with no equivalent examples or guidance for Linux-native tools or scripting languages (e.g., Bash, Python). All migration instructions and runbook examples are PowerShell-based, and there is no mention of alternatives for Linux users. While the page states support for both Linux and Windows VMs, the practical guidance is Windows-centric.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or clarify if PowerShell Core (cross-platform) is supported and provide explicit instructions for Linux/macOS environments.
- Add examples and instructions for importing and executing runbooks using Linux tools or Azure CLI.
- Mention PowerShell Core compatibility and any prerequisites for Linux users (e.g., installation steps for PowerShell on Linux).
- Include guidance for Linux users on managing Automation accounts and assets, especially for hybrid worker scenarios.
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 all major configuration steps, with REST API alternatives, but does not offer Azure CLI or bash examples. PowerShell is presented as the primary scripting interface, and Linux/macOS users are not shown equivalent command-line workflows. The only mention of Azure CLI is in the context of revoking access, and even there, no CLI example is provided.
Recommendations
- Add Azure CLI examples for all major steps (e.g., assigning managed identity, configuring Key Vault access policy, updating Automation account encryption).
- Where PowerShell is used, provide equivalent bash/CLI commands, or at least reference how Linux/macOS users can accomplish the same tasks.
- Clarify that PowerShell examples can be run cross-platform using PowerShell Core, if applicable, or note any Windows-specific requirements.
- Reorder sections or provide parallel examples so that Linux/macOS users do not feel secondary to Windows users.
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 only PowerShell examples for configuring public network access flags, with no equivalent CLI, Bash, or Azure CLI examples. The State Configuration scenario is described as PowerShell DSC-focused, and Windows terminology (PowerShell, DSC) is used before mentioning Linux. While Linux is referenced in the context of Update Management and Log Analytics agent support, actionable configuration examples and instructions are Windows/PowerShell-centric.
Recommendations
- Add Azure CLI and/or Bash examples alongside PowerShell for tasks such as setting publicNetworkAccess.
- Explicitly document Linux/macOS-compatible workflows for configuring Automation account network settings.
- In the State Configuration section, clarify how Linux nodes can be managed, and provide examples or references for Linux DSC equivalents.
- Where PowerShell is referenced, add a note or link to cross-platform alternatives (e.g., Azure CLI, REST API).
- Ensure screenshots and portal instructions are not Windows-specific (they appear neutral here, but review for any subtle bias).
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows registry/PowerShell tools and cmdlets are referenced more frequently and often first. Several backup and data management examples rely exclusively on Windows PowerShell cmdlets, with no equivalent Azure CLI, Bash, or cross-platform alternatives provided. Linux guidance is present but less detailed, and Linux users may need to infer or research equivalent steps.
Recommendations
- Add Azure CLI or REST API examples for tasks currently only documented with Windows PowerShell cmdlets, such as exporting runbooks and DSC configurations.
- When referencing platform-specific steps, present Linux and Windows guidance with equal prominence and detail.
- Provide Bash or shell script examples for Linux users where PowerShell cmdlets are used for Windows.
- Clarify when a feature or cmdlet is Windows-only, and suggest cross-platform alternatives if available.
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 exclusively uses Windows PowerShell examples and references Windows-specific PowerShell modules and cmdlets. There are no examples or guidance for Linux/macOS users, such as Bash, Azure CLI, or cross-platform scripting. The focus on PowerShell and Windows tools creates friction for users on non-Windows platforms.
Recommendations
- Add Azure CLI examples for credential asset creation and runbook authentication, which are cross-platform.
- Clarify whether PowerShell Core (pwsh) is supported in Azure Automation and provide examples if so.
- Mention that Azure Automation runbooks can be authored in Python and provide equivalent Python examples where possible.
- Explicitly note any limitations or requirements for Windows PowerShell vs. PowerShell Core, especially for Linux/macOS users.
- Provide links or references to Linux/macOS-specific guidance for Azure Automation authentication.
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 is heavily focused on PowerShell, with nearly all code examples, parameter handling, and automation workflows demonstrated using PowerShell or PowerShell Workflow. Windows tools and patterns (such as PowerShell cmdlets and .NET types) are referenced throughout, and examples for starting and passing parameters to runbooks are almost exclusively shown with PowerShell. Linux/macOS users are not provided with equivalent Bash, CLI, or Python examples for parameter assignment, nor are cross-platform alternatives discussed. The Python section is brief and lacks practical parameter assignment examples. The ordering of sections and examples consistently puts Windows/PowerShell first.
Recommendations
- Add Azure CLI examples for starting runbooks and assigning parameters, demonstrating cross-platform usage.
- Expand the Python runbook section with concrete examples of parameter assignment and invocation from Linux/macOS environments.
- Include Bash shell examples for calling the REST API to start runbooks and pass parameters, showing how Linux/macOS users can automate these tasks.
- Clarify which features are PowerShell-specific and which are cross-platform, and provide guidance for Linux/macOS users where possible.
- Consider reordering sections or providing parallel examples (PowerShell and CLI/Bash/Python) 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_first
windows_tools
missing_linux_example
Summary
The documentation is heavily focused on PowerShell modules and Windows-centric workflows, with most examples, tools, and instructions tailored to Windows environments. Internal cmdlets and features are explicitly unavailable on Linux Hybrid Runbook Workers, and Linux-specific guidance is minimal or absent. Python module support is mentioned but not detailed, and there are no Linux shell or cross-platform examples for module management. The documentation assumes familiarity with Windows/PowerShell tools and patterns, creating friction for Linux/macOS users.
Recommendations
- Add explicit guidance and examples for managing modules on Linux Hybrid Runbook Workers, including any limitations or alternative workflows.
- Provide parity for module import, update, and deletion using Linux-compatible tools (e.g., Azure CLI, REST API) and shell examples.
- Clarify which features are Windows-only and offer Linux alternatives or workarounds where possible.
- Expand the Python module section to include more details and cross-platform examples.
- Include a summary table of feature availability by OS (Windows, Linux, macOS) for clarity.
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, with all CLI instructions and code samples provided exclusively in PowerShell. There are no Bash, Linux CLI, or cross-platform shell examples for certificate management tasks. PowerShell is presented first and as the primary method, with Python examples included only for runbook scripting, not for certificate management operations. There is no mention of Linux-native tools or workflows for certificate handling in Azure Automation.
Recommendations
- Add Bash or Azure CLI examples for certificate management tasks, such as uploading and retrieving certificates.
- Clarify whether PowerShell cmdlets can be used cross-platform (on Linux/macOS) or if they are Windows-only, and provide alternatives if needed.
- Include guidance for Linux/macOS users on preparing and uploading certificates, including any OS-specific requirements or limitations.
- Present PowerShell and Python examples side-by-side, rather than PowerShell-first, to improve parity.
- Mention any limitations or differences for Linux/macOS users in Azure Automation certificate handling.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tooling. All CLI examples are in PowerShell, and references to credential objects and cmdlets are specific to Windows/PowerShell environments. The creation of credentials via CLI is only shown using Windows PowerShell, with no mention of Bash, Azure CLI, or Linux-native alternatives. The Python section is present, but only for runbooks, not for asset management or credential creation. Windows/PowerShell tools and patterns are mentioned first and exclusively in several sections.
Recommendations
- Add Azure CLI examples for credential asset management, if supported.
- Clarify whether credential management is possible via Bash or Linux shell scripts, and provide examples if so.
- Explicitly state platform limitations if credential management is only possible via PowerShell.
- Where possible, provide parity in examples for Linux/macOS users, such as using Azure CLI or REST API.
- Add a note about cross-platform support and limitations for credential management in Azure Automation.
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
windows_tools
missing_linux_example
Summary
The documentation covers both Windows and Linux platforms for Azure Change Tracking and Inventory, but several sections display Windows bias. Windows registry tracking is described in detail, with no equivalent Linux configuration file or daemon tracking examples. Windows terminology and tools (registry keys, Windows services) are mentioned exclusively or before Linux equivalents. There are no Linux-specific examples for tracking system changes, such as monitoring /etc files or Linux service changes. The file tracking and inventory features are described as cross-platform, but practical examples and screenshots are Windows-centric.
Recommendations
- Add examples of Linux-specific change tracking, such as monitoring changes to /etc/passwd, /etc/ssh/sshd_config, or systemd service files.
- Include a table or section for Linux daemon/service monitoring, similar to the Windows registry key table.
- Provide screenshots or walkthroughs showing Linux file change tracking and inventory features.
- Clarify parity between Windows and Linux features, explicitly stating which features are available on each platform.
- Mention Linux tools and terminology (e.g., systemd, init.d, configuration files) alongside Windows tools.
Azure Functions
Quickstart: Create a Durable Functions app that uses the MSSQL storage provider
...n/articles/azure-functions/durable/quickstart-mssql.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section on setting up a local SQL Server instance. PowerShell commands are used exclusively for Docker setup, and Windows tools like SQL Server Express are mentioned before Linux alternatives. No explicit Linux/macOS shell (bash) examples are provided for database setup, and troubleshooting steps reference Windows-centric paths and tools. While Docker is cross-platform, the instructions and examples are tailored toward Windows users, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent bash/zsh shell commands for Docker setup and SQL Server initialization, alongside PowerShell examples.
- Mention Linux-native SQL Server installation options (e.g., apt/yum install for SQL Server tools) and clarify how to run Docker commands on Linux/macOS.
- List Linux/macOS tools (such as Azure Data Studio, sqlcmd, or VS Code extensions) equally with Windows tools for database management.
- Ensure troubleshooting steps reference Linux/macOS file paths and common issues.
- Consider showing bash examples first or side-by-side with PowerShell to signal 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 cross-platform and does not focus on Windows-specific features. However, there is a minor bias in the 'Related content' section, where a PowerShell-based guide is linked for connecting virtual networks, and no equivalent CLI/Bash or Linux-native example is provided. Additionally, PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- In the 'Related content' section, add links to equivalent guides using Azure CLI (az) or Bash scripts for connecting virtual networks, ensuring Linux/macOS users have clear, native instructions.
- When referencing PowerShell-based operations, also mention or link to cross-platform alternatives (e.g., Azure CLI, REST API, or ARM templates) where available.
- Review other linked articles to ensure that Linux/macOS users are not forced to use Windows tools for critical operations.
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 troubleshooting guide provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented after the Linux example (using grep). The rest of the documentation uses cross-platform tools (kubectl, helm) and does not show significant Windows bias. However, the presence of explicit Windows/PowerShell command examples and tabs, even though parity is maintained, indicates a minor bias towards Windows users.
Recommendations
- Ensure Linux and Windows examples are always presented together, with equal prominence.
- Consider using cross-platform tools or commands where possible, and clarify any OS-specific differences.
- If possible, provide macOS-specific notes or examples, as macOS users may also be present.
- Review the order of examples to avoid always showing Windows second; alternate order or show both at once.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides a balanced overview of running C# Azure Functions in an isolated worker process, with clear support for both Windows and Linux environments. However, there are minor signs of Windows bias: Windows-specific tools (Visual Studio, PowerShell) are often mentioned before Linux equivalents (VS Code, Azure CLI), and some CLI examples default to Windows syntax. Azure PowerShell is listed as a deployment option alongside Azure CLI, but Linux-specific guidance is present and not missing. All critical tasks (creation, deployment, configuration, debugging) are documented for both platforms.
Recommendations
- Where multiple tools are listed (e.g., Visual Studio, VS Code, Azure CLI, Azure PowerShell), alternate the order or explicitly note Linux/macOS support for each.
- Ensure that CLI examples are shown for both Windows (PowerShell) and Linux (bash) where relevant, especially in deployment and configuration sections.
- Highlight Linux/macOS parity in introductory sections to reassure cross-platform users.
- Consider adding explicit 'Linux/macOS' tabs or callouts in sections where Windows tools are referenced, to guide non-Windows users.
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 Azure CLI examples for both Bash and PowerShell, but PowerShell syntax is consistently shown alongside Bash, sometimes immediately after Bash. Notes clarify that Azure CLI commands can run in PowerShell or Bash, but PowerShell examples are always present, and Bash is not always shown first. No Linux-specific tools or patterns are mentioned, and Visual Studio Code is the recommended editor, which is cross-platform. There are no Windows-only tools or instructions, but the frequent inclusion of PowerShell syntax and occasional 'Windows-first' ordering may create minor friction for Linux/macOS users.
Recommendations
- Show Bash examples first when presenting Azure CLI commands, as Bash is the default shell on Linux/macOS.
- Where possible, clarify that Visual Studio Code and Azure CLI are fully cross-platform.
- Consider grouping Bash and PowerShell examples under clearly labeled tabs or sections, rather than interleaving them.
- Explicitly mention Linux/macOS compatibility in prerequisites and instructions.
- Add a brief note that all steps are applicable on Linux/macOS unless otherwise stated.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are given alongside Bash for every CLI step, and in some cases, PowerShell syntax is shown first or is labeled as 'Formatted for PowerShell', which may subtly prioritize Windows users. There is no explicit Linux bias, but the presence of PowerShell examples throughout may create a perception of Windows preference.
Recommendations
- Clearly label Bash and PowerShell examples, and ensure Bash (Linux/macOS) examples are shown first where possible.
- Add a note clarifying that Bash examples are suitable for Linux/macOS terminals, while PowerShell is for Windows.
- Consider grouping Bash and PowerShell examples under separate tabs for clarity.
- Ensure variable naming and syntax are consistent and correct for each shell.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is mentioned alongside CLI throughout and receives equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is presented as a primary option, and the page includes a custom tag 'devx-track-azurepowershell'. However, Linux users are fully supported via Azure CLI, and all critical steps have CLI equivalents.
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 primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users about using Azure CLI in their environments.
- Ensure that any referenced prerequisites or setup instructions for Azure PowerShell also mention CLI alternatives for Linux/macOS.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides instructions primarily through the Azure portal and Azure CLI, with a brief mention of Azure PowerShell as an alternative tool for disabling regional gateways. The PowerShell cmdlet is referenced after the CLI example and is not the sole method shown. No Windows-specific tools or patterns are prioritized, and Linux parity is generally maintained. However, the PowerShell reference appears before any mention of Linux shell scripting, and there are no explicit Bash or Linux shell examples, which could be improved for parity.
Recommendations
- When referencing Azure PowerShell, also mention Bash or Linux shell alternatives explicitly, such as Azure CLI usage in Bash.
- Provide example CLI commands in both Windows (PowerShell) and Linux (Bash) syntax where relevant.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- If scripting is discussed, include sample Bash scripts alongside PowerShell scripts.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides Azure CLI examples for both Bash and PowerShell, with PowerShell (Windows) versions shown alongside Bash. However, PowerShell examples are formatted and labeled explicitly, and in some cases, Windows-style syntax is presented first or equally, which may create friction for Linux/macOS users. No Linux-specific tools or patterns are missing, but the presence of PowerShell examples may suggest a Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples, and ensure Bash (Linux/macOS) examples are shown first or equally prominent.
- Consider providing a single Bash example unless PowerShell syntax differs significantly, or use tabs to separate Bash and PowerShell.
- Add a note clarifying that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows.
- Ensure all CLI commands are cross-platform and avoid Windows-specific syntax unless necessary.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, with PowerShell being presented as a primary option alongside CLI. There is a slight Windows bias in the inclusion and prominence of PowerShell examples and requirements, but Linux parity is maintained through Azure CLI examples. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks.
Recommendations
- Ensure Azure CLI examples are always presented first, as CLI is cross-platform.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation guides for non-Windows platforms.
- Consider adding a note clarifying that all steps can be completed on Linux/macOS using Azure CLI or PowerShell Core.
- If possible, add Bash script examples for template deployment to further reinforce Linux parity.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. Both tools are cross-platform, but PowerShell is still more commonly used on Windows. The CLI example is given before PowerShell, but there is no explicit Linux/macOS example or mention of Linux-specific workflows. The documentation does not reference Windows-only tools, but the inclusion of PowerShell may create friction for Linux/macOS users who are less likely to use it.
Recommendations
- Explicitly mention that Azure CLI and PowerShell are both cross-platform, and provide links or notes about installing and using PowerShell on Linux/macOS.
- Add a note clarifying that the Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider adding a Bash shell example for Azure CLI to reinforce Linux parity.
- If PowerShell is included, provide installation instructions or links for Linux/macOS users.
- Ensure that screenshots and portal instructions are not Windows-specific (they currently are not).
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally presents Azure App Service Plans in a cross-platform manner, mentioning both Windows and Linux support. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (e.g., PowerShell, RDP, .NET Framework) are described first and in detail, with Linux explicitly noted as unsupported only at the end. The main documentation otherwise avoids Windows bias.
Recommendations
- In the 'Managed Instance' section, clarify at the beginning that this is a Windows-only feature to avoid confusion for Linux users.
- Where possible, provide parity or alternative guidance for Linux users, or explicitly state when a feature is not available for Linux.
- Ensure that links to plan details and pricing clearly distinguish between Windows and Linux options.
- Consider adding a short comparison table or callout summarizing which features are Windows-only versus cross-platform.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity for Azure CLI, PowerShell, ARM templates, and portal usage. However, PowerShell examples are prominent and often shown alongside or before CLI examples. The PowerShell section is detailed, and some tasks (e.g., assigning user-assigned identity for App Service) are noted as not supported in PowerShell, but alternatives are given. There is a slight bias in favor of PowerShell, which is more commonly used on Windows, and PowerShell is listed as a separate tab for token retrieval, even though the CLI and HTTP methods are cross-platform. The ordering of examples sometimes puts PowerShell before CLI, and PowerShell is referenced in code blocks for Azure CLI (likely a documentation error). However, Linux/macOS users can complete all tasks using Azure CLI, ARM templates, or HTTP requests.
Recommendations
- Ensure Azure CLI examples are always present and shown before or alongside PowerShell examples, as CLI is cross-platform.
- Correct any code block labeling errors (e.g., Azure CLI sections labeled as 'azurepowershell-interactive').
- Explicitly mention that Azure CLI works on Linux/macOS and is recommended for cross-platform scenarios.
- Add brief notes to PowerShell sections indicating that PowerShell Core is available for Linux/macOS, or link to CLI alternatives.
- Review the ordering of tabs to avoid implicit prioritization of Windows tools.
Low 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 (PowerShell), and terminology are often presented first or in greater detail. PowerShell commands are given alongside Bash/Azure CLI, but Windows-centric concepts (like IIS, .NET Framework, C:\home, Windows Server images) are described in depth, sometimes before Linux equivalents. Some sections (e.g., parent images, persistent storage) focus heavily on Windows before Linux, and troubleshooting/logging references Windows paths and tools. Linux parity is generally good, but Windows bias is evident in ordering and example prominence.
Recommendations
- Ensure Linux examples and terminology are presented with equal prominence and detail as Windows sections.
- Where possible, alternate the order of Windows and Linux pivots or provide a neutral introduction before splitting into OS-specific guidance.
- Expand Linux-specific troubleshooting, logging, and persistent storage details to match Windows depth.
- Avoid referencing Windows tools (e.g., PowerShell, IIS) in general sections unless a Linux equivalent is also provided.
- Review section ordering to avoid Windows-first bias, especially in shared guidance (e.g., parent images, environment variables, persistent storage).
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 for most steps, but PowerShell is featured alongside CLI in nearly every section, and in some cases, CLI and PowerShell are presented as equal tabs. PowerShell is a Windows-centric tool, and its inclusion throughout may signal a Windows bias. Additionally, PowerShell examples are sometimes shown before or as prominently as CLI, which is more cross-platform. However, all critical steps are covered with Azure CLI (which works on Linux/macOS), and kubectl is used for Kubernetes verification, so Linux/macOS users are not blocked.
Recommendations
- Consider marking Azure PowerShell examples as specifically for Windows users, and Azure CLI as the default/cross-platform option.
- Present Azure CLI examples first in all sections, with PowerShell as an optional tab for Windows users.
- Clarify that Azure CLI is recommended for Linux/macOS users.
- Review PowerShell-heavy sections to ensure CLI parity and that CLI commands are always present.
- If possible, add bash shell scripting examples for advanced scenarios.
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 setting instructions for Windows (cmd, PowerShell) before Linux/macOS (bash), and uses Windows terminology like 'command prompt' as the default. However, Linux/macOS equivalents are present and the Maven build/run instructions are cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows instructions, rather than after.
- Use neutral terminology such as 'terminal' instead of 'command prompt' to avoid implying Windows as the default.
- Explicitly state that Maven commands work on all platforms, and clarify any platform-specific steps.
- Consider grouping environment variable instructions by OS in a table or list for clarity.
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 Windows-specific commands (setx, PowerShell) with detailed restart instructions. Linux/macOS instructions are present and correct, but are listed after Windows examples. The use of Visual Studio Code is explicitly cross-platform. Build and run instructions use Maven, which is cross-platform. The curl example uses Windows cmd syntax, but is generic.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before or alongside Windows examples, rather than after.
- Clarify that all commands are cross-platform where applicable, and avoid implying Windows is the default.
- Provide curl examples using bash syntax (e.g., $ curl ...) or clarify that curl is available on all platforms.
- Consider grouping environment variable instructions by platform, or using tabs for Windows, macOS, and Linux.
- Explicitly mention that Maven commands work on all platforms.
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 both Azure Cloud Shell and local installation, it refers to 'Windows PowerShell' as the example for a local console, and the PowerShell section exclusively uses Windows PowerShell. The PowerShell instructions are presented as a separate tab, and the CLI tab mentions Windows PowerShell first when discussing local consoles. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there guidance for running PowerShell on non-Windows platforms, despite PowerShell Core being cross-platform.
Recommendations
- In CLI instructions, mention Bash or other common Linux/macOS shells alongside Windows PowerShell.
- Clarify that Azure CLI works on Bash, zsh, and other shells on Linux/macOS, not just Windows PowerShell.
- In PowerShell instructions, specify that PowerShell Core (pwsh) is available cross-platform, and provide examples for both Windows PowerShell and PowerShell Core.
- Add explicit notes or examples for Linux/macOS users where relevant, such as launching Azure CLI in Bash/zsh.
- Ensure screenshots and step-by-step instructions are not Windows-centric unless the feature is Windows-only.
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), but includes all platforms. No Windows-only tools or PowerShell-heavy examples are present. All code and build instructions are cross-platform (Java, Maven).
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group them equally.
- Explicitly state that all commands work on Windows, Linux, and macOS to reinforce parity.
- Consider adding a note that Maven and Java are cross-platform and supported on all major OSes.
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 (setx and PowerShell) before Linux/macOS (export), and includes explicit PowerShell examples. However, Linux/macOS instructions are present and the overall tutorial is cross-platform, with Java and Maven usage and Azure CLI commands.
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 for all platforms.
- Clarify that all steps can be performed on Linux/macOS, and highlight cross-platform tools (e.g., Azure CLI, Maven).
- Reduce emphasis on Windows-specific tools unless required, and ensure parity in example ordering.
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 are no explicit Linux/macOS-specific instructions or clarifications, and PowerShell is presented as a primary option alongside CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider listing Azure CLI examples first, or explicitly note that PowerShell is Windows-centric.
- Add a brief note for Linux/macOS users recommending Azure CLI and linking to installation instructions.
- If possible, provide bash shell or script examples for common tasks.
- Mention that Azure PowerShell can be used on Linux/macOS via PowerShell Core, but CLI is generally simpler.
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, the PowerShell section appears before the CLI section, and PowerShell is a Windows-centric tool (though available on Linux/macOS). There are no Linux/macOS-specific shell examples (e.g., Bash), but the CLI examples are cross-platform. The portal instructions are also platform-agnostic. There is a minor bias in presenting PowerShell before CLI, which may imply Windows-first thinking, but Linux users can complete all tasks using Azure CLI or portal.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more universally available across platforms.
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and PowerShell is available cross-platform but is more familiar to Windows users.
- Consider adding Bash script examples for common tasks, or clarify that Azure CLI commands can be run in Bash or other shells.
- Add a short statement at the start of scripting sections indicating that both CLI and PowerShell are supported on all major OSes, but CLI is typically preferred for Linux/macOS users.
Azure Functions
App settings reference for Azure Functions
...ain/articles/azure-functions/functions-app-settings.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides a comprehensive reference for Azure Functions app settings, covering both Windows and Linux environments. However, there are minor signs of Windows bias: Windows-specific examples (such as environment variable delimiters and sample paths) are sometimes presented first or exclusively, PowerShell settings are detailed, and Windows tools (Azure PowerShell) are mentioned alongside Azure CLI for managing settings. Linux equivalents are generally present, but Windows terminology or examples appear more frequently or are prioritized in some sections.
Recommendations
- Ensure all examples (e.g., environment variable syntax, file paths) are shown for both Windows and Linux, or clarify OS-specific differences.
- Where Windows tools (PowerShell) are mentioned, ensure Azure CLI or Linux-native alternatives are equally highlighted and placed before or alongside Windows tools.
- Review sample values and code snippets to provide Linux/macOS equivalents where applicable (e.g., paths, environment variable formats).
- Consider alternating the order of Windows and Linux examples to avoid implicit prioritization.
- Explicitly state OS applicability for settings that differ between Windows and Linux (e.g., WEBSITE_TIME_ZONE).