253
Pages Scanned
60
Pages Flagged
253
Changed Pages
23.7%
% Pages Flagged
Scan Information
Started At: 2026-01-26 00:00:07
Finished At: 2026-02-10 18:44:36
Status: completed
Target Repo: Azure
Current Phase: discovery
Files Queued: 253
Files Completed: 253
Problematic Pages
60 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
missing_linux_example
windows_tools
Summary
The tutorial is exclusively based on Azure PowerShell cmdlets and includes steps (such as certificate creation and export) that use Windows PowerShell-specific tools and file paths (e.g., cert:\localmachine\my, c:\appgwcert.pfx). There are no CLI, Bash, or cross-platform alternatives provided, making it difficult for Linux/macOS users to follow the tutorial end-to-end.
Recommendations
- Provide equivalent Azure CLI (az) commands for each step, especially for resource creation and management.
- Include instructions for creating and exporting self-signed certificates on Linux/macOS (e.g., using OpenSSL) alongside the PowerShell method.
- Use platform-neutral file paths in examples, or show both Windows and Linux/macOS paths where relevant.
- Explicitly note any steps that are Windows-only and offer alternatives or workarounds for other platforms.
Create Pull Request
Azure Relay
Tutorial: REST tutorial using Azure Relay
...rticles/azure-relay/service-bus-relay-rest-tutorial.md
High Priority
View Details →
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
The tutorial is heavily focused on Windows development environments and tools, specifically Visual Studio and the .NET Framework (WCF), with all examples and instructions tailored for Windows users. There are no instructions, examples, or notes on how to perform the same tasks on Linux or macOS, nor any mention of cross-platform alternatives. The documentation assumes the use of Visual Studio, Windows-specific DLLs, and Windows-centric development workflows, making it difficult or impossible for Linux/macOS users to follow along.
Recommendations
- Clearly state in the prerequisites and introduction that this tutorial is Windows-only due to its reliance on WCF and .NET Framework (not .NET Core/.NET 5+).
- If possible, provide guidance or links for Linux/macOS users on alternative approaches, such as using Azure Relay with .NET Core or other REST frameworks.
- Add a note explaining that WCF REST services and related tooling are not supported on Linux/macOS, and suggest supported cross-platform technologies where applicable.
- Consider including a section on how to use Azure Relay with cross-platform frameworks (e.g., ASP.NET Core, Node.js) if the service supports them.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides a 'Next steps' link that exclusively references Azure PowerShell for creating an autoscaling, zone-redundant Application Gateway, without mentioning or linking to equivalent Azure CLI or ARM template instructions. This creates a subtle bias toward Windows/PowerShell users, as PowerShell is most commonly used on Windows and is often presented as the default automation tool in Azure documentation.
Recommendations
- Add links or examples for creating autoscaling, zone-redundant Application Gateway using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include ARM/Bicep template instructions or links for infrastructure-as-code parity.
- Present cross-platform options (CLI, PowerShell, templates) together or in parallel, rather than PowerShell-only or PowerShell-first.
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 for managing credentials in Azure Automation is heavily focused on PowerShell and Windows-centric tools and patterns. All CLI examples use PowerShell cmdlets, and the only non-PowerShell language covered is Python (for runbooks). There are no Bash, Azure CLI, or Linux-native examples for credential asset management. The documentation refers to 'Windows PowerShell' specifically when describing how to create credential assets, and PowerShell cmdlets are listed before Python functions. No Linux/macOS shell or tool alternatives are mentioned.
Recommendations
- Add Azure CLI examples for creating, retrieving, and managing credential assets, if supported.
- Clarify whether PowerShell examples work cross-platform (e.g., PowerShell Core on Linux/macOS), or provide guidance for non-Windows environments.
- Include Bash or shell script examples for credential management, if possible.
- Explicitly state platform requirements and limitations for each method.
- Reorder examples to present cross-platform or platform-neutral options first, or in parallel.
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 provides Azure PowerShell examples first and in detail for feature registration, with only a brief mention that Azure CLI can be used as an alternative. The step-by-step instructions and code blocks are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. No explicit Linux/macOS examples or screenshots are provided.
Recommendations
- Provide Azure CLI command examples alongside PowerShell for feature registration and status checks.
- Include explicit instructions or screenshots for CLI usage where relevant.
- Clarify that both PowerShell and CLI are supported and link to CLI documentation directly in the relevant steps.
- Consider ordering examples so that CLI and PowerShell are presented equally, or based on platform detection.
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
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides general guidance for restoring Azure VMs using the portal and templates, but there is a noticeable Windows bias in several areas. Examples and links for post-restore steps, network configuration, and VM creation frequently reference Windows-specific documentation, PowerShell commands, and Windows VM scenarios. Linux-specific instructions are sparse or absent, and Windows examples are often presented first or exclusively.
Recommendations
- Add Linux-specific examples and links alongside Windows examples, especially for tasks like attaching disks, configuring network settings, and post-restore steps.
- Provide CLI (az) and Bash examples for VM creation and disk attachment, not just PowerShell.
- Reference Linux documentation (e.g., for restoring VMs, managing disks, resetting passwords, configuring network interfaces) where appropriate.
- Clarify when instructions or links are Windows-only, and offer Linux alternatives where possible.
- Ensure parity in guidance for restoring VMs with special configurations (e.g., multiple NICs, availability sets) for Linux VMs.
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 page demonstrates a Windows bias in its troubleshooting examples: Windows/PowerShell tools (psping.exe) are presented first and in more detail, with Linux alternatives (telnet) mentioned briefly and without equivalent depth. The recommended tools and commands are predominantly Windows-centric, and some troubleshooting steps lack Linux/macOS parity or omit cross-platform alternatives.
Recommendations
- Present Linux/macOS examples alongside Windows examples, giving equal detail and prominence.
- List Linux/macOS commands (e.g., nc, curl, tcpping for Linux) before or alongside Windows/PowerShell commands.
- Include download or installation instructions for Linux/macOS tools (e.g., how to install telnet, netcat, or tcpping on Ubuntu).
- Reference cross-platform tools (e.g., Wireshark, curl) where possible, and clarify platform-specific differences.
- Avoid assuming the use of Windows-only tools (like psping.exe) and provide alternatives for non-Windows users.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths (e.g., D:\home) and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS) are mentioned first or exclusively in several sections. Many examples and variable descriptions use Windows conventions before Linux equivalents, and some settings reference Windows-only features without always clarifying Linux alternatives. In some cases, Linux-specific details are present but less emphasized or appear after Windows details. Some sections (e.g., Build automation) are split into Windows (Kudu) and Linux (Oryx) tabs, which helps, but Windows terminology and examples are more prevalent overall.
Recommendations
- Where environment variable paths are shown, always provide both Windows and Linux examples side-by-side (e.g., D:\home and /home).
- When referencing tools or deployment methods (e.g., msbuild, Web Deploy), clarify Linux alternatives (e.g., Oryx, ZIP deploy) and provide parity in explanation and examples.
- Ensure Linux-specific settings and behaviors are documented with equal detail and visibility as Windows ones.
- Avoid listing Windows settings or examples first unless they are more widely used; consider alternating or grouping by OS.
- For settings that are Windows-only, explicitly state so, and for cross-platform settings, clarify differences and provide examples for both.
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 for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based scripts and workflows, with all examples, instructions, and tooling centered around Azure PowerShell. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples provided. The installation and usage patterns (e.g., Install-Script, .ps1 files, PowerShell Gallery) are Windows-centric and may create friction for users on Linux or macOS platforms, who typically use Bash and Azure CLI. The documentation does not mention or provide alternatives for non-Windows environments, nor does it clarify cross-platform compatibility of the provided scripts.
Recommendations
- Explicitly state whether the PowerShell scripts are cross-platform and can be run on PowerShell Core on Linux/macOS.
- Provide Azure CLI equivalents for key migration steps, or clarify if such automation is not available.
- Add Bash shell examples for common operations (e.g., retrieving resource IDs, uploading certificates) using Azure CLI.
- Include installation and usage instructions for PowerShell on Linux/macOS, or link to official guidance.
- Mention and link to Azure Cloud Shell as a cross-platform alternative for running PowerShell scripts.
- Add a section addressing Linux/macOS users, outlining any limitations or required adaptations.
Application Gateway
Overview of mutual authentication on Azure Application Gateway
.../application-gateway/mutual-authentication-overview.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides configuration instructions for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions are given first and in more detail, while Azure CLI examples are present but less comprehensive. There is no mention of Linux-specific tools or workflows, and the CLI example is minimal compared to the PowerShell section. The 'Next steps' section directs users to a PowerShell-focused guide, further reinforcing the Windows-first approach. No Linux/macOS-specific certificate management or workflow examples are provided.
Recommendations
- Expand Azure CLI examples to match the detail and coverage of PowerShell instructions, including full configuration steps.
- Provide explicit guidance or examples for Linux/macOS users, such as using OpenSSL for certificate extraction and management.
- Ensure that 'Next steps' includes links to both PowerShell and CLI-based guides, or a cross-platform guide.
- Clarify that both CLI and PowerShell are supported equally for configuration tasks, and highlight any platform-specific considerations.
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation on Application Gateway V1 retirement and migration to V2 is heavily focused on Azure PowerShell scripts for migration, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. All migration automation references are to PowerShell, and there are no examples or guidance for users on Linux or macOS platforms. This creates friction for non-Windows users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
- Provide equivalent migration instructions and scripts using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples for common migration tasks.
- Explicitly mention platform compatibility for provided scripts, and offer guidance for Linux/macOS users on how to run or adapt the migration process.
- List both PowerShell and CLI options side-by-side where automation is discussed.
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, with all detailed command-line examples using PowerShell cmdlets and Windows-centric patterns. The creation and management of certificates are demonstrated exclusively via PowerShell, with no equivalent CLI, Bash, or Linux-native instructions. While Python examples are provided for runbook usage, there are no Linux shell or cross-platform CLI examples for certificate management tasks. PowerShell is presented first and most thoroughly, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add Azure CLI examples for certificate management tasks (creation, retrieval, deletion) alongside PowerShell.
- Include Bash or shell script snippets for uploading certificates, using az CLI or REST API.
- Explicitly mention cross-platform alternatives where PowerShell is referenced, and clarify if PowerShell Core (pwsh) is supported on Linux/macOS for these tasks.
- Reorder examples or provide tabs for both PowerShell and CLI/Bash, so Linux/macOS users see parity.
- Document any limitations or differences for Linux/macOS users when using Azure Automation certificate features.
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 demonstrates a moderate Windows/PowerShell bias. Key migration and registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Azure CLI (cross-platform) or Bash examples. The 'Next steps' section links to a PowerShell-based tutorial, and PowerShell is referenced before CLI in preview registration instructions. This creates friction for Linux/macOS users who may prefer or require CLI/Bash instructions.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell commands for all registration, migration, and management tasks.
- Ensure tutorials and quickstarts are available for both PowerShell and Azure CLI workflows, and link to both in 'Next steps'.
- When listing command examples, present Azure CLI (cross-platform) instructions first or equally with PowerShell.
- Clarify in each section that both PowerShell and CLI can be used, and link to relevant cross-platform documentation.
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 a strong bias towards Windows and PowerShell. All migration examples and scripts are PowerShell-based, with no mention of Bash, Python, or Linux-native alternatives. The installation and migration instructions reference Windows tabs and PowerShell workflows first, and do not provide parity for Linux users or cross-platform scripting. Although Azure Automation supports both Linux and Windows VMs, Linux users are left to adapt Windows-centric instructions, which may create friction.
Recommendations
- Provide equivalent migration scripts or runbook examples using Bash, Python, or Azure CLI for Linux users.
- Explicitly document how Linux users can perform asset migration, including prerequisites and platform-specific steps.
- When referencing installation or configuration guides, ensure both Windows and Linux tabs/examples are present and equally visible.
- Clarify any platform limitations (e.g., if PowerShell is required regardless of OS, explain why and suggest installation steps for Linux).
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, with no mention of Bash, CLI, or Linux/macOS alternatives. All code examples and instructions use PowerShell, and the creation of credential assets is described only via the Azure portal or Windows PowerShell. There is no guidance for users who prefer or require Linux/macOS environments, nor are cross-platform tools like Azure CLI or REST API referenced.
Recommendations
- Add equivalent examples using Azure CLI and/or Bash scripts for credential asset creation and runbook management.
- Clarify which steps are platform-agnostic (e.g., Azure portal) and which are Windows/PowerShell-specific.
- Reference cross-platform authentication methods, such as using managed identities or service principals with Azure CLI.
- Explicitly state any platform limitations if certain features require PowerShell/Windows.
- Link to documentation for using Azure Automation with Linux/macOS where applicable.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux guidance for TLS configuration, but Windows instructions and PowerShell cmdlets are consistently mentioned first and more prominently. Backup and retention examples rely heavily on Windows PowerShell cmdlets, with no equivalent CLI or Linux-native examples. Windows registry settings and tools are referenced before Linux OpenSSL guidance, and asset management is described primarily in terms of Windows-centric tooling.
Recommendations
- Provide Azure CLI or Bash examples alongside PowerShell cmdlets for backup/export tasks, especially for runbooks and DSC configurations.
- Include Linux-native instructions for asset management and data retention tasks, such as using az CLI or REST API.
- Balance the order of platform-specific guidance so Linux instructions are presented alongside or before Windows instructions where appropriate.
- Reference Linux tools (e.g., OpenSSL, systemd, shell scripts) equally when discussing configuration or troubleshooting steps.
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
Summary
The documentation provides a balanced overview of Azure Change Tracking and Inventory, mentioning support for both Windows and Linux. However, the section on tracking registry keys is exclusively focused on Windows, with no mention of Linux equivalents (such as tracking configuration files or Linux system settings). Additionally, Windows registry monitoring is described in detail and given a dedicated table, while Linux-specific configuration tracking is not covered with similar depth or examples.
Recommendations
- Add a section describing how Change Tracking and Inventory monitors Linux-specific configuration changes, such as tracking changes in /etc files, systemd unit files, or other relevant Linux configuration locations.
- Provide Linux-focused examples or tables similar to the Windows registry key table, detailing which Linux configuration files or directories are tracked by default or can be configured for monitoring.
- Clarify in the registry section that registry tracking is Windows-specific, and provide a parallel explanation for Linux users about what types of configuration changes are monitored on Linux systems.
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_first
missing_linux_example
windows_tools
Summary
The documentation page on configuring runbook input parameters in Azure Automation exhibits a notable Windows/PowerShell bias. Most examples, code snippets, and workflows are centered around PowerShell, PowerShell Workflow, and graphical runbooks (which are inherently PowerShell-based). The use of PowerShell cmdlets, Windows-centric terminology, and screenshots of the Azure portal with PowerShell parameters dominate the content. Python runbooks are mentioned briefly, with minimal example coverage and no parity in walkthroughs or screenshots. There are no references to Linux shell (Bash) or cross-platform CLI usage, nor are Linux/macOS-specific considerations addressed.
Recommendations
- Add equivalent examples for starting and passing parameters to Python runbooks, including code snippets for Bash/CLI usage where applicable.
- Include explicit instructions or examples for using Azure CLI (az automation runbook start) to start runbooks and pass parameters, highlighting cross-platform compatibility.
- Clarify which features and workflows are platform-agnostic and which are PowerShell-specific, to help Linux/macOS users understand applicability.
- Provide screenshots or walkthroughs for Python runbooks and parameter assignment in the portal, not just PowerShell-based runbooks.
- Mention any limitations or differences when using Azure Automation from Linux/macOS environments, especially around authentication and context management.
Azure Functions
Guide for running C# Azure Functions in an isolated worker process
...icles/azure-functions/dotnet-isolated-process-guide.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation generally aims for cross-platform parity but exhibits some Windows bias in several areas: Windows-specific tools and configuration steps are often mentioned before or more prominently than their Linux equivalents, and some CLI examples and explanations are Windows-first or Windows-only. Azure PowerShell and Visual Studio (Windows-only) are highlighted as primary options for resource creation and deployment, while Linux-specific or cross-platform alternatives (like Bash, zsh, or Linux CLI nuances) are less emphasized or omitted. Some configuration and deployment instructions (such as ReadyToRun and .NET Framework debugging) are Windows-centric, with Linux guidance less detailed or only referenced via links.
Recommendations
- Ensure all CLI and configuration examples are provided for both Windows and Linux, using appropriate shell syntax (e.g., Bash for Linux, PowerShell for Windows) and clearly label them.
- When listing tools or approaches (e.g., Visual Studio, Visual Studio Code, Azure CLI, PowerShell), present cross-platform options first or in parallel, and avoid Windows-first ordering unless justified.
- Expand Linux-specific guidance where only Windows instructions are given, especially for deployment, debugging, and performance optimization scenarios.
- Where PowerShell is referenced, provide equivalent Bash/Azure CLI commands and clarify which platforms each applies to.
- In sections about project setup, debugging, and deployment, explicitly call out any differences or additional steps required for Linux/macOS users.
- Add more explicit Linux/macOS examples in code snippets, command lines, and configuration, especially in areas where Windows paths, tools, or behaviors are assumed.
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 several areas where Windows-centric tools and patterns are mentioned first or exclusively. Examples and instructions often reference Visual Studio and Windows-specific deployment flows before Linux alternatives. Some deployment technologies (like Source Control, Local Git, FTPS) are noted as 'Windows-only' in the availability table, but Linux equivalents or workarounds are not always explained in detail. The documentation also tends to present Windows deployment methods and concepts before Linux ones, which may create friction for Linux/macOS users.
Recommendations
- Where deployment methods are Windows-only, explicitly link to Linux alternatives or clarify what Linux users should do.
- Provide Linux/macOS-specific examples and command-line instructions alongside Windows/Visual Studio examples, especially in 'How to use it' sections.
- When listing tools (e.g., Visual Studio, Visual Studio Code, Core Tools), present cross-platform options first or in parallel, rather than Windows-first.
- Expand on Linux deployment limitations and workarounds, especially for methods marked 'Windows-only'.
- Add a summary table or section specifically for Linux/macOS users outlining their supported deployment paths.
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 guidance for both Linux and Windows-hosted Azure Functions apps, but there is a notable Windows bias in several areas. Windows/PowerShell/Azure CLI examples and instructions are frequently presented first or in greater detail, and Windows-specific tools and patterns (such as the use of Azure CLI commands that are only available for Windows, and more granular manual migration steps for Windows) are emphasized. The Linux migration process is more streamlined via a dedicated CLI command, but Windows users must follow a more manual, step-by-step approach. Some sections (e.g., Infrastructure as Code, deployment package retrieval) provide more detailed Windows instructions, and the overall structure tends to present Windows options before Linux ones.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence, ideally side-by-side or in parallel tabs.
- Where possible, provide parity in automation tools (e.g., develop and document a Windows equivalent to the Linux 'az functionapp flex-migration' command).
- Add more detailed Linux manual migration steps for cases where automation is not available, to match the depth of Windows guidance.
- Review the ordering of examples and instructions to avoid consistently presenting Windows options first.
- Explicitly call out any feature/tool that is Windows-only or Linux-only, and provide alternative steps for the other platform.
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 is a lack of explicit Linux/macOS instructions or examples for running the sample applications, and the highlighted code is Windows-centric. Although Java and JavaScript samples are linked, the walkthrough and code focus on .NET, which may create friction for Linux/macOS users.
Recommendations
- Add explicit instructions for running the sample applications on Linux/macOS, including prerequisites and environment setup.
- Provide highlighted code samples for Java and JavaScript, not just .NET/C#.
- When listing tools for role assignment, mention Azure CLI before or alongside PowerShell, and clarify cross-platform options.
- Include troubleshooting notes for common Linux/macOS issues (e.g., dependency installation, authentication differences).
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
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation exclusively describes creating a .NET Framework console application using Visual Studio, which is a Windows-only development environment and runtime. There are no instructions or examples for Linux/macOS users (e.g., .NET Core/.NET 5+ projects, cross-platform editors like VS Code, or CLI-based workflows). This creates friction for non-Windows users who wish to use Azure Relay with .NET.
Recommendations
- Add instructions for creating a cross-platform .NET (Core/5+) console application using the dotnet CLI.
- Include examples for using Visual Studio Code or other cross-platform editors.
- Clarify whether the Microsoft.Azure.Relay NuGet package and sample code work on Linux/macOS, and provide any necessary platform-specific notes.
- If .NET Framework is required, explicitly state that the instructions are Windows-only and link to cross-platform alternatives if available.
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
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is written with a Windows-first approach, instructing users to create a .NET Framework console application in Visual Studio and add NuGet packages via the Visual Studio GUI. There are no instructions or examples for Linux/macOS users, such as using .NET Core/.NET 5+ (cross-platform) or command-line tools like dotnet CLI and alternative editors. This creates friction for non-Windows users who may want to follow the tutorial on their platforms.
Recommendations
- Add instructions for creating a cross-platform .NET (Core/5+) console application using the dotnet CLI.
- Include examples for installing NuGet packages via the command line (e.g., 'dotnet add package Microsoft.Azure.Relay').
- Mention alternative editors (e.g., VS Code) and workflows for Linux/macOS users.
- Clarify whether the sample code is compatible with .NET Core/.NET 5+ and, if not, provide equivalent cross-platform samples.
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_first
missing_linux_example
Summary
The documentation instructs users to create a .NET Framework console application using Visual Studio, which is a Windows-centric IDE and framework. There are no instructions or examples for creating the equivalent application on Linux or macOS (e.g., using .NET Core/.NET 5+ with VS Code or CLI). The NuGet package installation steps are also tailored to Visual Studio's GUI, omitting cross-platform CLI alternatives.
Recommendations
- Add instructions for creating a .NET Core or .NET 5+ console application using the 'dotnet new console' CLI command, which works on Linux and macOS.
- Include NuGet package installation steps using the 'dotnet add package Microsoft.Azure.Relay' CLI command.
- Mention that the code sample is compatible with .NET Core/.NET 5+ and provide guidance for running it on Linux/macOS.
- Reference cross-platform editors like VS Code in addition to Visual Studio.
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
Summary
The documentation page demonstrates a notable Windows bias: the step-by-step instructions for authenticating with managed identities for Azure Relay resources exclusively use a Windows VM as the runtime environment, referencing Windows-specific setup (RDP, Windows VM creation) and omitting Linux VM or cross-platform instructions. While sample code is cross-platform (.NET, Java, JavaScript), the walkthrough for running the sample app is Windows-centric, with no guidance for Linux/macOS users.
Recommendations
- Add parallel instructions for running the sample app on a Linux VM, including VM creation, enabling managed identity, copying files (e.g., using SCP/SFTP), and running the executable via terminal.
- Reference both Windows and Linux VM setup guides when discussing enabling managed identity.
- Include notes or examples for macOS users where relevant, especially for local development.
- Clarify that the sample code itself is cross-platform and provide explicit instructions for building/running on Linux/macOS.
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_first
missing_linux_example
Summary
The documentation instructs users to create a .NET Framework console application using Visual Studio and provides steps that are specific to Windows development environments. There are no examples or guidance for Linux/macOS users, such as using .NET Core/.NET 5+ (which is cross-platform), nor are alternative development environments or package installation methods mentioned.
Recommendations
- Add instructions for creating a cross-platform .NET Core/.NET 5+ console application, which can run on Linux and macOS as well as Windows.
- Include command-line instructions for installing the Microsoft.Azure.Relay NuGet package (e.g., using dotnet CLI), which works on all platforms.
- Mention alternative editors (such as VS Code) and development workflows suitable for Linux/macOS users.
- Clarify that the code sample is compatible with .NET Core/.NET 5+ if applicable, or provide a separate sample for those frameworks.
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
windows_first
missing_linux_example
Summary
The documentation provides step-by-step instructions for integrating Azure Relay with Azure Private Link Service, focusing primarily on the Azure portal and Azure PowerShell. The only CLI example is for Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. The validation step explicitly instructs users to create a Windows VM and references the Windows VM creation guide, with no mention of Linux VM alternatives or parity. This creates friction for Linux/macOS users who may prefer Azure CLI or Bash and Linux-based validation steps.
Recommendations
- Add equivalent Azure CLI examples for creating private endpoints and related resources, as Azure CLI is cross-platform and widely used on Linux/macOS.
- In the validation section, provide instructions for creating and using a Linux VM (e.g., Ubuntu) alongside the Windows VM option, and reference the Linux VM creation guide.
- Show how to run the nslookup command on Linux/macOS, noting any differences if relevant.
- When listing command-line options, present Azure CLI and PowerShell examples side-by-side, or indicate both options are available.
- Avoid language or examples that assume Windows as the default unless the feature is Windows-only (which is not the case here).
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
missing_linux_example
Summary
The documentation provides instructions for configuring IP firewall rules for Azure Relay namespaces using the Azure portal and Resource Manager templates. However, when referencing deployment of the ARM template, it links only to PowerShell-based instructions, which are Windows-centric. There are no CLI or Linux/macOS-specific deployment examples or links, and PowerShell is implicitly prioritized over cross-platform alternatives.
Recommendations
- Add instructions or links for deploying ARM templates using Azure CLI (az deployment), which is cross-platform and works on Linux/macOS.
- Explicitly mention that ARM template deployment can be performed from any OS using Azure CLI or REST API, not just PowerShell.
- Provide example commands for both PowerShell and Azure CLI, or link to documentation for both methods.
- Ensure that references to deployment tools do not implicitly prioritize Windows/PowerShell unless the feature is Windows-only.
Azure Relay
Azure Relay Hybrid Connections - WebSockets in .NET
...e-relay/relay-hybrid-connections-dotnet-get-started.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation assumes the use of Visual Studio on Windows and provides instructions and examples only for C# console applications created in Visual Studio. There is no mention of cross-platform .NET development tools (such as VS Code or CLI), nor are there instructions for running the sample on Linux or macOS. This creates friction for developers using .NET Core/.NET 5+ on non-Windows platforms.
Recommendations
- Add instructions for creating and running the .NET console applications using the .NET CLI, which works on Windows, Linux, and macOS.
- Mention and provide examples for using Visual Studio Code or other cross-platform editors.
- Clarify that the sample works with .NET Core/.NET 5+ and is not limited to Windows, if applicable.
- Include notes or troubleshooting tips for running the sample on Linux/macOS (e.g., terminal commands, environment setup).
Azure Relay
Hybrid Connections - HTTP requests in .NET
...ay-hybrid-connections-http-requests-dotnet-get-started.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation assumes use of Visual Studio on Windows and does not mention or provide guidance for developing or running the .NET applications on Linux or macOS. All instructions and examples are tailored to Windows environments, with no parity for Linux users.
Recommendations
- Add instructions for creating and running the .NET applications using cross-platform tools such as Visual Studio Code, the .NET CLI, or JetBrains Rider.
- Include explicit steps for Linux/macOS users, such as installing the .NET SDK, creating projects via the command line, and running applications in a terminal.
- Clarify that .NET Core/.NET 5+ is cross-platform and provide sample commands for Linux/macOS where applicable.
- Mention alternative editors and development environments suitable for non-Windows platforms.
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 instructions for relocating Azure Firewall using the Azure Portal and Azure PowerShell. All command-line examples are exclusively in PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates friction for Linux/macOS users who do not use PowerShell, as Azure CLI is the standard cross-platform tool for Azure resource management.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command-line steps, including template export, modification, and deployment.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant Azure CLI documentation.
- Ensure that any referenced scripts or automation steps are compatible with Bash and other non-Windows shells.
- Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
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 provides both Windows and Linux parity in its conceptual coverage of encrypted VM backup and restore. However, in the 'Provide permissions' section, the example for identifying a VM's associated Key Vault uses only a PowerShell command (Get-AzVm), which is Windows-centric and may not be immediately accessible to Linux/macOS users. There is no equivalent Azure CLI or Bash example shown alongside. Additionally, PowerShell is mentioned before Azure CLI in the sentence about setting access policies, which subtly prioritizes Windows tooling.
Recommendations
- Add an Azure CLI example for identifying a VM's associated Key Vault, such as using 'az vm show' with appropriate query filters.
- When referencing automation options, list Azure CLI and Bash examples before or alongside PowerShell to avoid implicit prioritization.
- Ensure all command-line instructions are provided in both PowerShell and Azure CLI/Bash formats where possible.
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 VM backup scenarios, but there are notable signs of Windows bias. Windows-specific tools (MARS agent, DPM, MABS) are described in detail, with Linux support often marked as 'not supported' or omitted. Restore instructions frequently mention PowerShell and Windows-centric workflows, while Linux equivalents (such as Azure CLI or shell scripting) are not provided. Windows examples and features are often listed before Linux, and some restore scenarios reference Windows tools without Linux alternatives.
Recommendations
- Add Linux-specific examples and workflows for backup and restore operations, especially where PowerShell is mentioned for Windows.
- Where Windows tools (MARS agent, DPM, MABS) are discussed, clarify Linux alternatives or explicitly state the lack of parity.
- Provide Azure CLI or shell script examples for Linux users in restore and backup scenarios.
- Ensure that Linux support is described with equal detail and prominence as Windows support, especially in tables and step-by-step instructions.
- Where features are Windows-only, clearly label them as such to avoid confusion.
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 page for relocating an Azure Container Registry demonstrates a moderate Windows bias. Several command examples use Azure PowerShell cmdlets (e.g., Get-AzContainerRegistryRepository, Import-AzContainerImage, Set-AzAksCluster) without providing equivalent Azure CLI or Bash examples, especially in critical steps like retrieving images and integrating with AKS. Where Azure CLI is used, PowerShell alternatives are mentioned first or exclusively. There is a lack of explicit Linux/macOS shell examples for some operations, and the scripting guidance is inconsistent in platform parity.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI or Bash command, especially for tasks like listing repositories, importing images, and integrating with AKS.
- When referencing commands, list Azure CLI (cross-platform) examples before PowerShell, or present both side-by-side.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide sample Bash scripts for automation tasks.
- Review all steps to ensure Linux/macOS users can follow without needing PowerShell or Windows-specific tooling.
- Add notes or links to official Azure CLI documentation for each referenced PowerShell command.
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 on Azure VM restore describes general concepts and scenarios applicable to both Windows and Linux VMs. However, in the 'Restore an encrypted VM' scenario, the instructions and linked references are exclusively for Windows VMs, and mention using PowerShell to create the VM after restoring disks. There is no mention of Linux VM encryption restore, nor are Linux-specific tools or examples provided. This creates friction for Linux users seeking guidance on restoring encrypted Linux VMs.
Recommendations
- Add a section or links describing the restore process for encrypted Linux VMs, including any differences in workflow or prerequisites.
- Provide Linux-specific examples or references (e.g., using Azure CLI or Bash scripts) for restoring VMs and disks, especially in scenarios where PowerShell is currently referenced.
- Clarify in the encrypted VM restore scenario whether the process applies only to Windows VMs, and if so, provide a parallel explanation for Linux VMs or explicitly state the limitation.
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation for Azure Backup architecture is notably Windows-centric in its coverage of on-premises backup scenarios. It exclusively describes backup methods and agents (MARS, DPM, MABS) that only support Windows machines, with explicit statements that Linux machines aren't supported for direct backup. There are no Linux equivalents or alternative backup approaches mentioned for on-premises Linux systems, and Windows tools and patterns (MARS agent, VSS, DPM/MABS) are discussed in detail, while Linux backup scenarios are omitted.
Recommendations
- Clearly state the limitations for Linux on-premises backup and provide links or references to alternative solutions for Linux systems (e.g., third-party agents, Azure Backup integration via other means, or Azure-native Linux backup options if available).
- Add a section or note summarizing how Linux workloads can be protected, even if only via Azure VM backup or other Azure-native features.
- Where possible, balance the presentation by mentioning Linux support status earlier in the document, so Linux users can quickly understand their options.
- If Linux backup is not supported for certain scenarios, explicitly mention this and suggest best practices or alternatives.
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 exhibits bias by providing a PowerShell-based example for VM creation from restored disks without mentioning Linux-native alternatives (such as Azure CLI or ARM templates). The reference to swapping OS disks links only to Windows-specific documentation. Linux restore steps are separated into a brief section, lacking detailed guidance or examples comparable to those for Windows.
Recommendations
- Provide Azure CLI and/or ARM template examples for creating a VM from restored disks, especially for Linux users.
- Include a link or section on swapping OS disks for Linux VMs, or clarify the process if it differs from Windows.
- Ensure that Linux restore steps are as detailed as Windows steps, including troubleshooting and extension reinstallation commands.
- When referencing tools (e.g., PowerShell), mention cross-platform alternatives where available.
Cloud Services Extended Support
About Azure Cloud Services (extended support)
...n/articles/cloud-services-extended-support/overview.md
Medium Priority
View Details →
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references Windows-centric tools (PowerShell, Visual Studio) as primary deployment options, listing them before platform-neutral alternatives like ARM templates and the Azure Portal. There are no explicit Linux/macOS CLI examples or mentions of cross-platform tools such as Azure CLI, which may create friction for non-Windows users.
Recommendations
- Add explicit instructions and examples for deploying Cloud Services (extended support) using Azure CLI, which is cross-platform.
- List platform-neutral options (ARM templates, Azure Portal, Azure CLI) before Windows-specific tools (PowerShell, Visual Studio) when describing deployment methods.
- Clarify that PowerShell and Visual Studio are Windows-centric, and provide equivalent steps for Linux/macOS users.
- Include links to Azure CLI documentation for relevant deployment scenarios.
Data Share
Tutorial: Share outside your org - Azure Data Share
...-docs/blob/main/articles/data-share/share-your-data.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. PowerShell is given equal prominence to Azure CLI, but its usage and examples (such as file upload from D:\testFiles) are Windows-centric. The PowerShell examples reference Windows file paths and tools, and the PowerShell section is included as a primary method, which may create friction for Linux/macOS users. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a default automation option alongside CLI, despite its historical Windows bias.
Recommendations
- Add explicit Bash examples for key steps, especially for file upload and resource management, to ensure Linux/macOS users have parity.
- Clarify that PowerShell commands can be run cross-platform (e.g., in Azure Cloud Shell) and provide Linux/macOS path examples where relevant.
- Avoid using Windows-specific file paths (e.g., D:\testFiles) in PowerShell examples; use generic or platform-neutral paths.
- Consider listing Azure CLI (which is cross-platform) before PowerShell in example tabs to reduce perceived Windows-first bias.
Data Share
Tutorial: Accept & receive data - Azure Data Share
...ob/main/articles/data-share/subscribe-to-data-share.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides step-by-step instructions for accepting and receiving data via Azure Data Share using three interfaces: Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell examples are given equal prominence and detail, and in some cases, Windows-centric file paths (e.g., D:\testFiles) are used in examples. There is no mention of Linux/macOS-specific considerations, nor are Bash or shell script examples provided for tasks like file uploads. PowerShell is presented as a first-class option alongside CLI, but with Windows-centric patterns, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Bash/shell script examples for file uploads and other operations, especially where PowerShell uses Windows paths.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and provide links to CLI installation for those platforms.
- Where PowerShell is used for local operations, provide equivalent Bash commands for Linux/macOS users (e.g., using azcopy, Azure CLI, or REST API for file uploads).
- Avoid using Windows-specific file paths in examples; use generic or platform-neutral paths, or provide alternatives.
- Add a note or section for Linux/macOS users highlighting any differences or additional steps required.
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 detailed steps and screenshots for configuring DNS conditional forwarders using a Windows DNS server, but does not include equivalent instructions or examples for Linux-based DNS servers (e.g., BIND). Windows DNS is presented first and exclusively in the on-premises configuration section, which may create friction for users operating Linux-based DNS infrastructure.
Recommendations
- Add a section or example showing how to configure conditional forwarders on a popular Linux DNS server such as BIND.
- Include CLI commands or configuration file snippets for Linux DNS server setups.
- Clarify in the procedures that the steps for on-premises DNS configuration can be adapted for non-Windows DNS servers, and provide links to relevant external documentation for Linux/BIND.
- Present both Windows and Linux examples in parallel where possible, or at least mention Linux alternatives.
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, Azure CLI, PowerShell, and C#. While the Azure CLI is cross-platform, PowerShell is Windows-centric and is listed as a primary method. The examples and screenshots focus on the Azure portal (which is web-based and cross-platform), but PowerShell is mentioned before C# and no explicit Linux/macOS shell examples (e.g., Bash) are provided. There is no mention of Linux-specific tools or patterns, and the CLI example is brief compared to the PowerShell and C# sections.
Recommendations
- Expand the Azure CLI section with a full example, including sample output and error handling, to match the detail of PowerShell and C#.
- Add explicit Bash/shell scripting examples for Linux/macOS users, demonstrating how to use the Azure CLI for failover and management tasks.
- Clarify that PowerShell Core is available cross-platform, or recommend Azure CLI as the preferred cross-platform automation tool.
- Ensure parity in example detail and troubleshooting guidance for CLI and non-Windows environments.
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 subnet creation, with no Azure CLI (cross-platform) or Bash/Linux shell examples provided. References to PowerShell and REST APIs are present, but Linux/macOS users are not given parity in command-line instructions or tool recommendations.
Recommendations
- Add Azure CLI examples alongside PowerShell for all resource creation and configuration steps, especially subnet creation.
- Explicitly mention that Azure CLI works on Linux/macOS and provide equivalent Bash commands where appropriate.
- Where PowerShell cmdlets are referenced, also link to Azure CLI documentation and examples.
- Clarify that all operations can be performed from Linux/macOS using Azure CLI or REST API, not just PowerShell.
Azure Resource Manager
Template functions - resources
...ource-manager/templates/template-functions-resource.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for discovering list operations, but PowerShell is presented first and in more detail. The CLI example is present but less emphasized. There are no other notable Windows-specific tools, patterns, or examples; all ARM template examples are platform-neutral JSON. No Linux/macOS examples are missing for critical tasks.
Recommendations
- Present Azure CLI and PowerShell examples with equal prominence, alternating which is shown first or grouping them together.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide links to installation guides for each.
- Where possible, add Bash or shell script snippets for common template deployment tasks, especially in 'Next steps'.
- Ensure that references to deployment tooling (e.g., 'Deploy resources with ARM templates and Azure PowerShell') also mention Azure CLI and its parity.
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 provides command-line examples for managing multi-region API Management deployments using Azure CLI and PowerShell. While Azure CLI is cross-platform, the documentation explicitly mentions the Azure PowerShell cmdlet (set-azapimanagement) alongside CLI and REST API, and lists PowerShell before mentioning 'other Azure tools'. No Linux/macOS-specific tools or shell examples are provided, and PowerShell is referenced as a primary method for some operations. The general workflow and UI instructions are platform-agnostic, but command-line automation examples show a mild Windows/PowerShell bias.
Recommendations
- Ensure all command-line examples use Azure CLI as the default, since it is cross-platform.
- If PowerShell is mentioned, clarify that Azure CLI works on Linux/macOS and provide Bash shell examples where appropriate.
- Add explicit notes or examples for Linux/macOS users, such as shell scripting or automation approaches.
- Reorder references so that Azure CLI is listed before PowerShell, emphasizing cross-platform parity.
Azure Cache For Redis
Azure Cache for Redis with Azure Private Link
...n/articles/azure-cache-for-redis/cache-private-link.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing private endpoints, but PowerShell examples are presented first and in greater detail. This ordering and emphasis may create a perception of Windows bias, as PowerShell is most commonly used on Windows, while Azure CLI is cross-platform and preferred by many Linux/macOS users. However, all critical tasks are covered with Azure CLI instructions, and no Windows-only tools or patterns are required.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first to avoid implicit prioritization.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider adding a short note at the start of the scripting section clarifying that both CLI and PowerShell are supported and users should choose based on their environment.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
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 both Windows and Linux considerations for Azure Functions app settings. However, there are a few minor instances of Windows bias: (1) In the explanation of hierarchical delimiters, Windows behavior is described first, and the reserved colon delimiter is noted as Windows-only before clarifying Linux support; (2) The example for AzureWebJobs_TypeScriptPath uses a Windows-style path (%HOME%\typescript) without a Linux equivalent; (3) Some references to using Azure CLI or Azure PowerShell for programmatic configuration mention PowerShell before CLI, which may subtly prioritize Windows tooling.
Recommendations
- Provide Linux/macOS equivalents for all path examples (e.g., show $HOME/typescript alongside %HOME%\typescript).
- When referencing tools for programmatic configuration, mention Azure CLI before or alongside Azure PowerShell to reflect cross-platform parity.
- Ensure that any OS-specific behaviors (such as delimiter interpretation) are described with equal prominence for both Windows and Linux.
- Where possible, include both Windows and Linux/macOS sample values or commands in tables and examples.
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 generally maintains cross-platform parity, but there are some minor signs of Windows bias. In the 'Mount file shares' section, both Azure CLI (Linux/macOS friendly) and PowerShell (Windows-centric) examples are provided, but PowerShell is presented second. There are references to features that are 'Windows only' (such as Consumption plan scaling with Azure Files), but these are clearly marked and explained. The majority of the documentation is platform-neutral, and Linux-specific guidance is present where relevant (e.g., mounting Azure Files shares on Linux).
Recommendations
- Continue to provide both Azure CLI and PowerShell examples side-by-side, and consider listing CLI examples first to emphasize cross-platform support.
- Where features differ by OS (e.g., Azure Files usage in Consumption plans), ensure Linux/macOS limitations and alternatives are clearly documented.
- Add explicit Linux/macOS examples for any configuration or troubleshooting steps that currently only show Windows/PowerShell approaches.
- Highlight platform-specific sections with clear headers or notes to help users quickly identify relevant content.
Azure Government
Azure guidance for secure isolation
...es/azure-government/azure-secure-isolation-guidance.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 secure isolation. However, there are several instances where Windows tools, technologies, and terminology are mentioned first or in greater detail, such as Hyper-V, BitLocker, Windows Firewall, and PowerShell. Examples and references to Windows-specific features (e.g., RDP, Windows Server, Windows Firewall) often precede or are more detailed than their Linux equivalents (e.g., SSH, DM-Crypt). Azure PowerShell is frequently referenced as a management tool, sometimes before Azure CLI. While Linux is supported and mentioned, Windows-centric patterns and terminology are more prominent throughout the document.
Recommendations
- Ensure that Linux and cross-platform examples (e.g., Azure CLI, SSH, DM-Crypt) are presented alongside or before Windows/PowerShell examples where applicable.
- Where Windows tools or terminology are used (e.g., BitLocker, Windows Firewall, PowerShell), provide equivalent Linux references (e.g., DM-Crypt, iptables/firewalld, Azure CLI) with equal detail.
- Explicitly state cross-platform support in sections that discuss VM management, disk encryption, and network isolation.
- Balance the use of Windows-centric terminology with neutral or platform-agnostic language when describing Azure features that apply to both Windows and Linux workloads.
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 via the Portal, Azure CLI, REST API, and PowerShell. While Azure CLI and REST API are cross-platform, the PowerShell section is detailed and lists multiple connection types, and PowerShell is a Windows-centric tool (though available on Linux/macOS). The PowerShell instructions and references appear more extensive than for CLI, and PowerShell is mentioned after CLI but before REST API. There are no Linux/macOS-specific examples or tools (e.g., Bash, curl), and no explicit mention of Linux/macOS parity.
Recommendations
- Add explicit Bash or shell examples for connecting to Azure Government, especially for REST API access (e.g., using curl or wget).
- Clarify that Azure CLI is fully cross-platform and provide examples for Linux/macOS users, such as installation instructions or shell usage.
- Consider mentioning that PowerShell Core is available on Linux/macOS, or link to cross-platform PowerShell installation guides.
- Ensure parity in example depth between CLI and PowerShell sections, so Linux/macOS users do not feel CLI is less supported.
Azure Resource Manager
Bicep functions - resources
...ure-resource-manager/bicep/bicep-functions-resource.md
Low Priority
View Details →
Detected Bias Types
windows_tools
Summary
The documentation provides both PowerShell and Azure CLI examples for discovering list operations, but PowerShell (Get-AzProviderOperation) is mentioned first and in more detail, which may indicate a slight Windows bias. All other examples and instructions are platform-neutral and do not rely on Windows-specific tools or patterns.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tooling.
- Ensure that CLI examples are as detailed as PowerShell ones, including output formatting and filtering.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, and provide links to installation guides for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
windows_first
windows_tools
Summary
The 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, and the VSS (Windows Volume Shadow Copy Service) entry links only to Windows documentation. In the 'Application consistent backup' entry, VSS is mentioned before Linux scripts. The 'Snapshot' entry links to a Windows-specific disk snapshot page first. However, most terms are generic or Azure-specific, and Linux workloads (such as Azure File shares, PostgreSQL) are included. No critical Linux/macOS functionality is omitted.
Recommendations
- For terms like VSS, clarify that Linux uses pre/post scripts and link to relevant Linux backup documentation.
- In entries where both Windows and Linux approaches exist (e.g., application consistent backup), present them with equal prominence.
- Where possible, provide links to Linux/macOS backup documentation or mention Linux equivalents alongside Windows tools.
- For 'Snapshot', include links to both Windows and Linux disk snapshot documentation if available.
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
missing_linux_example
Summary
The documentation page presents deployment options for Azure Container Apps but demonstrates subtle Windows bias. Visual Studio is mentioned before Visual Studio Code, and PowerShell is referenced alongside Bash in CLI automation, but no Linux/macOS-specific editors or workflows are highlighted. There are no explicit Linux/macOS examples or tool recommendations, and Windows-oriented tools (Visual Studio, PowerShell) are referenced first or exclusively.
Recommendations
- Include explicit examples and guidance for Linux/macOS users, such as using VS Code on Linux, JetBrains IDEs, or other cross-platform editors.
- Provide Bash-only automation examples, or clarify parity between PowerShell and Bash for CLI tasks.
- Mention Linux/macOS prerequisites and workflows where relevant, such as Docker installation or CLI usage on those platforms.
- Balance the order of tool presentation (e.g., mention VS Code before Visual Studio, or together) to avoid Windows-first perception.
Low Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The Azure Bastion FAQ page demonstrates minor Windows bias in several areas. Browser recommendations mention Windows first and provide more detail for Windows users, while Linux is not mentioned at all. Keyboard layout configuration instructions are only provided for Windows workstations, with no guidance for Linux or macOS users. There are no explicit examples or instructions for Linux users regarding connecting to VMs, configuring keyboard layouts, or using native clients.
Recommendations
- Include browser recommendations for Linux (e.g., Chrome, Firefox) alongside Windows and macOS.
- Add instructions or references for configuring keyboard layouts on Linux and macOS systems.
- Provide examples or notes for connecting to Linux VMs, including any OS-specific considerations for SSH/RDP via Bastion.
- Ensure parity in native client documentation by mentioning Linux-compatible clients and workflows.
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
powershell_heavy
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently shown first. This ordering may subtly signal a Windows-first approach, and the explicit use of PowerShell tabs could be interpreted as a slight bias toward Windows users. However, curl examples are present and fully functional for Linux/macOS users. All core deployment and setup instructions use Azure CLI, which is cross-platform.
Recommendations
- Alternate the order of PowerShell and curl examples, or show curl first to better represent Linux/macOS users.
- Explicitly state that curl commands work on Linux/macOS and that PowerShell is for Windows users.
- Consider adding bash script examples for multi-step processes, if applicable.
- Ensure screenshots and portal instructions do not assume Windows-only environments.
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 and PowerShell examples for all Azure CLI commands, ensuring cross-platform coverage. However, PowerShell examples are present throughout, and in some sections (such as deployment and log viewing), PowerShell examples are shown immediately after Bash, which may suggest a slight Windows-first bias. There are no Linux-specific tools or patterns missing, and all instructions are compatible with Linux/macOS. The presence of PowerShell examples is helpful for Windows users but could be seen as slightly favoring Windows environments.
Recommendations
- Consider explicitly stating that Bash examples work on Linux/macOS and WSL, while PowerShell is for Windows users.
- Ensure that Bash examples are presented first in all sections to reinforce Linux parity.
- Add a note clarifying that all steps can be completed on Linux/macOS without PowerShell.
- Where possible, mention that Azure CLI is cross-platform and does not require PowerShell.
Container Apps
Troubleshooting in Azure Container Apps
...s/blob/main/articles/container-apps/troubleshooting.md
Low Priority
View Details →
Detected Bias Types
windows_tools
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Container Apps, but there is mild evidence of Windows bias. Windows/PowerShell tools and terminology are mentioned (e.g., 'elevated command prompt', 'cmdlets from the Az.App module'), and PowerShell examples are given alongside Bash, but Windows-specific instructions (such as running Docker on Windows) are referenced before Linux equivalents. There are no explicit Linux/macOS instructions or references to Linux-specific tools, and some steps (like 'elevated command prompt') assume a Windows environment.
Recommendations
- Include explicit instructions and examples for Linux/macOS users, such as running Docker commands in a Linux terminal.
- When referencing command-line actions, avoid Windows-centric terms like 'elevated command prompt'; instead, mention both Windows and Linux/macOS equivalents (e.g., 'run in an elevated command prompt (Windows) or with sudo in a Linux/macOS terminal').
- Provide parity in CLI examples, ensuring both Bash and PowerShell are equally represented and contextualized.
- Reference Docker installation and usage guides for Linux/macOS alongside Windows.
- Clarify that Azure CLI and PowerShell modules are cross-platform, and provide installation/update instructions for Linux/macOS where relevant.
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides authentication setup instructions for Azure CycleCloud, including built-in, Active Directory, LDAP, and Entra ID methods. In the Active Directory section, Windows authentication patterns (DOMAIN\user) are described first and highlighted in the example, with no mention of Linux authentication patterns (e.g., user@domain.com) or Linux-specific considerations. However, the overall instructions are platform-neutral, and the LDAP and Entra ID sections mention Linux clusters and SSH keys.
Recommendations
- In the Active Directory section, explicitly mention Linux authentication patterns (e.g., user@domain.com) and clarify that both Windows and Linux users can authenticate using UPN format.
- Add examples or notes for Linux/macOS users where authentication patterns or tools differ (e.g., clarify that DOMAIN\user is typical for Windows, while user@domain.com is common for Linux/macOS).
- Ensure screenshots and examples show both Windows and Linux authentication scenarios where relevant.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_tools
Summary
The documentation is generally platform-neutral, but there are minor signs of Windows bias. Specifically, mitigation steps for adding tags to Azure Firewall Policy mention using the Azure PowerShell cmdlet (`Set-AzFirewallPolicy`), with no mention of equivalent CLI or REST API methods. Additionally, the 'Missing PowerShell and CLI support for ICMP' issue references Azure PowerShell and CLI, but does not clarify Linux/macOS alternatives or parity. There are also references to IIS for FTP configuration, which is a Windows-specific tool, without mentioning Linux FTP server equivalents.
Recommendations
- Where PowerShell is suggested for configuration (e.g., updating tags), also provide Azure CLI and REST API alternatives, and clarify their cross-platform availability.
- When referencing FTP server configuration, include examples or links for popular Linux FTP servers (such as vsftpd or ProFTPD) alongside IIS.
- Explicitly state platform parity for Azure CLI and REST API usage, especially for tasks currently only documented with PowerShell.
- Review mitigation steps to ensure Linux/macOS users are not left without guidance for critical operations.