274
Pages Scanned
113
Pages Flagged
274
Changed Pages
41.2%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-09 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 274
Files Completed: 274
Problematic Pages
113 issues found
Service Fabric
Azure Service Fabric reverse proxy
...articles/service-fabric/service-fabric-reverseproxy.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation clearly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples, explanations, and guidance are implicitly Windows-focused. There are no Linux-specific instructions or examples, and Linux users are informed upfront that the feature is unavailable to them.
Recommendations
- Explicitly clarify early in the documentation that reverse proxy is Windows-only, and link to any Linux alternatives or workarounds if available.
- Consider adding a section for Linux users explaining the current limitations and suggesting possible approaches for service discovery and communication in Linux clusters.
- If/when Linux support is added, update documentation to include Linux-specific examples, instructions, and parity in guidance.
Create Pull Request
Service Fabric
Standalone Service Fabric clusters overview
...-fabric/service-fabric-standalone-clusters-overview.md
High Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation later states that Linux is not yet supported for standalone clusters. All supported operating systems listed are Windows Server versions, and security sections reference Windows-specific features (Active Directory, group Managed Service Accounts). There are no Linux-specific instructions, examples, or supported OS listings.
Recommendations
- Clarify early and prominently that standalone clusters are currently Windows-only, to avoid misleading Linux users.
- Remove or rephrase statements suggesting Linux support for standalone clusters until such support is available.
- If Linux support is planned, provide a roadmap or link to updates.
- When Linux support is available, add equivalent Linux instructions, supported OS listings, and security guidance.
Service Fabric
Configure the upgrade of a Service Fabric application
...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically Visual Studio and PowerShell. All upgrade instructions and examples are given for Visual Studio (a Windows-only IDE) and PowerShell (primarily a Windows shell), with no mention of Linux/macOS alternatives or cross-platform tools. There are no CLI or script examples for Linux users, and the only upgrade methods described require Windows tools.
Recommendations
- Add instructions for upgrading Service Fabric applications using cross-platform tools such as Azure CLI or REST APIs.
- Include examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or other supported methods.
- Clarify which steps are Windows-only and provide links or guidance for Linux users where possible.
- Mention any limitations or parity gaps explicitly so Linux/macOS users know what is and isn't possible.
Service Fabric
Monitor Azure Service Fabric
...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation covers monitoring for Azure Service Fabric across Windows and Linux clusters, but there is a noticeable Windows bias. Windows-specific tools (such as EventStore APIs, Event Log, Diagnostics Agent) are mentioned first or in more detail, and some examples/tutorials focus on .NET applications (typically Windows-centric). Linux equivalents are referenced, but often as secondary notes or with less detail. Some sections lack explicit Linux examples or guidance, especially around cluster monitoring and event access.
Recommendations
- Provide Linux-specific examples and walkthroughs alongside Windows ones, especially for cluster monitoring and event access.
- Ensure Linux tools (such as LTTng, Syslog, and relevant agents) are described in equal detail and prominence as Windows tools.
- Add tutorials for monitoring Service Fabric applications on Linux, including instrumenting with Application Insights and logging frameworks.
- Clarify which features are Windows-only and which are cross-platform, to help users understand parity.
- Include sample queries and alert rules that are applicable to Linux clusters, and reference Linux event sources explicitly.
Service Fabric
RunToCompletion semantics and specifications
...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for RunToCompletion semantics in Azure Service Fabric is notably Windows-centric. All code examples reference Windows containers (nanoserver), Windows-specific commands (cmd, set, ping), and Windows container compatibility. Query instructions are given only for PowerShell and C#, with no mention of Linux shell or cross-platform tools. There is no example or guidance for Linux containers or Linux-based Service Fabric clusters, despite Service Fabric supporting Linux containers.
Recommendations
- Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
- Include instructions for querying deployment status using Linux tools (e.g., Bash, sfctl CLI).
- Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide relevant guidance.
- Present examples for both Windows and Linux environments, or explicitly state if the feature is Windows-only.
- Mention cross-platform tools (like sfctl) alongside PowerShell.
Service Fabric
Advanced Application Upgrade Topics
...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides numerous PowerShell-based examples and references, with no equivalent CLI or Linux/macOS instructions. All command-line upgrade operations are shown using PowerShell cmdlets, and the workflow assumes familiarity with Windows tooling. There is no mention of Service Fabric CLI (sfctl) or Bash scripting, nor are Linux/macOS users guided on how to perform these tasks. The page also references Visual Studio as a deployment tool, which is primarily Windows-centric.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
- Explicitly mention that PowerShell examples can be adapted for PowerShell Core on Linux/macOS, if applicable.
- Provide Bash or shell script snippets for common upgrade tasks.
- Include a section or note clarifying which tools are available for Linux/macOS users and link to relevant documentation.
- When referencing Visual Studio, also mention cross-platform alternatives (e.g., VS Code, CLI tools) for non-Windows environments.
Service Fabric
Cluster Resource Manager - Management Integration
...fabric-cluster-resource-manager-management-integration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example for querying partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux/macOS CLI example (such as Service Fabric CLI or REST API usage) is given. The example is presented early and exclusively, which may create friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
- Add equivalent Linux/macOS examples using Service Fabric CLI (sfctl) or REST API for querying partition health.
- Mention cross-platform management tools and provide links or examples for Linux/macOS users.
- Clarify that PowerShell is one option, and highlight alternatives for non-Windows environments.
Service Fabric
Learn more about Azure Service Fabric
...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned before Linux equivalents, and Windows terminology (e.g., auto-start Windows service, FabricHost.exe) is used without parallel Linux explanations. Standalone cluster creation is only described for Windows, with Linux support explicitly missing. Examples and instructions often default to Windows-first, and Linux-specific guidance is limited or absent.
Recommendations
- Provide Linux-specific examples and instructions alongside Windows ones, especially for cluster creation, management, and lifecycle operations.
- Mention Linux tools (e.g., Bash, Linux CLI usage) equally with Windows tools like PowerShell.
- Clarify when features or instructions are Windows-only, and provide alternative Linux guidance where possible.
- Add links and references to Linux documentation and tutorials in 'Next steps' and throughout the article.
- Use neutral language when describing concepts that apply to both platforms, and explicitly note differences where relevant.
Service Fabric
Upgrading Azure Service Fabric clusters
...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux-specific tools or examples are not provided. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node upgrade information. Windows terminology and tools are referenced first or exclusively in some sections.
Recommendations
- Add explicit Linux node upgrade guidance and link to relevant documentation for patching/upgrading Linux-based Service Fabric clusters.
- Provide examples using Bash/Azure CLI for cluster management tasks, not just PowerShell.
- Clarify when instructions or links are Windows-specific and provide Linux equivalents where possible.
- Mention Linux support and limitations for Service Fabric clusters where relevant.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page presents Windows/PowerShell examples first and in more detail, notably referencing the PowerShell cmdlet New-ServiceFabricApplication before mentioning sfctl (the cross-platform CLI). Visual Studio and PowerShell scripts are emphasized, which are primarily Windows tools, while Linux/macOS equivalents are less prominent. However, sfctl and Jenkins are mentioned, providing some Linux parity.
Recommendations
- Present sfctl (the cross-platform CLI) examples before or alongside PowerShell examples.
- Include explicit Linux/macOS command-line examples for application creation and parameter passing.
- Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
- Expand on Jenkins usage with example scripts for parameter substitution, not just a brief mention.
- Add guidance for configuring applications using Linux/macOS development environments.
Service Fabric
Azure Service Fabric application resource model
...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page demonstrates notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) with no mention of Azure CLI or other cross-platform tools. Application packaging instructions reference Visual Studio, a Windows-centric IDE, and do not provide alternatives for Linux/macOS users. There are no Linux/macOS-specific examples or guidance, and Windows tools and patterns are presented exclusively and first.
Recommendations
- Add Azure CLI examples for deployment and deletion tasks alongside PowerShell.
- Provide instructions for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, SF SDK, or manual zip commands).
- Mention and link to Visual Studio Code or other cross-platform editors for application packaging.
- Clearly indicate if certain steps are Windows-only and provide Linux/macOS alternatives where possible.
- Consider including bash shell commands for file manipulation (zipping, renaming) and uploading blobs using Azure CLI.
Service Fabric
Azure Service Fabric Events
...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page primarily references Windows-specific event logging mechanisms (ETW/Windows Event logs, Windows Azure diagnostics agent) and tools, with no mention of Linux equivalents or guidance for accessing Service Fabric events on Linux clusters. Windows tools and patterns are discussed first and exclusively, creating friction for Linux users seeking parity.
Recommendations
- Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, Azure Monitor integration for Linux).
- Mention Linux-compatible diagnostic agents or methods, and clarify any differences in event collection or visualization.
- Provide examples or links for querying and monitoring Service Fabric events on Linux, ensuring parity with Windows instructions.
- If certain event types or logging channels are Windows-only, clearly state this and provide alternatives for Linux users.
Service Fabric
Specifying Service Fabric service endpoints
...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell example for deploying Service Fabric applications, which is Windows-centric. The schema file path is given only in Windows format. Linux-specific information is limited to a single note about certificate storage, and Linux deployment commands or examples are missing. Windows tools and patterns (PowerShell, Windows file paths) are mentioned first and exclusively in critical deployment sections.
Recommendations
- Add equivalent Linux deployment examples using Azure CLI or bash scripts.
- Mention Linux file paths and schema locations alongside Windows paths.
- Clarify which steps or commands differ for Linux clusters, especially for endpoint and certificate configuration.
- Provide links or references to Linux-specific Service Fabric tooling and documentation.
- Ensure that Linux/macOS users can follow the deployment workflow without relying on Windows-only tools.
Virtual Machine Scale Sets
Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration
...lexible-virtual-machine-scale-sets-migration-resources.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating and migrating Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and PowerShell is referenced alongside Azure CLI without clear Linux guidance. Some example commands (e.g., az vm create) are shown without specifying shell context, potentially defaulting to Windows/PowerShell usage. Linux-specific migration steps, tools, or troubleshooting are not covered.
Recommendations
- Add explicit bash/Linux shell examples alongside PowerShell for all CLI instructions.
- Ensure Linux package manager update scenarios are described with equal detail as Windows update/activation.
- Mention Azure CLI usage in Linux/macOS contexts, and clarify shell compatibility for example commands.
- Provide troubleshooting guidance for Linux VM migration, including common issues and solutions.
- Where PowerShell is referenced, add equivalent bash/CLI instructions and links to Linux documentation.
Service Fabric
Azure Service Fabric infrastructure as Code Best Practices
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell (a Windows-centric tool) is given a dedicated section and is the only scripting language shown for advanced cluster upgrade operations. Windows-specific registry settings and template properties are discussed in detail, while Linux equivalents are not mentioned. Windows configuration is described first and in more depth, with Linux-specific guidance only referenced via external links.
Recommendations
- Provide equivalent Linux/bash examples for all PowerShell commands, especially for cluster upgrade operations.
- Include Linux-specific configuration guidance (e.g., how to disable automatic updates on Linux VMSS nodes) alongside Windows instructions.
- When discussing OS-specific settings (like registry keys or Windows Update), add parallel Linux instructions or explicitly state if not applicable.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which OS is discussed first or present both together).
Service Fabric
Manage certificates in a Service Fabric cluster
...vice-fabric/cluster-security-certificate-management.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a notable bias toward Windows environments and tooling. PowerShell is the only scripting example provided for certificate enrollment and management. The Key Vault VM extension is discussed exclusively in its Windows variant, and the documentation references Windows-specific certificate store concepts (e.g., 'LocalMachine', 'MY'). There is no mention of Linux equivalents, such as the Key Vault VM extension for Linux, nor are there any Bash/CLI examples. The documentation also discusses Windows-specific certificate linking and S-channel behaviors without referencing Linux or cross-platform considerations.
Recommendations
- Provide equivalent Bash/Azure CLI examples for certificate enrollment and management, especially for tasks currently shown only in PowerShell.
- Include guidance and examples for using the Key Vault VM extension for Linux (if supported), or clarify if autorollover and certificate provisioning are Windows-only.
- When discussing certificate stores and provisioning, mention Linux equivalents (e.g., file paths, OpenSSL, or system trust stores) and how Service Fabric on Linux nodes should be configured.
- If certain features are Windows-only, explicitly call this out at the start of relevant sections to set expectations for Linux/macOS users.
- Add troubleshooting and FAQ entries relevant to Linux environments, or link to cross-platform documentation where appropriate.
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_tools
windows_first
Summary
The documentation provides examples for managing Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI tool shown for scripting/command-line automation, with no mention of Azure CLI, Bash, or cross-platform scripting alternatives. PowerShell examples are presented as the primary automation method, and there is no guidance for Linux/macOS users who may not have access to PowerShell or prefer other tools. This creates friction for non-Windows users, though the ARM template and Portal methods are cross-platform.
Recommendations
- Add Azure CLI examples for all operations currently shown with PowerShell (e.g., adding/removing/scaling node types, configuring properties). Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell examples require Azure PowerShell module, and provide guidance or links for installing PowerShell Core on Linux/macOS if PowerShell is to remain the only CLI example.
- Where possible, clarify that ARM templates and the Azure Portal are fully cross-platform and can be used from any OS.
- Consider reordering sections so that cross-platform methods (Portal, ARM template, Azure CLI) are presented before Windows-specific tools like PowerShell.
- If some operations are only possible with PowerShell, clearly state this and provide workarounds or alternatives for Linux/macOS users.
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides examples and links primarily for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its mention precedes alternatives like Azure CLI or sfctl. While Azure CLI and ARM/Bicep are referenced, the step-by-step guidance and linked examples focus on PowerShell, which may create friction for Linux/macOS users.
Recommendations
- Add explicit Azure CLI command examples alongside PowerShell examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
- Ensure that CLI and cross-platform tools are mentioned equally or before PowerShell in guidance sections.
- Clarify that Azure CLI and sfctl are fully supported on Linux/macOS and provide links to their documentation.
- Where possible, provide code snippets for both PowerShell and CLI to improve accessibility.
Service Fabric
X.509 Certificate-based Authentication in a Service Fabric Cluster
...ticles/service-fabric/cluster-security-certificates.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides thorough coverage of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows terminology and tools (e.g., certificate store paths like LocalMachine\My, Win32 CryptoAPI references, and event log channels) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting and configuration examples focus on Windows-specific patterns, and PowerShell/C++ error codes are given without Linux alternatives. While Linux is supported for Service Fabric, parity in examples and troubleshooting guidance is lacking.
Recommendations
- Add Linux-specific certificate store paths and management instructions alongside Windows examples (e.g., expand on /var/lib/sfcerts).
- Include troubleshooting steps for Linux nodes, such as relevant log locations and commands (e.g., journalctl, syslog, openssl).
- Provide Linux equivalents for error codes and certificate provider types, or clarify cross-platform differences.
- Reference Linux certificate management tools (e.g., openssl, certutil) and include sample commands.
- Ensure that configuration examples and explanations are platform-neutral or explicitly show both Windows and Linux variants.
Service Fabric
Introduction to the Service Fabric Infrastructure Service
.../articles/service-fabric/infrastructure-service-faq.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux alternatives. No Linux/macOS command-line examples or equivalent tooling are provided, and Windows tools are mentioned first and exclusively.
Recommendations
- Add equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API where possible.
- Clarify whether Service Fabric Explorer is cross-platform or suggest alternatives for Linux users.
- Provide guidance on how Linux/macOS administrators can perform the same operations, or explicitly state if certain actions are Windows-only.
- Ensure that command examples are shown for both Windows and Linux environments, or note platform limitations.
Service Fabric
Initializer CodePackages in Service Fabric
...in/articles/service-fabric/initializer-codepackages.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for Initializer CodePackages in Service Fabric presents only Windows container examples, uses Windows-specific container images (nanoserver), Windows filesystem paths, and Windows command syntax (cmd.exe). There are no Linux container examples, nor is there guidance for Linux-based Service Fabric clusters or containers. The page assumes Windows familiarity and does not mention Linux alternatives or parity.
Recommendations
- Add examples using Linux containers (e.g., Ubuntu or Alpine images) with Linux shell commands.
- Show how to specify Initializer CodePackages for Linux-based Service Fabric clusters, including Linux path conventions and command syntax.
- Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation.
- If Linux support exists, provide ApplicationManifest and ServiceManifest examples using Linux volume mounts and container images.
- If Windows-only, add a clear note at the top indicating this feature is not supported on Linux clusters.
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_first
Summary
The documentation page primarily references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, with no explicit mention of Linux/macOS equivalents or Azure CLI usage. While 'az resource' is mentioned once for deleting applications, PowerShell examples and terminology dominate, and PowerShell cmdlets are listed before Azure CLI commands. This creates friction for Linux/macOS users who typically rely on Azure CLI.
Recommendations
- Add Azure CLI examples for all operations (e.g., deleting, creating, scaling resources) alongside PowerShell cmdlets.
- Clarify which commands are cross-platform and which are Windows-only.
- Where possible, provide ARM template examples for resource management.
- Ensure Azure CLI commands are listed before or alongside PowerShell cmdlets to improve parity.
Service Fabric
Learn about Azure Service Fabric application security
...ric/service-fabric-application-and-service-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation provides a general overview of Service Fabric application security, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before Linux equivalents, and some examples/tools (like disk encryption) reference only Windows/PowerShell. Linux-specific guidance is missing or relegated to TODOs, and Windows terminology (e.g., NetworkService, Fabric.exe) is used without Linux alternatives.
Recommendations
- Add Linux-specific examples and guidance, especially for disk encryption and user account management.
- Ensure parity in describing how to secure Service Fabric applications on Linux clusters (e.g., mention Linux user/group management, SELinux/AppArmor, Linux disk encryption options).
- Where Windows tools (e.g., BitLocker, PowerShell) are referenced, provide equivalent Linux tools (e.g., dm-crypt/LUKS, bash scripts) and examples.
- Avoid presenting Windows-specific features first unless they are more widely used; consider parallel structure for Windows and Linux.
- Clarify when a feature is Windows-only and provide alternative approaches for Linux where possible.
Service Fabric
Migrate an Azure Service Fabric cluster to availability zone support
...ce-fabric/migrate-service-fabric-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides migration guidance for Azure Service Fabric clusters to availability zone support. While most of the guidance is platform-agnostic (focused on ARM templates and Azure resources), the step-by-step migration for clusters with Basic SKU load balancer and IP resources relies heavily on PowerShell commands and Windows-centric tooling. PowerShell examples are given exclusively, and Windows paths (e.g., 'D:\\SvcFab') appear in configuration snippets. Linux equivalents (such as Azure CLI or Bash) are missing, and the PowerShell approach is presented as the default, creating friction for Linux/macOS users.
Recommendations
- Add Azure CLI or Bash script equivalents for all PowerShell migration steps, especially for resource deployment, node disabling/removal, and DNS updates.
- Clarify that PowerShell commands are Windows-specific and provide links or instructions for Linux/macOS users.
- Where file paths are shown (e.g., 'D:\\SvcFab'), mention Linux alternatives or note how to configure for Linux VMSS.
- Ensure sample templates and references include both Windows and Linux cluster scenarios.
- Consider reordering examples so platform-agnostic approaches (ARM templates, Azure CLI) are shown first, with PowerShell as an alternative.
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 contains a notable Windows bias in its guidance for validating manifest XML schemas. It exclusively references opening the Service Fabric XSD schema file in Visual Studio using a Windows file path (C:\Program Files\...), with no mention of Linux/macOS equivalents or cross-platform tooling. Additionally, the only command-line tooling mentioned for service creation is the ServiceFabric PowerShell module, with no reference to Azure CLI or other cross-platform tools.
Recommendations
- Provide instructions or alternatives for validating manifest XML on Linux/macOS, such as using cross-platform editors (e.g., VS Code) or command-line XML validation tools.
- Include Linux/macOS file paths for the Service Fabric XSD schema, or clarify where to find these files on non-Windows systems.
- Mention and provide examples for using Azure CLI or other cross-platform tools for service creation and management, not just PowerShell.
- When referencing tools like Visual Studio, note cross-platform alternatives or clarify if a step is only required/supported on Windows.
Service Fabric
Deploy and upgrade with Azure Resource Manager
...vice-fabric/service-fabric-application-arm-resource.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell-only examples for removing Service Fabric application resources and references PowerShell before CLI in the 'Next steps' section. There are no CLI (az or sfctl) or bash examples for Linux/macOS users, and the PowerShell-centric approach may create friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI (az) and/or Service Fabric CLI (sfctl) examples for managing and removing application resources, especially for the 'Remove Service Fabric Resource Provider Application resource' section.
- In the 'Next steps' section, mention CLI and PowerShell equally, or provide parallel links/examples for both.
- Explicitly note that all operations shown with PowerShell can also be performed with CLI/REST, and link to relevant Linux/macOS-friendly instructions.
- Consider providing bash shell script examples where appropriate.
Service Fabric
Application upgrade: upgrade parameters
...abric/service-fabric-application-upgrade-parameters.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page presents PowerShell and Visual Studio (Windows tools) upgrade parameters first and in greater detail, with Linux/macOS (SFCTL/CLI) parameters covered only after. Most parameter tables and explanations are focused on PowerShell and Visual Studio, with SFCTL (cross-platform CLI) relegated to a later section. Examples and parameter descriptions are more extensive for Windows tools, and the only explicit example syntax is PowerShell. Linux CLI (SFCTL) is covered, but not with equal prominence or detail.
Recommendations
- Present SFCTL (Service Fabric CLI) parameters and usage examples alongside PowerShell and Visual Studio, not after them.
- Provide example commands for SFCTL in the same way as for PowerShell, including parameter usage.
- Clarify at the start that all features are available cross-platform via SFCTL, and that PowerShell/Visual Studio are Windows-specific.
- Reorganize parameter tables to show all tools (PowerShell, Visual Studio, SFCTL) in parallel, or provide a comparison table.
- Add explicit Linux/macOS usage notes or callouts where relevant.
Service Fabric
Architecture of Azure Service Fabric
...articles/service-fabric/service-fabric-architecture.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions PowerShell cmdlets as the primary example for management operations, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). Windows security is mentioned alongside X509 certificates in the transport subsystem, with Windows listed first. These patterns suggest a Windows-first bias, especially in management and security contexts.
Recommendations
- Add examples or references to Azure CLI and REST API usage for management operations, highlighting cross-platform options.
- Clarify that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide alternative commands where applicable.
- When mentioning security mechanisms, list X509 certificates before Windows security, and clarify Linux/macOS support.
- Review the documentation for other Windows-centric language and ensure Linux/macOS parity is explicitly addressed.
Service Fabric
Application lifecycle in Service Fabric
...service-fabric/service-fabric-application-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page frequently references PowerShell cmdlets and Windows-specific tools (e.g., Register-ServiceFabricApplicationType, Remove-ServiceFabricApplicationPackage) as primary examples for managing the Service Fabric application lifecycle. While REST API and .NET methods are also mentioned, there is a notable absence of Linux-focused command-line examples (such as Azure CLI or sfctl usage), and PowerShell is consistently presented before other options. This creates friction for Linux/macOS users, as they must infer or seek out equivalent commands.
Recommendations
- Add explicit Linux/macOS command-line examples using Azure CLI and sfctl for each lifecycle operation (deploy, upgrade, remove, etc.).
- Where PowerShell cmdlets are referenced, provide parallel examples using sfctl or Azure CLI, and clarify their cross-platform applicability.
- Reorder examples so that cross-platform tools (REST API, Azure CLI, sfctl) are presented before or alongside Windows-specific tools.
- Include a section or note clarifying which tools are supported on Linux/macOS and linking to relevant documentation.
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 focuses on C# and .NET serialization, which are cross-platform, but the 'Next steps' section highlights Windows-centric tools (Visual Studio and PowerShell) for application upgrades, with no mention of Linux/macOS equivalents or CLI options. This creates friction for non-Windows users seeking guidance on upgrading applications in Service Fabric.
Recommendations
- Add examples or links for upgrading applications using cross-platform tools, such as Azure CLI or Service Fabric CLI (sfctl), especially for Linux/macOS users.
- Mention or link to documentation for Linux/macOS development environments and workflows, if supported.
- Ensure that upgrade tutorials are available for non-Windows platforms, or clarify platform limitations if certain features are Windows-only.
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
missing_linux_example
windows_first
Summary
The documentation page for Service Fabric application upgrade demonstrates a notable Windows bias. PowerShell is used exclusively in code examples, and Windows-specific tools (e.g., PowerShell cmdlets, http.sys) are referenced without Linux equivalents or guidance. There are no examples or instructions for Linux/macOS users, and Windows terminology and tools are presented first and exclusively throughout the page.
Recommendations
- Add equivalent CLI examples using Azure CLI or Service Fabric CLI (sfctl) for Linux/macOS users.
- Provide guidance on performing application upgrades on Linux-based Service Fabric clusters, including relevant commands and tools.
- Clarify which features or steps are Windows-only and which are cross-platform.
- Include troubleshooting and upgrade instructions for Linux environments.
- Mention any limitations or differences for Linux clusters, especially regarding HTTPS endpoints and certificate management.
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
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric exclusively provides PowerShell-based examples and instructions, including module installation, cluster connection, and API invocation. All CLI and scripting guidance is Windows-centric, with no mention of Linux/macOS equivalents (such as Bash, curl, or Azure CLI). The Service Fabric Explorer UI is platform-neutral, but all code samples and automation guidance assume a Windows/PowerShell environment.
Recommendations
- Add Bash/curl examples for REST API calls, showing how Linux/macOS users can trigger backups and track progress.
- Mention Azure CLI commands if available for Service Fabric backup operations.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required only for Windows/PowerShell users, and provide alternatives for Linux/macOS users.
- Add a section or note explaining how Linux/macOS users can perform the same tasks, and reference any cross-platform tools or SDKs.
- Ensure REST API documentation links are prominent, and provide sample requests in both PowerShell and Bash/curl formats.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation page is mostly platform-neutral, focusing on Service Fabric's backup configuration via REST APIs and JSON policy definitions. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Windows authentication mechanisms are described. There is no mention of Linux-compatible file share paths (e.g., SMB/CIFS mounts), nor guidance for Linux clusters or users. This creates a gap for Linux/macOS users who may wish to use file shares for backup storage.
Recommendations
- Add examples and instructions for configuring file share backup storage on Linux clusters, including SMB/CIFS mount paths and authentication methods.
- Clarify whether file share backup storage is supported on Linux Service Fabric clusters, and if so, provide Linux-specific guidance.
- If file share backup is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
- Ensure parity in documentation by mentioning Linux-compatible storage options and authentication patterns where relevant.
Service Fabric
Restoring backup in Azure Service Fabric
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, including REST API calls, and require the Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform tools. The documentation assumes the reader is on Windows and does not mention alternative approaches for non-Windows environments.
Recommendations
- Add Bash/curl examples for REST API calls to demonstrate how Linux/macOS users can trigger restores and track progress.
- Mention that the REST API can be used from any platform and provide sample requests using curl or HTTPie.
- Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly without it.
- Include guidance on certificate handling for Linux/macOS (e.g., how to pass client certificates with curl).
- Consider providing a table or section comparing Windows/PowerShell and Linux/Bash approaches for common tasks.
Service Fabric
Capacity planning and scaling for Azure Service Fabric
...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides only PowerShell-based examples for critical Service Fabric cluster operations (e.g., scaling in/out, disabling nodes), with no mention of Linux/macOS equivalents (such as Service Fabric CLI or REST API). This creates friction for users managing Linux-based clusters or working from non-Windows environments.
Recommendations
- Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform, for all PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState).
- Where PowerShell is referenced, clarify if the commands are available on Linux/macOS via PowerShell Core, or provide REST API alternatives.
- Explicitly mention and link to Linux/macOS management tooling (sfctl, REST API) in sections describing operational tasks.
- Consider including bash/shell script snippets or command-line instructions for Linux users alongside PowerShell examples.
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
Summary
The documentation provides both Windows and Linux guidance for key security tasks, but Windows examples (PowerShell, Windows Defender, Windows security baselines) are often presented first or in greater detail. Windows-specific tools and concepts (PowerShell, Windows Defender, DSC) are mentioned without Linux equivalents, and some sections (Windows Defender, security baselines) are Windows-only, though they do note Linux limitations. Linux examples are present for certificate and secret encryption, but overall, Windows is prioritized in ordering and tool references.
Recommendations
- Reorder sections to present Windows and Linux examples side-by-side or alternate which comes first.
- Add Linux equivalents for Windows-specific tools where possible (e.g., mention Linux security baselines or antivirus options).
- Clarify when a feature or tool is Windows-only and provide Linux alternatives or workarounds.
- Ensure Linux guidance is as detailed and prominent as Windows guidance, especially for critical security tasks.
- Where PowerShell is used, provide Bash or CLI equivalents for Linux clusters.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides some cross-platform information (e.g., mentions both 'ServiceFabricLinuxNode' and 'ServiceFabricNode'), but there are notable Windows biases. Examples and property tables use Windows-style paths (e.g., 'D:\\SvcFab'), and 'Next steps' links focus on RDP and PowerShell scripts, which are Windows-centric, with no Linux/SSH equivalents provided. There are no explicit Linux/macOS remote connection or management examples.
Recommendations
- Include Linux/SSH-based remote connection instructions and examples alongside or before Windows/RDP examples.
- Provide Linux-style file path examples (e.g., '/var/lib/servicefabric') in property tables and code snippets.
- Add links to Linux management scripts or documentation in the 'Next steps' section.
- Clarify when a step or tool is Windows-only, and offer Linux/macOS alternatives where possible.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology (e.g., 'MY' certificate store, 'LocalMachine', NTLM authentication, Windows Defender Firewall) is used throughout, and Windows-specific settings are often mentioned before Linux equivalents. Some settings default to Windows values or are described as 'Windows only', while Linux-specific guidance is minimal or absent. Linux is referenced in a few places (e.g., LinuxExternalExecutablePath, ContainerNetworkSetup), but parity is not consistent.
Recommendations
- Add explicit Linux/macOS equivalents for settings where Windows tools or terminology are used (e.g., certificate store names, authentication methods).
- Where settings are Windows-only, clarify Linux alternatives or note if the setting is not applicable.
- Ensure Linux-specific guidance is provided for configuration upgrade, certificate management, and firewall settings.
- Review default values and descriptions to ensure they are not Windows-centric unless the feature is truly Windows-only.
- Consider providing examples or references for Linux cluster configuration and management, not just standalone Windows clusters.
Service Fabric
Service Fabric Cluster Resource Manager - Placement Policies
...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides code examples primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS command-line examples (such as Azure CLI, Bash, or REST API) are provided. All PowerShell examples appear before any mention of alternative tooling, and there is no guidance for Linux users on how to perform these tasks. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
- Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform.
- Include REST API examples for configuring placement policies, which are usable from any OS.
- Explicitly mention whether PowerShell commands can be run on PowerShell Core (cross-platform), or if they require Windows PowerShell.
- Provide Bash script snippets or references for Linux/macOS users where applicable.
- Clarify any OS-specific limitations for Service Fabric management tools.
Service Fabric
Manage Azure Service Fabric app load using metrics
...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides code examples for C# and PowerShell, but omits equivalent Linux/macOS CLI examples (such as Azure CLI or REST API). PowerShell is featured prominently and appears before any mention of cross-platform alternatives. There is no guidance for Linux users on how to perform the same operations, creating friction for non-Windows users.
Recommendations
- Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform.
- Include REST API sample calls for relevant operations (service creation, metric updates, load reporting).
- Clarify which PowerShell commands are available cross-platform (PowerShell Core) and which are Windows-only.
- Add a section or notes for Linux/macOS users, outlining supported tools and workflows.
- Consider referencing or linking to Service Fabric SDK documentation for Linux/macOS, if available.
Service Fabric
Azure Service Fabric dynamic node tags
...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-node-tagging.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides PowerShell examples for managing node tags and service requirements, but does not include equivalent CLI or scripting examples for Linux/macOS users (e.g., Bash, Azure CLI). PowerShell is presented first and exclusively as the shell-based method, which may create friction for non-Windows users. The C# API examples are cross-platform, but shell/command-line guidance is Windows-centric.
Recommendations
- Add Azure CLI or Bash examples for managing node tags and service requirements, if supported.
- Clarify whether PowerShell commands are available cross-platform (e.g., via PowerShell Core) or if they are Windows-only.
- If PowerShell is the only supported CLI, explicitly state this and provide guidance for Linux/macOS users (e.g., using REST APIs or C#).
- Consider including REST API examples for node tag management, as these are platform-agnostic.
Service Fabric
Azure Service Fabric standalone cluster scaling
...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific scaling guide. There are no examples or guidance for Linux-based standalone clusters, nor are Linux-native tools or commands mentioned.
Recommendations
- Add examples and instructions for scaling standalone clusters deployed on Linux machines, including relevant Linux-native tools and commands.
- Reference any cross-platform or Linux-specific Service Fabric management tools (such as sfctl or REST APIs) alongside PowerShell.
- Provide parity in guidance for both Windows and Linux environments, including links to Linux documentation if available.
- Clarify if standalone clusters are Windows-only, or explicitly state Linux support status.
Service Fabric
Service Fabric Cluster Resource Manager - Application Groups
...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides only PowerShell and C# examples for managing Service Fabric Application Groups, with no Linux/macOS CLI or scripting equivalents. All command-line instructions use PowerShell cmdlets, which are native to Windows, and there is no mention of cross-platform tools or Azure CLI commands. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform.
- Mention if PowerShell Core (pwsh) can be used on Linux/macOS, and provide guidance if so.
- Include REST API examples for relevant operations, as these are platform-agnostic.
- Clarify any limitations or requirements for Linux/macOS users in the introductory section.
- Consider linking to documentation about Service Fabric management on Linux clusters.
Service Fabric
Azure Service Fabric Auto Scaling Services and Containers
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-autoscaling.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. The PowerShell examples are presented alongside C# and XML, but there is no mention of Linux-native tooling or cross-platform CLI usage. While Service Fabric supports Linux containers, the documentation does not demonstrate how Linux users can configure auto scaling via CLI or scripting, creating friction for non-Windows users.
Recommendations
- Add equivalent Bash or Azure CLI examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
- Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples.
- Clarify which PowerShell commands are available on Linux (via PowerShell Core) and which are Windows-only.
- Add a section summarizing Linux-specific considerations for auto scaling, including any limitations or differences.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for both Windows (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configurations, but Windows-specific XML examples and PowerShell commands are presented first and more frequently. There are no explicit Linux/macOS command-line examples (e.g., Bash, CLI), and the XML configuration is shown only for WindowsServer clusters, potentially implying Windows as the default or primary platform. However, JSON-based configuration is also covered, which is applicable to Linux clusters and cross-platform scenarios.
Recommendations
- Add explicit Linux cluster configuration examples (e.g., ClusterManifest.xml for Linux, if supported, or clarify if only JSON is used for Linux).
- Include Azure CLI or Bash command examples for service creation and updates alongside PowerShell and C#.
- Clarify in the configuration sections which examples are for Windows, which are for Linux, and which are cross-platform.
- Ensure parity in example ordering (e.g., JSON before XML, CLI before PowerShell) to avoid implicit Windows-first bias.
Service Fabric
Service Fabric Cluster Resource Manager: Movement cost
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-movement-cost.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation provides PowerShell and C# examples for configuring Service Fabric move cost, but does not include equivalent Linux/macOS command-line examples (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of cross-platform tools or guidance for non-Windows environments.
Recommendations
- Add Azure CLI examples for creating and updating Service Fabric services with move cost settings, as Azure CLI is cross-platform.
- If REST APIs are available for these operations, provide REST or HTTP request examples.
- Explicitly mention whether PowerShell Core (cross-platform) can be used, or clarify if only Windows PowerShell is supported.
- Include notes or links for Linux/macOS users on how to perform equivalent operations.
- Consider reordering examples so that cross-platform methods (CLI/REST) are shown before or alongside PowerShell.
Service Fabric
Service sensitivity
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (such as Bash or Azure CLI). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. However, the core configuration can also be performed via manifest files (XML/JSON), which are cross-platform, and the C# API is platform-neutral. The bias is mostly in the scripting examples and ordering.
Recommendations
- Add Bash or Azure CLI examples for creating and updating services with sensitivity and maximum load settings, if supported.
- Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide alternative instructions for non-Windows environments.
- Consider presenting cross-platform manifest (XML/JSON) examples first, followed by scripting/API examples.
- Explicitly mention any limitations or parity gaps for Linux/macOS users in scripting or tooling.
Service Fabric
Secure an Azure Service Fabric cluster
...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page provides security guidance for Azure Service Fabric clusters, referencing both Azure-hosted and standalone Windows clusters. However, it consistently presents Windows-specific instructions, tools, and links before Linux equivalents, and omits explicit Linux standalone cluster guidance. Certificate creation and security setup are described with Windows-centric tools and references, while Linux-specific instructions, examples, or links are missing or only briefly mentioned.
Recommendations
- Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
- Provide Linux-focused examples for certificate creation and management (e.g., using OpenSSL or Linux certificate authorities), rather than only referencing Windows Server certificate services.
- Clarify which instructions apply to Linux clusters and which are Windows-only, to avoid confusion.
- Ensure parity in recommendations and tooling references for Linux users (e.g., mention Linux-native certificate management tools alongside Windows tools).
Service Fabric
Upgrade an Azure Service Fabric standalone cluster
...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows. There are no explicit Linux or cross-platform instructions or links, and Windows terminology appears before any mention of Linux equivalents (if any exist).
Recommendations
- Add or link to Linux-specific upgrade and configuration guides for Service Fabric standalone clusters, if supported.
- Clarify in the introduction whether the standalone cluster upgrade process is Windows-only or cross-platform.
- If Linux clusters are supported, provide equivalent examples, instructions, and references for Linux environments.
- Mention Linux patch orchestration options or explicitly state if POA is Windows-only.
- Ensure that references to configuration files and procedures are platform-neutral where possible.
Service Fabric
Scalability of Service Fabric services
.../service-fabric/service-fabric-concepts-scalability.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides code examples and administrative patterns primarily using PowerShell and C#, with no equivalent Linux CLI or scripting examples. Windows tooling (PowerShell cmdlets) is mentioned exclusively and first, and Linux-specific guidance is missing. The only explicit Linux mention is in a platform comparison section, but Linux operational parity is not demonstrated in scaling scenarios.
Recommendations
- Add equivalent Linux CLI examples (e.g., using sfctl or REST API) alongside PowerShell for service and application management tasks.
- Mention Linux tooling and patterns (such as sfctl, bash scripts, or Azure CLI) wherever PowerShell is referenced.
- Clarify which administrative actions are possible on Linux clusters and provide links to Linux-specific documentation.
- Ensure that Linux users can follow scaling workflows without relying on Windows/PowerShell tools.
Service Fabric
Azure Service Fabric DNS service
...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides PowerShell examples for setting DNS names but does not offer equivalent Linux CLI (e.g., Bash, Azure CLI) examples. Windows tools (PowerShell, ApplicationManifest.xml via Visual Studio) are mentioned before Linux alternatives, and Linux limitations are noted without guidance or parity. There are no Linux-specific walkthroughs or examples for enabling or configuring DNS service, especially for containerized services.
Recommendations
- Add Azure CLI or Bash examples for configuring DNS service and setting DNS names, especially for Linux clusters.
- Include instructions for editing ARM templates and deploying from Linux environments (e.g., using az CLI).
- Clarify how Linux users can set DNS names for services (e.g., via ARM templates, Docker Compose, or other methods).
- Provide guidance for Linux users on verifying DNS settings and troubleshooting, including alternatives to Service Fabric Explorer if not available.
- Explicitly state any workarounds or alternative approaches for Linux users where portal or PowerShell options are unavailable.
Service Fabric
Azure Service Fabric hosting activation and deactivation life cycle
...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations. However, the 'Next steps' section directs users to deployment instructions specifically in PowerShell, and the only linked example for downloading a ServicePackage references a PowerShell cmdlet. There are no Linux or cross-platform CLI examples or links, and PowerShell is mentioned before any Linux alternatives, which may create friction for Linux/macOS users.
Recommendations
- Add links to equivalent Linux/macOS deployment instructions using Azure CLI or Service Fabric CLI (sfctl), where available.
- Provide examples for downloading ServicePackages and deploying/removing applications using cross-platform tools (e.g., Azure CLI, sfctl) alongside PowerShell.
- Clarify in the 'Next steps' section that PowerShell is one option, and offer alternatives for Linux/macOS users.
- Ensure that conceptual sections reference platform-agnostic tools or note platform-specific differences where relevant.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters, and links to PowerShell-based deployment/removal guides. While REST and .NET are mentioned as alternatives, PowerShell is presented first and most prominently. There are no explicit Linux/macOS CLI or tooling examples (e.g., Azure CLI, Bash), nor is cross-platform parity discussed.
Recommendations
- Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, where possible.
- Mention cross-platform tools and workflows (e.g., Azure CLI, REST API usage from Bash or Python) alongside PowerShell.
- Clarify whether PowerShell Core (cross-platform) is supported, and provide instructions for Linux/macOS users.
- Include links to Linux/macOS-specific documentation or note any limitations for non-Windows users.
Service Fabric
Health monitoring in Service Fabric
...s/service-fabric/service-fabric-health-introduction.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a PowerShell-only example for reporting and evaluating application health in Service Fabric, without offering equivalent Linux/macOS CLI or REST API examples. While Service Fabric supports cross-platform management, the exclusive use of PowerShell in the example creates friction for Linux/macOS users.
Recommendations
- Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
- Include REST API sample requests for health reporting and querying.
- Mention cross-platform tools and clarify PowerShell is one option among several.
- Consider showing Linux/macOS examples before or alongside Windows/PowerShell examples.
Service Fabric
Azure Service Fabric hosting model
...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page for the Azure Service Fabric hosting model presents PowerShell examples exclusively, with no equivalent Linux CLI or cross-platform examples. Windows tooling (PowerShell) is mentioned first and most prominently for service creation and management, while REST API and .NET client alternatives are referenced but not demonstrated for Linux. There is no mention of Linux-specific tools or workflows, and no guidance for Linux/macOS users on how to perform equivalent tasks.
Recommendations
- Add CLI examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and usable on Linux/macOS.
- Include REST API usage examples with curl or similar tools to demonstrate Linux-friendly workflows.
- Explicitly mention that PowerShell commands can be run on Linux/macOS using PowerShell Core, or provide alternatives if not possible.
- Ensure that links to management documentation include Linux/macOS-compatible options.
- Where PowerShell is referenced, add a note or section for Linux/macOS users describing equivalent steps.
Service Fabric
Azure Service Fabric container application manifest examples
...abric/service-fabric-manifest-example-container-app.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation page provides container application manifest examples for Azure Service Fabric, but it is based on Windows Server 2016 Container Sample manifests and frequently references Windows-specific concepts (e.g., 'winver' for OS build, Windows file paths, and Windows container compatibility). There are no explicit Linux examples or Linux-specific guidance, and Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
- Add equivalent Linux-based manifest examples, referencing Linux container samples and using Linux file paths.
- Include guidance on obtaining OS build/version information on Linux (e.g., using 'uname' or '/etc/os-release').
- Clarify which features and manifest settings are cross-platform and which are Windows-only.
- Mention Linux-specific container image tags or compatibility considerations.
- Provide links to Linux container sample repositories, if available.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
windows_first
Summary
The documentation page for Service Fabric Reliable Services app manifest examples shows a moderate Windows bias. It references Windows-specific concepts (such as 'NetworkService', 'Administrators' group, and 'Setup.bat'), and mentions the ServiceFabric PowerShell module as a way to create service instances, without providing equivalent Linux/bash examples or guidance. The manifest examples use Windows-style user/group names and scripts, and do not clarify cross-platform differences or provide Linux-specific instructions. While Service Fabric supports Linux, the page does not demonstrate Linux parity in its examples or guidance.
Recommendations
- Add Linux-specific examples, such as using bash scripts for SetupEntryPoint (e.g., 'Setup.sh' instead of 'Setup.bat'), and clarify how user/group principals map on Linux clusters.
- Mention and provide examples for creating service instances using CLI tools available on Linux (e.g., Azure CLI or Service Fabric CLI), not just PowerShell.
- Document any differences in account types, system groups, and security policies between Windows and Linux Service Fabric clusters.
- Ensure that manifest examples and explanations are annotated to indicate which elements are Windows-only, Linux-only, or cross-platform.
- Add a section or note explicitly addressing Linux/macOS users, including links to relevant documentation.
Service Fabric
Networking patterns for Azure Service Fabric
...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows-centric tools (e.g., RDP, Windows directory paths, PowerShell commands) throughout. There are no equivalent Linux/macOS CLI (Azure CLI) examples, and Windows patterns (such as RDP and PowerShell) are mentioned exclusively or before any Linux alternatives. This creates friction for Linux/macOS users, who must translate the instructions themselves.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all deployment steps.
- Mention SSH as a remote access alternative to RDP, and provide SSH examples for accessing VMs.
- Use platform-neutral file paths or clarify that paths are examples.
- Explicitly state that both Windows and Linux VM scale sets are supported, and note any platform-specific differences.
- Provide sample ARM templates and deployment instructions for Linux-based Service Fabric clusters, if supported.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation provides both Windows-specific (HTTP.sys) and cross-platform (Kestrel) guidance for ASP.NET Core in Service Fabric. However, Windows tools and patterns (HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail, often before their Linux equivalents. HTTP.sys is clearly marked as Windows-only, but Linux-specific guidance is limited. Kestrel, the cross-platform option, is recommended for Linux, but Linux-specific instructions, troubleshooting, or examples are missing. Windows tools (like netsh) are referenced without Linux alternatives.
Recommendations
- Add explicit Linux/macOS instructions for Service Fabric and ASP.NET Core integration, including any OS-specific configuration steps.
- Provide troubleshooting guidance for Linux scenarios (e.g., firewall, port allocation, permissions) similar to the Windows/HTTP.sys coverage.
- Include Linux/macOS-specific examples or notes where Windows tools (like netsh) are mentioned.
- Clarify cross-platform support in each section, especially when recommending Kestrel for Linux.
- Consider adding a comparison table or section summarizing Windows vs. Linux differences for Service Fabric Reliable Services with ASP.NET Core.
Service Fabric
Replica soft delete for enhanced data protection in Service Fabric
...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation page heavily references PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica, Get-ServiceFabricReplica) and provides examples and API links exclusively for PowerShell. There is no mention of Linux or cross-platform equivalents (such as CLI, REST, or SDK usage), nor are Linux-specific instructions or examples provided. The documentation assumes familiarity with Windows tooling and patterns, potentially creating friction for Linux/macOS users managing Service Fabric clusters.
Recommendations
- Add examples and instructions for using the relevant Service Fabric APIs via cross-platform tools (e.g., Azure CLI, REST API, or .NET SDK) where possible.
- Explicitly mention whether the PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide alternative commands for Linux users.
- Clarify if the feature is supported on Linux-based Service Fabric clusters and, if so, provide Linux-specific guidance.
- Include sample commands or code snippets for Linux environments, such as bash scripts or CLI usage.
- Document any limitations or differences in feature support between Windows and Linux clusters.
Service Fabric
Add custom Service Fabric health reports
...rticles/service-fabric/service-fabric-report-health.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page provides detailed examples for reporting health in Service Fabric using PowerShell, with explicit PowerShell command snippets and references to Windows paths (e.g., PS C:\>). There are no equivalent Linux/bash examples or mentions of Linux-native tools for interacting with Service Fabric health reporting. The PowerShell examples are presented before REST API examples, and REST is only briefly mentioned without concrete sample payloads or curl commands. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific tooling.
Recommendations
- Add equivalent bash or shell examples for health reporting using REST APIs, including sample curl commands and payloads.
- Clarify whether PowerShell commands can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide guidance for Linux/macOS users.
- Present REST API examples with full request/response samples before or alongside PowerShell examples to ensure parity.
- Mention any available CLI tools (e.g., Azure CLI, sfctl) that can be used on Linux/macOS for Service Fabric health reporting, with examples.
- Explicitly state platform requirements for PowerShell examples, and provide alternatives for non-Windows environments.
Service Fabric
Define Service Configuration in StartupServices.xml for a Service Fabric Application
...service-fabric/service-fabric-startupservices-model.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is heavily focused on Visual Studio workflows, referencing Windows-specific build and deployment actions (Build/Rebuild/F5/Ctrl+F5/Publish) and GUI interactions. There are no Linux/macOS equivalents or CLI-based examples provided. The only alternative mentioned is ARM or PowerShell cmdlets, but these are not explained or demonstrated in detail, and the primary guidance is for Windows/Visual Studio users.
Recommendations
- Add explicit instructions or examples for Linux/macOS users, such as using Service Fabric CLI (sfctl) or Azure DevOps pipelines.
- Clarify whether StartupServices.xml can be used or managed outside Visual Studio, and if not, state this limitation clearly.
- Provide sample workflows or scripts for deploying Service Fabric applications on Linux, including how to handle service-level configuration.
- Mention cross-platform tools and alternatives before or alongside Windows/Visual Studio-specific guidance.
Service Fabric
Fault Analysis Service overview
.../service-fabric/service-fabric-testability-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides usage guidance for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the ServiceFabric PowerShell module), but does not mention or provide examples for Linux/macOS command-line tools, Bash, or cross-platform CLI usage. There is no mention of Linux-specific tools or instructions, which may create friction for non-Windows users.
Recommendations
- Add examples or instructions for using the Fault Analysis Service from Linux/macOS environments, such as via the Service Fabric CLI (sfctl), REST API, or Bash scripting.
- Clarify whether the PowerShell and C# approaches are supported on Linux (e.g., PowerShell Core, .NET Core), or if they are Windows-only.
- If the Fault Analysis Service is only accessible via Windows tools, explicitly state this limitation to set user expectations.
- Provide links or references to cross-platform tools or documentation where available.
Virtual Machine Scale Sets
Create an Azure scale set that uses Availability Zones
...s/virtual-machine-scale-sets-use-availability-zones.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is presented before REST API and ARM template examples. There is no explicit Linux shell example (e.g., Bash), and PowerShell is a Windows-centric tool, although it is now cross-platform. The documentation does not exclusively mention Windows tools, but the presence of PowerShell examples without explicit Linux shell alternatives may create friction for Linux/macOS users.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, clarifying that CLI is cross-platform and works on Linux/macOS.
- Where PowerShell is used, note its cross-platform availability, but also provide Bash alternatives for Linux users.
- Ensure that CLI examples are shown before PowerShell examples, as CLI is the primary cross-platform tool.
- Clarify in introductory sections that all methods (portal, CLI, PowerShell, ARM templates) are available to all OS users, and link to platform-specific getting started guides.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides both Windows and Linux coverage in the CLI and API sections, but there are notable signs of Windows bias. PowerShell examples and references are consistently present and detailed, while there is no mention of Bash or Linux-native scripting. The ARM template example is Windows-centric, with only Windows Server images and parameters. Windows-specific terminology (e.g., password complexity, RDP port 3389) appears in portal and ARM template instructions. Linux parity is present in CLI examples (e.g., Ubuntu image), but overall, Windows tools and patterns are more prominent and detailed.
Recommendations
- Add Linux-specific ARM template examples, including imageReference for popular Linux distributions (e.g., Ubuntu, CentOS).
- Provide Bash or shell script equivalents for PowerShell commands, or clarify that CLI commands are cross-platform.
- In portal instructions, mention Linux-specific options (e.g., SSH authentication, Linux username requirements) alongside Windows password guidance.
- In ARM template parameters, include Linux OS versions and adjust security rules to show SSH (port 22) as well as RDP (port 3389).
- Balance PowerShell and CLI coverage, ensuring CLI examples are as detailed as PowerShell and clearly marked as cross-platform.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides deployment instructions for Premium SSD v2 managed disks using Azure CLI, PowerShell, and the Azure portal. However, all CLI and PowerShell examples use Windows-centric VM images (e.g., 'Win2016Datacenter') and do not show Linux VM image values or mention Linux-specific deployment considerations. PowerShell is inherently Windows-focused, but the CLI examples could easily be adapted for Linux users. The documentation does not provide explicit Linux VM deployment examples or highlight Linux parity, despite the feature being cross-platform.
Recommendations
- Add CLI example scripts that use a Linux VM image (e.g., 'UbuntuLTS', 'CentOS', etc.) and clarify any Linux-specific parameters or considerations.
- Explicitly mention that the Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell syntax for Bash (e.g., export variables instead of using $var assignments).
- In the PowerShell section, note that PowerShell Core is cross-platform, but most Linux users will use Azure CLI.
- In the 'Next steps' section, link to Linux-specific disk attachment documentation more prominently and clarify Linux support.
- Consider alternating the order of examples (show Linux/CLI first, then Windows/PowerShell) or provide parallel examples for both OS types.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides parity between Azure CLI (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for deploying ZRS managed disks. However, PowerShell and Windows-centric tools are heavily featured, especially in the Resource Manager Template section, where PowerShell is used for deployment commands. Windows/PowerShell examples are shown before Linux equivalents in some sections, and the 'Next steps' link points to a PowerShell-focused sample repository. There are no Linux-specific shell examples for ARM template deployment (e.g., Bash with az CLI), and PowerShell is used for feature registration and template deployment, which may create friction for Linux/macOS users.
Recommendations
- Add Bash/az CLI examples for ARM template deployment and feature registration, so Linux/macOS users can follow without PowerShell.
- Provide explicit instructions or links for Linux/macOS users on how to perform feature registration and template deployment using Azure CLI.
- Ensure that CLI examples are presented before or alongside PowerShell examples to avoid Windows-first bias.
- Include links to cross-platform sample repositories, not just PowerShell-centric ones.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples. There are no Linux VM image examples (such as Ubuntu, CentOS, etc.), nor any Linux-specific guidance for disk partitioning or formatting. The Quickstart link in the Portal section points only to Windows VM creation. This creates friction for Linux users, who must adapt the examples themselves.
Recommendations
- Provide Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in CLI and PowerShell sections.
- Add links to Linux VM Quickstart documentation in the Portal section.
- Include Linux-specific guidance for partitioning and formatting Ultra Disks after attachment.
- Ensure that all sample scripts and commands are presented for both Windows and Linux VM scenarios, or clarify how to adapt them for Linux.
- When referencing VM creation, mention both Windows and Linux options equally.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides extensive Azure PowerShell examples and scripts, which are primarily Windows-centric. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and gives installation instructions using cmd.exe and PowerShell. Windows tools and patterns are mentioned before Linux equivalents, and there are no explicit Linux shell (bash) or macOS instructions for REST API tooling. However, Azure CLI examples are included, which are cross-platform, and the feature itself is not Windows-only.
Recommendations
- Add bash/Linux/macOS instructions for installing REST API tooling (e.g., armclient or alternatives), or clarify cross-platform options.
- Provide example scripts using Azure CLI for all scenarios currently covered by PowerShell, ensuring parity for Linux/macOS users.
- Mention cross-platform alternatives to Chocolatey (such as Homebrew for macOS, apt/yum for Linux) when describing tool installation.
- Where PowerShell is used, clarify that Azure CLI is fully supported and provide equivalent CLI examples.
- Reorder sections so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker or Corosync), nor are Linux-specific limitations or guidance provided. Windows clustering is mentioned in every disk type section, and the proximity placement group link uses a Windows-specific URL, suggesting Windows is the primary context.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to Linux clustering documentation and requirements where Windows Failover Cluster is referenced.
- Clarify if shared disks are supported for Linux clusters, and if so, provide parity in limitations and guidance.
- Use neutral URLs for features like proximity placement groups, or provide both Windows and Linux links.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, frequently references Windows-specific tools (notably Hyper-V and the Convert-VHD PowerShell cmdlet) for VHD creation and conversion, and provides detailed steps for using Hyper-V Manager. Equivalent Linux-native tooling (such as qemu-img or VBoxManage) is not mentioned or demonstrated. This creates friction for Linux/macOS users who may not have access to Windows environments.
Recommendations
- Add instructions and examples for creating and converting VHD files using Linux-native tools such as qemu-img or VBoxManage.
- Provide a Linux workflow for the VHD creation and conversion steps, including commands for converting raw disk images to fixed-size VHD.
- Reorder sections or provide parallel instructions so that Linux-native approaches are presented before or alongside Windows/Hyper-V/PowerShell methods.
- Clarify which steps are Windows-only and provide alternatives for Linux/macOS users where possible.
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
powershell_heavy
missing_linux_example
Summary
The documentation provides a Windows-style AzCopy example (using 'AzCopy.exe' and Windows file paths) but does not offer a Linux/macOS equivalent. The AzCopy upload command is shown only for Windows, and the file path syntax is Windows-specific. There is no explicit Linux/macOS AzCopy example, even though the rest of the CLI instructions use Bash syntax and variables. The Windows example is presented first and exclusively, creating friction for Linux/macOS users.
Recommendations
- Add a Linux/macOS AzCopy example, e.g., 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Mention that file path syntax differs between Windows and Linux/macOS.
- Consider showing both Windows and Linux/macOS AzCopy examples side-by-side.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Windows and Linux examples for Azure Image Builder templates, but there is a notable Windows bias in several areas. PowerShell commands and tools are frequently referenced, often before Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are less prominent. SHA256 checksum generation is shown with PowerShell first, and Windows-specific troubleshooting and RBAC instructions are highlighted. Some sections (e.g., restart customizer) explicitly state Linux is not supported, but Linux alternatives or workarounds are not discussed.
Recommendations
- Ensure Linux and macOS command-line examples (e.g., Azure CLI, shell commands) are always provided alongside PowerShell, and shown first or equally.
- Add Linux-specific troubleshooting guidance and RBAC instructions where only Windows is mentioned.
- Where Windows customizers (e.g., WindowsRestart) are described, clarify Linux alternatives or explicitly state limitations.
- For checksum generation, provide Linux/macOS commands (e.g., sha256sum) before or alongside PowerShell.
- Balance the prominence of Windows and Linux customizer examples, ensuring Shell customizer usage is as detailed as PowerShell.
- Where Windows tools (e.g., Invoke-WebRequest) are mentioned, also reference Linux equivalents (e.g., wget, curl).
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is focused on Linux VMs and provides comprehensive Azure CLI examples for Linux shell scripts. However, PowerShell examples are given equal or greater prominence, and some PowerShell sections reference Windows-specific tools and patterns (e.g., 'ipconfig', 'myscript.ps1', 'Secondary Logon' service). REST API and ARM template examples use Windows-centric script examples (e.g., 'Write-Host Hello World!', '.ps1' scripts) even though the page is about Linux VMs. The PowerShell section is extensive and sometimes references Windows-specific behaviors before Linux equivalents.
Recommendations
- Ensure REST API and ARM template examples use Linux shell scripts (e.g., 'echo Hello World!' or '.sh' files) instead of PowerShell scripts.
- Clarify in PowerShell examples when a command or parameter is Windows-only, and provide Linux-specific alternatives or explanations.
- Avoid referencing Windows tools (e.g., 'ipconfig') in Linux documentation; use Linux equivalents like 'ifconfig' or 'ip'.
- Where PowerShell is used, explicitly show Linux shell script usage and clarify cross-platform applicability.
- Review and adjust example ordering so Linux CLI and shell examples are shown first, with Windows/PowerShell as secondary.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page exhibits mild Windows bias. The introductory section and terminology focus on 'custom windows images' and Windows-specific concepts, with Windows mentioned before Linux. The only command-line example provided is a PowerShell command for role assignment, with no equivalent Linux/CLI example. However, the page does reference Linux custom image creation and Azure CLI for browsing images, and the ARM template examples are platform-agnostic.
Recommendations
- Provide Azure CLI or Bash equivalents for the PowerShell role assignment command.
- Clarify that custom images can be Linux or Windows, and adjust introductory language to be more inclusive.
- Add explicit examples or links for Linux custom image usage and deployment.
- Ensure parity in guidance for both Windows and Linux image scenarios.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, including development environments and SDKs. However, Windows development (Visual Studio and PowerShell) is described before Linux development (Eclipse and Yeoman), and the quickstart link points to a .NET (likely Windows-centric) guide. There are no Linux-specific examples or links provided in the 'Next steps' section, and Windows tools are mentioned first.
Recommendations
- Provide Linux-specific quickstart links alongside Windows/.NET quickstart.
- Alternate the order of Windows and Linux development environment descriptions, or present them side-by-side.
- Include examples or links for Linux development and deployment in the 'Next steps' section.
- Clarify that .NET Core/.NET 5+ workloads are cross-platform and provide guidance for Linux users.
Virtual Machine Scale Sets
Rolling upgrades with MaxSurge for Virtual Machine Scale Sets
...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI example is cross-platform, the PowerShell example is Windows-centric and is presented immediately after the CLI example, potentially giving undue prominence to Windows tooling. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for CLI commands. The PowerShell section is substantial, but not exclusive, and the CLI example is suitable for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Consider placing the CLI example before the PowerShell example to reinforce cross-platform parity.
- Add a note for Linux/macOS users clarifying that PowerShell is optional and not required for these tasks.
- Optionally, provide Bash shell scripting examples for advanced automation scenarios.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation presents Windows operating system support details before Linux, but otherwise provides parity in describing both platforms. No Windows-specific tools, examples, or patterns are favored, and Linux support is clearly outlined. The 'Next steps' section references CLI, Portal, and PowerShell, but does not show preference for Windows tools.
Recommendations
- Consider presenting Linux and Windows operating system support sections in parallel or alphabetical order to avoid perceived prioritization.
- Explicitly mention that CLI and Portal are cross-platform in the 'Next steps' section for clarity.
- If possible, provide links to Linux-specific guidance or troubleshooting for restore points.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation covers both Linux and Windows VMs and provides Azure CLI and PowerShell examples for listing affected disks. However, the PowerShell example is presented first, which is a minor 'windows_first' bias. Both Linux and Windows are explicitly supported, and Azure CLI (cross-platform) is included, so Linux users are not significantly impacted.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Consider providing Bash shell script examples for bulk operations if relevant.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation is generally Linux-focused and provides parity between Azure CLI and Azure PowerShell examples for managing VM extensions. However, PowerShell examples are consistently presented alongside CLI examples, and in some sections (such as 'Discover VM extensions'), PowerShell is shown immediately after CLI, which may subtly reinforce Windows-centric workflows. The documentation also references ARM templates and the Azure portal, both of which are cross-platform. There are no missing Linux examples, and all CLI and script examples use Linux conventions. Overall, the bias is minor and does not impede Linux/macOS users.
Recommendations
- Consider presenting Azure CLI examples before PowerShell in all sections, as CLI is more native to Linux/macOS users.
- Explicitly note that Azure PowerShell is cross-platform, but CLI is often preferred for Linux workflows.
- Add a brief section clarifying that all examples are applicable to Linux VMs and that Azure CLI is recommended for Linux administrators.
- Where possible, highlight Bash scripting and Linux-native tools for troubleshooting and automation.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is largely platform-neutral and focuses on Azure Disk Storage features and regional availability. However, there are minor signs of Windows bias: in some sections, Windows documentation links are presented before Linux equivalents (e.g., disk expansion), and references to Windows-specific documentation (such as PowerShell or Windows disk management) appear without always mentioning Linux alternatives. No critical tasks are Windows-only, but Linux/macOS users may experience slight friction due to Windows-first ordering and occasional omission of Linux-specific links.
Recommendations
- Ensure Linux and macOS documentation links are presented alongside Windows links, ideally with equal prominence.
- When referencing disk management or expansion, always include both Windows and Linux documentation links in the same sentence or section.
- Where Azure CLI or PowerShell is mentioned, clarify cross-platform support and provide examples for both environments.
- Review linked articles (e.g., expand-disks, find-unattached-disks) to confirm Linux parity and update main page links if needed.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation generally covers both Linux and Windows VM scenarios, but there are instances where Windows terminology, tools, and links are presented first or exclusively. For example, partitioning guidance references Windows documentation and tools (MBR/GPT) before mentioning Linux equivalents. In the 'Upload your VHD or VHDX' section, both Azure CLI (Linux) and PowerShell (Windows) links are provided, but Windows terminology and links are often listed first. The OS disk section references Windows drive letters and partitioning, with Linux details appearing later or less prominently.
Recommendations
- Ensure Linux partitioning guidance (MBR/GPT) is equally referenced, with links to relevant Linux documentation (e.g., fdisk, parted, Linux GPT/MBR guides).
- When discussing disk roles, mention Linux device paths (e.g., /dev/sda, /dev/disk/azure/resource) alongside Windows drive letters, and do so in parallel.
- Alternate the order of example links (Azure CLI and PowerShell) or present them together to avoid Windows-first bias.
- Add explicit Linux examples or links where only Windows documentation is referenced (e.g., partitioning, disk conversion).
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management exhibits mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are referenced as default exclusions, and no Linux container image examples or references are provided. The configuration examples and descriptions do not mention Linux-specific images or patterns, nor do they clarify parity for Linux-based Service Fabric clusters.
Recommendations
- Add examples or references to Linux container images (e.g., Ubuntu, Alpine) in the 'ContainerImagesToSkip' setting.
- Clarify whether the described cleanup features and settings apply equally to Linux-based Service Fabric clusters.
- Provide sample configurations or notes for Linux container scenarios, including any differences in behavior or recommended practices.
- Mention common Linux container base images alongside Windows ones to ensure parity.
Service Fabric
Azure Service Fabric networking best practices
...ice-fabric/service-fabric-best-practices-networking.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
windows_tools
minor_windows_example
Summary
The documentation provides networking best practices for Azure Service Fabric clusters and covers both Windows and Linux scenarios. However, there is a mild bias toward Windows: PowerShell is referenced as the primary client API example, Windows-specific tools and scenarios (e.g., RDP, Windows Update, Windows containers) are mentioned before or more prominently than Linux equivalents, and some sample links and templates are Windows-focused. Linux is referenced, but examples and explanations are often Windows-first or Windows-heavy.
Recommendations
- Add explicit Linux CLI (az, bash) examples alongside PowerShell for client API access and cluster management.
- Provide links to Linux-focused ARM templates and sample clusters, not just Windows ones.
- Clarify when a feature or example applies to both Windows and Linux, and provide parity in explanations.
- Where Windows tools (e.g., netsh) are mentioned, add Linux equivalents (e.g., ss, netstat, iptables) or note differences.
- Ensure reverse proxy and container networking guidance includes Linux container scenarios, not just Windows containers.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but Windows-specific tools and scenarios (such as IIS lift-and-shift and Mirantis Container Runtime) are mentioned in detail, and Windows examples and links are sometimes presented before Linux equivalents. However, Linux support and examples are also clearly included.
Recommendations
- Ensure Linux and Windows examples are presented in parallel, with equal prominence.
- Add more Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to match the Windows IIS example.
- Clarify Linux container runtime options beyond Docker, if relevant.
- Where Windows tools are mentioned (e.g., Mirantis Container Runtime), provide equivalent Linux context or alternatives.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) instructions for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in more detail, which may suggest a Windows-first approach. The CLI section is present and sufficient for Linux/macOS users, but the initial emphasis on PowerShell may create minor friction.
Recommendations
- Present CLI (sfctl) instructions before or alongside PowerShell examples to emphasize cross-platform support.
- Explicitly state that sfctl is cross-platform and suitable for Linux/macOS users.
- Consider balancing the detail and prominence of PowerShell and CLI examples.
- Add a short note clarifying that all deployment operations can be performed using sfctl on any OS.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits mild Windows bias. The schema definition for manifest files is referenced with a Windows file path, and there is no mention of Linux/macOS equivalents or installation locations. The examples and directory structure use Windows conventions (e.g., .exe files, Windows-style paths). There are no explicit Linux/macOS examples or guidance, and Visual Studio (a Windows-centric tool) is mentioned as a packaging option without alternatives for Linux/macOS users.
Recommendations
- Include Linux/macOS file path examples for schema definitions and manifest locations.
- Provide guidance or links for packaging and deploying guest executables using cross-platform tools (e.g., Azure CLI, Service Fabric CLI, or VS Code).
- Clarify whether the Service Fabric SDK and packaging tools are available and supported on Linux/macOS, and provide installation instructions if so.
- Add examples using Linux/macOS executables (e.g., ELF binaries, shell scripts) and directory structures.
- Mention alternative editors or IDEs for Linux/macOS users if Visual Studio is not available.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides conceptual and code examples for Reliable Collection object serialization in Azure Service Fabric, focusing on .NET/C# usage. While the main content is platform-neutral, the 'Next steps' section lists 'Upgrading your Application Using Visual Studio' and 'Upgrading your Application Using PowerShell' before any mention of Linux/macOS tools or equivalents. There are no Linux-specific examples or references to cross-platform tooling, which may create a minor perception of Windows bias.
Recommendations
- Add links or references to Linux/macOS-compatible upgrade tools (e.g., Azure CLI, Service Fabric CLI) in the 'Next steps' section.
- Include examples or guidance for developers using Service Fabric on Linux, such as how to register custom serializers in .NET Core/.NET 5+ environments.
- Clarify that Service Fabric supports both Windows and Linux clusters, and note any platform-specific differences in serialization or upgrade processes.
- Consider alternating the order of Windows and Linux/macOS tooling references, or grouping them together for parity.
Virtual Machine Scale Sets
Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview)
...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to Azure CLI, and Windows-specific extension names (e.g., ApplicationHealthWindows) are used in PowerShell examples, while Linux-specific extension names (ApplicationHealthLinux) are used in CLI examples. Portal instructions are platform-neutral, but PowerShell is a Windows-centric tool and is presented alongside CLI, which is cross-platform. The PowerShell examples and references to Windows-specific extension types are not always matched with Linux equivalents or explanations, and PowerShell is given as a primary automation option, which may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell can be used cross-platform (on Linux/macOS via PowerShell Core), but CLI is generally preferred for Linux users.
- In PowerShell examples, provide both ApplicationHealthWindows and ApplicationHealthLinux extension types, or explain when to use each.
- Consider showing Azure CLI examples first, as CLI is more universally available across platforms.
- Add a note about PowerShell Core support for Linux/macOS, or link to guidance for Linux users.
- Ensure that all extension configuration examples are clearly labeled for Windows or Linux VM images.
Virtual Machine Scale Sets
Configure rolling upgrades on Virtual Machine Scale Sets
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell is featured equally alongside CLI and is presented in its own dedicated sections. PowerShell is a Windows-centric tool, and its presence may create friction for Linux/macOS users who do not have access to PowerShell by default. However, Azure CLI examples are present and shown before PowerShell in each section, ensuring Linux parity. No Windows-only tools or patterns are mentioned, and the documentation is not Windows-specific.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider explicitly stating that PowerShell examples are primarily for Windows users, while Azure CLI is suitable for all platforms.
- Add a brief note at the start of the 'PowerShell' sections indicating PowerShell Core is available for Linux/macOS, but Azure CLI is generally easier for non-Windows users.
- Ensure that CLI examples remain prominent and are not overshadowed by PowerShell content.
Virtual Machine Scale Sets
Networking for Azure Virtual Machine Scale Sets
...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) show PowerShell examples before CLI or in more detail. Portal instructions are generic, but scripting examples sometimes favor PowerShell. There are no Windows-only tools or patterns used, and Linux parity is generally maintained, but the ordering and occasional emphasis on PowerShell may create minor friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell in all sections, as CLI is cross-platform.
- Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying resources.
- Explicitly note that Azure CLI is recommended for Linux/macOS users.
- Where possible, add Bash shell script examples for common tasks.
- Review example ordering in tabbed content to avoid 'windows_first' bias.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation page is generally platform-neutral and describes Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific terminology (e.g., 'Windows service', 'EXE/DLL files') and Windows tools (e.g., 'FabricHost.exe') are mentioned first or exclusively in some sections, even though Linux is supported. Linux equivalents or clarifications are not always provided alongside Windows references.
Recommendations
- Where Windows-specific tools or executables are mentioned (e.g., 'FabricHost.exe', 'EXE/DLL files'), clarify if/how these concepts apply on Linux clusters, or explicitly state differences.
- When describing node startup processes, include Linux-specific details or note if the process differs.
- When referencing file types (e.g., EXE/DLL), add Linux equivalents (e.g., ELF binaries, .so files) or clarify that Linux binaries are supported.
- Ensure that examples and terminology are equally representative of both Windows and Linux environments.
- Add links or references to Linux-specific documentation where relevant.
Virtual Machine Scale Sets
Attach or detach a virtual machine to or from a Virtual Machine Scale Set
...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, move VMs between scale sets), but consistently includes Azure PowerShell examples alongside Azure CLI, which is primarily a Windows-centric tool. Azure PowerShell examples are often more detailed and shown immediately after CLI, potentially creating a perception of Windows preference. However, Azure CLI is cross-platform and all examples use it, including Linux-centric VM images (e.g., Ubuntu2204), and there are no Windows-only tools or patterns. No critical steps are Windows-only.
Recommendations
- Consider explicitly noting that Azure CLI is cross-platform and preferred for Linux/macOS users.
- If possible, provide Bash shell script examples for common tasks (especially for Linux users) in addition to Azure CLI.
- Clarify that Azure PowerShell is available on Linux/macOS, but CLI is generally more native for those platforms.
- Ensure parity in detail between CLI and PowerShell examples.
- If showing both CLI and PowerShell, consider showing CLI first to reinforce cross-platform parity.
Virtual Machine Scale Sets
Automatic OS image upgrades with Azure Virtual Machine Scale Sets
...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
minor_windows_defaults
Summary
The documentation provides both Windows and Linux coverage for Azure Virtual Machine Scale Sets automatic OS image upgrades. However, there are several signs of Windows bias: Windows terminology and configuration properties (e.g., enableAutomaticUpdates, Windows Update) are discussed in detail, often before or more prominently than Linux equivalents. PowerShell examples (a Windows-centric tool) are given equal prominence to Azure CLI, but are listed first in most cases. ARM template and Bicep examples default to Windows images. Some explanations reference Windows-specific behaviors (e.g., drive letter reassignment) without Linux equivalents. However, Linux images and Azure CLI examples are present throughout, and the feature is not Windows-only.
Recommendations
- Ensure ARM template and Bicep examples use both Windows and Linux images, or provide Linux-focused variants.
- When discussing configuration properties, clarify Linux-specific requirements or behaviors alongside Windows (e.g., mention Linux patching differences).
- Alternate the order of PowerShell and Azure CLI examples, or explicitly state that Azure CLI is cross-platform.
- Add notes about Linux disk mount behavior (e.g., device naming) where Windows drive letter reassignment is mentioned.
- Where possible, use neutral language and avoid defaulting to Windows terminology when describing generic features.
Virtual Machine Scale Sets
Orchestration modes for Virtual Machine Scale Sets in Azure
...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a comprehensive overview of orchestration modes for Azure Virtual Machine Scale Sets, focusing on platform features and APIs. While most content is platform-neutral, there are minor instances where Windows terminology or links are presented before Linux equivalents, such as referencing managed identities with a Windows VMSS portal link and mentioning Azure Site Recovery 'via PowerShell' without a Linux CLI equivalent. However, the majority of examples and guidance are generic and applicable to both Linux and Windows VM workloads.
Recommendations
- Ensure that all references to managed identities and Azure Site Recovery include both Linux and Windows guidance, or clarify if a feature is Windows-only.
- Where PowerShell is mentioned, provide equivalent Azure CLI or Bash examples for Linux/macOS users.
- Review links and examples to ensure Linux parity, especially in sections referencing VM extensions, backup, and recovery.
- Explicitly state when a feature or example is Windows-only to avoid confusion.
Virtual Machine Scale Sets
Custom metrics for rolling upgrades on Virtual Machine Scale Sets
...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Linux and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets, but there is a notable Windows bias. PowerShell examples and Windows-specific extension types (ApplicationHealthWindows) are presented alongside Linux equivalents, but Windows terminology and tools (PowerShell, Windows extension type) are often shown first or in parallel. The PowerShell section is more detailed than the Bash section, and Windows-specific extension names are used in several code snippets. The CLI and REST examples are neutral, but the PowerShell examples are prominent and sometimes precede Linux/Bash examples. Overall, Linux users can complete all tasks, but Windows tools and patterns are emphasized.
Recommendations
- Ensure Linux examples (Bash, ApplicationHealthLinux) are presented before or equally with Windows examples in all sections.
- Expand Bash/Linux sample scripts to match the detail and completeness of PowerShell examples.
- Clarify extension type usage: explicitly state when to use ApplicationHealthLinux vs ApplicationHealthWindows, and provide Linux-focused sample JSON.
- Balance CLI and PowerShell coverage, ensuring Linux commands are not overshadowed by Windows/PowerShell.
- Add troubleshooting steps for Linux/Bash environments, not just generic or Windows-centric guidance.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation is generally balanced and explicitly applies to both Linux and Windows VMs. However, in several sections, Windows-specific tools and mechanisms (such as Volume Shadow Service and SQL Server Always On Availability Groups) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced later and with less detail. Some backup consistency methods are described in greater depth for Windows, while Linux approaches are briefly noted. SQL Server backup options are discussed in detail, but comparable Linux database backup guidance is not provided.
Recommendations
- Provide equal detail for Linux backup consistency tools (e.g., elaborate on fsfreeze usage and limitations, and mention other Linux tools for application-consistent backups).
- When mentioning Windows-specific mechanisms (like VSS), immediately follow with Linux alternatives and examples, ensuring parity in explanation and guidance.
- Include examples or references for backing up popular Linux databases (e.g., MySQL, PostgreSQL) in Azure VMs, similar to the SQL Server guidance.
- Ensure that comparison tables and solution descriptions explicitly state Linux support and any limitations, not just Windows features.
- Where possible, provide links to Linux-focused backup and disaster recovery documentation.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides general best practices for virtual machine cost optimization and references both Windows and Linux VM pricing. However, there is a minor bias in the development/test environment section, where B-Series recommendations specify 'Use at least B2 for Windows machines' without an equivalent Linux guidance, and Windows is mentioned first in pricing links. There are no PowerShell-heavy examples or Windows-only tools, and Linux is referenced in VM creation and pricing links.
Recommendations
- Add equivalent Linux guidance for B-Series VM sizing if applicable (e.g., 'Use at least B2 for Linux machines' or clarify if sizing differs).
- Ensure Linux examples or recommendations are provided alongside Windows-specific advice in all relevant sections.
- When linking to pricing pages or VM sizes, mention Linux and Windows equally (e.g., 'Review pricing for both Windows and Linux VMs').
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both. However, throughout the page, Windows/PowerShell examples and links are consistently mentioned before Linux/CLI equivalents, and PowerShell is referenced as a primary tool for certain operations (e.g., revoking access, enabling features). This ordering and emphasis may create a perception of Windows/PowerShell as the default or preferred platform/tool, even though Linux/CLI parity is present.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI examples and links, or present them side-by-side to reinforce equal support.
- Explicitly state that all features and procedures are equally available for Linux and Windows VMs at the start of relevant sections.
- Where PowerShell is referenced for tasks (e.g., revoking access), ensure CLI and/or Bash equivalents are also mentioned with equal prominence.
- Consider adding sample code snippets for both PowerShell and CLI in the main body, not just in linked articles.
- Review the 'Next steps' and in-text links to ensure Linux/CLI resources are not consistently listed after Windows/PowerShell.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation page shows a mild Windows/PowerShell bias. In the 'Custom role' section, the link for creating a custom RBAC role points to a PowerShell-specific guide, with no mention of CLI or ARM template alternatives. In the 'Configure the Network access policy' section, both Azure CLI and PowerShell are mentioned, but PowerShell is listed second. However, there are no explicit Linux/bash examples or links for custom role creation, and PowerShell is referenced multiple times without Linux-first parity.
Recommendations
- Add links or references to creating custom RBAC roles using Azure CLI and ARM templates, not just PowerShell.
- Ensure that for every PowerShell example or link, an equivalent Azure CLI (bash/Linux) example or link is provided.
- Consider listing CLI (cross-platform) options before PowerShell to avoid a Windows-first impression.
- Where possible, provide code snippets or links for both Linux and Windows users.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are often presented before CLI (which is more cross-platform). References to role assignment and policy assignment include portal, PowerShell, and CLI, but PowerShell is frequently mentioned first. The 'Next steps' section does provide both Linux and Windows-specific links for VHD upload/download, but overall, there is a slight tendency to foreground Windows/PowerShell tools.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Where possible, clarify that Azure CLI commands work on all platforms, and explicitly mention Linux/macOS compatibility.
- Ensure parity in example scripts and screenshots for Linux/macOS users, especially in sections where PowerShell is highlighted.
- Consider adding a short note about platform compatibility for each tool (e.g., 'Azure CLI works on Windows, Linux, and macOS').
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types, but PowerShell (a Windows-centric tool) is consistently given equal prominence and sometimes appears first in sections. There are no Linux-specific shell examples (e.g., Bash), and no Linux-specific guidance for disk attachment or SCSI PR usage. However, Azure CLI is cross-platform and all critical operations are covered via CLI, so Linux/macOS users can complete all tasks.
Recommendations
- Explicitly note that Azure CLI commands work on Linux/macOS and provide Bash shell invocation examples where relevant.
- Consider showing Azure CLI examples before PowerShell, or clarifying that PowerShell is primarily for Windows users.
- Add a brief section or link describing how to mount and use shared disks on Linux VMs after attachment (e.g., using 'lsblk', 'mount', etc.), especially for clustered applications.
- If SCSI PR commands require OS-level configuration, provide Linux-specific instructions or references.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation covers both Linux and Windows VMs for ephemeral OS disks, with clear applicability to both. However, there are minor signs of Windows bias: Windows Server image sizing is discussed first in the 'Size requirements' section, and PowerShell is mentioned before CLI in the 'Customer Managed key' section. Linux examples and tools are present but sometimes secondary.
Recommendations
- Present Linux and Windows examples/tools in parallel or alternate order to avoid implicit prioritization.
- In the 'Size requirements' section, mention Linux image sizing before or alongside Windows image sizing.
- In the 'Customer Managed key' section, list CLI and PowerShell together or alternate their order.
- Ensure that any linked deployment guides or scripts provide both Linux and Windows instructions equally.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples for deploying the extension, even though PowerShell is primarily a Windows-centric tool. The PowerShell example is presented before the Azure CLI example, which is more commonly used on Linux/macOS. However, the overall content and examples are Linux-focused, and Linux CLI and ARM template examples are provided throughout. No Windows tools or patterns are mentioned exclusively, and Linux-specific troubleshooting and manual steps are included.
Recommendations
- Move the Azure CLI example before the PowerShell example in the deployment section to prioritize Linux-native tooling.
- Clarify that PowerShell can be used cross-platform, but Azure CLI is recommended for Linux/macOS users.
- Consider adding Bash script examples for extension deployment, as Bash is the default shell on most Linux systems.
- Explicitly state that PowerShell examples are optional for Linux users and provide links to Azure CLI installation instructions if needed.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation is primarily focused on Linux, as expected given the page title and content. However, there are some minor signs of Windows bias: PowerShell deployment instructions are presented before Azure CLI instructions in several sections, and troubleshooting commands reference Azure PowerShell first. There are also warnings about PowerShell-specific issues, which may not be relevant to Linux users. All examples, paths, and instructions are Linux-centric, and no Windows-only tools or patterns are promoted for core tasks.
Recommendations
- Present Azure CLI deployment instructions before PowerShell, as CLI is more commonly used on Linux.
- Clarify that PowerShell instructions are for users managing Linux VMs from Windows or cross-platform environments.
- Move PowerShell-specific warnings to a dedicated section for cross-platform administrators.
- Ensure troubleshooting sections highlight Azure CLI commands first, or equally with PowerShell.
- Add a brief note explaining that PowerShell can be used from any OS, but Azure CLI is native to Linux.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides clear, separate instructions for both Linux and Windows VMs, with Linux steps appearing first. Both platforms are covered with their respective tools (waagent for Linux, Sysprep for Windows), and Azure CLI commands are used for Linux, while PowerShell is used for Windows. There is no evidence of missing Linux examples, Windows-only tools, or Windows-first ordering. The only minor bias is that the Windows section includes a PowerShell example for marking the VM as generalized, while the Linux section uses Azure CLI. However, this reflects typical platform usage rather than bias.
Recommendations
- Consider providing both Azure CLI and PowerShell examples for marking VMs as generalized in both Linux and Windows sections to ensure parity.
- Ensure that any Azure portal steps or cross-platform tools are referenced equally for both OS types.
- Explicitly mention that Azure CLI can be used for Windows VMs as well, if applicable.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys, but the PowerShell section is presented first and is more detailed. The prerequisites and linked articles also prioritize PowerShell and Windows-specific instructions before CLI or portal options. While Linux is supported and CLI examples are present, the overall structure and example order show a mild Windows bias.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially since CLI is cross-platform and preferred by many Linux/macOS users.
- Expand CLI examples to match the detail and complexity of PowerShell examples, ensuring parity in guidance.
- Review linked prerequisite articles to ensure Linux/CLI instructions are not secondary to Windows/PowerShell instructions.
- Explicitly mention that both PowerShell and CLI can be used on any supported OS, and clarify any OS-specific limitations if present.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
minor_windows_example
Summary
The documentation provides cross-platform guidance for creating image definitions and versions in Azure Compute Gallery, with CLI, PowerShell, Portal, and REST examples. However, PowerShell examples are Windows-centric by default, and Windows is often mentioned first or as the primary example in PowerShell sections. Linux is referenced in CLI and REST examples, but PowerShell examples default to Windows, and Windows terminology appears before Linux in some cases. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- In PowerShell sections, provide explicit Linux examples alongside Windows examples, or clarify that PowerShell can be used for Linux images by showing -OsType Linux.
- Ensure that Linux and Windows examples are presented with equal prominence, alternating which OS is shown first in code samples.
- Add notes or links for Linux/macOS users about using Azure CLI or REST as preferred cross-platform tools.
- Where possible, clarify that PowerShell can be used on macOS/Linux via PowerShell Core, and provide guidance for those environments.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples and terminology (cmdlets, parameters, scripts) are frequently mentioned first or in prominent positions, even though the page is Linux-focused. PowerShell is a Windows-native tool, and while it is available cross-platform, Linux users typically prefer Bash/CLI. Some instructions reference using PowerShell sessions for Azure CLI, which may confuse Linux users. There are no missing Linux examples, but the overall tone and ordering subtly favor Windows/PowerShell patterns.
Recommendations
- Present Azure CLI examples and instructions before PowerShell, as CLI is more native and familiar to Linux users.
- Clarify that Azure CLI can be used in Bash shells and is the recommended tool for Linux environments.
- Avoid suggesting PowerShell sessions for Azure CLI usage; instead, mention Bash or native Linux shells.
- Add explicit notes about cross-platform support for PowerShell, but emphasize CLI for Linux scenarios.
- Review terminology to ensure Linux-native patterns (e.g., Bash, shell scripting) are referenced where appropriate.
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
powershell_heavy
Summary
The documentation is overwhelmingly Linux-focused, with detailed, distribution-specific guidance for Ubuntu, SUSE, and Red Hat (with and without LVM). However, there is a single section at the end that uses PowerShell to check classic VM SKU support for expanding disks without downtime. This section is not accompanied by a Linux/CLI equivalent, which could create friction for Linux users managing classic VM SKUs.
Recommendations
- Provide an Azure CLI or Bash equivalent for checking classic VM SKU support for expanding disks without downtime, or clarify if this check is only possible via PowerShell.
- If PowerShell is required for this specific check, explicitly state its necessity and provide guidance for Linux users on how to install/use Azure PowerShell cross-platform.
- Consider linking to relevant Azure CLI documentation or tools for VM SKU capability queries, if available.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
Summary
The documentation provides comprehensive instructions for creating and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is presented first in nearly every major section and is referenced as the primary example for VM creation and disk conversion. Windows tools and terminology (e.g., Hyper-V Manager, 'Connect', 'Action > Shut Down') are used before Linux-native alternatives. Linux/KVM/VMware instructions are present and detailed, but Windows/Hyper-V steps are prioritized and sometimes referenced as the canonical workflow.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V, or at least in parallel.
- Add a summary table or navigation at the top to help users quickly find instructions for their preferred platform.
- Where possible, avoid referencing Hyper-V steps as canonical (e.g., 'Follow the steps in Hyper-V Manager...') in Linux/KVM/VMware sections; instead, provide full instructions within each section.
- Clarify that Hyper-V is Windows-only and provide explicit guidance for Linux/macOS users on alternative workflows.
- Ensure that conversion steps (e.g., VHD creation) reference both Windows and Linux tools equally, and do not assume Hyper-V as the default.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the opening sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific information. This creates a minor 'windows_first' bias, as Windows context is presented before Linux details, despite the page being Linux-focused.
Recommendations
- Move Windows Server 2016 context to a background or infrastructure section, clarifying its relevance to Linux VM time sync.
- Begin the documentation with Linux-specific time sync concepts and configuration options.
- Ensure Linux guidance and examples are always presented first and are the primary focus.
- If referencing Windows documentation, clearly explain its relevance to Linux VM users.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but PowerShell examples are presented before Azure CLI, and are more extensive. This creates a minor Windows bias, as PowerShell is less commonly used on Linux compared to Bash/Azure CLI. However, Linux-native CLI and OS-level commands are also included, ensuring Linux users can complete all tasks.
Recommendations
- Present Azure CLI (bash) examples before PowerShell, as CLI is more native to Linux environments.
- Expand Azure CLI sections to match the detail and coverage of PowerShell examples, ensuring parity.
- Clarify that PowerShell examples are optional for Linux users, and highlight Azure CLI as the primary method.
- Consider removing or minimizing PowerShell sections unless there is a clear Linux PowerShell user base.
- Add explicit Bash scripting examples where appropriate, especially for OS-level checks.