229
Pages Scanned
51
Pages Flagged
229
Changed Pages
22.3%
% Pages Flagged
Scan Information
Started At: 2026-01-25 00:00:09
Finished At: 2026-02-10 18:00:39
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 229
Files Completed: 229
Problematic Pages
51 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 tools, such as the use of New-SelfSignedCertificate and Export-PfxCertificate, which are only available on Windows. All code examples are in PowerShell, and there are no CLI, Bash, or Linux/macOS alternatives provided. The instructions for certificate creation and file paths (e.g., c:\appgwcert.pfx) are Windows-centric, making it difficult for Linux/macOS users to follow the tutorial without significant adaptation.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource creation and management steps.
- Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting them to PFX format.
- Use platform-neutral file paths in examples, or clarify how to adapt them for Linux/macOS.
- Add notes or sections explicitly addressing how Linux/macOS users can complete each step.
- Consider offering downloadable scripts or templates for both PowerShell and Bash/CLI.
Create Pull Request
Load Balancer
Tutorial: Protect your public load balancer with Azure DDoS Protection
...s/load-balancer/tutorial-protect-load-balancer-ddos.md
High Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The tutorial exclusively uses Windows Server VM images and provides only Windows PowerShell commands for installing and configuring IIS. There are no Linux VM options, nor are there Bash or Linux-native instructions for web server setup. Windows-specific tools (PowerShell, IIS) are mentioned and used without Linux equivalents or alternatives.
Recommendations
- Provide parallel instructions for deploying Linux VMs (e.g., Ubuntu) in the backend pool.
- Include Bash commands for installing and configuring a web server (such as Apache or Nginx) on Linux VMs.
- Offer users a choice between Windows and Linux VM images during the VM creation steps.
- Add screenshots and example outputs for Linux-based web server configuration and testing.
- Clarify that IIS/Windows is used for demonstration, but Linux alternatives are fully supported.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS upgrades, but Windows instructions and references (including PowerShell cmdlets and registry settings) are presented first and more frequently. Backup and retention examples rely heavily on Windows PowerShell cmdlets, with no equivalent CLI or Linux-native examples. References to asset management and DSC node removal use Windows PowerShell cmdlets exclusively.
Recommendations
- Provide Azure CLI or REST API examples alongside PowerShell cmdlets for backup/export and asset management tasks.
- Include Linux/macOS-specific instructions or scripts for tasks like exporting runbooks, DSC configurations, and managing assets.
- Balance the order of presentation so Linux examples are not consistently secondary to Windows examples.
- Reference cross-platform tools and commands (e.g., az CLI, Bash scripts) where possible.
Automation
Manage certificates in Azure Automation
...n/articles/automation/shared-resources/certificates.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page for managing certificates in Azure Automation demonstrates a notable Windows/PowerShell bias. Most examples and instructions use PowerShell cmdlets, which are traditionally associated with Windows environments. The creation and management of certificates are shown almost exclusively with PowerShell, and PowerShell examples are presented first. There is minimal mention of Linux/macOS workflows, and no CLI, Bash, or Linux-native tooling is referenced. Python examples are provided, but only for accessing certificates in runbooks, not for certificate creation or management.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) to support Linux/macOS users.
- Include Bash or shell script examples where possible, especially for uploading certificates or interacting with Azure Automation.
- Clarify whether PowerShell examples are cross-platform (i.e., usable on PowerShell Core on Linux/macOS), and provide guidance for non-Windows users.
- Explicitly mention any platform limitations, and provide alternative workflows for Linux/macOS users if certain features are Windows-only.
- Consider reordering examples so that platform-neutral or cross-platform approaches are presented before Windows/PowerShell-specific ones.
Automation
Configure runbook input parameters in Azure Automation
...b/main/articles/automation/runbook-input-parameters.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling, with nearly all examples, code snippets, and workflows using PowerShell cmdlets and patterns. There is minimal mention of Linux/macOS workflows, and no Bash, CLI, or cross-platform examples for starting or interacting with runbooks. Python runbooks are briefly mentioned, but only in the context of parameter passing, not in terms of how to invoke or manage them from Linux/macOS environments.
Recommendations
- Add Azure CLI examples for starting runbooks and passing parameters, demonstrating usage on Linux/macOS.
- Include Bash or shell script samples for interacting with the REST API to start runbooks and assign parameters.
- Clarify which features and workflows are cross-platform and which are Windows/PowerShell-specific.
- Provide parity in examples for Python runbooks, including how to invoke them from Linux/macOS environments.
- Mention any platform-specific limitations or differences explicitly, so users know what is supported on their OS.
Azure Resource Manager
Relocate Azure Virtual Machine Scale Sets to another region
...nt/relocation/relocation-virtual-machine-scale-sets.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides instructions for relocating Azure Virtual Machine Scale Sets but consistently references the Azure portal and PowerShell/ARM templates without offering Linux/macOS-specific command-line examples (e.g., Azure CLI bash commands). The use of screenshots and instructions is portal-centric, which is platform-agnostic, but when mentioning Infrastructure as Code tools, PowerShell is listed alongside Azure CLI and ARM templates, with no explicit Linux/macOS shell examples or guidance. There are no references to Linux-specific tools or workflows, and example commands/scripts are absent.
Recommendations
- Add explicit Azure CLI bash examples for key steps, such as exporting and deploying templates, to ensure Linux/macOS users have parity.
- Clarify that all steps can be performed using Azure CLI on any platform, not just PowerShell or the Azure portal.
- When listing Infrastructure as Code tools, mention Azure CLI first or equally with PowerShell, and provide sample commands for both.
- Include notes or links to cross-platform documentation for template export and deployment.
Azure Resource Manager
Relocation guidance for Azure Firewall
...e-manager/management/relocation/relocation-firewall.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides step-by-step guidance for relocating Azure Firewall, with examples and automation instructions exclusively using Azure PowerShell. There are no CLI (az) or Bash examples, and all scripting guidance is PowerShell-centric, which is more familiar and accessible to Windows users. This creates friction for Linux/macOS users who typically use Bash and Azure CLI for automation.
Recommendations
- Add equivalent Azure CLI (az) examples for all template export, modification, and deployment steps.
- Include Bash shell commands for template handling (e.g., unzipping, file editing) alongside PowerShell instructions.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI and provide links to relevant CLI documentation.
- Consider reordering or parallelizing examples so CLI/Bash instructions are not secondary to PowerShell.
Backup
Support matrix for Azure VM backups
...lob/main/articles/backup/backup-support-matrix-iaas.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides comprehensive coverage of both Windows and Linux Azure VM backup scenarios, but there are notable signs of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are described in detail, with examples and restore methods often referencing PowerShell and Windows-centric workflows. Linux support is covered, but Linux-specific limitations and exclusions are listed more than actionable guidance. Windows examples and tools are mentioned first and more frequently, and Linux alternatives (where available) are not always given equal detail or prominence.
Recommendations
- Provide Linux CLI or script examples alongside PowerShell references, especially in restore workflows.
- Add more actionable Linux backup and restore scenarios, including step-by-step guides for common tasks.
- Where Windows tools (MARS agent, DPM, MABS) are mentioned, clarify Linux alternatives or explicitly state their absence and suggest best practices for Linux users.
- Balance the order of presentation so Linux support is not consistently listed after Windows support.
- Expand documentation on Linux-specific backup limitations with troubleshooting and mitigation steps.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation provides command-line examples for managing API Management multi-region deployments using Azure CLI and Azure PowerShell, but does not mention or provide examples for Linux/macOS shell environments or tools. PowerShell is referenced explicitly, and the Azure CLI examples use the 'azurecli' code block, but there is no discussion of shell differences or Linux-specific considerations. The order of tool mention often puts PowerShell before CLI, and no Bash or Linux-specific guidance is given.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide Bash shell examples where appropriate.
- When referencing PowerShell, explicitly state that it is available on Linux/macOS, or provide equivalent Bash or shell commands for common tasks.
- Avoid listing PowerShell before CLI unless there is a technical reason; consider listing CLI first as it is more universally available.
- Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and PowerShell Core.
- Where screenshots or UI instructions are given, clarify if any steps differ for Linux/macOS users.
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 only to an Azure PowerShell tutorial for creating an autoscaling, zone redundant application gateway. No equivalent example or guidance is provided for Linux/macOS users using Azure CLI, which is cross-platform. This creates friction for non-Windows users who may not have access to PowerShell or prefer CLI tools.
Recommendations
- Add links or examples for creating autoscaling, zone redundant application gateways using Azure CLI, which is available on Linux and macOS.
- Ensure that tutorials and walkthroughs cover both PowerShell and CLI approaches, or clarify platform requirements where relevant.
- Consider listing CLI examples before or alongside PowerShell examples to promote parity.
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 generally covers both Windows and Linux, but there is a consistent pattern of Windows-specific details, tools, and paths being mentioned first or exclusively in several sections. Some examples and descriptions use Windows paths (e.g., D:\home), reference Windows tools (e.g., msbuild, Web Deploy/MSDeploy), or focus on IIS and Windows-specific behaviors. In some cases, Linux equivalents are mentioned, but often as an afterthought or with less detail. There are also sections where only Windows tools or patterns are described, and Linux users must infer or seek out external documentation.
Recommendations
- Ensure that all examples and environment variable descriptions provide both Windows and Linux paths and behaviors where applicable, with equal prominence.
- When referencing Windows tools (e.g., msbuild, Web Deploy), also mention Linux equivalents (e.g., Oryx, Kudu for Linux) and provide links or brief explanations.
- Avoid defaulting to Windows paths or terminology (e.g., D:\home) in general sections; instead, show both (e.g., D:\home (Windows), /home (Linux)).
- Where tabs are used for Windows and Linux (e.g., Kudu vs. Oryx), ensure both are equally detailed and easy to find.
- Add Linux/macOS-specific examples and troubleshooting notes where only Windows is currently covered.
- Review for sections where Windows-only features are described without a Linux note, and clarify platform applicability.
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
missing_linux_example
Summary
The documentation for Azure Application Gateway v2 shows a notable bias towards Windows/PowerShell tooling. Migration guidance and preview registration/unregistration steps are provided only as Azure PowerShell commands, with no equivalent Azure CLI (bash) or ARM template examples. The main tutorial link also points to a PowerShell-based guide, and there are no Linux/macOS-specific instructions or examples. This creates friction for users on Linux or macOS who prefer or require bash/CLI workflows.
Recommendations
- Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for migration and preview registration/unregistration.
- Include links to tutorials using Azure CLI, ARM templates, or the Azure Portal for cross-platform parity.
- Explicitly state that both PowerShell and CLI can be used, and clarify any platform-specific requirements.
- Add examples or notes for Linux/macOS users where workflows or commands differ.
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
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets, with all migration instructions, examples, and downloadable tools provided exclusively in PowerShell. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are Linux/macOS-specific instructions or examples given. The installation and usage patterns assume a Windows/PowerShell environment, creating friction for users on Linux or macOS who may prefer or require Bash or Azure CLI.
Recommendations
- Provide equivalent Azure CLI scripts and examples for all migration steps, including configuration cloning and public IP retention.
- Add explicit instructions for running PowerShell scripts on Linux/macOS (e.g., using PowerShell Core), including prerequisites and troubleshooting tips.
- Offer Bash script alternatives or at least document how to adapt the PowerShell scripts for Bash/CLI environments.
- Include notes or sections highlighting cross-platform compatibility and any limitations for non-Windows users.
- Present examples for both PowerShell and Azure CLI, and alternate their order or group them together to avoid 'windows_first' bias.
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 instructions for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions are presented first and in greater detail than Azure CLI, and the 'Next steps' section directs users to a PowerShell-specific guide. There is no mention of Linux/macOS-specific tools or workflows, and the CLI example is minimal compared to PowerShell. No Linux or macOS certificate management tools (e.g., OpenSSL) are referenced for extracting or preparing certificates.
Recommendations
- Provide equally detailed Azure CLI examples alongside PowerShell, including step-by-step instructions for all major configuration tasks.
- Include references or examples using cross-platform tools (such as OpenSSL) for certificate extraction and management.
- In 'Next steps', offer links to CLI and ARM template/Bicep guides, not just PowerShell.
- Explicitly mention that both PowerShell and CLI are cross-platform, and clarify any platform-specific limitations if present.
- Ensure that instructions for certificate file preparation (PEM/CER) include Linux/macOS workflows.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation repeatedly references an Azure PowerShell script as the primary or sole migration tool for Application Gateway V1 to V2, without 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 explicitly state if CLI support is unavailable.
- Include Bash or cross-platform script examples where possible, or clarify PowerShell Core compatibility on Linux/macOS.
- Add a section outlining migration options for Linux/macOS users, including prerequisites for running PowerShell scripts cross-platform.
- If PowerShell is required, link to documentation on installing and using PowerShell Core on Linux/macOS.
Automation
Disaster recovery for Azure Automation
...in/articles/automation/automation-disaster-recovery.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides disaster recovery guidance for Azure Automation that applies to both Linux and Windows VMs. However, all migration scripts and runbook examples are exclusively PowerShell-based, with no mention of Bash, Python, or CLI alternatives. The only automation asset migration tools referenced are PowerShell scripts and workflows, and all step-by-step instructions assume use of PowerShell. There are no Linux-native scripting examples or guidance for users who prefer Bash or Python, which creates friction for Linux-focused users.
Recommendations
- Provide equivalent migration scripts or runbooks using Azure CLI, Bash, or Python for users who do not use PowerShell.
- Explicitly mention if PowerShell is the only supported method for asset migration, and provide guidance for Linux users on how to install and use PowerShell Core if necessary.
- Add examples or references for Linux/macOS users, such as using PowerShell Core on Linux, or alternative approaches using REST API or Azure CLI.
- Clarify in the prerequisites that PowerShell is required, and link to instructions for installing PowerShell on Linux/macOS if no alternatives exist.
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 PowerShell and Windows-centric tooling, with all code examples and module references using PowerShell. There are no Bash, CLI, or Linux/macOS-specific examples or guidance. Windows terminology (e.g., 'Windows PowerShell') is used, and Linux alternatives are not mentioned, which may create friction for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for credential management and runbook authentication.
- Clarify which steps are platform-agnostic and which require Windows/PowerShell, and provide alternatives where possible.
- Include notes or links for Linux/macOS users on how to perform similar tasks using supported tools.
- If Azure Automation supports Python runbooks or other languages, mention and provide examples.
- Avoid using 'Windows PowerShell' terminology when referring to cross-platform PowerShell Core, unless specifically required.
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 cmdlets and Windows tooling for managing credentials in Azure Automation. All CLI examples are PowerShell-based, and references to creating credentials outside the portal are exclusively via Windows PowerShell. The documentation does mention Python runbooks, but there are no examples or guidance for Linux/macOS shell environments or cross-platform CLI tools (e.g., Azure CLI, Bash). Windows/PowerShell tools are presented first and in greater detail.
Recommendations
- Add examples for creating and managing credential assets using Azure CLI, which is cross-platform and works on Linux/macOS.
- Clarify which steps or cmdlets are PowerShell-specific and provide alternative instructions for Linux/macOS users where possible.
- Include Bash or shell scripting examples for credential retrieval and usage, if supported.
- Explicitly state platform requirements for PowerShell-based steps, and link to cross-platform alternatives.
- Ensure parity in example detail and guidance for Python runbooks and other supported languages.
Azure Change Tracking Inventory
Azure Change Tracking and Inventory Overview by Using Azure Monitor Agent
...change-tracking-inventory/overview-monitoring-agent.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a general overview of Azure Change Tracking and Inventory with the Azure Monitor Agent, stating support for both Windows and Linux. However, there is a notable Windows bias: registry key tracking is described in detail with a large table of Windows registry keys, while no equivalent Linux configuration tracking (e.g., for /etc files or systemd units) is mentioned. Windows terminology and features (e.g., registry, Internet Explorer, explorer.exe) are explained, but Linux-specific examples or details are absent. The file tracking and inventory sections mention both OSes, but examples and screenshots do not clarify Linux-specific scenarios.
Recommendations
- Add examples of Linux-specific configuration tracking, such as monitoring changes to /etc/passwd, /etc/ssh/sshd_config, or systemd service files.
- Include a table or list of commonly tracked Linux files or directories, analogous to the Windows registry key table.
- Provide explicit Linux examples/screenshots for file change and inventory tracking, showing how the feature works on Linux systems.
- Clarify any Linux limitations or differences in feature support compared to Windows.
Azure Resource Manager
Relocate an Azure Container Registry to another region
...management/relocation/relocation-container-registry.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation includes several PowerShell-specific commands (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without providing equivalent Bash/Azure CLI or cross-platform alternatives. In some sections, PowerShell commands are presented before or instead of Azure CLI examples, and there is at least one instance where only a PowerShell command is given for a key step. This creates friction for Linux/macOS users who may not have access to or familiarity with Azure PowerShell modules.
Recommendations
- For every PowerShell command provided, include an equivalent Azure CLI or Bash example, especially for common tasks like listing repositories or importing images.
- When referencing both Azure CLI and PowerShell, present Azure CLI (which is cross-platform) examples first, or clearly indicate both options.
- Audit the documentation to ensure that all critical steps can be completed using cross-platform tools, and explicitly mention if a step is only possible with PowerShell.
- Where possible, use Bash scripting for automation examples, as it is more universally accessible across platforms.
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 and in detail for feature registration, with only a brief mention of Azure CLI as an alternative. The step-by-step instructions and screenshots are focused on the Azure Portal GUI, which is platform-agnostic, but the command-line guidance is Windows/PowerShell-centric. There are no explicit Linux/macOS command examples, and the CLI alternative is referenced only via a link, not shown inline.
Recommendations
- Provide explicit Azure CLI command examples alongside PowerShell for feature registration and status checks.
- Show both PowerShell and CLI commands in parallel, or indicate which is recommended for Linux/macOS users.
- Add a note clarifying that all portal steps are cross-platform and accessible from any OS.
- Consider ordering CLI and PowerShell examples together, or alternate which is shown first.
Backup
About the Azure Virtual Machine restore process
...cs/blob/main/articles/backup/about-azure-vm-restore.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page describes the Azure VM restore process in a mostly OS-neutral way, but the 'Restore an encrypted VM' scenario exclusively references Windows VM encryption and PowerShell-based restoration, with no mention of Linux VM disk encryption or Linux restoration workflows. Additionally, the encrypted VM restore scenario links only to Windows-specific documentation, and PowerShell is presented as the sole automation tool for restoring encrypted VMs, with no Bash, CLI, or Linux-native alternatives. This creates friction for Linux VM users seeking parity in encrypted VM restore guidance.
Recommendations
- Add equivalent guidance for restoring encrypted Linux VMs, including links to Linux disk encryption documentation and restore workflows.
- Provide examples using Azure CLI or Bash scripts for restoring encrypted VMs, not just PowerShell.
- Clarify in the encrypted VM restore scenario whether Linux VMs are supported, and if not, explicitly state the limitation.
- Ensure restore scenarios and linked documentation cover both Windows and Linux VM types where applicable.
Backup
Back Up and Restore Encrypted Azure VMs
...ob/main/articles/backup/backup-azure-vms-encryption.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation generally covers both Windows and Linux Azure VMs, including references to ADE (BitLocker for Windows, dm-crypt for Linux). However, there is a notable Windows bias in the 'Provide permissions' section, where the PowerShell example to identify a VM's associated key vault is given first and exclusively, without an equivalent Azure CLI or Bash example. This may create friction for Linux/macOS users who prefer CLI or Bash commands. Additionally, PowerShell is mentioned before Azure CLI in the context of setting access policies.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell commands, especially for tasks like identifying the associated Key Vault.
- When referencing automation options (e.g., setting access policies), mention Azure CLI and Bash alternatives before or alongside PowerShell.
- Ensure screenshots and instructions are OS-agnostic or clarify when steps differ for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively describes the use of the MARS agent (Windows-only) and DPM/MABS (Windows-based tools) for on-premises backups, with explicit statements that Linux machines aren't supported for direct backup. There are no Linux backup agent options or Linux-specific examples provided for on-premises scenarios, and Windows tools are referenced first and exclusively. However, for Azure VM backups, the documentation is OS-agnostic, and Linux is referenced in the context of managed disks.
Recommendations
- Clarify in the 'Back up on-premises machines' section that direct backup of Linux machines is not supported, and provide guidance or references for Linux backup strategies (e.g., using third-party tools, Azure File Sync, or custom scripts).
- If Azure Backup now supports any Linux on-premises backup scenarios, add documentation and examples for those workflows.
- In tables and feature lists, explicitly indicate Linux support status for each backup method, rather than omitting Linux entirely.
- Consider adding a short section or FAQ entry addressing common Linux backup needs and Azure-compatible solutions, even if Azure Backup does not natively support them.
Backup
Restore VMs by using the Azure portal using Azure Backup
...b/main/articles/backup/backup-azure-arm-restore-vms.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides a generally cross-platform overview of restoring Azure VMs using the portal, but there are several areas where Windows bias is evident. PowerShell is frequently referenced as the automation/CLI method, often without mentioning Azure CLI or Bash alternatives. Many links and examples for advanced scenarios (e.g., restoring with special network configurations, availability sets, or post-restore steps) point to Windows-specific guides or use PowerShell. Some sections (like resetting static IPs or restoring special VMs) reference Windows-centric tools or documentation first, and Linux-specific guidance is minimal or absent. There are also post-restore steps and troubleshooting commands that are Windows-specific, with no Linux equivalents provided.
Recommendations
- Where PowerShell is referenced as a method to create or restore VMs, add equivalent Azure CLI and/or Bash examples and links, especially for Linux users.
- When linking to guides for creating VMs from restored disks, include both Windows and Linux documentation (e.g., /azure/virtual-machines/linux/attach-managed-disk-portal alongside the Windows link).
- In post-restore steps, provide Linux-specific guidance for common tasks (e.g., resetting static IPs, rejoining domains, troubleshooting boot issues) and reference relevant Linux documentation.
- For sections on restoring special VMs (e.g., SQL VMs, domain controllers), clarify when steps are Windows-only and provide Linux alternatives or explicitly state if not applicable.
- Review all automation and scripting references to ensure both PowerShell and Azure CLI are covered, or clarify when only one is supported.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation covers restoring both Windows and Linux encrypted Azure VMs, but there is a notable bias towards Windows/PowerShell workflows. In the 'Recreate the virtual machine instance' section, only PowerShell is mentioned for creating a VM from restored disks, with no Linux/CLI or Azure CLI example provided. Additionally, the step for swapping the OS disk links to a Windows-specific article. The Linux-specific restore instructions are brief and lack detailed, step-by-step guidance or command examples, while Windows/PowerShell options are more explicitly referenced.
Recommendations
- Add Azure CLI and/or Bash examples for creating a VM from restored disks, alongside or before PowerShell examples.
- Provide a Linux-specific step-by-step guide (with command examples) for restoring and reconfiguring ADE on Linux VMs, including how to reinstall the ADE extension.
- Where possible, link to Linux documentation for tasks like swapping the OS disk, not just Windows guides.
- Ensure that Linux and Windows instructions are presented with equal detail and prominence.
Event Grid
Troubleshoot network connectivity issues - Azure Event Grid | Microsoft Docs
...ticles/event-grid/troubleshoot-network-connectivity.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation frequently presents Windows/PowerShell examples and tools (e.g., psping.exe) first, with Linux alternatives either mentioned after or omitted. Some troubleshooting commands are only shown for Windows (psping.exe), while Linux users are only briefly referenced (telnet) without parity in advanced troubleshooting steps. The use of Windows-specific tools and the lack of equivalent Linux/macOS commands in some sections create friction for non-Windows users.
Recommendations
- Provide Linux/macOS equivalents for all troubleshooting commands, such as using 'nc' (netcat) or 'nmap' for port checks and connection tests.
- When introducing tools like psping.exe, also mention cross-platform alternatives (e.g., 'hping3', 'nc', or 'nmap') and provide example commands.
- Ensure that Linux/macOS examples are given equal prominence, ideally presenting both Windows and Linux/macOS commands side by side.
- Avoid referencing Windows tools (like .exe utilities) without Linux/macOS counterparts, or clearly state if a step is Windows-only and provide alternatives where possible.
Event Hubs
Geo-disaster recovery - Azure Event Hubs| Microsoft Docs
...ocs/blob/main/articles/event-hubs/event-hubs-geo-dr.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides platform-specific instructions for manual failover using Azure portal, CLI, PowerShell, and C#. While the Azure CLI is cross-platform, PowerShell and C# are Windows-centric and are listed before Linux-native options (such as Bash scripting or REST API usage). There are no explicit Linux/macOS examples, and no mention of Linux tools or workflows. The sample code references are .NET/C# and Java, but operational examples (e.g., scripting failover) are Windows-first.
Recommendations
- Add explicit Linux/macOS examples for scripting failover, such as using Bash with Azure CLI or REST API.
- Clarify that Azure CLI commands work on Linux/macOS and provide sample Bash scripts.
- Include REST API examples for failover operations, which are platform-neutral.
- Balance the order of examples so that cross-platform tools (CLI, REST API) are shown before Windows-centric tools (PowerShell, C#).
- Reference Linux/macOS automation scenarios in the 'Manual failover' section.
DNS
Resolve Azure and on-premises domains.
.../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides step-by-step guidance for configuring hybrid DNS resolution between Azure and on-premises environments. However, when detailing the configuration of on-premises DNS conditional forwarders, only Windows DNS Server is shown in the example, with no mention or example for Linux-based DNS servers (such as BIND or dnsmasq). Additionally, the only illustrated procedure for on-premises DNS is Windows-centric, and Linux alternatives are not referenced or linked.
Recommendations
- Add a section or example for configuring conditional forwarders on common Linux DNS servers (e.g., BIND/named, dnsmasq, or Unbound).
- Explicitly state that the procedure for on-premises DNS applies to both Windows and Linux DNS servers, and provide links to relevant Linux DNS documentation.
- Where possible, show both Windows and Linux DNS configuration screenshots or command-line examples side by side.
- Clarify in the 'Configure on-premises DNS conditional forwarders' section that the example is for Windows DNS, and mention that similar steps can be performed on Linux DNS servers.
Expressroute
About ExpressRoute virtual network gateways
...ssroute/expressroute-about-virtual-network-gateways.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for ExpressRoute virtual network gateways demonstrates a moderate Windows bias. PowerShell is the only command-line example shown for gateway subnet creation, and the REST API/PowerShell section lists only PowerShell resources (no Azure CLI or Linux/macOS shell equivalents). There are no Azure CLI or Bash examples, and Windows-centric tools (PowerShell) are referenced exclusively for configuration tasks.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line tasks, especially for gateway subnet creation.
- Include Bash or shell script equivalents where relevant.
- In the REST APIs and command-line tools section, provide links and examples for Azure CLI and Bash, not just PowerShell.
- Ensure that configuration guidance is not exclusively presented in PowerShell syntax; alternate with CLI examples or present both together.
Load Balancer
Move an Azure Load Balancer to another Azure region
...ad-balancer/move-across-regions-azure-load-balancer.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides detailed instructions for moving an Azure Load Balancer to another region using the Azure portal and Azure PowerShell. While the portal instructions are cross-platform, all CLI-based automation examples are exclusively in Azure PowerShell. There are no Azure CLI (az) or Bash/Linux shell examples, which are preferred by many Linux/macOS users. The PowerShell instructions assume use of Windows tools (e.g., notepad.exe), and no alternative editors or shell environments are mentioned.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell steps, including resource export, deployment, and verification.
- When referencing file editing, suggest cross-platform editors (e.g., code, nano, vim) or note that any text editor can be used.
- Explicitly state that all steps can be performed from Linux/macOS using Azure CLI and provide those instructions.
- Where possible, provide Bash shell command snippets alongside PowerShell, or link to Azure CLI documentation for template deployment.
- Clarify that Azure PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
Load Balancer
Quickstart: Create a public load balancer - ARM template
...r/quickstart-load-balancer-standard-public-template.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash instructions. The step-by-step deployment section is written for PowerShell users, and the screenshots and output are PowerShell-centric. Although the Azure portal and CLI are mentioned as alternatives, no concrete examples or guidance are given for Linux/macOS users.
Recommendations
- Add Azure CLI (az) example commands for deploying the ARM template, alongside the PowerShell example.
- Present both PowerShell and CLI/Bash examples side-by-side, or clearly indicate which steps are platform-specific.
- Include screenshots or output examples from Azure CLI/Bash where relevant.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and guide users to select their preferred shell.
Load Balancer
Outbound-only load balancer configuration
...e-docs/blob/main/articles/load-balancer/egress-only.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively provides instructions for creating and configuring a Windows Server 2022 VM, with no mention of Linux VM options or examples. All testing steps assume a Windows environment (e.g., using Microsoft Edge), and there are no Linux-specific notes, commands, or parity guidance. This creates friction for Linux users who wish to follow the same process.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu or CentOS) in the 'Create virtual machine' section, including appropriate image selection and authentication options.
- Include Linux-specific testing steps (e.g., using Firefox or curl/wget from the command line to verify outbound connectivity).
- Clarify that the load balancer configuration is OS-agnostic and works for both Windows and Linux VMs.
- Where screenshots or UI steps reference Windows-specific elements, add notes or examples for Linux VM creation and management.
- Explicitly state that the process applies to both Windows and Linux, and provide links to Linux VM documentation.
Load Balancer
Quickstart: Create a public load balancer - Bicep
...ncer/quickstart-load-balancer-standard-public-bicep.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell deployment instructions, but PowerShell is shown as an alternative rather than the primary method. The example VMs are configured with IIS (Internet Information Services), which is Windows-specific, and there are no examples or notes for deploying Linux VMs or using Linux-native web servers (e.g., Apache, Nginx). There are no Linux shell-specific instructions or troubleshooting notes, and the test step assumes IIS is present.
Recommendations
- Add an explicit Linux VM deployment example in the Bicep file, or provide a note on how to modify the template to deploy Linux VMs (e.g., Ubuntu) and install a Linux web server (Apache or Nginx).
- Include a section or tabbed instructions for testing the load balancer with a Linux-based web server, showing the expected default page.
- If using PowerShell, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider providing Bash shell command examples for common tasks (e.g., file downloads, template deployment) where relevant.
Load Balancer
Quickstart: Create a public load balancer - Azure portal
...cer/quickstart-load-balancer-standard-public-portal.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides step-by-step instructions for creating a public load balancer in the Azure portal, but the section on configuring the backend VMs is exclusively Windows-focused. It instructs users to install IIS using Windows PowerShell, with no mention of Linux VMs or how to configure a Linux-based web server (e.g., Apache or Nginx). All provided scripts and screenshots are Windows-centric, and there are no Linux equivalents or alternative instructions.
Recommendations
- Add parallel instructions for deploying and configuring Linux VMs in the backend pool, including steps to install a web server (e.g., Apache or Nginx) and create a test index.html file.
- Provide Bash shell commands for Linux VM setup, similar to the PowerShell commands given for Windows.
- Include screenshots or notes indicating that both Windows and Linux VMs are supported as backend pool members.
- Explicitly state that the backend VMs can be either Windows or Linux, and link to relevant documentation for Linux VM setup if not included inline.
Load Balancer
Tutorial: Create a public load balancer with an IP-based backend - Azure portal
...d-balancer/tutorial-load-balancer-ip-backend-portal.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides only Windows Server VM creation instructions and exclusively uses Windows PowerShell commands to install IIS for testing. There are no examples or guidance for deploying Linux VMs or using Linux-native web servers (e.g., Apache, Nginx) for the backend pool, nor are there Bash/SSH examples. This creates friction for users preferring or required to use Linux VMs.
Recommendations
- Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in the 'Create virtual machines' section.
- Provide Linux-based examples for installing a web server (e.g., using SSH and apt to install Apache or Nginx, and echoing a custom index.html).
- Show both Windows and Linux options for backend pool configuration and testing, or clarify that either OS can be used.
- Explicitly mention that the load balancer works with both Windows and Linux VMs, and link to relevant Linux VM documentation.
Data Share
Tutorial: Share outside your org - Azure Data Share
...-docs/blob/main/articles/data-share/share-your-data.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and some examples (such as file upload paths) use Windows-style paths (e.g., D:\testFiles\textfile.csv) without mentioning Linux/macOS equivalents. Additionally, PowerShell examples and references are given equal prominence to Azure CLI, and sometimes appear before CLI in the tab order, which may subtly prioritize Windows tooling. There are no explicit Linux/macOS examples (e.g., Bash, Linux file paths) for local file operations.
Recommendations
- Add explicit Linux/macOS examples for file paths and local operations (e.g., use /home/user/testFiles/textfile.csv alongside D:\testFiles\textfile.csv).
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and highlight any OS-specific considerations.
- Consider adding Bash examples for common operations, especially for file uploads to Azure Storage.
- When showing PowerShell examples, note that PowerShell Core is available cross-platform, but provide guidance for Linux/macOS users where relevant.
- Ensure tab order does not always put PowerShell before CLI, or clarify that CLI is the recommended cross-platform approach.
Load Balancer
Tutorial: Create a single virtual machine inbound NAT rule - Azure portal
...ancer/tutorial-load-balancer-port-forwarding-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides SSH connection instructions for both Mac/Linux (Bash prompt) and Windows (PowerShell prompt) users. However, the SSH command examples use Windows path syntax ('.\Downloads\lb-key-pair.pem'), and the instructions present the Windows/PowerShell context first, which may create minor friction for Linux/macOS users. No Windows-only tools or patterns are used, and Linux-specific steps (such as installing NGINX via apt-get) are included.
Recommendations
- Provide separate SSH command examples for Windows (PowerShell) and Linux/macOS (Bash), using appropriate path syntax (e.g., './Downloads/lb-key-pair.pem' for Linux/macOS).
- Explicitly show both sets of commands side-by-side or in tabs to improve clarity for users on different platforms.
- Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
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 detailed Azure portal instructions (which are cross-platform), then offers PowerShell examples before Azure CLI examples for scripting tasks. PowerShell is Windows-centric, while Azure CLI is cross-platform. No Linux/macOS-specific tools or shell examples are given, but all critical tasks are covered via the portal and CLI. There are no exclusive Windows tools or patterns, but the ordering and prominence of PowerShell may create a mild Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Where possible, add Bash shell script snippets for common tasks to further support Linux/macOS users.
- Clarify that PowerShell Core is available cross-platform, if relevant, or link to instructions for using Azure CLI on Linux/macOS.
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 instructions and examples for both Windows and Linux. However, there are minor instances of Windows bias: Windows deployment/configuration commands and runtime identifiers are presented before Linux equivalents, and some CLI examples default to Windows terminology. Windows tools (e.g., Visual Studio) are mentioned before Linux alternatives (e.g., VS Code, Azure CLI), and some ReadyToRun and debugging instructions are Windows-centric before Linux is addressed.
Recommendations
- Ensure Linux examples and instructions are presented alongside or before Windows equivalents, especially in deployment, configuration, and performance optimization sections.
- Where CLI commands are shown, provide both Windows and Linux syntax in parallel tabs or sections.
- Highlight cross-platform tools (VS Code, Azure CLI) equally or before Windows-only tools (Visual Studio) when listing options.
- In tables and lists, alternate the order of Windows and Linux to avoid implicit prioritization.
- Add explicit notes that all major features and workflows are supported on both Windows and Linux, unless otherwise stated.
Azure Functions
App settings reference for Azure Functions
...ain/articles/azure-functions/functions-app-settings.md
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is generally cross-platform and includes Linux-specific content and settings. However, there are minor instances of Windows bias: some examples and explanations present Windows first (e.g., in the WEBSITE_TIME_ZONE table), and a few settings reference Windows paths or behaviors (e.g., AzureWebJobs_TypeScriptPath uses a Windows-style path). Some legacy or platform-specific settings are clearly marked as Windows-only, but these are not the focus of the page. There is a slight preference for mentioning Windows or Windows tools first in a few places, but Linux parity is mostly maintained.
Recommendations
- When showing OS-specific examples (such as paths or time zones), always provide both Windows and Linux/macOS equivalents, or show Linux first if usage is common.
- For settings like AzureWebJobs_TypeScriptPath, provide a Linux-style path example alongside the Windows one.
- Where behaviors differ between Windows and Linux (e.g., delimiter handling in app setting names), consider highlighting Linux behavior first or equally.
- Continue to clearly mark Windows-only settings as such, and ensure Linux/macOS users are directed to equivalent settings or documentation where applicable.
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
powershell_heavy
windows_tools
windows_first
Summary
The documentation is mostly cross-platform, but there are some areas of Windows bias. The 'managedDependency' feature is described as PowerShell-only, and references to Windows-specific tools and environment variables (e.g., %TEMP%, LOCALAPPDATA, APPDATA) appear in snapshot configuration. In the explanation of tempFolder and shadowCopyFolder, Windows environment variables are mentioned first, with no explicit Linux/macOS equivalents. The ordering of examples and references sometimes favors Windows conventions (e.g., timespan format, environment variable naming), and there is little explicit mention of Linux/macOS paths or conventions.
Recommendations
- Clarify when features are Windows-only or PowerShell-only, and provide Linux/macOS alternatives or explicitly state when none exist.
- When referencing environment variables or file paths, include both Windows and Linux/macOS equivalents (e.g., $HOME, /tmp).
- Add examples or notes for Linux/macOS users where file paths, environment variables, or behaviors differ.
- Ensure ordering of examples and references does not consistently favor Windows conventions when the feature is cross-platform.
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 is generally cross-platform and covers both Windows and Linux hosting scenarios for Azure Functions. However, there are instances of Windows bias, such as Windows-specific plans being mentioned first, and PowerShell examples being provided alongside Azure CLI, even in Linux-only sections. Some minor friction exists for Linux users, but most guidance is applicable to both platforms.
Recommendations
- When listing hosting plans or features, alternate or balance the order between Windows and Linux to avoid implicit prioritization.
- In sections specifically about Linux functionality (e.g., mounting file shares), consider providing Bash or Linux-native examples before PowerShell, or clarify that PowerShell is cross-platform.
- Where PowerShell is shown, ensure that equivalent Bash/CLI examples are present and clearly marked for Linux/macOS users.
- Explicitly note platform differences or limitations where relevant, to help users quickly identify applicable guidance.
Azure Resource Manager
Template functions - resources
...ource-manager/templates/template-functions-resource.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for discovering list operations, but the PowerShell (Windows-centric) example is presented before the Azure CLI (cross-platform) example. No other evidence of Windows bias is present; all code samples are in JSON ARM template syntax, which is platform-agnostic.
Recommendations
- Present Azure CLI examples before PowerShell examples, or provide both side-by-side to emphasize cross-platform parity.
- Explicitly note that Azure CLI is available on Linux/macOS/Windows when giving CLI examples.
- Where possible, link to cross-platform deployment guides (e.g., deploying ARM templates with Azure CLI) in the 'Next steps' section.
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The Azure Backup glossary is generally cross-platform and workload-neutral, but there are minor signs of Windows bias: Windows tools (VSS, DPM, MABS, MARS agent) are referenced without equivalent Linux mentions, and the VSS (Windows Volume Shadow Copy Service) entry is included while Linux snapshot mechanisms are not. In the 'Application consistent backup' section, VSS is mentioned first, with Linux scripts as a parenthetical afterthought. However, most terms are platform-agnostic and the glossary covers Azure-native concepts.
Recommendations
- Add references or links to Linux snapshot/backup mechanisms (e.g., LVM snapshots, fsfreeze) where relevant, especially in sections like 'Application consistent backup' and 'File system consistent backup'.
- Where Windows tools (VSS, DPM, MABS, MARS agent) are mentioned, clarify their platform specificity and, if applicable, mention Linux alternatives or note that no equivalent exists.
- Consider adding a glossary entry for Linux backup concepts if Azure Backup supports them, or explicitly state when a term is Windows-only.
- In 'Application consistent backup', present Linux and Windows approaches with equal prominence, not as a parenthetical.
- For 'Snapshot', include a brief note about Linux snapshot technologies if relevant to Azure Backup workloads.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation shows a mild Windows bias by listing Visual Studio (a Windows-first IDE) before Visual Studio Code in the code editor section, and by mentioning PowerShell before Bash when discussing CLI automation. However, Linux/macOS users are not blocked, and alternatives are referenced. No critical sections are Windows-only, and most tools (VS Code, Azure CLI, AZD) are cross-platform.
Recommendations
- When listing code editors, mention Visual Studio Code before Visual Studio, or clarify their cross-platform support.
- When referencing CLI automation, list Bash before PowerShell or mention both equally.
- Add explicit notes or links for Linux/macOS users where relevant, especially in sections referencing PowerShell or Visual Studio.
- Ensure all example commands and scripts are shown for both Bash and PowerShell where automation is discussed.
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The Azure Bastion FAQ documentation displays a mild Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users. Keyboard layout configuration instructions are only given for Windows, with no guidance for Linux or macOS users. There are references to Windows-specific tools and settings (e.g., Windows key, Windows toolbar, Windows Settings), and some examples (such as keyboard focus) are described using Windows terminology. There are no explicit Linux/macOS examples or instructions for equivalent actions.
Recommendations
- Provide keyboard layout configuration steps for Linux and macOS, or link to relevant documentation.
- When describing browser support, list platforms in a neutral order and clarify support for Linux browsers if applicable.
- For instructions involving keyboard shortcuts or focus, include equivalents for macOS and Linux where possible.
- Avoid using Windows-specific terminology (e.g., 'Windows key') without also referencing macOS/Linux equivalents, or clarify if the action is Windows-only.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently shown before curl (Linux/macOS) examples. All other instructions use cross-platform Azure CLI commands. There are no missing Linux examples, and no exclusive use of Windows tools.
Recommendations
- Present curl (Linux/macOS) and PowerShell examples in parallel tabs, or alternate the order to avoid consistently prioritizing Windows.
- Explicitly mention that all Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding bash or zsh shell examples if relevant, though curl is sufficient for HTTP requests.
Container Apps
Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file
...iner-apps/microservices-dapr-azure-resource-manager.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all Azure CLI and resource management commands. However, PowerShell examples are consistently presented alongside Bash, and in some sections (such as the deployment and log viewing steps), PowerShell is given equal prominence. There is a slight Windows-first bias in the use of PowerShell tabs and the inclusion of Azure PowerShell references in metadata, but Linux/macOS users are not blocked from completing any steps.
Recommendations
- Ensure Bash examples are shown first in all code tabs, as Bash is the default shell for most cross-platform CLI users.
- Add a brief note clarifying that Bash commands work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Review metadata and custom tags (e.g., 'devx-track-azurepowershell') to ensure equal representation of Bash and Azure CLI usage.
- Consider mentioning that Azure CLI is cross-platform and preferred for scripting on Linux/macOS.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority
View Details →
Detected Bias Types
windows_tools
Summary
The documentation is generally platform-neutral, focusing on Azure Firewall service issues and limitations. However, there is a minor instance of Windows bias: in the mitigation for FTP server configuration issues, the documentation links to an IIS (Windows-only) example, without providing a Linux equivalent or mentioning cross-platform alternatives.
Recommendations
- Add links or examples for configuring FTP servers on popular Linux platforms (e.g., vsftpd, ProFTPD, Pure-FTPd) alongside the IIS example.
- Explicitly state that the FTP configuration guidance applies to both Windows and Linux servers, and provide parity in troubleshooting steps.
- Where platform-specific examples are given, ensure Linux/macOS equivalents are referenced or linked.
Logic Apps
Call Azure Functions from workflows
...cles/logic-apps/call-azure-functions-from-workflows.md
Low Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
Summary
The documentation provides a list of tools for creating Azure Functions, including Azure CLI, Azure PowerShell, Visual Studio, and Visual Studio Code. While Azure CLI and VS Code are cross-platform, the inclusion of Visual Studio and Azure PowerShell (which are Windows-centric) is notable. Additionally, in the authentication section, PowerShell is mentioned as a way to retrieve the tenant ID, with no equivalent Linux/macOS shell example (e.g., Azure CLI). However, the overall workflow and examples are platform-neutral, focusing on Azure portal and JavaScript/C# code.
Recommendations
- When listing tools for creating Azure Functions, clarify which are cross-platform (e.g., Azure CLI, VS Code) and which are Windows-only (e.g., Visual Studio, Azure PowerShell).
- Provide Azure CLI equivalents for PowerShell commands, especially for retrieving tenant IDs and other Azure resource properties.
- Where possible, present cross-platform tools and examples first, or side-by-side with Windows-specific options.
- Explicitly state that Azure CLI and VS Code are recommended for Linux/macOS users.