251
Pages Scanned
48
Pages Flagged
251
Changed Pages
19.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:30
Scan Information
Started At: 2026-02-14 00:00:30
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 251
Files Completed: 251
Problematic Pages
49 issues found
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation with New-SelfSignedCertificate and Export-PfxCertificate, which are Windows-only tools. No Bash, Azure CLI, or Linux/macOS-compatible instructions are provided, and Windows-specific file paths (e.g., c:\appgwcert.pfx) are used throughout. The documentation assumes a Windows environment and does not mention alternatives for Linux/macOS users.
Recommendations
- Provide Azure CLI equivalents for all steps, especially resource creation and configuration.
- For certificate creation, include instructions using OpenSSL (cross-platform) alongside New-SelfSignedCertificate.
- Use generic file paths or note differences for Linux/macOS (e.g., /tmp/appgwcert.pfx).
- Add a section or callout for Linux/macOS users, clarifying how to adapt the tutorial.
- Link to cross-platform documentation where possible.
Create Pull Request
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity for Azure CLI, PowerShell, ARM templates, and portal instructions for managing identities in Azure App Service and Functions. However, PowerShell examples are prominent and often shown alongside or before CLI examples, and PowerShell is referenced in a way that may imply Windows environments. There are no explicit Linux/macOS-specific instructions or clarifications, and PowerShell is not flagged as cross-platform. Azure CLI is available on all platforms, but PowerShell instructions may create friction for Linux/macOS users unfamiliar with it.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or link to installation instructions for Linux/macOS.
- Ensure Azure CLI examples are shown first or equally with PowerShell, as CLI is more commonly used on Linux/macOS.
- Add explicit notes or links for Linux/macOS users, e.g., 'Azure CLI works on Linux/macOS; see installation instructions.'
- Where PowerShell is used, note that Bash or shell scripting alternatives exist for Linux/macOS.
- Consider adding Bash shell script examples for token retrieval, especially in sections where only PowerShell is shown.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation consistently references Azure PowerShell scripts as the primary or only migration tooling, without mentioning Azure CLI or Bash alternatives. All migration automation examples and scripts are PowerShell-based, and there are no Linux/macOS-specific instructions or parity examples. This creates friction for users on non-Windows platforms.
Recommendations
- Provide Azure CLI (az) or Bash script equivalents for migration steps currently described with PowerShell.
- Explicitly state whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation guidance if so.
- Add examples or links for Linux/macOS users, including any prerequisites or environment considerations.
- If PowerShell is required, clarify this early and suggest supported ways for Linux/macOS users to run the scripts.
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 heavily focuses on Windows-specific tools and workflows, especially SignTool, with all installation and usage instructions tailored for Windows environments. PowerShell commands and Windows Package Manager (winget) are used exclusively for setup. There are no Linux/macOS equivalents or guidance for cross-platform users, even though some integrations (like GitHub Actions, Azure DevOps, and SDK) could be relevant for non-Windows environments.
Recommendations
- Add explicit guidance for Linux/macOS users, including supported signing tools and setup instructions.
- Provide cross-platform examples for Artifact Signing SDK usage, including sample commands for Linux/macOS.
- Clarify which integrations (e.g., GitHub Actions, Azure DevOps tasks, SDK) are cross-platform and provide platform-specific instructions.
- If SignTool is Windows-only, state this clearly and direct Linux/macOS users to alternative signing methods.
- Include installation instructions for .NET 8.0 Runtime and Artifact Signing dlib package on Linux/macOS, if supported.
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 page is heavily focused on PowerShell modules and Windows-centric workflows, with almost all examples, tools, and instructions centered around PowerShell and Windows Automation 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 briefly mentioned, but no Linux-native module management or examples are provided.
Recommendations
- Add explicit guidance and examples for managing modules on Linux Hybrid Runbook Workers, including any limitations and supported workflows.
- Provide parity in module import, update, and deletion instructions for Linux environments, including CLI or scripting alternatives where PowerShell is not available.
- Include Linux-specific troubleshooting, best practices, and known issues for module management in Azure Automation.
- Expand documentation for Python modules and other non-PowerShell runtimes, including how to manage them on Linux Hybrid Runbook Workers.
- Clearly indicate which features are Windows-only and offer alternative approaches for Linux users where possible.
Automation
Manage credentials in Azure Automation
...in/articles/automation/shared-resources/credentials.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with all CLI examples using PowerShell cmdlets and objects (PSCredential). The creation and management of credentials outside the portal is only shown with Windows PowerShell. There is no mention of Linux-native CLI tools (e.g., Bash, Azure CLI) or cross-platform scripting approaches for credential management. While Python runbook usage is covered, all asset management examples outside the portal are Windows/PowerShell-only.
Recommendations
- Add Azure CLI examples for credential asset creation and management, if supported.
- Clarify whether credential management via CLI is possible on Linux/macOS, and provide relevant instructions.
- If PowerShell Core (pwsh) is supported cross-platform, note this explicitly and provide examples for non-Windows environments.
- Consider including Bash or other scripting examples for credential retrieval and usage, where applicable.
- Explicitly state any platform limitations for credential management features.
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 examples for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI-based examples are exclusively in Azure PowerShell, with no mention of Azure CLI or Bash scripting, which are cross-platform and preferred on Linux/macOS. Additionally, PowerShell instructions are presented before ARM template examples, and there is no guidance for Linux/macOS users on equivalent commands or tools.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks (creating resource groups, API Management instances, assigning identities, updating instances).
- Explicitly mention that Azure CLI is cross-platform and provide links to Azure CLI installation and usage guides.
- Where possible, show Bash scripting examples for automation.
- Consider presenting Azure CLI and PowerShell examples together, or alternate their order to avoid Windows-first bias.
- Clarify that PowerShell can be used on Linux/macOS, but Azure CLI is often preferred for those platforms.
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 described in detail and shown first, with C# and Java examples for Windows. Linux guidance is less prominent, with Linux-specific code examples only for C# and no explicit examples for Node.js, PHP, Python, or Java. Windows tools and patterns (certificate store, environment variables, user profile loading) are discussed more thoroughly, and Linux instructions are often deferred to external language/platform documentation.
Recommendations
- Add explicit Linux code examples for Node.js, PHP, Python, and Java, showing how to load certificates from the Linux file paths provided.
- Present Linux and Windows guidance in parallel sections or tabs, rather than Windows-first.
- Expand Linux-specific instructions to match the detail given for Windows, including environment variable usage and certificate file handling.
- Clarify any differences in certificate handling between Linux and Windows, especially for containerized workloads.
- Where possible, avoid referring Linux users to external documentation; provide at least basic sample code inline.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC assignment, but PowerShell is featured equally and referenced in several places. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned for exporting certificates, while Linux tools (OpenSSL) are also included. However, Windows tools are referenced before Linux equivalents in some sections, and PowerShell is given equal prominence to Azure CLI. There are links to Windows Server documentation for certificate export, but no explicit Linux/macOS export guidance. Overall, the bias is moderate, with Windows tools and patterns mentioned alongside but sometimes before Linux equivalents.
Recommendations
- Add explicit Linux/macOS guidance for exporting certificates (e.g., OpenSSL usage for certificate requests and exports).
- Ensure Linux/OpenSSL instructions are presented before or alongside Windows/IIS/Certreq.exe instructions, not after.
- Where PowerShell is used, always provide Azure CLI equivalents and highlight cross-platform options.
- Link to Linux/macOS documentation for certificate management/export, not just Windows Server docs.
- Clarify that Azure CLI is cross-platform and encourage its use for non-Windows users.
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, supporting both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths (e.g., 'D:\home'), tools (e.g., msbuild, Web Deploy/MSDeploy), and IIS-related settings are often mentioned first or exclusively. Windows terminology and examples (such as `%HOME%` and `.dll` extensions) appear before or instead of Linux equivalents. While Linux-specific variables and sections exist (e.g., Oryx build automation, Linux container settings), Windows settings and tools are more prominently described, and Linux examples are sometimes missing or less detailed.
Recommendations
- Ensure Linux paths and equivalents are mentioned alongside Windows paths in all examples and tables.
- Provide Linux-specific examples and explanations where Windows tools (e.g., msbuild, Web Deploy) are referenced.
- Balance the order of presentation so Linux and Windows are treated equally (e.g., list both '/home' and 'D:\home' for HOME variable).
- Expand Linux build automation (Oryx) documentation to match the detail given for Windows (Kudu).
- Clarify which settings are Windows-only and which are cross-platform, ideally with clear labels or pivots.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent examples for Linux/macOS users (such as Azure CLI or Bash). The PowerShell example is the only command-line method shown, and is presented before any mention of portal-based configuration. There is no mention of Azure CLI or Bash scripting, which are cross-platform and commonly used on Linux/macOS. Additionally, references to log conversion tools are C#/.NET-centric, with no mention of Python or other cross-platform alternatives.
Recommendations
- Add Azure CLI examples for enabling diagnostic logging, alongside the PowerShell example.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide equivalent commands.
- Include references to cross-platform log conversion tools (e.g., Python scripts) or note that the provided C# tool works on any OS with .NET Core.
- Present command-line options in a neutral order (e.g., PowerShell and Azure CLI side-by-side), or lead with the portal method as the most universal.
- Clarify that PowerShell Core is available on Linux/macOS, but Azure CLI is often preferred for cross-platform scripting.
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, there are two notable instances of Windows bias: (1) Troubleshooting guidance for Dedicated Backend Connections refers to Kerberos and NTLM authentication, linking to Windows and IIS documentation, and (2) Windows authentication patterns are mentioned first and exclusively in the troubleshooting section, with no Linux equivalents or guidance for Linux-based authentication systems. There are no PowerShell-heavy examples, missing Linux examples, or CLI bias, but the troubleshooting section assumes Windows-centric backend environments.
Recommendations
- Add troubleshooting guidance for Linux-based authentication systems (e.g., SPN configuration for Samba, Kerberos on Linux, or other common Linux web servers).
- Include links to Linux authentication documentation (such as Apache, NGINX, or generic Kerberos guides) alongside Windows/IIS references.
- Clarify that the troubleshooting steps for NTLM/Kerberos are relevant only if the backend is Windows-based, and provide alternative guidance for Linux backends.
- Where possible, mention Linux authentication patterns or note their applicability in Azure Application Gateway scenarios.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides configuration examples for mutual authentication on Azure Application Gateway primarily using Azure PowerShell, with Azure CLI examples included but less detailed. The 'Next steps' section directs users to a PowerShell-specific guide, and there is no mention of Linux-specific tools or workflows (e.g., Bash scripting, OpenSSL usage for certificate extraction). The ordering and emphasis on PowerShell and the lack of Linux/macOS-specific guidance or parity in examples create friction for non-Windows users.
Recommendations
- Ensure that all configuration examples provided in PowerShell are also provided in Azure CLI, with equal detail and explanation.
- In the 'Next steps' section, include links to both PowerShell and Azure CLI (and/or ARM/Bicep) guides for mutual authentication setup.
- Where certificate extraction or manipulation is discussed, provide cross-platform command-line examples (e.g., using OpenSSL) for Linux/macOS users.
- Explicitly state that all features can be configured using Azure CLI and REST API, and clarify any exceptions.
- Consider the ordering of examples: present CLI and PowerShell examples side-by-side or in parallel tabs, rather than PowerShell first.
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 assumes the use of Windows throughout: it creates a SQL Server VM using a Windows Server image, and the only client tool mentioned for connecting to SQL Server is SQL Server Management Studio (SSMS), which is Windows-only. There are no instructions or examples for deploying a Linux-based SQL Server VM or for connecting from Linux/macOS clients (e.g., using sqlcmd or Azure Data Studio). This creates friction for Linux/macOS users who wish to follow the guide.
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 SQL Server using cross-platform tools such as sqlcmd (available on Linux/macOS) or Azure Data Studio.
- Clarify that the steps are applicable regardless of the SQL Server OS, and highlight any differences if present.
- Add screenshots or command-line examples for Linux/macOS where relevant, especially for the client connection step.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and tooling based on PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all script downloads and usage instructions are PowerShell-centric. This creates friction for Linux/macOS users who may prefer or require Bash or Azure CLI workflows.
Recommendations
- Provide Azure CLI equivalents for all migration steps and scripts, or clearly state if PowerShell is the only supported method.
- Add Bash/Linux shell examples for script execution, especially for users running Azure Cloud Shell in Bash mode.
- Clarify OS requirements for script execution (e.g., if PowerShell Core is required, note its cross-platform support and installation steps for Linux/macOS).
- Offer guidance on using PowerShell Core on Linux/macOS, including installation links and troubleshooting tips.
- If migration scripts are truly PowerShell-only, add a prominent note explaining this limitation and suggest alternatives or workarounds for Linux/macOS users.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for Azure Application Gateway v2 shows notable Windows bias, primarily through the use of PowerShell-based examples and migration scripts, and references to Azure PowerShell tools. Azure CLI commands are also shown, but the registration/unregistration examples use PowerShell cmdlets. The 'Next steps' section links to a PowerShell tutorial first, and the migration script is only available via PowerShell. There is no mention of Bash, Linux, or cross-platform alternatives for these critical operations.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell scripts, especially for migration and registration tasks.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant tutorials.
- Ensure that tutorials and 'Next steps' include both PowerShell and Azure CLI options, with clear labeling for platform compatibility.
- Where possible, avoid referencing PowerShell gallery as the sole source for migration scripts; offer downloadable scripts or CLI alternatives.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell scripts and workflows for migration tasks, with no mention of Bash, Python, or other cross-platform scripting alternatives. All migration examples and instructions are PowerShell-centric, and the tabs/links for Hybrid Runbook Worker installation default to Windows. There are no Linux-specific examples or guidance for asset migration, and Linux users are implicitly expected to use PowerShell, which may not be native or preferred on Linux/macOS systems.
Recommendations
- Provide equivalent Bash or Python scripts for asset migration, or clarify PowerShell Core (pwsh) compatibility for Linux/macOS users.
- Add explicit instructions or examples for Linux/macOS users, including how to install and use PowerShell Core if required.
- Ensure that links and tabs for Hybrid Runbook Worker installation are balanced, showing both Windows and Linux options equally.
- Mention any limitations or requirements for Linux/macOS users when using PowerShell scripts, such as module compatibility or installation steps.
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 and related tools, with all examples and instructions given in PowerShell. There are no Bash, Python, or Linux/macOS shell examples, nor is there mention of cross-platform alternatives. Windows-specific terminology and tools (e.g., PSCredential, Windows PowerShell modules) are used throughout, and Linux/macOS users are not provided with equivalent guidance.
Recommendations
- Add examples using Azure CLI and/or Python SDK for authentication and credential management, which are cross-platform.
- Clarify which steps are PowerShell-specific and provide Linux/macOS alternatives where possible.
- Mention that Azure Automation runbooks can use Python or other languages, and link to relevant documentation.
- Provide guidance for Linux/macOS users on how to create and manage credential assets via the Azure portal or CLI.
- Reorder sections to avoid always presenting Windows/PowerShell methods first.
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 heavily emphasizes PowerShell and Windows-centric tools and patterns throughout, with nearly all code examples, parameter configuration, and usage scenarios presented in PowerShell or C#. There are no Linux/bash examples for starting runbooks or passing parameters, and PowerShell is consistently presented first and in greater detail. The only mention of Python runbooks is brief and lacks practical examples for Linux/macOS users. The guidance for calling runbooks from a local machine is exclusively PowerShell-based, with no mention of cross-platform alternatives.
Recommendations
- Add examples for starting runbooks and passing parameters using Azure CLI (az), which is cross-platform and works on Linux/macOS.
- Include bash shell examples for calling REST APIs to start runbooks and pass parameters, demonstrating usage from Linux/macOS environments.
- Expand the Python runbook section with concrete examples for parameter handling and invocation from Linux/macOS.
- Clarify which PowerShell instructions are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide guidance for non-Windows users.
- Consider reordering sections so that cross-platform tools (Azure CLI, REST API) are presented alongside or before Windows-specific tools.
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation shows a moderate Windows bias. Windows/PowerShell tools and cmdlets are mentioned first or exclusively in several sections (e.g., DSC node removal, runbook export, DSC configuration export). Linux guidance is present for TLS configuration, but Linux alternatives for PowerShell cmdlets or asset export are missing or less detailed.
Recommendations
- Provide Linux/CLI/REST API equivalents for PowerShell cmdlets where possible (e.g., for unregistering DSC nodes, exporting runbooks, and exporting DSC configurations).
- When referencing PowerShell cmdlets, also mention if and how the same tasks can be performed using Azure CLI, Azure portal, or REST API, especially for Linux/macOS users.
- In tables and step-by-step guides, present Linux and Windows options with equal prominence, not always listing Windows first.
- Add explicit examples or links for Linux users where only Windows/PowerShell guidance is currently given.
Automation
Encryption of secure assets in Azure Automation
...icles/automation/automation-secure-asset-encryption.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides extensive PowerShell-based examples for configuring encryption of secure assets in Azure Automation, with REST API alternatives. There are no examples using Azure CLI, Bash, or cross-platform scripting tools. PowerShell is presented as the primary scripting interface, and Linux/macOS users are not shown equivalent workflows, creating friction for non-Windows users.
Recommendations
- Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Where possible, provide Bash script snippets or guidance for Linux/macOS users.
- Explicitly mention that PowerShell Core (pwsh) is cross-platform if PowerShell is required, and clarify if Windows PowerShell-specific modules are needed.
- Reorder or parallelize examples so that REST API and CLI options are shown alongside PowerShell, not only after.
- Add a note clarifying that all operations can be performed from any OS using REST API or Azure CLI, and link to relevant cross-platform tooling.
Automation
Use Azure Private Link to securely connect networks to Azure Automation
...in/articles/automation/how-to/private-link-security.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, with no equivalent CLI, REST API, or Linux-native example. The State Configuration scenario references PowerShell DSC, which is cross-platform but is often perceived as Windows-centric. The documentation does mention Linux support in the context of Update Management and Log Analytics agents, but practical configuration steps and code samples are Windows/PowerShell-focused.
Recommendations
- Add Azure CLI and/or REST API examples for setting 'publicNetworkAccess', alongside PowerShell.
- Include explicit Linux/macOS command-line examples where relevant, especially for DNS configuration and agent setup.
- Clarify that PowerShell DSC can be used on Linux, and provide links or brief instructions for Linux-based DSC agent installation.
- Where screenshots or portal instructions are given, note any platform-specific differences (if any) for Linux/macOS users.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page heavily features PowerShell cmdlets and examples, with all certificate management tasks (creation, retrieval, deployment) demonstrated using PowerShell. There is no mention of Linux shell (bash) or cross-platform CLI equivalents for certificate management. PowerShell is presented as the primary and default method, with no Linux/macOS-specific guidance or parity for certificate operations outside of Python runbooks.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, removal) alongside PowerShell examples.
- Explicitly state PowerShell Core (pwsh) compatibility and whether examples work on Linux/macOS, or provide Linux-specific instructions if needed.
- Include bash or shell script examples for uploading and managing certificates, or clarify if PowerShell is required for all platforms.
- Mention any limitations or requirements for Linux/macOS users, such as needing PowerShell Core or alternate tools.
- Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside PowerShell.
Azure App Configuration
Monitor Azure App Configuration
...s/azure-app-configuration/monitor-app-configuration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides instructions for monitoring Azure App Configuration using the Azure portal, Azure CLI, and PowerShell. While the Azure CLI section is cross-platform, the PowerShell section is Windows-centric and explicitly references 'Windows PowerShell'. Additionally, in the CLI instructions, Windows PowerShell is mentioned as an example of a command console application before other platforms. No Linux/macOS-specific shell examples (e.g., Bash) are provided, and PowerShell is given a dedicated tab, which may suggest a Windows-first approach.
Recommendations
- In CLI instructions, mention Bash or other Linux/macOS shells alongside Windows PowerShell when referring to command consoles.
- Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and provide example commands in Bash where relevant.
- For PowerShell instructions, note that PowerShell Core is available cross-platform, and provide guidance for Linux/macOS users if applicable.
- Consider adding explicit Bash examples or notes for Linux/macOS users to ensure parity and reduce friction.
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 provides a general overview of Azure Change Tracking and Inventory, mentioning compatibility with both Windows and Linux. However, critical sections such as registry key tracking are exclusively Windows-focused, with no equivalent Linux example or mention of Linux configuration file tracking. Windows registry keys and tools are discussed in detail, while Linux-specific features (such as tracking changes to configuration files or systemd services) are not covered or illustrated. Windows terminology and examples are presented first and in greater depth.
Recommendations
- Add examples and explanations for Linux-specific change tracking, such as monitoring changes to key configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config) or tracking Linux daemon/service changes.
- Include a table or section describing Linux equivalents to Windows registry tracking, such as monitoring changes in /etc, systemd unit files, or other critical system files.
- Provide screenshots or walkthroughs for Linux scenarios, not just Windows.
- Clarify which features are Windows-only and which are cross-platform, to help Linux users understand applicability.
- Ensure parity in documentation depth for Linux and Windows, especially in sections describing tracked objects and configuration.
Azure Functions
Quickstart: Create a Durable Functions app that uses the MSSQL storage provider
...n/articles/azure-functions/durable/quickstart-mssql.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell-based examples for setting up a local SQL Server instance in Docker, and references SQL Server Express as a local development option specifically for Windows. While it mentions that PowerShell can be installed on Linux/macOS and that Docker-based SQL Server is cross-platform, the step-by-step commands and troubleshooting are PowerShell-centric. There are no equivalent Bash or shell script examples for Linux/macOS users, and Windows tools (SQL Server Express) are mentioned before Docker as local options.
Recommendations
- Add Bash/zsh shell script examples for Docker setup and database creation, alongside PowerShell.
- Explicitly mention and provide instructions for using Docker on Linux/macOS, including any OS-specific caveats.
- Clarify that SQL Server Express is Windows-only and recommend Docker as the primary cross-platform local development option.
- Provide troubleshooting steps relevant to Linux/macOS environments (e.g., file permissions, Docker networking).
- Ensure that all CLI commands (e.g., az CLI, sqlcmd) are shown in a way that is OS-agnostic or with clear platform-specific notes.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the Bicep file, with CLI (cross-platform) and PowerShell (Windows-centric) options shown in parallel. There is minor bias in that PowerShell is mentioned alongside CLI throughout, and the metadata includes 'devx-track-azurepowershell', but Linux/macOS users are not excluded and can follow the CLI instructions. No critical sections are Windows-only.
Recommendations
- Ensure Azure CLI examples are shown first in each section, as CLI is cross-platform.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows users.
- Add a note clarifying that all steps can be completed on Linux/macOS using Azure CLI.
- Consider including Bash shell examples for file operations (e.g., copying/uploading files) if relevant.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented after the Linux example (using grep). The rest of the troubleshooting steps and commands are platform-neutral, relying on kubectl and bash syntax, which are standard for Kubernetes environments. There is no exclusive use of Windows tools or missing Linux examples, but Windows is explicitly called out as a separate tab, which may create minor friction for non-Windows users.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence, possibly side-by-side or in a single code block with comments for each platform.
- Clarify that most commands are cross-platform unless otherwise noted.
- Consider adding macOS-specific notes if there are any platform differences.
- Explicitly state that the primary troubleshooting steps are platform-agnostic, and only the log filtering command differs.
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 prioritized. There are no Linux-specific tools or workflows mentioned, but the documentation does not exclusively reference Windows tools. Visual Studio Code is recommended, which is cross-platform, and all CLI instructions are compatible with Linux/macOS. However, PowerShell syntax is given equal prominence to bash throughout, and Windows portal screenshots are used.
Recommendations
- Show bash examples first, with PowerShell as an alternative.
- Explicitly state that all CLI commands work on Linux/macOS and provide any necessary Linux-specific notes (e.g., file path differences, environment setup).
- Include screenshots or instructions for Azure portal access from Linux/macOS (if relevant).
- Where possible, clarify that Visual Studio Code and Azure Functions extension are fully supported on Linux/macOS.
- Consider adding a section or note for Linux/macOS users about any potential differences or tips.
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 for Windows and are presented immediately after the Bash examples. There is no explicit Linux bias, but the presence of PowerShell examples and their placement may suggest a slight Windows-first approach.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell examples are for Windows users.
- Consider labeling the code blocks more explicitly, e.g., 'Bash (Linux/macOS)' and 'PowerShell (Windows)'.
- Ensure Bash examples are presented first, or alternate their order to avoid implicit Windows prioritization.
- Add a note that Azure CLI works cross-platform and that Bash examples are generally preferred for Linux/macOS.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, but PowerShell is mentioned prominently in metadata and examples. Azure PowerShell is a Windows-centric tool, and its requirements are listed alongside Azure CLI. However, both CLI and PowerShell examples are given, and the CLI is cross-platform. There are no Linux-specific instructions or examples, but Linux/macOS users can use Azure CLI without issue.
Recommendations
- Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
- Consider mentioning Bash or shell scripting as an alternative for Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as file path conventions or uploading files in Cloud Shell.
- Ensure that PowerShell is not presented as the default or primary method unless required.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and its example is given equal prominence to CLI. The PowerShell section is detailed and included alongside CLI, but there are no Linux/macOS-specific examples or notes. The order of examples (portal, CLI, PowerShell) is neutral, but the presence of PowerShell as a main workflow may create friction for Linux/macOS users if they are unfamiliar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but may be more familiar to Windows users.
- Add explicit notes or examples for Linux/macOS users, such as using Bash or zsh with Azure CLI.
- Consider including sample CLI commands that demonstrate Linux/macOS shell usage (e.g., environment variable syntax differences).
- Mention that Azure CLI is fully cross-platform and preferred for Linux/macOS environments.
- If PowerShell is not required for Linux/macOS, indicate that CLI covers all functionality.
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 shown immediately after Bash for each step, and the PowerShell formatting is explicitly called out ('Formatted for PowerShell'), which may indicate a slight Windows bias. There are no Linux-specific tools or patterns mentioned, but Bash is used, which is common on Linux/macOS. The ordering and explicit PowerShell labeling suggest Windows users are prioritized, but Linux/macOS users can complete all tasks without friction.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Consider grouping Bash and PowerShell examples under clearly labeled tabs (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to improve clarity.
- Ensure Bash examples are shown first or equally with PowerShell to avoid perceived prioritization.
- Add a brief note indicating cross-platform compatibility of Azure CLI commands.
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 tools for managing API Management instances, it lists Azure PowerShell cmdlets alongside Azure CLI and REST API, with PowerShell mentioned before Linux-native equivalents. There are no explicit Linux/macOS examples or references to Bash scripting, and PowerShell is referenced as a primary automation tool. However, all core tasks can be completed via the Azure CLI or REST API, which are cross-platform.
Recommendations
- Add explicit Bash/Linux/macOS examples where scripting is discussed, especially for automation tasks.
- When listing automation tools, mention Azure CLI (cross-platform) before Azure PowerShell, or at least equally.
- Clarify that Azure CLI and REST API are fully supported on Linux/macOS, and provide links to their documentation.
- Consider including sample Bash scripts for common operations, such as disabling a regional gateway.
- Ensure screenshots and UI instructions are not Windows-specific (e.g., avoid referencing Windows-only portal features).
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, but there is a subtle Windows bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks, and no equivalent CLI/Bash/Linux example is provided or referenced. No explicit Linux examples are missing from the main content, but the PowerShell-first reference may create friction for non-Windows users.
Recommendations
- Add references to Azure CLI or Bash-based guides for connecting virtual networks, alongside or in place of the PowerShell-specific link.
- Where possible, provide cross-platform command examples (Azure CLI, ARM templates) in addition to or instead of PowerShell.
- Review other related content links to ensure parity for Linux/macOS users.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is structured to support both Windows and Linux containers via pivot sections, but there are several signs of Windows bias. Windows-specific information and examples (such as PowerShell commands, Windows parent images, IIS/.NET Framework details, and Windows directory paths) are often presented first or in greater detail. PowerShell commands are given alongside Bash/Azure CLI, but sometimes Windows-specific tools and patterns (like Kudu, C:\home, and Windows memory/core settings) are emphasized. Linux equivalents are present but sometimes less detailed or appear after Windows content.
Recommendations
- Ensure Linux and Windows examples are equally detailed and presented in parallel, not always Windows-first.
- Where PowerShell commands are given, provide equivalent Bash or Linux shell commands with equal prominence.
- Expand Linux-specific guidance (e.g., persistent storage, diagnostic logs, SSH setup) to match the depth of Windows sections.
- Review pivoted content for parity: ensure Linux pivots are as comprehensive as Windows pivots.
- Where possible, mention Linux tools and patterns before or alongside Windows ones, especially in general sections.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is primarily 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 is prevalent, and Linux users are not given guidance or parity for troubleshooting or testing network connectivity.
Recommendations
- Clarify early and prominently that gateway-required virtual network integration is Windows-only, which is done, but reinforce this in troubleshooting sections.
- Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (e.g., nc, curl, netstat, ss) for users who may be managing hybrid environments.
- Explicitly state that Linux App Service plans cannot use this feature, and direct Linux users to regional virtual network integration or other alternatives.
- Add links or references to Linux/macOS troubleshooting guides for App Service networking issues.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_path_patterns
Summary
The documentation provides both Azure portal and Azure CLI instructions, which are cross-platform. However, there are several subtle signs of Windows bias: Windows file paths and environment variables (e.g., `%HOME%`, `D:\home\site\wwwroot\`), references to Kudu DebugConsole (which is more familiar to Windows users), and FTP upload instructions using Windows-style paths. Linux paths and equivalents are mentioned but generally after Windows examples. The documentation does not provide explicit Linux/macOS-specific instructions or examples for file operations, and Windows path conventions are used throughout.
Recommendations
- Add Linux/macOS path examples alongside Windows paths (e.g., `/home/site/wwwroot/` instead of only `D:\home\site\wwwroot\`).
- Clarify that `%HOME%` is equivalent to `/home` for Linux App Service apps.
- Provide explicit instructions for uploading files using Linux/macOS tools (e.g., SCP, SFTP, or Azure CLI) in addition to FTP.
- Mention that Kudu DebugConsole is available for both Windows and Linux App Service apps, and provide Linux-specific navigation tips if applicable.
- Where file paths are referenced, show both Windows and Linux formats in tables or code blocks.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides Azure CLI, PowerShell, and portal instructions for all major steps. While both CLI (cross-platform) and PowerShell (Windows-centric) examples are present, PowerShell examples are always shown after CLI, and there are no steps or examples that are Windows-only. However, the presence of PowerShell examples throughout, and the explicit mention of Azure PowerShell in the metadata, may create a slight perception of Windows bias, especially since PowerShell is more commonly used on Windows. All features and instructions are available to Linux/macOS users via the Azure CLI and portal.
Recommendations
- Continue to provide Azure CLI and portal instructions for all steps, as these are cross-platform.
- Consider clarifying that Azure PowerShell is available cross-platform (Windows, macOS, Linux) to reduce perception of Windows bias.
- If possible, mention that all migration steps can be performed from Linux/macOS using the Azure CLI or portal.
- Ensure that any future advanced troubleshooting or scripting examples also include Bash/CLI equivalents if PowerShell is used.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always present and often shown immediately after CLI examples. Windows-specific Helm installation instructions (using winget) are given before Linux instructions, and Windows is mentioned explicitly in the Helm install section. However, Linux parity is generally maintained, with Bash-compatible CLI commands and Linux Helm install instructions included. There are no critical sections that are Windows-only, but Windows is often referenced first or with more detail.
Recommendations
- Present Linux and Windows instructions with equal prominence, alternating which comes first or grouping by OS.
- Add explicit Bash/Linux command tabs for all steps where PowerShell is shown, especially for Azure CLI usage.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS as well as Windows.
- For Helm installation, provide parity in detail for Linux (e.g., mention package managers like apt/yum alongside curl script).
- Consider adding macOS-specific instructions where relevant, especially for Helm installation.
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
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most steps, but PowerShell is presented as a first-class option throughout, and in some sections (especially resource group deletion), PowerShell is shown alongside CLI without explicit Linux/macOS alternatives. There is no explicit mention of Linux/macOS-specific considerations, and Windows/PowerShell patterns are given equal prominence to CLI, which is more cross-platform. Some PowerShell commands (e.g., Set-AzAksCluster) are Windows-centric and may not be directly usable on Linux/macOS. No Linux-specific troubleshooting or parity notes are provided.
Recommendations
- Clearly indicate that Azure CLI is the recommended cross-platform tool and present CLI examples first in all sections.
- Add explicit notes clarifying that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Remove or de-emphasize PowerShell examples in sections where CLI is sufficient and more portable.
- Add troubleshooting or parity notes for Linux/macOS users, especially where PowerShell commands may not work or require additional setup.
- Ensure all code blocks and instructions are tested and validated on Linux/macOS shells (bash/zsh) and clarify any differences.
Azure App Configuration
Use dynamic configuration using push refresh - Java Spring
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and includes explicit PowerShell and Windows command prompt examples. However, Linux/macOS instructions are also present and clearly labeled. The bias is minor, mostly in the ordering and prominence of Windows tools.
Recommendations
- Present Linux/macOS (bash) environment variable instructions before Windows examples, or group all OS instructions together for parity.
- Add clarifying statements that all commands are cross-platform unless otherwise noted.
- Where possible, use generic shell commands (e.g., 'export') as the primary example, with OS-specific variants as secondary notes.
- Ensure screenshots and UI references are not Windows-centric (none detected here, but review for future updates).
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 setting instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), but includes all platforms. No Windows-only tools or patterns are used, and all code and build/run steps are cross-platform. No critical Linux/macOS omissions are present.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group them equally.
- Explicitly note that all steps are cross-platform and that Maven and Java are available on all major OSes.
- Add a brief statement at the start of the 'Build and run the app locally' section clarifying cross-platform support.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but the PowerShell section appears first and is more detailed, which may create a perception of Windows bias. However, Azure CLI examples are present and fully functional for Linux/macOS users. The portal-based instructions are platform-agnostic, as the Azure portal is web-based. No Windows-specific tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid 'windows_first' bias.
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, and PowerShell is available cross-platform, to reassure non-Windows users.
- Consider adding Bash shell script examples for common tasks, or clarify that Azure CLI commands are suitable for Linux/macOS environments.
- Where possible, ensure parity in detail and explanation between PowerShell and CLI sections.
Azure App Configuration
Quickstart to learn how to use Azure App Configuration
.../azure-app-configuration/quickstart-java-spring-app.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before Linux/macOS (bash), and uses Windows terminology ('command prompt') in build/run steps. However, Linux/macOS equivalents are present, and all code examples are platform-neutral Java/Maven.
Recommendations
- Present Linux/macOS environment variable instructions before Windows, or group them equally.
- Use neutral terminology such as 'terminal' instead of 'command prompt'.
- Explicitly mention that Maven and curl commands work identically on Linux/macOS.
- Consider adding a note that all steps are cross-platform unless otherwise stated.
Azure App Configuration
Tutorial for using Azure App Configuration Key Vault references in a Java Spring Boot app | Microsoft Docs
...-configuration/use-key-vault-references-spring-boot.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides environment variable setup instructions for Windows (cmd and PowerShell) before mentioning Linux/macOS equivalents. Windows-specific tools (setx, PowerShell) are described first, and Linux/macOS instructions are grouped together and shown after Windows. However, all critical steps are covered for Linux/macOS users, and the Azure CLI is used throughout, which is cross-platform.
Recommendations
- Present Linux/macOS environment variable instructions before or alongside Windows examples, rather than after.
- Explicitly mention that Azure CLI commands work on all platforms.
- Consider using a tabbed layout for environment variable setup (Windows CMD, PowerShell, Linux/macOS) to improve clarity and parity.
- Avoid phrasing that implies Windows is the default or primary platform.
Azure Functions
App settings reference for Azure Functions
...ain/articles/azure-functions/functions-app-settings.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides a comprehensive reference for Azure Functions app settings, covering both Windows and Linux scenarios. However, there are minor signs of Windows bias: Windows-specific examples (e.g., path syntax, Node.js version setting) are sometimes shown first or exclusively, PowerShell settings are detailed, and Windows tools (Azure PowerShell) are mentioned alongside Azure CLI. Linux equivalents are generally present, but Windows terminology and settings appear earlier or more prominently in some sections.
Recommendations
- Ensure all examples (e.g., path syntax, environment variable values) are shown for both Windows and Linux/macOS, or use cross-platform syntax where possible.
- When mentioning tools for managing settings (Azure CLI, Azure PowerShell), list Azure CLI first or equally, and provide Bash shell examples alongside PowerShell.
- For settings that are Windows-only, clearly label them as such and provide Linux/macOS alternatives or clarifications where applicable.
- Review ordering of settings and examples to avoid consistently showing Windows-specific content first.
- Expand Linux/macOS guidance in sections where Windows terminology dominates (e.g., file paths, environment variable delimiters).
Azure Cache For Redis
Deploy Azure Cache for Redis using Bicep
...s/azure-cache-for-redis/redis-cache-bicep-provision.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are presented alongside CLI examples in every section, and the PowerShell tool is Windows-centric. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor are Bash or other Linux-native shell examples provided. Azure CLI is cross-platform, but PowerShell is listed as an equal option, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add explicit notes that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Consider providing Bash shell script examples (using Azure CLI) for Linux users.
- List Azure CLI examples first in each section to reinforce cross-platform parity.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a generally cross-platform guide for running C# Azure Functions in an isolated worker process, with explicit support for both Windows and Linux. However, there are several instances where Windows tools, commands, and configuration options are mentioned first or more prominently than their Linux equivalents. Windows-specific instructions (e.g., for ReadyToRun, checking 32/64-bit, and preview SDK configuration) are often presented before Linux, and Windows CLI commands are sometimes shown without immediately adjacent Linux alternatives. Azure PowerShell is listed as a deployment option, but Linux users may not use PowerShell as commonly. Nevertheless, Linux deployment and configuration are covered, and Linux-specific instructions are included.
Recommendations
- Ensure that Linux and macOS examples are presented alongside Windows examples, ideally in parallel or with equal prominence.
- Where CLI commands are shown for Windows, immediately provide the Linux equivalent (especially for az CLI commands and configuration checks).
- When listing deployment tools, clarify which are cross-platform (e.g., Azure CLI, Core Tools) and which are Windows-centric (e.g., Azure PowerShell, Visual Studio).
- Consider adding explicit macOS notes where relevant, especially for development and debugging.
- In sections where Windows instructions are given first, alternate the order or use tabs to allow users to select their OS.