247
Pages Scanned
47
Pages Flagged
247
Changed Pages
19.0%
% Pages Flagged
Scan Information
Started At: 2026-02-02 00:00:06
Finished At: 2026-02-10 18:44:36
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 247
Files Completed: 247
Problematic Pages
47 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 is heavily focused on Azure PowerShell and Windows-specific tooling, such as the use of New-SelfSignedCertificate and Export-PfxCertificate PowerShell cmdlets, which are only available on Windows. There are no CLI (az), Bash, or cross-platform examples provided, and the instructions assume a Windows environment (e.g., referencing C:\ paths and local certificate stores). This creates friction for Linux/macOS users, who cannot follow key steps (like certificate creation) without significant adaptation.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource creation steps, especially for resource group, VNet, public IP, and application gateway setup.
- Include cross-platform instructions for creating self-signed certificates, such as using OpenSSL (available on Linux/macOS/Windows) and explain how to export to PFX format.
- Avoid hardcoding Windows-specific paths (e.g., c:\appgwcert.pfx) and use environment-agnostic file paths or explain alternatives.
- Add notes or sections for Linux/macOS users, highlighting differences and providing adapted commands.
- Consider restructuring the tutorial to offer both PowerShell and CLI/Bash alternatives side-by-side.
Create Pull Request
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, with all setup instructions, prerequisites, and examples centered around Windows tools (SignTool.exe, MSI installers, WinGet, PowerShell). There are no instructions or examples for Linux or macOS users, nor is there mention of equivalent signing workflows or tools for non-Windows platforms. The only integrations described in detail are Windows-specific, and even general integrations (GitHub Actions, Azure DevOps) are referenced only via external links without parity in setup instructions.
Recommendations
- Add explicit guidance for Linux/macOS users, including supported signing tools and workflows if available.
- Clarify whether Artifact Signing is Windows-only or if cross-platform support is planned or available.
- Provide examples for using Artifact Signing in Linux/macOS CI environments (e.g., with GitHub Actions, Azure DevOps pipelines running on Linux agents).
- If SignTool is Windows-only, highlight alternative signing methods for non-Windows platforms, or state limitations clearly.
- Include installation and usage instructions for the Artifact Signing SDK on Linux/macOS, if supported.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-client.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides instructions for creating a .NET Framework console application using Visual Studio, which is a Windows-only IDE and targets the Windows-only .NET Framework. There are no examples or guidance for Linux/macOS users, such as using .NET Core/.NET 5+ or cross-platform development tools.
Recommendations
- Add instructions for creating a cross-platform .NET (Core/.NET 5+) console application using the 'dotnet' CLI, which works on Windows, Linux, and macOS.
- Include examples for installing the NuGet package via CLI (e.g., 'dotnet add package Microsoft.Azure.Relay').
- Clarify whether the Azure Relay client library supports .NET Core/.NET 5+ and provide sample code for those platforms.
- Mention alternative development environments (e.g., VS Code, JetBrains Rider) that are available on Linux/macOS.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-dotnet-get-started-server.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation instructs users to create a .NET Framework console app in Visual Studio, which is a Windows-centric workflow. There are no instructions or examples for creating the equivalent application on Linux or macOS (e.g., using .NET Core/.NET 5+ and cross-platform tools like VS Code or CLI). The steps and code are specific to .NET Framework, which is Windows-only, and do not mention alternatives for non-Windows environments.
Recommendations
- Add instructions for creating a cross-platform .NET (Core/5+) console application using the dotnet CLI.
- Include guidance for using VS Code or other cross-platform editors.
- Clarify that the current instructions are for .NET Framework (Windows-only), and provide links or steps for Linux/macOS users to achieve similar functionality with .NET Core/5+.
- If Azure Relay supports .NET Core/5+, provide sample code and setup steps for those platforms.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC assignment, but PowerShell is given equal prominence, and references to Windows tools (IIS, Certreq.exe) are present for certificate export. The instructions for exporting certificates mention Windows-specific tooling before Linux equivalents (OpenSSL), and the FAQ automation section lists PowerShell and CLI scripts, with PowerShell mentioned second. There are no Linux/macOS-specific examples or explicit parity notes.
Recommendations
- Ensure all automation and scripting examples include both Azure CLI and PowerShell, with CLI (cross-platform) shown first.
- When discussing certificate export, mention OpenSSL (Linux/macOS) before Windows tools (IIS, Certreq.exe), and provide explicit instructions for both platforms.
- Add notes or links for Linux/macOS users where Windows tools are referenced, clarifying alternatives.
- Where screenshots or UI steps are shown, clarify that the Azure portal is platform-agnostic.
- Consider including a short section or callout for Linux/macOS users on common certificate management workflows.
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 presents Windows-centric instructions and examples first, especially for loading certificates in app code. Windows certificate store access is explained in detail for C# and Java, while Linux guidance is limited to file-based access and only C# examples are provided for Linux. There are no Linux-specific code samples for popular languages like Python, Node.js, or Java, and references to those platforms are deferred to external documentation. Windows tools and patterns (certificate store, environment variables, etc.) are described more thoroughly than their Linux equivalents.
Recommendations
- Add Linux-specific code examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the provided Linux file paths.
- Present Linux and Windows instructions in parallel or in tabs, rather than leading with Windows-only approaches.
- Expand discussion of Linux environment variables and best practices for certificate access, matching the detail given to Windows.
- Clarify which approaches are cross-platform and which are Windows-specific earlier in the document.
- Provide direct links or inline examples for Linux container scenarios in languages other than C#.
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation is generally cross-platform, describing both Windows and Linux as supported operating systems for App Service plans. However, the 'Managed Instance on Azure App Service' section is Windows-only and highlights Windows-specific tools (PowerShell, RDP, IIS, registry access, MSI installers, COM components) without mentioning Linux equivalents or alternatives. Windows features and tooling are described in detail, while Linux-specific capabilities or migration scenarios are not discussed, creating a subtle Windows-first bias in advanced hosting scenarios.
Recommendations
- Add a parallel section describing advanced Linux hosting options, if available, or clarify the absence of equivalent features for Linux.
- Where Windows-specific tools (PowerShell, RDP, IIS) are mentioned, note that these are not available on Linux and suggest Linux-native alternatives or workflows where possible.
- Explicitly state the limitations and feature parity between Windows and Linux App Service plans, especially for advanced scenarios.
- Provide links to Linux migration guidance or documentation for legacy Linux workloads.
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
missing_linux_example
Summary
The documentation page provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux scenarios. However, there are several instances where Windows-specific details, tools, and patterns are mentioned first or exclusively, and Linux equivalents are either referenced later, less prominently, or omitted. Examples and paths often default to Windows formats (e.g., D:\home), and some deployment/build automation sections provide more detail for Windows (Kudu) than Linux (Oryx). Windows tools (such as msbuild, Web Deploy/MSDeploy, IIS, and .bat files) are referenced directly, while Linux alternatives are less emphasized. Some environment variables are described only in Windows contexts, with Linux applicability noted as an aside or not at all.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows examples, especially for environment variable paths and configuration patterns.
- When describing environment variables, list both Windows and Linux default values and usage patterns equally.
- In build automation and deployment sections, expand Linux (Oryx) documentation to match the detail given for Windows (Kudu), including explicit examples and links.
- Avoid listing Windows tools and patterns first unless they are the only supported option; otherwise, alternate or parallelize the order.
- Where environment variables are Windows-only, clearly mark them as such and provide Linux alternatives or note their absence.
- Add more explicit Linux/macOS troubleshooting notes and references where applicable.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation heavily references Azure PowerShell scripts as the primary (and seemingly only) migration tooling, with no mention of Azure CLI, Bash, or cross-platform alternatives. All migration automation examples and scripts are PowerShell-based, and there are no Linux/macOS-specific instructions or parity guidance. This creates friction for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration steps, or clearly state if they are not available.
- Add Bash/shell script examples or guidance for Linux/macOS users where possible.
- Explicitly mention platform requirements for the PowerShell scripts (e.g., if they require Windows PowerShell or can run in PowerShell Core on Linux/macOS).
- Link to or document any cross-platform migration tooling, or provide a roadmap for parity.
- If PowerShell is the only supported method, acknowledge this limitation and suggest workarounds (e.g., using Azure Cloud Shell, which supports PowerShell and Bash).
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page includes a 'Next steps' section that links to a tutorial specifically using Azure PowerShell for creating an autoscaling, zone redundant application gateway. No equivalent example or guidance is provided for Linux/macOS users (e.g., Azure CLI, ARM templates, or Bicep). Azure PowerShell is typically associated with Windows environments, and its mention without parity for cross-platform tools may create friction for non-Windows users.
Recommendations
- Add links or examples for creating autoscaling, zone redundant application gateways using Azure CLI, ARM templates, or Bicep, which are cross-platform and commonly used on Linux/macOS.
- In the 'Next steps' section, provide parallel tutorials for Azure CLI and/or ARM/Bicep to ensure Linux/macOS users have clear guidance.
- Explicitly note that Azure PowerShell is available cross-platform, but highlight alternatives for users who prefer CLI or template-based workflows.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides explicit instructions for enabling diagnostic logging using PowerShell, with no equivalent CLI, Bash, or Linux/macOS example. The PowerShell method is presented before the Azure portal method, and there is no mention of Azure CLI or REST API alternatives, which are cross-platform. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Add equivalent instructions and examples for enabling diagnostic logging using Azure CLI (az monitor diagnostic-settings) and/or REST API, which are cross-platform.
- Present cross-platform methods (CLI, REST API) before or alongside PowerShell examples to avoid Windows-first bias.
- Explicitly state that PowerShell is one option and provide guidance for Linux/macOS users.
- Include Bash or shell script examples where appropriate.
- Add a note clarifying that PowerShell Core is available cross-platform, if relevant, but still provide CLI examples.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and downloadable tools provided exclusively in PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS usage patterns or prerequisites addressed. The documentation assumes the user is familiar with PowerShell and Windows-centric tooling, which creates friction for Linux/macOS users who may prefer or require Azure CLI or Bash scripting.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
- Add explicit instructions and examples for running migration from Linux/macOS environments, including use of Azure Cloud Shell (Bash) and Azure CLI.
- Clarify whether the PowerShell scripts can be run in Azure Cloud Shell (Bash) or only in PowerShell, and if so, provide guidance for Linux/macOS users.
- List prerequisites for Linux/macOS environments, such as installation of Azure CLI and authentication steps.
- Where possible, offer downloadable Bash scripts or cross-platform alternatives alongside PowerShell scripts.
- Reorder examples so that cross-platform (Azure CLI/Bash) instructions are presented before or alongside PowerShell examples.
Application Gateway
What is Azure Application Gateway v2?
.../blob/main/articles/application-gateway/overview-v2.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows/PowerShell bias. Migration guidance and preview registration/unregistration are provided exclusively with Azure PowerShell commands, without equivalent Azure CLI (cross-platform) or Bash examples. The main tutorial link is also PowerShell-focused. This creates friction for Linux/macOS users who may prefer or require CLI/Bash instructions.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell commands for migration and preview registration/unregistration steps.
- Provide links to tutorials using Azure CLI or ARM templates, not just PowerShell.
- Ensure that all procedural instructions are available in cross-platform formats, especially for critical operations like migration.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents Windows/PowerShell guidance and tools more prominently than Linux equivalents. Windows registry settings and PowerShell cmdlets are referenced repeatedly, while Linux guidance is less detailed and sometimes limited to external links or a single Python script. Most backup and export examples use Windows PowerShell cmdlets, with no Linux CLI or automation examples provided.
Recommendations
- Provide equivalent Linux CLI (e.g., Azure CLI, Bash) examples for tasks currently shown only with PowerShell cmdlets, such as exporting runbooks and DSC configurations.
- Include Linux-specific instructions or scripts for managing TLS settings, backing up assets, and other automation tasks, not just a single Python script.
- Present platform guidance in parallel (Windows and Linux side by side), rather than listing Windows first or in more detail.
- Reference cross-platform tools (e.g., Azure CLI, REST API) where possible, and clarify which steps are platform-agnostic.
- Add explicit notes when a feature or cmdlet is Windows-only, and suggest Linux alternatives if available.
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 for disaster recovery in Azure Automation presents only PowerShell and PowerShell Workflow scripts for asset migration, with no Bash, CLI, or Python alternatives. Steps and tabs for Hybrid Runbook Worker installation reference Windows first, and there are no Linux-specific examples or instructions for migration. This creates friction for Linux/macOS users who may prefer or require non-PowerShell tooling.
Recommendations
- Provide equivalent migration scripts using Azure CLI, Bash, or Python for Linux/macOS users.
- Include explicit Linux/macOS instructions and examples for Hybrid Runbook Worker installation and migration steps.
- When listing tabs or instructions, alternate or parallelize Windows and Linux options rather than presenting Windows first.
- Clarify any PowerShell requirements for Linux users (e.g., PowerShell Core installation) and provide guidance.
Automation
Use Microsoft Entra ID in Azure Automation to authenticate to Azure
...ob/main/articles/automation/automation-use-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell, referencing Windows PowerShell modules and cmdlets throughout. All code examples and instructions are provided exclusively for PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The use of Windows-specific terminology and tools (e.g., PSCredential, Windows PowerShell modules) is prevalent, and Linux/macOS users are not given guidance for equivalent workflows.
Recommendations
- Add Azure CLI examples for credential management and authentication to Azure using Microsoft Entra ID.
- Clarify which steps are cross-platform and which are Windows-specific, especially around credential assets and runbook scripting.
- Provide Bash or Python runbook examples, or reference how Linux/macOS users can achieve similar automation tasks.
- Explicitly state PowerShell Core (pwsh) compatibility if applicable, and note any limitations for non-Windows platforms.
- Mention that Azure Automation supports Python runbooks and link to relevant documentation for Linux/macOS users.
Azure Netapp Files
Create volume replication for Azure NetApp Files
...etapp-files/cross-region-replication-create-peering.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides Azure PowerShell examples first for feature registration and status checking, with only a brief mention that Azure CLI commands can also be used. The command examples and step-by-step instructions are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. No explicit Linux/macOS CLI examples are shown, and the PowerShell commands are presented as the primary method.
Recommendations
- Add explicit Azure CLI command examples alongside PowerShell for feature registration and status checking.
- Where possible, show both PowerShell and CLI commands in parallel, or provide tabs for users to select their preferred environment.
- Clarify that all steps can be performed using Azure CLI on Linux/macOS and provide links to relevant CLI documentation.
- Consider listing CLI examples first or equally to avoid Windows-first impression.
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
missing_linux_example
windows_first
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples for configuring and invoking runbooks use PowerShell cmdlets or C# SDKs, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or Python SDK). The only mention of Python is for runbook authoring, not for parameter assignment or invocation. There are no Linux-native shell or cross-platform CLI examples for starting or managing runbooks, and PowerShell is always presented first and in detail.
Recommendations
- Add Azure CLI examples for starting runbooks and passing parameters, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples for invoking runbooks via the REST API, demonstrating how Linux users can automate these tasks.
- Provide parity in SDK examples by including Python or JavaScript/TypeScript code snippets for starting runbooks and passing parameters.
- Clarify in each section whether the instructions are cross-platform or Windows-specific, and link to cross-platform alternatives where possible.
- Highlight any platform-specific limitations or differences explicitly, so users know what is or isn't supported on their OS.
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 use PowerShell, and cmdlet references are exclusively for Windows PowerShell/Az modules. The process for creating credentials outside the portal is described only for Windows PowerShell, with no mention of Bash, Azure CLI, or Linux-native approaches. Python examples are included, but only as runbook code, not for asset management. There is no guidance for Linux/macOS users who may wish to automate credential management outside the portal.
Recommendations
- Add Azure CLI examples for credential asset management, if supported.
- Clarify whether credential management via CLI is possible on Linux/macOS, and provide instructions or alternatives.
- If PowerShell is required, note cross-platform availability (PowerShell Core) and provide installation guidance for non-Windows platforms.
- Explicitly state any limitations or platform requirements for credential management tasks.
- Consider including Bash or REST API examples for asset creation and retrieval, if supported.
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 generally describes Azure Change Tracking and Inventory as supporting both Windows and Linux. However, the section on registry key tracking is exclusively Windows-focused, with no mention of Linux equivalents (such as tracking changes to Linux configuration files or directories). Additionally, the registry tracking section is lengthy and detailed, while there is no comparable section for Linux-specific change tracking (e.g., monitoring /etc, systemd units, or other Linux configuration artifacts). Throughout the document, Windows terminology and tools (e.g., registry keys, Internet Explorer, explorer.exe) are described in detail, while Linux-specific examples or explanations are minimal or absent.
Recommendations
- Add a section or table describing Linux-specific change tracking capabilities, such as monitoring changes to key configuration files (e.g., /etc/passwd, /etc/ssh/sshd_config), systemd service files, or package installations.
- Provide Linux-specific examples or screenshots where appropriate, especially in sections that currently focus on Windows artifacts.
- Clarify in the registry tracking section that this feature is Windows-only, and provide a parallel explanation of what is tracked on Linux systems.
- Ensure that examples and explanations are balanced between Windows and Linux, or clearly indicate when a feature is platform-specific.
Azure Netapp Files
Create an SMB volume for Azure NetApp Files
...-netapp-files/azure-netapp-files-create-volumes-smb.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
powershell_heavy
Summary
The documentation is focused on creating and managing SMB volumes for Azure NetApp Files, which is inherently a Windows-centric protocol. However, the sections on managing permissions and share access exclusively reference Windows tools (MMC, Windows SMB client) and provide no guidance for Linux or macOS users who may need to access or manage SMB shares. There are no examples or instructions for mounting or managing SMB volumes from non-Windows clients.
Recommendations
- Add instructions or references for mounting SMB volumes from Linux and macOS clients (e.g., using the 'mount.cifs' command on Linux or 'Connect to Server' on macOS).
- Include examples of setting permissions or accessing SMB shares from Linux (e.g., using 'smbclient' or 'setfacl' where applicable).
- Clarify which management tasks (such as modifying share permissions) are only possible from Windows, and suggest alternatives or limitations for non-Windows users.
- Link to the 'Mount a volume for Windows or Linux virtual machines' page earlier in the workflow, especially in the 'Control access' section.
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 for managing certificates in Azure Automation is heavily focused on PowerShell cmdlets and workflows, which are most commonly used on Windows. All example scripts for certificate creation and management use PowerShell, with no equivalent CLI, Bash, or Linux-native instructions. The portal workaround also recommends PowerShell. While Python examples are provided for runbook access, all asset management and deployment examples are PowerShell-centric, and there are no Linux/macOS-specific instructions or parity for certificate creation or management.
Recommendations
- Add Azure CLI examples for certificate creation, management, and deployment, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples for uploading certificates, leveraging az CLI or REST API.
- Clarify which steps are platform-agnostic and which are PowerShell-specific, and provide alternatives where possible.
- Mention any limitations or differences for Linux/macOS users explicitly, and link to relevant cross-platform guidance.
- Reorder examples so that platform-neutral or cross-platform methods (such as Azure portal or Azure CLI) are presented before PowerShell.
Azure Functions
Migrate C# app from in-process to isolated worker model
...es/azure-functions/migrate-dotnet-to-isolated-model.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only Azure PowerShell scripts for identifying function apps to migrate, with no equivalent Azure CLI or Bash examples for Linux/macOS users. Windows-centric tools and workflows (PowerShell, Visual Studio) are mentioned first or exclusively in several sections, while Linux alternatives (such as Azure CLI, VS Code) are referenced only briefly or not at all. This creates friction for users on non-Windows platforms, especially in the initial steps of migration and deployment.
Recommendations
- Add Azure CLI and/or Bash script examples alongside PowerShell for identifying function apps and managing Azure resources.
- Explicitly mention VS Code and cross-platform publishing/deployment workflows, with step-by-step instructions for Linux/macOS users.
- Ensure that all critical steps (such as updating app settings, deploying to slots) have both PowerShell and CLI examples.
- Consider reordering examples or using tabs to present Windows and Linux/macOS instructions equally.
- Clarify which tools are cross-platform and provide links to relevant installation guides for Linux/macOS.
Azure Functions
Deployment technologies in Azure Functions
...s/azure-functions/functions-deployment-technologies.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation generally covers both Windows and Linux deployment options for Azure Functions, but there are subtle biases. Windows-based deployment methods (such as source control, local Git, and FTPS) are called out explicitly in the technology availability table, while Linux equivalents are less emphasized or described as limited. Examples and instructions often mention Windows tools (Visual Studio, Kudu) first or exclusively, with Linux-specific details following or requiring additional configuration. Some deployment methods (like source control and FTPS) are described as 'Windows-only' without offering Linux alternatives or workarounds, and the documentation sometimes assumes use of Windows-based tooling before mentioning Linux-specific settings or requirements.
Recommendations
- Provide Linux/macOS-specific examples and instructions alongside Windows ones, especially for deployment methods marked as 'Windows-only'.
- Clarify or link to Linux alternatives or workarounds where Windows-only deployment technologies are mentioned.
- When listing tools or methods, present cross-platform options first or in parallel (e.g., Azure CLI, Core Tools) before Windows-specific tools (Visual Studio, Kudu).
- Explicitly state limitations for Linux users and suggest recommended Linux-compatible deployment workflows.
- Add more guidance for Linux users on troubleshooting and configuration, especially for remote builds and storage settings.
Azure Functions
Migrate Consumption plan apps to Flex Consumption in Azure Functions
...unctions/migration/migrate-plan-consumption-to-flex.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides migration instructions for both Linux and Windows Azure Functions Consumption plan apps to Flex Consumption. However, there is a notable Windows bias: Windows migration steps are more manual and detailed, with Windows-specific CLI commands and portal instructions often presented before or in greater depth than Linux equivalents. The Linux migration is streamlined via a dedicated Azure CLI command, while Windows users must perform many steps manually. Windows-centric tools and patterns (such as references to Windows-specific storage, file shares, and configuration settings) are prevalent, and Windows examples are frequently shown first or in more detail.
Recommendations
- Provide parity in automation: Develop and document an equivalent automated migration command for Windows apps, similar to 'az functionapp flex-migration' for Linux.
- Ensure example parity: For every Windows-specific CLI or portal example, provide a corresponding Linux example, and vice versa.
- Balance presentation order: Alternate or randomize the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Clarify platform differences: Clearly state where features or commands are Linux-only or Windows-only, and explain the rationale.
- Expand Linux coverage: Where Windows tools or patterns are mentioned (e.g., file shares, PowerShell), offer Linux alternatives or note their absence.
- Add cross-platform troubleshooting: Ensure troubleshooting and recovery sections include Linux-specific guidance, not just Windows/PowerShell-centric steps.
Azure Netapp Files
SMB performance best practices for Azure NetApp Files
...ure-netapp-files/azure-netapp-files-smb-performance.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is heavily Windows-centric, with nearly all examples, commands, and performance monitoring instructions referencing Windows tools (PowerShell cmdlets, Performance Monitor, Hyper-V adapters). There are no Linux or macOS SMB client examples, nor any mention of how to achieve similar monitoring or configuration on non-Windows platforms. The use of Windows terminology and tools is pervasive throughout, creating friction for Linux/macOS users who may also use SMB with Azure NetApp Files.
Recommendations
- Add equivalent Linux/macOS SMB client configuration and performance tuning instructions, e.g., using smbclient, mount.cifs, or relevant sysctl parameters.
- Provide Linux/macOS examples for monitoring SMB performance, such as using iostat, atop, or other network/file system monitoring tools.
- Include notes on how SMB Multichannel, Signing, and Encryption are supported or configured on Linux/macOS clients (e.g., Samba settings, kernel support).
- Clarify which recommendations are Windows-only and which are cross-platform, to help users understand applicability.
- Where PowerShell or Windows-specific commands are shown, offer Linux/macOS alternatives or explicitly state if no equivalent exists.
Azure Netapp Files
Troubleshoot volume errors for Azure NetApp Files
...in/articles/azure-netapp-files/troubleshoot-volumes.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides troubleshooting guidance for Azure NetApp Files volumes across SMB, NFS, and dual-protocol scenarios. While it covers both Windows (SMB/AD DS) and Linux (NFS) use cases, there is a notable Windows bias: Active Directory and Windows-centric tools (e.g., PowerShell, Server Manager) are referenced for key administrative tasks, and Windows terminology and examples (such as AD DS, OU paths, and PowerShell commands) are presented before or more prominently than Linux equivalents. Linux troubleshooting steps are present but sometimes less detailed or secondary.
Recommendations
- Where PowerShell or Windows UI tools are referenced for AD/LDAP tasks (e.g., setting Kerberos encryption type, managing machine accounts), provide equivalent Linux/UNIX commands (such as using ldapmodify, samba-tool, or other CLI utilities) for environments where AD is managed from Linux.
- When describing troubleshooting steps for AD DS, clarify which steps are applicable to Linux-based AD management and provide links or examples for common Linux tools.
- Ensure that NFS and Linux-specific troubleshooting sections are as detailed as their Windows counterparts, including explicit Linux command-line examples for DNS, Kerberos, and LDAP configuration and validation.
- Where possible, alternate the order of Windows and Linux examples, or group them clearly so Linux users can easily find relevant guidance.
- Add explicit notes or callouts for cross-platform differences in terminology, tools, and workflows.
Azure Relay
Authenticate from an application - Azure Relay
.../main/articles/azure-relay/authenticate-application.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page primarily features .NET (C#) console application samples, which are most commonly run on Windows, and references PowerShell for role assignment management before mentioning Azure CLI. There are no explicit Linux/macOS setup or run instructions, nor are there examples for running the sample applications on non-Windows platforms. While Java and JavaScript samples are linked, the main walkthrough and code snippets are Windows-centric (.NET).
Recommendations
- Add explicit instructions or examples for running the sample applications on Linux/macOS, including any required dependencies or environment setup.
- Provide equivalent shell (bash) commands for Azure CLI alongside PowerShell commands, and consider listing Azure CLI before PowerShell to avoid Windows-first bias.
- Highlight cross-platform compatibility of .NET Core/.NET 5+ samples, and clarify if the provided .NET samples can be run on Linux/macOS.
- Include code snippets or walkthroughs for Java and JavaScript samples, not just links, to improve parity.
- Mention any platform-specific considerations or limitations for Linux/macOS users.
Azure Relay
Authenticate with managed identities for Azure Relay resources
.../articles/azure-relay/authenticate-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a notable Windows bias by providing a step-by-step walkthrough that exclusively uses a Windows 10 VM, references RDP for access, and links only to Windows VM setup guides. There are no equivalent instructions or examples for Linux VMs or non-Windows environments, even though managed identities and Azure Relay are cross-platform features. While code samples are cross-platform (.NET, Java, JavaScript), the operational guidance is Windows-centric.
Recommendations
- Add parallel instructions for creating and configuring a Linux VM with managed identity enabled.
- Include guidance for connecting to Linux VMs (e.g., using SSH) and copying files to Linux VMs.
- Provide Linux/macOS command-line examples for running the sample applications.
- Link to both Windows and Linux VM creation guides in the setup steps.
- Clarify that the sample apps can be run on Linux/macOS and provide any necessary prerequisites or differences.
Azure Relay
Configure IP firewall for Azure Relay namespace
...n/articles/azure-relay/ip-firewall-virtual-networks.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces using the Azure portal and Resource Manager templates. When referencing command-line deployment, it links specifically to PowerShell-based instructions, which are Windows-centric, and does not mention or provide parity for Linux/macOS CLI alternatives (such as Azure CLI or Bash). Additionally, the deployment link for Resource Manager templates is PowerShell-focused and appears before any mention of cross-platform tools.
Recommendations
- Include instructions or links for deploying Resource Manager templates using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- When referencing command-line deployment, mention both PowerShell and Azure CLI options, or provide a neutral landing page that covers both.
- Ensure examples and links do not default to Windows tools unless the feature is Windows-only (which is not the case here).
Azure Relay
Integrate Azure Relay with Azure Private Link Service
...blob/main/articles/azure-relay/private-link-service.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides detailed instructions for integrating Azure Relay with Azure Private Link Service, but it demonstrates a notable Windows bias. The only CLI-based automation example is in Azure PowerShell, with no equivalent Azure CLI or Bash example. The validation section explicitly instructs users to create a Windows VM and references the Windows VM creation guide, with no mention of Linux VMs or cross-platform alternatives. This may create friction for Linux/macOS users who prefer Azure CLI or want to validate from a Linux VM.
Recommendations
- Add Azure CLI (az) examples alongside or in place of PowerShell for creating and managing private endpoints.
- In the validation section, provide instructions for creating a Linux VM and running the nslookup command from a Linux shell, or clarify that the validation steps are OS-agnostic.
- When referencing VM creation, link to both Windows and Linux VM creation guides.
- Where possible, use cross-platform language and tools in examples to ensure parity for Linux/macOS users.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md
...id-connections-http-requests-dotnet-get-started-client.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation assumes the use of Visual Studio and .NET Framework, both of which are primarily Windows tools. There are no instructions or examples for creating the application or installing packages using cross-platform tools (e.g., .NET Core/SDK CLI, VS Code, or Linux/macOS environments). All steps and code samples are tailored for a Windows-centric workflow.
Recommendations
- Provide alternative instructions for creating the project and managing NuGet packages using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package Microsoft.Azure.Relay'), which work on Linux and macOS.
- Clarify whether the code and package are compatible with .NET Core/.NET 5+ and cross-platform environments, or explicitly state if .NET Framework is required.
- Mention and provide examples for using cross-platform editors like VS Code.
- Add a note about running the sample on Linux/macOS, including any prerequisites or limitations.
Azure Relay
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-server.md
...id-connections-http-requests-dotnet-get-started-server.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation assumes the use of Visual Studio and the .NET Framework, both of which are Windows-centric. It provides instructions for creating a console app using Visual Studio and .NET Framework, with no mention of cross-platform alternatives like .NET Core/.NET 5+ or Visual Studio Code. There are no instructions or examples for Linux/macOS users.
Recommendations
- Add instructions for creating the project using .NET Core or .NET 5+ (which are cross-platform) and Visual Studio Code or the 'dotnet' CLI.
- Clarify whether the Microsoft.Azure.Relay package and the code sample work on .NET Core/.NET 5+ and, if so, provide equivalent steps for Linux/macOS.
- If the feature is not Windows-only, provide explicit guidance for non-Windows users, including package installation and running the sample.
- If the feature is Windows-only, state this clearly at the top of the documentation.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows instructions are presented first. All other examples and commands use Azure CLI, Bash, and Kubernetes tools, which are cross-platform and do not show a Windows bias. No PowerShell-heavy or Windows-only tooling is present.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or list Linux first, as Linux is the more common OS for Kubernetes workloads.
- Explicitly state that all Azure CLI and Kubernetes commands work on Linux, macOS, and Windows (with WSL or Bash).
- Consider adding a note for macOS users in the Helm installation section.
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
missing_linux_example
Summary
The documentation provides step-by-step instructions for creating and managing Azure Cache for Redis private endpoints primarily via the Azure portal (GUI), followed by detailed PowerShell scripts and then Azure CLI examples. PowerShell examples are presented before CLI, and there are no explicit Linux/macOS shell examples or notes about cross-platform usage. The FAQ and troubleshooting sections reference commands like nslookup but do not clarify platform differences. There is a mild Windows bias in the ordering and example selection.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell examples are Windows-centric (unless using PowerShell Core).
- Include bash shell examples for DNS verification (e.g., dig, host) alongside nslookup, or clarify nslookup usage on Linux/macOS.
- Where possible, provide parity in troubleshooting and verification steps for Linux/macOS users (e.g., mention how to install Azure CLI, use REST API with curl, etc.).
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI examples for both bash and PowerShell shells throughout, with PowerShell examples consistently shown second. There is no evidence of Windows-only tools, PowerShell-heavy bias, or missing Linux/macOS examples. All commands are cross-platform and the documentation explicitly states that commands can be run in either shell, providing syntax for both.
Recommendations
- Maintain the current parity by continuing to provide both bash and PowerShell examples.
- Consider alternating the order of examples (sometimes showing bash first, sometimes PowerShell) to avoid subtle perception of Windows-first bias.
- Explicitly mention macOS compatibility where relevant, to reassure users on that platform.
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_tools
powershell_heavy
windows_first
Summary
The documentation page provides command-line examples for managing Azure API Management multi-region deployments using Azure CLI and PowerShell. While Azure CLI is cross-platform, the explicit mention and linking of Azure PowerShell cmdlets (set-azapimanagement) and the ordering of PowerShell before other tools in the disable routing section indicate a mild Windows bias. There are no Linux/macOS-specific examples or explicit parity notes, and the documentation does not mention Bash scripting or Linux shell usage. However, the core instructions are portal-based or use Azure CLI, which is available on all platforms.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- When listing command-line tools, mention Azure CLI first as it is cross-platform, and provide parity examples for Bash or shell scripting if relevant.
- Add a note that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide equivalent Bash/CLI examples where possible.
- Avoid listing Windows-specific tools (PowerShell) before cross-platform tools unless there is a technical reason.
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 immediately after Bash, and the formatting and comments explicitly highlight PowerShell usage, suggesting a slight preference for Windows/PowerShell environments. There is no mention of Linux-specific tools or workflows, but Bash examples are present and correct.
Recommendations
- Clarify that both Bash and PowerShell examples are equivalent and suitable for Linux/macOS and Windows, respectively.
- Consider listing Bash (Linux/macOS) examples first to reduce perceived Windows-first bias.
- Add a short note at the top of the CLI section explaining which examples are for which platforms.
- Ensure parity in explanation and troubleshooting steps for both Bash and PowerShell users.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are always shown immediately after Bash, and are labeled as 'Formatted for PowerShell'. There is a minor bias in that PowerShell is given explicit formatting, but Linux/macOS users are not given additional context or troubleshooting. However, all critical steps are covered for both platforms.
Recommendations
- Clarify that the Bash examples are suitable for Linux/macOS and WSL users, and PowerShell is for Windows users.
- Consider using tabs or explicit headings for 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to make platform targeting clearer.
- Add a brief note about which shell to use on each platform, and mention that Azure CLI commands work cross-platform.
- Ensure variable naming is consistent between Bash and PowerShell examples to avoid confusion.
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, Azure PowerShell, and Azure Portal instructions for all major steps. However, PowerShell examples are always present and shown after CLI, and the documentation does not explicitly mention Linux/macOS environments or provide shell-specific guidance for those platforms. The use of PowerShell as a primary scripting example may create friction for Linux/macOS users, though Azure CLI is cross-platform and included throughout. There are no Windows-only tools or patterns, and Linux support is explicitly referenced in feature tables.
Recommendations
- Add explicit notes that Azure CLI commands work on Linux/macOS and Windows, and clarify that PowerShell examples are for Windows and PowerShell Core users.
- Consider including Bash or shell script examples for common Linux/macOS workflows, or clarify that Azure CLI is the recommended approach for cross-platform automation.
- Reorder examples to show Azure CLI first, as it is cross-platform, and clarify the intended audience for PowerShell examples.
- Add a brief section or note for Linux/macOS users confirming that all migration steps can be performed using Azure CLI on their platforms.
Azure App Configuration
Configuration Provider Overview
...e-app-configuration/configuration-provider-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation lists .NET-based provider libraries first and provides .NET/ASP.NET/Functions/.NET Framework examples before Java, Python, JavaScript, and Go. However, the page covers cross-platform libraries and includes samples and release notes for all major languages, with no exclusive Windows/PowerShell examples or tools. There is a minor ordering bias favoring Windows/.NET technologies.
Recommendations
- Reorder the provider libraries table to alternate or group by platform type (e.g., .NET, Java, Python, JavaScript, Go) rather than listing all .NET/Windows-centric libraries first.
- Explicitly mention cross-platform compatibility for .NET Standard and ASP.NET Core libraries (e.g., Linux/macOS support).
- Consider providing a summary table or section that highlights Linux/macOS usage or parity.
- Ensure that sample links for .NET libraries include Linux/macOS usage notes if relevant.
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
powershell_heavy
Summary
The documentation generally provides parity for both Windows and Linux users, but there are several instances where Windows tools, commands, or configuration steps are mentioned before their Linux equivalents, or where Windows-specific instructions are more prominent. Some CLI examples and explanations default to Windows, and PowerShell is referenced as a deployment method before Linux alternatives. However, Linux equivalents are usually present, and critical tasks are not Windows-only.
Recommendations
- Ensure that all CLI and deployment instructions are presented with both Windows and Linux examples side-by-side or with clear tabs for each OS.
- When listing deployment or resource creation methods, avoid listing Windows/PowerShell first by default; alternate or group by platform.
- Where PowerShell is referenced, ensure Bash/Azure CLI equivalents are equally visible and not relegated to secondary status.
- In sections where Windows-specific configuration is discussed, immediately follow with Linux equivalents, or use tabbed content for clarity.
- Audit for any subtle language that implies Windows is the default or primary platform, and rephrase for neutrality.
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 is generally cross-platform and covers both Windows and Linux scenarios for Azure Functions app settings. However, there are minor signs of Windows bias: some examples use Windows-style paths (e.g., %HOME%\typescript), Windows-specific settings are sometimes listed first, and PowerShell settings are documented in detail. There are also references to using Azure PowerShell and Azure CLI for managing settings, but CLI is mentioned alongside PowerShell. Most settings are OS-agnostic, and Linux-specific notes are present where relevant.
Recommendations
- When showing path examples (e.g., AzureWebJobs_TypeScriptPath), provide both Windows (e.g., %HOME%\typescript) and Linux (e.g., $HOME/typescript) formats.
- Where settings have OS-specific behaviors (e.g., WEBSITE_TIME_ZONE), ensure both Windows and Linux examples are shown side-by-side.
- When referencing tools for managing settings, mention Azure CLI before Azure PowerShell, or present both equally.
- For PowerShell-specific settings, clarify their applicability and provide equivalent guidance for other platforms/languages where possible.
- Review ordering of examples and settings to avoid listing Windows-specific options before Linux equivalents unless contextually necessary.
Azure Functions
host.json reference for Azure Functions 2.x
...b/main/articles/azure-functions/functions-host-json.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is largely cross-platform, but there are minor signs of Windows bias. PowerShell-based managed dependency is mentioned as a feature, and some references (such as environment variable examples and folder paths like %TEMP%) use Windows conventions. The documentation does not provide Linux/macOS-specific examples or clarify platform differences in areas like file paths or environment variable usage. Windows terminology (e.g., 'server host', '%TEMP%') appears before or without Linux equivalents.
Recommendations
- Add Linux/macOS equivalents for environment variable and folder path examples (e.g., $TMPDIR or /tmp instead of %TEMP%).
- Clarify that managed dependency is PowerShell-specific and provide links or notes for dependency management in other languages/platforms.
- Where file paths or environment variables are referenced, include both Windows and Linux/macOS conventions.
- If relevant, provide Linux/macOS examples for overriding settings, running locally, and other operational tasks.
- Review terminology to ensure platform neutrality (e.g., use 'host' instead of 'server host' where possible).
Azure Netapp Files
Azure NetApp Files for Azure Government
...b/main/articles/azure-netapp-files/azure-government.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides access instructions for Azure NetApp Files in Azure Government using the Azure portal, Azure CLI, REST API, and PowerShell. While the Azure CLI and REST API sections are platform-neutral, the PowerShell section is detailed and includes multiple connection examples, and PowerShell is a Windows-centric tool (though available on Linux/macOS). The PowerShell section appears after CLI and REST API, but the 'Next steps' section highlights PowerShell-specific REST API usage before mentioning general REST API documentation. There are no Linux/macOS-specific examples or mentions of tools like Bash, nor guidance for Linux users beyond CLI/REST.
Recommendations
- Add explicit Bash or shell examples for connecting to Azure Government using Azure CLI on Linux/macOS.
- Clarify that PowerShell Core is cross-platform and provide installation guidance for Linux/macOS users.
- Ensure parity in example depth between PowerShell and CLI sections (e.g., show equivalent resource management commands in both).
- In 'Next steps', list platform-neutral REST API documentation before PowerShell-specific usage.
Azure Functions
Storage considerations for Azure Functions
...ain/articles/azure-functions/storage-considerations.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for Azure Functions storage, but there are several instances of Windows-first bias. Windows hosting plans and settings are mentioned before Linux equivalents, and PowerShell examples are given alongside Azure CLI, sometimes with more detail. Some sections (such as Azure Files usage and scaling) emphasize Windows scenarios before Linux, and certain features are described as 'Windows only' without immediately clarifying Linux alternatives.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which is shown first.
- Ensure all features/settings are clearly marked as Windows-only or Linux-only, and provide Linux alternatives or workarounds where possible.
- Expand Linux-specific guidance, especially for mounting file shares and deployment scenarios.
- Where PowerShell is used, always provide equivalent Azure CLI or Bash examples.
- Clarify which hosting plans and features are available on Linux, and provide links to Linux-specific documentation where relevant.
Azure Netapp Files
Create a capacity pool for Elastic zone-redundant service in Azure NetApp Files
...icles/azure-netapp-files/elastic-capacity-pool-task.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page mentions PowerShell and the Az.NetAppFiles module explicitly in the 'Before you begin' section, including instructions and a link for updating the module. While Azure CLI and REST API are also referenced, PowerShell is called out separately and before REST API, with no equivalent Linux/macOS shell guidance (e.g., Bash, zsh). There are no command-line examples for any platform, but the explicit PowerShell mention may create a perception of Windows-first bias.
Recommendations
- Add explicit instructions or links for updating Azure CLI for Linux/macOS users, similar to the PowerShell guidance.
- Clarify that both Azure CLI and PowerShell are cross-platform, and provide parity in setup instructions for each.
- If relevant, include example commands for both Azure CLI (Bash/zsh) and PowerShell, or clarify that all steps can be performed in the Azure Portal regardless of OS.
- Consider reordering the 'Before you begin' section to list Azure CLI before PowerShell, or group them together as cross-platform options.