1642
Pages Scanned
58
Pages Flagged
1642
Changed Pages
3.5%
% Pages Flagged
Scan Information
Started At: 2026-01-10 00:00:06
Finished At: 2026-01-11 02:52:32
Status: completed
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 1642
Files Completed: 1642
Problematic Pages
58 issues found
Service Fabric
Service Fabric app upgrade tutorial
...-fabric/service-fabric-application-upgrade-tutorial.md
High Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The tutorial is heavily focused on Visual Studio, a Windows-centric tool, with all steps and screenshots assuming a Windows environment. There are no Linux/macOS equivalents or alternative instructions for non-Windows users. The only alternative mentioned is a separate PowerShell tutorial, which is also Windows-focused. No cross-platform CLI or Linux-native tooling is referenced.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl).
- Include examples and screenshots for Linux/macOS environments, such as using VS Code or command-line workflows.
- Explicitly mention platform requirements and offer guidance for non-Windows users at the start of the tutorial.
- Link to or create tutorials for Linux/macOS users covering the same upgrade workflow.
Create Pull Request
Service Fabric
Update the RDP username and password in PowerShell
...ts/service-fabric-powershell-change-rdp-user-and-pw.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples and instructions use Azure PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS-compatible workflows. The script and command explanations are PowerShell-only, and installation instructions reference only the Azure PowerShell guide. There are no Linux or cross-platform alternatives provided.
Recommendations
- Add equivalent Azure CLI or Bash examples for updating RDP credentials on VMSS nodes.
- Include installation instructions for Azure CLI and note its cross-platform compatibility.
- Explicitly state platform requirements and provide guidance for Linux/macOS users.
- Reorder sections to present cross-platform solutions before or alongside Windows/PowerShell ones.
Service Fabric
How to migrate to TLS (Transport Layer Security) 1.3 for Service Fabric
...vice-fabric/how-to-migrate-transport-layer-security.md
High Priority
View Details â
Detected Bias Types
windows_only
missing_linux_example
windows_tools
windows_first
Summary
The documentation is explicitly Windows-centric, stating that Linux is not supported for TLS 1.3 migration in Service Fabric clusters. All prerequisites, upgrade instructions, and compatibility notes reference Windows Server, PowerShell, and Windows application manifests. There are no Linux equivalents, examples, or instructions, and Linux users are told outright that the steps do not apply to them.
Recommendations
- Add a clear roadmap or timeline for Linux support for TLS 1.3 in Service Fabric clusters.
- Provide alternative instructions or workarounds for Linux users, or explicitly link to relevant Linux documentation.
- Include a prominent callout at the top of the article clarifying the lack of Linux support and suggesting next steps for Linux users.
- When Linux support is available, ensure examples, prerequisites, and upgrade steps are provided for both Windows and Linux, with parity in detail and order.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
High Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias: all code examples use Windows containers and Windows-specific commands (cmd, set, exit, etc.), and the example explicitly references Windows container images. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux CLI or cross-platform alternatives. There are no Linux container or macOS examples, nor any guidance for non-Windows environments.
Recommendations
- Add parallel examples using Linux containers (e.g., Ubuntu or Alpine images) with equivalent shell commands.
- Include instructions for querying deployment status using Service Fabric CLI (sfctl), which is cross-platform.
- Clarify which features and patterns are supported on Linux clusters, and note any differences.
- Present examples for both Windows and Linux side-by-side, or indicate platform-specific sections.
- Reference Linux container compatibility and provide links to relevant documentation.
Service Fabric
Troubleshooting application upgrades
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-troubleshooting.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page exclusively uses PowerShell commands and outputs for troubleshooting Service Fabric application upgrades, with no mention of Linux or macOS equivalents (such as Azure CLI, REST API, or Service Fabric CLI). All example commands and troubleshooting steps are Windows-centric, and the 'Next steps' section prioritizes Visual Studio and PowerShell, both Windows-focused tools. There is no guidance for users on Linux or macOS platforms, nor any cross-platform instructions.
Recommendations
- Add equivalent examples using Azure CLI, Service Fabric CLI (sfctl), or REST API for all PowerShell commands.
- Explicitly mention cross-platform tools and workflows for troubleshooting upgrades on Linux/macOS clusters.
- Include sample outputs and troubleshooting steps for Linux environments.
- In the 'Next steps' section, link to upgrade tutorials using CLI or REST API, not just Visual Studio and PowerShell.
- Where possible, provide a table or side-by-side comparison of commands for Windows (PowerShell) and Linux/macOS (CLI).
Service Fabric
On-demand backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-ondemand-backup.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell and require the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no CLI or script examples for Linux/macOS users (e.g., Bash, Azure CLI, curl). The prerequisites and workflow assume a Windows environment, and Windows tools are mentioned exclusively and first. This creates friction for Linux/macOS users and may prevent them from completing the task without significant adaptation.
Recommendations
- Provide equivalent examples using Bash, Azure CLI, or curl for Linux/macOS users.
- Clarify whether the PowerShell module is cross-platform (PowerShell Core) or Windows-only, and offer alternatives if needed.
- Add instructions for connecting to clusters and triggering backups using REST APIs with non-PowerShell tools.
- Mention Linux/macOS compatibility and requirements explicitly in the prerequisites.
- Reorder examples to present cross-platform or REST API methods before Windows/PowerShell-specific ones.
Virtual Machines
Deploy Ephemeral OS disks
...articles/virtual-machines/ephemeral-os-disks-deploy.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both platform-neutral (ARM template, REST, Azure CLI) and Windows-specific (PowerShell) instructions, but there is a noticeable Windows bias. PowerShell examples are given their own section, with no equivalent for Linux shell scripting. VM template examples use Windows images and passwords, and admin credentials are Windows-style. Windows tools and patterns (PowerShell, Windows image references) are mentioned exclusively or before Linux equivalents, and Linux-specific examples (e.g., Bash scripting, Linux image references) are missing.
Recommendations
- Add explicit Linux shell (Bash) scripting examples for deploying ephemeral OS disks, especially for tasks currently only shown in PowerShell.
- In ARM template examples, provide both Windows and Linux image references, and use platform-neutral admin credential patterns (e.g., SSH keys for Linux).
- In CLI examples, clarify Linux-specific options (e.g., --generate-ssh-keys) and show full Linux VM deployment flows.
- Where PowerShell is mentioned, also mention Bash/Cloud Shell alternatives for Linux/macOS users.
- Ensure screenshots and UI instructions are not Windows-centric.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides a detailed PowerShell script as the only example for determining VM size support for ephemeral OS disks, with no equivalent CLI, Bash, or Linux-native example. Windows/PowerShell tooling is mentioned first and exclusively in the example, creating friction for Linux/macOS users who may prefer or require Azure CLI or Bash scripts.
Recommendations
- Add equivalent Azure CLI and Bash examples for checking VM size support for ephemeral OS disks.
- Present both PowerShell and CLI/Bash examples side-by-side, or alternate which is shown first.
- Explicitly mention Linux/macOS compatibility and provide guidance for non-Windows users.
- Clarify which tools are cross-platform and which are Windows-specific.
Container Instances
Standby pools for Azure Container Instances
...instances/container-instances-standby-pool-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation demonstrates a moderate Windows bias, primarily through the use of PowerShell for provider registration and by presenting PowerShell examples before Linux-friendly CLI equivalents in key sections. The initial prerequisite for provider registration is shown only with PowerShell, and in the availability zones section, PowerShell is listed before REST and CLI, which may create friction for Linux/macOS users.
Recommendations
- Provide Azure CLI commands alongside PowerShell for all resource provider registration and management tasks, especially in the prerequisites section.
- Present CLI examples before PowerShell, or at least in parallel, to avoid implying Windows-first workflows.
- Explicitly mention that all commands can be run from Azure Cloud Shell, which is cross-platform.
- Where possible, include bash and shell script examples for Linux/macOS users.
- Add notes or links for Linux/macOS users on how to install and use Azure CLI.
Container Instances
Get standby pool for Azure Container Instances details
...tances/container-instances-standby-pool-get-details.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. While the CLI and REST sections are cross-platform, the PowerShell example is Windows-centric and is presented before any Linux/macOS shell alternatives (e.g., Bash). There are no Linux-specific shell examples (such as Bash or scripting with curl/jq), and PowerShell is featured as a primary method, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add Bash or shell script examples using curl and jq for Linux/macOS users.
- Clarify that Azure CLI and REST API examples are cross-platform and can be run on Linux/macOS.
- Consider moving PowerShell examples after CLI/Bash examples or grouping them in a separate Windows section.
- Explicitly mention Linux/macOS compatibility in the CLI and REST sections.
Container Instances
Request a container from a Standby pool for Azure Container Instances
...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-request-container.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for requesting a container from a standby pool, but PowerShell (a Windows-centric tool) is given its own dedicated section and example. The ARM template section references both CLI and PowerShell deployment methods, but PowerShell is mentioned explicitly. There are no Linux shell-specific examples (e.g., Bash scripts), and PowerShell is presented as a primary method alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, especially for scripting and automation.
- Clarify that Azure CLI commands work cross-platform and provide any necessary notes for Linux/macOS usage (e.g., line continuation differences).
- If PowerShell is mentioned, also mention Bash or other popular Linux shells in parallel.
- Avoid presenting PowerShell as a primary or default method unless parity is maintained with Linux/macOS alternatives.
- Ensure that all referenced tools and patterns are available and documented for Linux/macOS users.
Container Instances
Use Azure Log Analytics to monitor standby pool events for Azure Container Instances
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pools-monitor-pool-events.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring diagnostic settings, but PowerShell is given equal prominence despite being Windows-centric. The instructions for creating a Log Analytics workspace and setting up alerts are exclusively portal-based, which is platform-neutral but may favor Windows users due to the portal's typical association with Windows workflows. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a primary SDK alternative alongside CLI, with no mention of Bash or Linux-specific tools. REST API usage is included, which is cross-platform, but overall, the documentation leans toward Windows/PowerShell usage and does not offer Linux-specific guidance or parity.
Recommendations
- Add explicit Bash examples for configuring diagnostic settings using Azure CLI to demonstrate Linux/macOS workflows.
- Clarify that Azure CLI commands work natively on Linux/macOS and provide any necessary platform-specific notes (e.g., authentication, environment setup).
- Include references to Linux/macOS terminal usage where appropriate, especially in sections discussing SDK alternatives.
- If PowerShell is mentioned, also mention Bash or other Linux-native scripting environments to ensure parity.
- Consider reordering examples to show CLI/Bash first, then PowerShell, to avoid implicit Windows-first bias.
Container Instances
Tutorial - Trigger container group by Azure function
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-tutorial-azure-function-trigger.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 all code samples and automation steps using Azure PowerShell cmdlets. There are no equivalent Bash, Azure CLI, or Linux-native examples for function creation, resource management, or automation. Visual Studio Code is referenced, but only in the context of PowerShell and the Azure Functions extension, with no mention of Linux/macOS-specific workflows or alternatives. The prerequisites and step-by-step instructions assume use of PowerShell and Windows tools, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all resource management tasks, such as enabling managed identity, assigning roles, and creating container groups.
- Include Bash or cross-platform scripting samples for the function code, or reference how to use other supported languages (e.g., Python, JavaScript) in Azure Functions.
- Explicitly mention Linux/macOS support in prerequisites and provide links to relevant setup guides.
- Show how to use Visual Studio Code and the Azure Functions extension on Linux/macOS, including any differences in workflow.
- Offer a parallel tutorial using Azure CLI and Bash for users who prefer or require non-Windows environments.
Container Instances
Update or delete a standby pool for Azure Container Instances
...nces/container-instances-standby-pool-update-delete.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given its own tab and is featured equally alongside CLI. There is no mention of Linux/macOS-specific shell patterns, nor are there Bash or shell script examples. PowerShell is a Windows-first tool, and its inclusion without equivalent Linux/macOS scripting guidance may create friction for non-Windows users.
Recommendations
- Add Bash or shell script examples for Linux/macOS users, especially for tasks that might require scripting.
- Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
- Consider reordering tabs to show Azure CLI first, as it is the most cross-platform tool.
- Explicitly state platform compatibility for each tool (e.g., 'PowerShell: Windows only', 'Azure CLI: Windows, Linux, macOS').
- Provide troubleshooting or installation guidance for Linux/macOS users where PowerShell is mentioned.
Service Fabric
Use Application Gateway in a Service Fabric managed cluster
...e-fabric/how-to-managed-cluster-application-gateway.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only PowerShell-based command examples for critical steps (e.g., getting the Service Principal and assigning roles), with no equivalent CLI or Bash examples for Linux/macOS users. Windows/PowerShell tooling is referenced exclusively and presented first, creating friction for non-Windows users.
Recommendations
- Add Azure CLI equivalents for all PowerShell commands (e.g., az ad sp show, az role assignment create).
- Explicitly mention that steps can be performed on Linux/macOS using Azure CLI or Bash.
- Provide example scripts for Linux/macOS environments alongside PowerShell examples.
- Consider reordering examples so that cross-platform (CLI) options are shown first or side-by-side with PowerShell.
Service Fabric
Use Azure DDoS Protection in a Service Fabric managed cluster
...rvice-fabric/how-to-managed-cluster-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell examples for key steps (service principal lookup, role assignment), mentioning PowerShell before Azure CLI, and omitting equivalent Linux/macOS-friendly CLI commands. No Bash or Azure CLI examples are given for tasks that can be performed cross-platform, creating friction for non-Windows users.
Recommendations
- Add Azure CLI examples for all PowerShell commands, especially for service principal lookup and role assignment.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI.
- Present CLI/Bash examples before or alongside PowerShell to improve parity.
- Include notes or links to cross-platform tooling for ARM template deployment and role assignment.
Service Fabric
Create a Service Fabric managed cluster (SFMC) with Ephemeral OS disks for node types
...ce-fabric/how-to-managed-cluster-ephemeral-os-disks.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for ARM template deployment, referencing RDP (a Windows-specific remote access protocol) for admin access, and omitting equivalent Linux/macOS command-line instructions (such as Azure CLI or Bash). Windows tools and patterns are mentioned exclusively or before Linux alternatives, making it harder for non-Windows users to follow the guide.
Recommendations
- Add Azure CLI examples for ARM template deployment, showing Linux/macOS compatible commands.
- Mention SSH as an alternative to RDP for VM access, and clarify admin username/password usage for Linux-based VMs.
- Present deployment options for both Windows and Linux/macOS users side-by-side, or in parallel sections.
- Explicitly state that the instructions apply to both Windows and Linux, or note any platform-specific differences.
- Include Bash script examples for template deployment where appropriate.
Service Fabric
Set up IP tags on a Service Fabric managed cluster
...icles/service-fabric/how-to-managed-cluster-ip-tags.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation page references provisioning IP tags using a PowerShell module (Az.Network) and links to a PowerShell-specific example, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or REST API). This creates a bias towards Windows environments and tools.
Recommendations
- Include Azure CLI examples for provisioning IP tags, as CLI is cross-platform and widely used on Linux/macOS.
- Reference REST API methods for advanced users who may prefer scripting outside of PowerShell.
- Explicitly state that the process can be completed on Linux/macOS and provide links to relevant documentation.
- Reorder examples so that cross-platform tools (CLI, REST) are mentioned before or alongside PowerShell.
Service Fabric
Deploy application secrets to a Service Fabric managed cluster
...e-fabric/how-to-managed-cluster-application-secrets.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (such as the Key Vault VM extension for Windows) and certificate store names (e.g., 'MY'), and links to Windows-focused documentation. There are no explicit Linux/macOS examples or guidance, and Linux equivalents for certificate installation and management are not mentioned, making it harder for non-Windows users to follow the instructions.
Recommendations
- Add explicit instructions and examples for Linux-based Service Fabric clusters, including how to install certificates and manage secrets using Linux tools.
- Reference the Key Vault VM extension for Linux and provide a link to its documentation.
- Clarify certificate store naming conventions for Linux and macOS environments.
- Present cross-platform guidance side-by-side, or clearly indicate platform-specific steps.
- Include PowerShell, CLI, and bash examples where relevant.
Service Fabric
Configure maintenance control for Service Fabric managed cluster
...e-fabric/how-to-managed-cluster-maintenance-control.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation exclusively provides PowerShell-based examples for all resource creation, deployment, and status checking steps, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows/PowerShell tooling is assumed throughout, and Linux/macOS users are not given alternative commands or guidance.
Recommendations
- Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Explicitly mention that the steps can be performed from any OS using Azure CLI, and provide Bash script snippets where appropriate.
- Include a note or section on platform compatibility, clarifying that the process is not Windows-specific and listing supported tools for Linux/macOS.
- Reorder examples so that cross-platform tools (Azure CLI) are shown first or alongside PowerShell.
Service Fabric
Add a virtual machine scale set extension to a Service Fabric managed cluster node type
...ervice-fabric/how-to-managed-cluster-vmss-extension.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates a notable Windows bias. The only CLI example provided is for PowerShell (Add-AzServiceFabricManagedNodeTypeVMExtension), with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The VM extension example uses 'KeyVaultForWindows', a Windows-specific extension type, without referencing Linux equivalents or cross-platform options. Windows-centric tools and patterns are mentioned exclusively and appear first, while Linux support is not addressed.
Recommendations
- Add Azure CLI and/or Bash examples for adding VM scale set extensions to Service Fabric managed cluster node types.
- Explicitly mention and provide examples for Linux-compatible VM extensions (e.g., KeyVaultForLinux) in ARM templates.
- Clarify cross-platform support for Service Fabric managed clusters and extensions, including any OS-specific requirements or limitations.
- Reorder examples to present cross-platform or Linux options alongside or before Windows-specific ones.
- Include a table or section comparing extension types and their OS compatibility.
Service Fabric
Configure or modify a Service Fabric managed cluster node type
...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure placement properties), but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its usage is presented as the sole scripting option. There is no mention of cross-platform alternatives, and PowerShell examples are given before or instead of any Linux-friendly options. This creates friction for users on non-Windows platforms.
Recommendations
- Add Azure CLI examples for all operations currently shown only with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant, and clarify any differences in usage.
- Provide Bash or REST API examples where appropriate.
- In each section, present cross-platform options (Azure CLI, REST) before or alongside PowerShell, not after.
- Include notes or links to cross-platform tooling documentation for Service Fabric management.
Service Fabric
Service Fabric Explorer blocking operations
...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources. There is no mention of Linux/macOS equivalents, such as Bash/CLI commands, nor are cross-platform instructions provided. The examples and guidance assume the use of Windows-centric tools, creating friction for users on Linux or macOS.
Recommendations
- Include Azure CLI examples for each operation alongside PowerShell cmdlets, as Azure CLI is cross-platform.
- Explicitly state which commands/tools are supported on Linux/macOS and provide links to relevant documentation.
- Add Bash script examples for common operations, or clarify how Linux/macOS users can perform these tasks.
- Reorder examples so that cross-platform tools (e.g., Azure CLI) are presented before or alongside Windows-specific tools.
Service Fabric
Add application cert to a cluster in PowerShell
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/scripts/service-fabric-powershell-add-application-certificate.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation is exclusively focused on Azure PowerShell, providing only PowerShell script examples and instructions. There are no Bash, Azure CLI, or Linux/macOS-specific examples or guidance. Windows-centric terminology (e.g., certificate store paths like LocalMachine\My) is used, and all tooling references are for PowerShell, which is native to Windows. This creates friction for Linux/macOS users who may prefer or require Bash/Azure CLI workflows.
Recommendations
- Add equivalent Azure CLI and/or Bash script examples for each major step (certificate creation, upload, VMSS update).
- Include notes on cross-platform compatibility of PowerShell Core, and clarify if scripts work on Linux/macOS PowerShell.
- Mention Linux certificate store paths and how to handle certificates on Linux VMSS nodes.
- Provide links to Linux/macOS-specific documentation or troubleshooting guides.
- Reorder or parallelize examples so Linux/Azure CLI options are presented alongside PowerShell/Windows options.
Service Fabric
Add a managed identity to a Service Fabric managed cluster node type
...ed-identity-managed-cluster-virtual-machine-scale-sets.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page is heavily biased towards Windows and PowerShell usage. All command-line examples use PowerShell cmdlets, with no Azure CLI or Bash alternatives provided. The VM image example uses Windows Server exclusively, and there is no mention of Linux-based node types or deployment patterns. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using Bash/Azure CLI.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples, especially for identity creation, role assignment, and deployment steps.
- Include examples of deploying Service Fabric node types using Linux VM images (e.g., Ubuntu), and clarify any differences or limitations.
- Add notes or sections specifically addressing Linux/macOS users, including setup instructions and troubleshooting relevant to those platforms.
- Present examples for both Windows and Linux in parallel, or at least alternate which is shown first to avoid implicit prioritization.
Service Fabric
Describing Azure Service Fabric apps and services
...ic/service-fabric-application-and-service-manifests.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation page displays mild Windows bias, primarily in its tooling recommendations and file path references. The only explicit tool suggestion for authoring manifests is to open the ServiceFabricServiceModel.xsd schema in Visual Studio, referencing a Windows file path (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). No Linux/macOS equivalent tool or workflow is mentioned. Additionally, the PowerShell module is referenced for service creation, but no Linux CLI alternative is provided or discussed.
Recommendations
- Include instructions or recommendations for editing and validating manifest XML files on Linux/macOS, such as using VS Code, JetBrains Rider, or command-line XML validators.
- Provide Linux/macOS file paths for Service Fabric SDK schema files, if available, or clarify how to obtain them on non-Windows platforms.
- Mention cross-platform Service Fabric CLI (sfctl) commands for service creation and management, alongside or instead of PowerShell.
- Avoid referencing Windows tools (Visual Studio, PowerShell) exclusively; offer parity in examples and tool suggestions.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased towards Windows, with all command-line examples using PowerShell cmdlets and references to Windows-centric tools (Visual Studio, PowerShell). There are no CLI, Bash, or Linux-native examples, nor are cross-platform alternatives mentioned. This creates friction for Linux/macOS users who may use Service Fabric CLI (sfctl) or ARM templates exclusively.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for all PowerShell cmdlets.
- Explicitly mention cross-platform tools and workflows, such as ARM templates and REST APIs, where applicable.
- Include Linux/macOS-specific instructions for common upgrade scenarios.
- Reorder examples to present cross-platform options first, or side-by-side with Windows/PowerShell examples.
- Clarify which features are available via CLI, REST, or ARM, and note any platform limitations.
Service Fabric
Application upgrade: data serialization
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-application-upgrade-data-serialization.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page exhibits Windows bias by referencing Visual Studio and PowerShell as primary upgrade methods, both of which are Windows-centric tools. There are no explicit Linux/macOS equivalents or examples provided for application upgrades, and the upgrade tutorials listed in 'Next steps' focus on Windows tools first, with no mention of cross-platform CLI alternatives.
Recommendations
- Add explicit instructions and examples for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which work on Linux/macOS.
- Include links to tutorials or documentation for Linux/macOS users, ensuring parity with Visual Studio and PowerShell guides.
- Reorder 'Next steps' to present cross-platform methods before or alongside Windows-specific tools.
- Clarify which tools are Windows-only and provide alternatives for other platforms.
Service Fabric
Service Fabric application upgrade
...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent CLI or Linux/macOS instructions. Windows-specific tools (PowerShell, http.sys) are referenced exclusively or before any cross-platform alternatives. The troubleshooting and next steps sections also direct users to Windows/PowerShell/Visual Studio-based tutorials, with no mention of Linux or cross-platform workflows.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
- Explicitly mention Linux/macOS support and provide links to relevant documentation for those platforms.
- When referencing Windows-specific tools (e.g., http.sys), clarify the behavior or alternatives on Linux.
- Ensure that upgrade instructions and troubleshooting guides include both Windows and Linux/macOS workflows.
- Reorder examples so that cross-platform tools (CLI) are shown before or alongside Windows/PowerShell examples.
Service Fabric
Create clusters on Windows Server and Linux
...rvice-fabric/service-fabric-azure-clusters-overview.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page describes Service Fabric clusters on both Windows Server and Linux, but the technical details and examples focus exclusively on Windows-specific tools and processes (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe). There are no Linux-specific equivalents or instructions, nor any mention of Linux service management or process names, which may leave Linux users unclear about how the cluster operates or is managed on their platform.
Recommendations
- Add explicit references to Linux equivalents for Service Fabric processes (e.g., systemd service names, process names, or management commands).
- Include examples or explanations for how cluster nodes are managed and started on Linux (e.g., how the Service Fabric runtime is launched, what services are involved, and how to troubleshoot).
- Where Windows-specific executables are mentioned, provide a parallel description for Linux (e.g., what replaces FabricHost.exe, Fabric.exe, and FabricGateway.exe on Linux).
- Clarify any differences in deployment, management, or troubleshooting between Windows and Linux clusters.
- Consider adding a table or section that compares Windows and Linux cluster node architecture and management.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias primarily in the backup storage configuration section, where file share examples use Windows UNC paths (\\StorageServer\BackupStore) and reference Integrated Windows Authentication. No Linux or cross-platform file share examples (e.g., NFS, SMB mounting on Linux) are provided, nor are Linux authentication patterns discussed. Windows-specific terminology and patterns are presented first and exclusively, potentially leaving Linux/macOS users without clear guidance for on-premises backup storage configuration.
Recommendations
- Add examples for configuring file share backup storage using Linux-compatible paths and protocols (e.g., NFS, SMB/CIFS mounts).
- Document authentication methods for Linux environments, such as username/password for SMB, Kerberos, or NFS exports.
- Clarify whether Service Fabric supports Linux-based file shares and provide step-by-step instructions for Linux/macOS users.
- Reorder or parallelize examples so that Windows and Linux approaches are presented side-by-side.
- Explicitly mention any platform limitations or differences in backup storage configuration.
Service Fabric
Set up Microsoft Entra ID for client authentication in the Azure portal
...vice-fabric-cluster-creation-setup-azure-ad-via-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides only PowerShell-based examples for connecting to Service Fabric clusters with Microsoft Entra ID, with no mention of Linux/macOS command-line alternatives (e.g., Azure CLI, REST API, or cross-platform SDKs). Troubleshooting and connection instructions are exclusively focused on PowerShell, which is primarily a Windows tool. There is a brief note about Linux limitations, but no Linux-specific guidance or parity in examples.
Recommendations
- Add equivalent Linux/macOS connection instructions using Azure CLI, REST API, or cross-platform SDKs.
- Include troubleshooting steps for Linux users, especially given the known portal viewing issue.
- Clearly indicate which steps are platform-agnostic and which require Windows-specific tools.
- Provide links or references to Service Fabric tools and SDKs available for Linux/macOS.
- If PowerShell is required on Linux, explain how to install and use PowerShell Core on Linux.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific tools (PowerShell, Windows Defender, DSC) are mentioned and exemplified before or more prominently than Linux equivalents. Some sections (e.g., Windows Defender, security baselines) are Windows-only, and Windows examples (PowerShell) are presented before Linux (bash/openssl) in encryption workflows. Linux guidance is present but less detailed or secondary in order.
Recommendations
- Present Linux and Windows examples side-by-side or in parallel sections, rather than Windows first.
- Provide equivalent Linux tooling recommendations (e.g., mention Linux antivirus solutions, security baselines) where Windows tools are discussed.
- Clarify when a feature or tool is Windows-only and suggest Linux alternatives or workarounds.
- Expand Linux-specific instructions and examples to match the detail provided for Windows.
- Where possible, use cross-platform commands or scripts (e.g., Azure CLI) as primary examples.
Service Fabric
Create a cluster using certificate common name
...-fabric/service-fabric-create-cluster-using-cert-cn.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page exclusively provides PowerShell commands and Windows file path examples for certificate management and cluster deployment, with no mention of Linux/macOS equivalents or cross-platform tools. All scripting and automation steps assume a Windows environment, creating friction for users on other platforms.
Recommendations
- Provide equivalent Bash/Azure CLI examples for certificate upload and deployment steps.
- Mention cross-platform tools (e.g., Azure CLI, OpenSSL) for certificate handling and template deployment.
- Use platform-neutral file paths in examples, or show both Windows and Linux/macOS paths.
- Explicitly state platform requirements or limitations, and link to Linux/macOS instructions if available.
Service Fabric
Service Fabric Backup and Restore
...ric/service-fabric-reliable-services-backup-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit tooling example for testing backup and restore is the PowerShell cmdlet 'Start-ServiceFabricPartitionDataLoss', with no mention of Linux/macOS equivalents or cross-platform CLI alternatives. There are references to .NET APIs and Windows-specific workarounds (e.g., kernel32 APIs for long paths), but no guidance for Linux/macOS users. There are no Linux shell or cross-platform CLI examples for backup/restore operations, and Windows tools are mentioned exclusively.
Recommendations
- Provide equivalent Linux/macOS instructions for testing backup and restore, such as using Azure CLI, Service Fabric CLI (sfctl), or REST APIs.
- Mention and demonstrate cross-platform alternatives to PowerShell cmdlets, e.g., sfctl commands for inducing data loss and restoring partitions.
- Add notes or examples for handling long file paths on Linux/macOS, including relevant system calls or utilities.
- Ensure that tooling and code samples are presented in a platform-neutral way, or provide parallel examples for both Windows and Linux/macOS environments.
Service Fabric
Change FabricTransport settings
...service-fabric-reliable-actors-fabrictransportsettings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias in several ways: certificate configuration examples consistently use Windows-centric terminology and values (e.g., 'LocalMachine', 'My', 'WinFabric-Test-SAN1-Alice'), and do not provide equivalent Linux configuration examples. While there is a brief note about PEM-formatted certificates for Linux, all XML examples and parameter values are tailored to Windows certificate stores and naming conventions. There are no Linux-specific configuration samples or guidance for Linux certificate store locations, names, or patterns.
Recommendations
- Add explicit Linux configuration examples, including XML snippets with Linux-appropriate values for certificate store location and name.
- Document the differences in certificate handling between Windows and Linux, such as where certificates should be placed and how to reference them.
- Provide guidance on converting Windows-centric parameters (e.g., 'LocalMachine', 'My') to their Linux equivalents, or clarify which parameters are ignored or required on Linux.
- Include a section or table summarizing platform-specific differences for all relevant settings.
Virtual Machines
Share an Azure managed disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows clustering tools (WSFC) and workloads are described first and in greater detail, with explicit references to Windows-specific features (CSV, Scale-Out File Server, RDS UPD). Windows sample workloads are more numerous and detailed, including links to templates and migration guides. Linux equivalents (Pacemaker, Corosync, ocfs2/gfs2) are mentioned, but with less detail and fewer concrete examples or step-by-step guides. No Linux command-line or configuration examples are provided, while Windows receives more actionable guidance. The examples section also leads with Windows scenarios before Linux.
Recommendations
- Provide Linux-specific step-by-step configuration examples, including commands for Pacemaker, Corosync, and SCSI PR utilities (e.g., sg_persist, fence_scsi).
- Add parity in sample workloads for Linux, such as NFS server clustering, SAP on Linux, and general file server HA setups.
- Include links to Linux templates, guides, or walkthroughs similar to those provided for Windows.
- Present Linux and Windows sections in parallel, or alternate which platform is described first.
- Expand on Linux-specific limitations, best practices, and troubleshooting tips.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page is primarily a changelog and summary of new features for Azure Disk Storage, but there are several instances of Windows bias. Windows documentation links are sometimes listed before Linux equivalents, and some feature references point only to Windows-specific documentation or tools (such as PowerShell). In a few cases, Linux examples or documentation are missing or less visible, which may create friction for Linux/macOS users.
Recommendations
- Ensure all feature documentation links include both Windows and Linux/macOS examples and guides.
- When referencing documentation, list Linux and Windows links together, or alternate which is listed first.
- Avoid referencing Windows-specific tools (e.g., PowerShell) without mentioning or linking to equivalent Linux/macOS tools (e.g., Azure CLI, Bash scripts).
- Audit linked articles to confirm Linux parity in examples and instructions.
- Add explicit notes or sections for Linux/macOS users where workflows differ.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. The primary upload example uses 'AzCopy.exe' with a Windows-style path (c:\somewhere\mydisk.vhd), and does not provide a Linux/macOS equivalent (e.g., 'azcopy' or './azcopy' with POSIX paths). The mention of preparing VHDs links to a Windows-specific guide, with no Linux preparation guidance. While most Azure CLI examples are cross-platform, the AzCopy usage and file path conventions are Windows-centric, and Linux usage is not explicitly shown.
Recommendations
- Provide AzCopy example commands for Linux/macOS, using POSIX-style paths (e.g., '/home/user/mydisk.vhd') and the appropriate binary name ('azcopy' or './azcopy').
- Add a link or section for preparing VHDs on Linux, not just Windows.
- Explicitly mention that AzCopy is available for Linux/macOS and provide installation instructions or a reference.
- Where file paths are shown, include both Windows and Linux/macOS variants, or use generic placeholders.
- Clarify that all Azure CLI commands work on Linux/macOS, and highlight any OS-specific caveats if present.
Virtual Machines
How to Connect to the Azure Image Builder build VM
...al-machines/linux/image-builder-connect-to-build-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits moderate Windows bias. Windows terminology (RDP, WinRM) is frequently mentioned, sometimes before or instead of Linux equivalents (SSH). Examples and links for Windows are often listed first or exclusively, especially in Azure Bastion and Serial Console sections. The password reset instructions reference the Azure portal's 'Reset Password' blade, which is primarily relevant for Windows VMs. Linux-specific connection patterns and troubleshooting steps are less detailed or referenced secondarily.
Recommendations
- Provide explicit Linux SSH examples and command-line instructions alongside Windows RDP/WinRM steps.
- Ensure Linux connection documentation links are presented before or equally with Windows links.
- Clarify which steps (e.g., password reset) apply to Linux VMs and provide Linux-specific guidance (such as SSH key management).
- Avoid using Windows-centric terminology as the default (e.g., mention SSH before RDP/WinRM when discussing connection methods).
- Include troubleshooting tips for Linux users, such as handling SSH connectivity issues or configuring Linux firewalls.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
Although the documentation is targeted at Linux VMs and includes Linux OS-level commands, it presents PowerShell examples before Azure CLI and Linux-native commands. The PowerShell section is extensive, with multiple detailed examples, while Linux-native commands (bash, lsblk, cryptsetup) are only covered at the end and in less detail. This ordering and emphasis may create friction for Linux users who are less familiar with PowerShell or prefer Linux-native tooling.
Recommendations
- Present Azure CLI and Linux-native commands before PowerShell examples, as these are more commonly used by Linux administrators.
- Expand the Linux OS-level section to include more detailed examples, such as checking encryption status for multiple disks, scripting checks, and interpreting output.
- Clarify that PowerShell examples are optional and primarily for users who manage Azure resources from Windows or cross-platform PowerShell.
- Add a summary table comparing methods (Portal, PowerShell, Azure CLI, Linux OS) with pros/cons for Linux users.
- Ensure parity in depth and detail between PowerShell and CLI/Linux-native sections.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows-specific details (such as page file placement and OS image sizing) are often mentioned first or exclusively, and PowerShell is referenced before CLI in some places. Windows tools and patterns (like PowerShell) are highlighted, sometimes before their Linux equivalents. However, Linux examples and references are present, and most features are described for both OS types.
Recommendations
- Ensure that Linux and Windows examples are presented side-by-side or in parallel, rather than Windows first.
- When referencing command-line tools, mention Azure CLI (cross-platform) before PowerShell, or provide both examples together.
- Include explicit Linux-specific details where Windows-specific details are given (e.g., page file placement for Linux).
- Avoid using Windows-centric terminology or examples in sections that apply equally to Linux.
- Where links to PowerShell instructions are provided, ensure equivalent Linux/CLI links are equally prominent.
Virtual Machines
Azure Linux VM Agent Overview
...in/articles/virtual-machines/extensions/agent-linux.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_reference
Summary
The documentation is overwhelmingly Linux-focused, as expected for the Azure Linux VM Agent. However, there is a minor Windows bias in the configuration section: the SSH key type recommendation references putty.exe on Windows, and one of the external links in the Ubuntu Cloud Images section points to a Windows VM deployment tutorial. These inclusions may distract Linux users or suggest Windows tooling as a default.
Recommendations
- Remove or rephrase the reference to putty.exe in the SSH key type section. If mentioning Windows SSH clients, also mention Linux/macOS equivalents for parity.
- Replace or supplement the Windows VM deployment tutorial link in the Ubuntu Cloud Images section with a Linux-focused tutorial or documentation.
- Ensure all external references and examples are relevant to Linux users, given the page's audience and intent.
Virtual Machines
Chef extension for Azure VMs
...blob/main/articles/virtual-machines/extensions/chef.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides examples and instructions for both Linux and Windows, but there is a subtle Windows bias. The publisher value is 'Chef.Bootstrap.WindowsAzure', which references Windows Azure branding. The extension type for Linux ('LinuxChefClient') is mentioned after the Windows type ('ChefClient'). File paths for logs are given for both OSes, but the Windows path is shown second. There are no PowerShell-heavy examples, and the Azure CLI is used throughout, which is cross-platform. However, there is a lack of explicit Linux-first examples and some terminology (e.g., publisher name) is Windows-centric.
Recommendations
- Present Linux and Windows extension types in parallel or with Linux first, especially in tables and examples.
- Clarify that 'Chef.Bootstrap.WindowsAzure' is used for both Linux and Windows extensions, and explain the naming convention.
- Add explicit Linux-specific examples where possible, such as troubleshooting steps or log file analysis.
- Consider updating terminology to be more OS-neutral (e.g., avoid 'WindowsAzure' in publisher name if possible).
Azure Impact Reporting
Azure Impact Reporting Connectors for Azure Monitor: FAQ
...main/articles/azure-impact-reporting/connectors-faq.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for enabling debug mode and verifying connector creation, but PowerShell (Windows) examples are consistently listed after Bash. There is no exclusive use of Windows tools, but the presence of PowerShell examples and terminology may indicate a slight Windows bias. No Linux/macOS functionality is missing, and all tasks can be completed on both platforms.
Recommendations
- Ensure parity by providing examples for other shells (e.g., zsh, fish) if relevant.
- Explicitly mention that Bash examples work on Linux and macOS, and PowerShell examples work on Windows and PowerShell Core (cross-platform).
- Consider alternating the order of examples or grouping them together to avoid perceived prioritization.
- Add a note clarifying platform compatibility for each example.
Service Fabric
Service Fabric Azure Resource Manager deployment guardrails
...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page lists Windows Server cluster creation before Linux cluster creation in the 'Next steps' section, which may subtly prioritize Windows users. However, the main content is platform-neutral and does not provide OS-specific examples or instructions.
Recommendations
- List Linux and Windows cluster creation links together or alternate their order to avoid implicit prioritization.
- Explicitly state that the guidance applies equally to both Windows and Linux deployments where relevant.
- Add platform-specific notes or examples if there are differences in deployment or troubleshooting steps.
Azure Impact Reporting
Azure Impact Reporting: Create an Azure Monitor Alert Connector
...ure-impact-reporting/create-azure-monitor-connector.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Bash and PowerShell script examples for creating the connector, but PowerShell examples are listed first and in more detail. There is a slight Windows-first bias in the ordering and emphasis. The prerequisites mention Bash and PowerShell equally, but the command-line instructions and examples prioritize PowerShell before Bash. No Linux-specific troubleshooting or considerations are mentioned, and there are no explicit Linux/macOS environment notes.
Recommendations
- Alternate the order of Bash and PowerShell examples, or present Bash first to balance representation.
- Explicitly mention Linux/macOS compatibility and any environment-specific considerations (e.g., file permissions, shell requirements).
- Provide troubleshooting steps or notes relevant to Linux/macOS users, such as common script execution issues.
- Clarify that both Bash and PowerShell scripts are supported on Azure Cloud Shell, which runs on Linux.
- Include a note about how to install prerequisites (e.g., AzCLI) on Linux/macOS.
Azure Impact Reporting
Azure Impact Reporting: Connectors Troubleshooting Guide
...e-impact-reporting/connectors-troubleshooting-guide.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for most troubleshooting steps, but PowerShell (Windows) examples are consistently listed after Bash, and some troubleshooting advice (such as updating modules and error handling) is specific to PowerShell. There is no explicit Linux/macOS bias, but the presence of PowerShell-specific guidance and tools may create friction for non-Windows users.
Recommendations
- Add explicit Linux/macOS troubleshooting steps where PowerShell-specific advice is given (e.g., for module updates and error handling).
- Ensure parity in guidance for Bash users, such as how to handle errors and update the Azure CLI.
- Consider grouping Bash and PowerShell examples together or clarifying which OS each applies to.
- Where PowerShell advice is given (e.g., $ErrorActionPreference), provide equivalent Bash error handling tips.
Container Instances
Big containers on Azure container instances
...ob/main/articles/container-instances/big-containers.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation lists PowerShell as a deployment option before Linux-friendly tools (Azure CLI), and does not provide any concrete examples or command snippets for either platform. The mention of PowerShell without equivalent emphasis on Bash or Linux shell usage suggests a subtle Windows-first bias. There are no explicit Linux/macOS examples, nor any mention of platform-specific considerations for deploying Big Containers.
Recommendations
- Provide explicit deployment examples using both Azure CLI (Bash) and PowerShell, with equal prominence.
- List Azure CLI (cross-platform) before PowerShell when enumerating deployment options.
- Add a section on platform-specific prerequisites or tips for Linux/macOS users.
- Ensure that all instructions and tooling references are cross-platform, or provide alternatives where necessary.
Container Instances
Config Maps for Azure Container Instances
.../container-instances/container-instances-config-map.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major workflows, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and some ARM template and REST examples reference PowerShell deployment commands. The section on accessing config maps in containers gives a Linux example (mount path) and a Windows example (PowerShell command), but the Windows method is less clear and relies on Windows tooling. There is no explicit Linux shell example for accessing config map values inside the container, and PowerShell is mentioned before Linux shell alternatives in several places.
Recommendations
- Add explicit Linux shell examples for accessing config map values inside containers (e.g., using 'cat' or 'ls' on the mount path).
- Clarify the Windows container config map access method, and provide a more concrete example (e.g., using 'type' or other Windows shell commands, not just PowerShell).
- Consider listing CLI (cross-platform) examples before PowerShell in each tab group to reduce Windows-first perception.
- Where ARM template and REST examples mention deployment tools, highlight cross-platform options (e.g., Azure CLI, Bicep) before PowerShell.
- Add notes about which commands are cross-platform and which are Windows-only, especially for PowerShell scripts.
Container Instances
Create a standby pool for Azure Container Instances
...r-instances/container-instances-standby-pool-create.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major steps, but PowerShell is given equal prominence as CLI, and is referenced throughout. PowerShell is a Windows-centric tool, and its inclusion as a primary method (alongside CLI) can indicate a Windows bias, especially since PowerShell is still more commonly used on Windows. Additionally, deployment instructions for ARM templates mention PowerShell (New-AzResourceGroupDeployment) before CLI in some places, and PowerShell modules are referenced directly. There are no explicit Linux/macOS-only examples or notes, and no mention of Bash scripting or Linux-native tools. However, the Azure CLI examples are cross-platform and shown first in each tab set, which helps mitigate bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Add explicit notes or callouts for Linux/macOS users, such as installation instructions for Azure CLI on those platforms.
- Include Bash script examples or usage patterns where appropriate.
- De-emphasize PowerShell as a primary method, or clarify its cross-platform availability (PowerShell Core), but note that CLI is more common on Linux/macOS.
- Ensure that all deployment instructions (e.g., for ARM templates) show CLI commands before PowerShell, or provide parity in ordering.
Container Instances
Understand the health state of your standby pool for Azure Container Instances
...ances/container-instances-standby-pool-health-state.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving the health state of the standby pool, but the PowerShell example is given equal prominence to the CLI example. PowerShell is a Windows-centric tool, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash) or guidance for non-Windows environments. The CLI example is cross-platform, but the documentation does not clarify this or encourage its use for Linux/macOS users. No Linux-specific tools or patterns are mentioned.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add Bash shell usage examples for Linux/macOS users, if applicable.
- Clarify that PowerShell is primarily for Windows users, or mention PowerShell Core compatibility with Linux/macOS if relevant.
- Consider listing CLI examples before PowerShell to reduce perceived Windows-first bias.
- Add a note or section on using these commands in Linux/macOS environments.
Container Instances
Get prediction results for standby pools for Azure Container Instances (Preview)
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is given a dedicated tab and example, which is a Windows-centric tool. The CLI example is cross-platform, but PowerShell is presented before REST and with equal prominence, suggesting a Windows-first approach. There are no Linux/macOS-specific instructions or examples, and no mention of Bash scripting or native Linux tools.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for parsing or processing results.
- Clarify that Azure CLI works on Windows, Linux, and macOS, and consider showing Bash usage (e.g., with jq for JSON parsing).
- If PowerShell is included, also mention PowerShell Core compatibility on Linux/macOS, or provide equivalent Linux-native instructions.
- Consider listing CLI examples before PowerShell, as CLI is cross-platform.
Container Instances
Override entrypoint in container instance
...ntainer-instances/container-instances-start-command.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows shell examples in the shell table, but in the command line syntax section, Azure PowerShell is mentioned as a primary method alongside Azure CLI, and the PowerShell cmdlet is given a dedicated example before the portal and template methods. There is a slight emphasis on Windows tools (PowerShell, 'cmd') and the PowerShell cmdlet is referenced directly, while Linux-specific tools (e.g., bash scripting, shell utilities) are not highlighted as much. However, the main CLI examples use bash syntax and Linux-style commands, and there are no critical omissions for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS shell examples alongside PowerShell, such as using bash/zsh in terminal.
- Mention Linux-native tools or scripting patterns where relevant, such as using shell scripts for entrypoint overrides.
- Ensure that PowerShell and Windows-specific instructions are not presented before Linux equivalents, or present them in parallel.
- Clarify that Azure CLI works cross-platform and provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) environments.
Service Fabric
Create an Azure Load Balancer rule for a cluster
...n/articles/service-fabric/create-load-balancer-rule.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating Azure Load Balancer rules. While the Azure CLI is cross-platform and presented first, the PowerShell section is given equal prominence and detail, despite being Windows-centric. There are no Linux/macOS-specific examples or mentions of platform differences, and PowerShell is described as a standard alternative rather than a Windows-only tool.
Recommendations
- Clarify that PowerShell is primarily a Windows tool and mention cross-platform alternatives if available.
- Add explicit notes that Azure CLI works on Linux/macOS and is the recommended method for non-Windows users.
- Consider removing or de-emphasizing PowerShell instructions unless there is a unique capability not available in Azure CLI.
- If PowerShell Core (cross-platform) is supported, specify compatibility and installation instructions for Linux/macOS.
Virtual Machines
Availability options for Azure Virtual Machines
...cs/blob/main/articles/virtual-machines/availability.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page is generally cross-platform, but there is a subtle Windows bias in the 'Load balancer' section, where PowerShell is mentioned and linked before the CLI, and both are presented as quickstart options. No Linux-specific tools or examples are highlighted, and PowerShell (primarily a Windows tool, though available on Linux) is given equal or slightly more prominence than CLI, which is more universal. The rest of the page is neutral and references both Linux and Windows VMs equally.
Recommendations
- Present CLI examples and links before PowerShell, as CLI is more universal and preferred on Linux/macOS.
- Explicitly mention that PowerShell is available on Linux/macOS if linking to PowerShell instructions.
- Add Bash or Linux-specific command examples where relevant, especially in sections discussing VM creation or management.
- Ensure that any referenced quickstarts or tutorials include both Linux and Windows instructions, or clarify platform applicability.
Virtual Machines
Azure CLI - Enable customer-managed keys with SSE - managed disks
...chines/linux/disks-enable-customer-managed-keys-cli.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is primarily Linux-oriented in its Azure CLI examples, but there is mild Windows bias in the 'Next steps' section, where PowerShell-based disaster recovery guides for VMware and Hyper-V are highlighted before any Linux alternatives. Additionally, the page references Windows VMs alongside Linux VMs in applicability, but does not provide Windows-specific CLI or PowerShell examples, nor does it mention Linux tools or patterns in the 'Next steps'.
Recommendations
- Add equivalent Linux-based disaster recovery guides or CLI-based instructions in the 'Next steps' section.
- Ensure that Linux and Windows tools are mentioned with equal prominence, or group them by platform.
- Where PowerShell is referenced, provide a CLI or Bash alternative if possible.
- Explicitly state that the Azure CLI examples are cross-platform, and note any platform-specific considerations.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details â
Detected Bias Types
windows_tools
powershell_heavy
Summary
The documentation is overwhelmingly focused on Linux, with all main examples, commands, and procedures using Linux tools and conventions. However, the only mention of Windows tooling is in the final section, where a PowerShell script is provided to check classic VM SKU support for disk expansion without downtime. There is no equivalent Bash/Azure CLI script for Linux users in this section, and PowerShell is presented as the only option.
Recommendations
- Provide an equivalent Bash/Azure CLI script for Linux/macOS users to check classic VM SKU support for disk expansion without downtime.
- Clarify that the PowerShell script is only needed for users who manage Azure resources from Windows, and offer guidance for Linux users.
- Consider moving the PowerShell example to a separate section or tab labeled 'Windows' and add a 'Linux/macOS' tab with a CLI or REST API example.