← Back to Dashboard
290
Pages Scanned
97
Pages Flagged
290
Changed Pages
33.4%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08 Scan started

Scan Information

Started At: 2026-02-12 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 290

Files Completed: 290

Problematic Pages

97 issues found
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation for Initializer CodePackages in Service Fabric is heavily focused on Windows containers. All examples use Windows container images, Windows paths (C:\), and Windows commands (cmd, echo, type, ping). There are no examples or guidance for Linux containers or Linux-based workloads, and Windows-specific tools and patterns are referenced throughout. The page assumes familiarity with Windows container applications and does not mention Linux equivalents.
Recommendations
  • Add examples using Linux container images (e.g., Ubuntu, Alpine) and Linux commands (bash, echo, cat, etc.).
  • Provide guidance on how Initializer CodePackages work with Linux containers, including differences in volume mounting and command syntax.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if not, explicitly state this limitation.
  • If Linux containers are supported, ensure parity in documentation by including Linux-focused snippets and walkthroughs.
  • Mention Linux paths and conventions alongside Windows paths when discussing volume mounts.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and instructions are Windows-centric. There are no Linux equivalents or workarounds provided, and the feature is unavailable for Linux users.
Recommendations
  • Clearly indicate at the top that the reverse proxy feature is Windows-only to prevent confusion for Linux users.
  • Provide guidance or links to alternative approaches for Linux clusters, such as recommended patterns for service discovery and communication.
  • If/when Linux support is planned, add a roadmap or status note.
  • Consider creating a separate documentation page for Linux users explaining the limitations and possible alternatives.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
Although the introduction claims Service Fabric clusters can run on Windows Server and Linux, the documentation page exclusively lists Windows Server versions as supported operating systems for standalone clusters, and provides Windows-specific security guidance. There are no Linux-specific examples, instructions, or supported OS listings. Windows authentication and tools are mentioned, but Linux equivalents are not provided.
Recommendations
  • Clarify whether standalone Service Fabric clusters are supported on Linux, as the OS support section currently states Linux isn't supported.
  • If Linux support is planned or available, add Linux-specific instructions, examples, and supported OS listings.
  • Provide parity in security guidance for Linux clusters, including certificate management and authentication options relevant to Linux environments.
  • If standalone clusters are Windows-only, update the introduction to avoid implying Linux support and make the Windows-only nature explicit.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation is heavily focused on Windows-centric tools, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and upgrade instructions reference Visual Studio (a Windows-only IDE) and PowerShell (primarily used on Windows for Service Fabric management), with no mention of Linux/macOS alternatives or CLI-based workflows. There are no examples or guidance for Linux users, and Windows tools are presented as the default and only option.
Recommendations
  • Add instructions for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include examples for configuring upgrade parameters and health policies using command-line tools available on Linux/macOS.
  • Mention and link to any available cross-platform tools or workflows for Service Fabric application upgrades.
  • Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page prioritizes Windows-centric tools (PowerShell, Visual Studio) in both structure and parameter tables, with detailed examples and descriptions for these tools. Linux-compatible tools (SFCTL/CLI) are covered later and less thoroughly, with fewer concrete examples and less guidance. No explicit Linux/macOS command examples are provided for parameter usage, and Windows tools are consistently mentioned first.
Recommendations
  • Add explicit Linux/macOS command examples using SFCTL for each parameter, similar to the PowerShell examples.
  • Reorganize the page to present all upgrade methods (PowerShell, Visual Studio, SFCTL, REST) equally, or group by platform rather than tool.
  • Include a comparison table showing parameter mapping between PowerShell and SFCTL to help Linux users.
  • Ensure that Linux CLI options are described with the same level of detail and examples as Windows tools.
  • Consider mentioning cross-platform tools (e.g., Azure CLI, REST API) earlier in the article.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) alongside REST APIs, but does not provide Linux-specific CLI examples (such as Azure CLI or sfctl) for critical lifecycle operations. PowerShell commands are often listed before REST API alternatives, and there is no explicit guidance for Linux/macOS users, despite Service Fabric supporting cross-platform clusters and management.
Recommendations
  • Add equivalent Azure CLI and sfctl command examples for all major lifecycle operations (deploy, upgrade, remove, etc.), especially in sections where only PowerShell cmdlets are shown.
  • Explicitly mention cross-platform tools (Azure CLI, sfctl) in each operation, not just in the introductory include.
  • Where PowerShell is referenced, clarify its platform limitations and suggest alternatives for Linux/macOS users.
  • Consider showing REST API, CLI, and PowerShell examples side-by-side, or in a consistent order (e.g., CLI first, then PowerShell), to avoid Windows-first bias.
  • Add a short section or note about managing Service Fabric applications from Linux/macOS, linking to relevant guides.
GitHub Create Pull Request
Service Fabric Advanced Application Upgrade Topics ...-fabric/service-fabric-application-upgrade-advanced.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page heavily features PowerShell cmdlets for Service Fabric application upgrades, with all command-line examples and upgrade procedures shown exclusively in PowerShell syntax. There is no mention of Linux/macOS equivalents, such as the Service Fabric CLI (sfctl), nor are cross-platform tools or workflows discussed. Windows tools and patterns (PowerShell, Visual Studio) are referenced first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Mention and link to documentation for sfctl and other cross-platform tools where PowerShell is referenced.
  • Clarify which features or commands are Windows-only, and which are available cross-platform.
  • Provide guidance for Linux/macOS users on how to perform upgrades and configuration using sfctl or REST APIs.
  • Include notes or sections for Linux/macOS users, especially where PowerShell or Visual Studio are referenced.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page is not strictly Windows-only, but it demonstrates Windows bias by consistently referring to 'custom windows images' and providing PowerShell examples for role assignment. Linux equivalents (such as Bash/CLI commands) are not provided, and Windows terminology is used first throughout. However, links to Linux custom image creation and Azure CLI image browsing are included, mitigating some bias.
Recommendations
  • Clarify that custom images can be Linux or Windows, and provide examples for both.
  • Add Azure CLI (bash) examples for role assignment alongside PowerShell.
  • Use neutral language (e.g., 'custom images' instead of 'custom windows images') unless the feature is truly Windows-only.
  • Show Linux ARM template image references and marketplace plan examples.
  • Explicitly state Linux support and link to relevant Linux documentation where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux examples for key security tasks, such as certificate generation and secret encryption. However, Windows examples (PowerShell) are often presented first, and Windows-specific tools (Windows Defender, Azure DSC, PowerShell commands) are discussed in dedicated sections. Windows terminology and tools are referenced more frequently, and some sections (Windows Defender, security baselines) are Windows-only, with Linux alternatives not always described. Linux examples are present but sometimes less detailed or positioned after Windows instructions.
Recommendations
  • Present Windows and Linux examples side-by-side or in parallel sections to avoid Windows-first ordering.
  • Expand Linux-specific guidance for security baselines and antimalware, referencing common Linux tools (e.g., SELinux, AppArmor, ClamAV) or Azure-supported Linux security extensions.
  • Clarify when a feature or tool is Windows-only and provide Linux alternatives or explicitly state if none exist.
  • Ensure parity in detail and clarity between Windows and Linux instructions, especially for certificate and secret management.
  • Add links to Linux-focused documentation where only Windows links are currently provided.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily biased towards Windows/PowerShell usage. All code examples and instructions rely exclusively on PowerShell and the Microsoft.ServiceFabric.Powershell.Http module, with no mention of Linux/macOS-compatible tools or CLI alternatives. REST API usage is also shown only via PowerShell, and there are no Bash/cURL or cross-platform examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or the required modules.
Recommendations
  • Add Bash/cURL examples for REST API calls, showing how to trigger backups and track progress using standard Linux/macOS tools.
  • Mention cross-platform alternatives to Microsoft.ServiceFabric.Powershell.Http, if available, or clarify if PowerShell Core (pwsh) is supported on Linux/macOS.
  • Provide guidance for Linux/macOS users on connecting to Service Fabric clusters and performing backup operations without PowerShell.
  • Explicitly state any limitations or requirements for non-Windows environments, and link to relevant documentation for Linux/macOS users.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using C#, application manifests, and PowerShell. The PowerShell examples are Windows-specific, and there are no equivalent Linux CLI or scripting examples (such as Bash or Azure CLI). The documentation references Windows-specific tools and patterns (e.g., PowerShell cmdlets) without mentioning or demonstrating Linux alternatives, which may create friction for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for configuring auto scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly state when a given example or tool (such as PowerShell) is Windows-only, and provide guidance or links for Linux users.
  • Where possible, provide cross-platform instructions or note any limitations for Linux clusters (e.g., which features are supported on Linux vs. Windows).
  • Include a section or table summarizing which management tools and APIs are available on each platform (Windows, Linux, macOS).
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters (e.g., retrieving the cluster manifest), and links to PowerShell-based deployment guidance first. There is no explicit mention of Linux/macOS command-line tools or examples (such as Bash, Azure CLI, or cross-platform SDKs), and Windows-centric tools like Visual Studio are referenced for publishing. While Service Fabric is cross-platform, the documentation leans toward Windows workflows.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, highlighting cross-platform approaches.
  • Mention cross-platform SDKs (e.g., .NET Core, Python) for programmatic access, and provide sample code or links.
  • Clarify that PowerShell examples can be run on Linux/macOS via PowerShell Core, or provide alternative commands.
  • Reference Visual Studio Code as a cross-platform IDE for deployment, not just Visual Studio.
  • Ensure links to deployment guides include both Windows and Linux/macOS workflows.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., links ending with '-windows-server.md'), and the Patch Orchestration Application is described only for Windows. There are no explicit Linux examples or equivalent Linux-focused upgrade/configuration guidance, suggesting a Windows-first approach and missing Linux parity.
Recommendations
  • Add links and examples for Linux-based Service Fabric standalone clusters, including upgrade and configuration instructions.
  • Clarify whether Service Fabric standalone clusters are supported on Linux, and if so, provide Linux-specific guidance or note any limitations.
  • Mention or link to any Linux patch orchestration solutions if available, or explicitly state if POA is Windows-only.
  • Ensure that references to configuration files and procedures are applicable to both Windows and Linux, or clearly differentiate when they are not.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is heavily oriented toward Visual Studio workflows, referencing Windows-specific actions (Build/Rebuild/F5/Ctrl+F5/Publish) and UI elements. There are no examples or guidance for Linux/macOS users or cross-platform CLI workflows. The only mention of non-Visual Studio deployment is a brief reference to ARM and PowerShell cmdlets, with no Linux equivalents or detailed instructions.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage StartupServices.xml outside Visual Studio.
  • Provide CLI-based examples (e.g., Azure CLI, Service Fabric CLI) for deploying and configuring applications, not just PowerShell.
  • Clarify which parts of the workflow are Visual Studio/Windows-only and offer alternatives for cross-platform development.
  • Mention any limitations or support status for StartupServices.xml in non-Windows environments.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides a PowerShell-only example for deploying Service Fabric applications, references Windows file paths and certificate stores before mentioning Linux equivalents, and generally assumes a Windows-centric workflow. Linux-specific instructions are minimal and appear after the Windows context.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI, sfctl) examples alongside PowerShell commands for deploying applications and overriding parameters.
  • Mention Linux certificate store paths and behaviors earlier and more prominently, not only as a note after Windows instructions.
  • Clarify any platform-specific differences in endpoint configuration and deployment, and link to Linux/macOS-specific guides where available.
  • Where file paths are referenced (e.g., schema definitions), include Linux equivalents if applicable.
GitHub Create Pull Request
Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images. However, PowerShell examples are significantly more verbose and detailed, including full network setup and VM configuration, while CLI examples are concise and focus only on the core VM creation steps. PowerShell is a Windows-centric tool, and its prominence and detail may create friction for Linux/macOS users. Additionally, PowerShell examples are often presented immediately after CLI, suggesting a Windows-first approach. No Linux-specific tools (e.g., Bash scripts) or macOS guidance are provided, but Azure CLI is cross-platform.
Recommendations
  • Provide equally detailed Azure CLI examples, including network setup and VM configuration, to match the depth of PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider including Bash shell script examples for Linux users, especially for more complex scenarios.
  • Clarify that PowerShell examples are primarily for Windows users, and encourage Linux/macOS users to use Azure CLI.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
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-specific terminology and tools (e.g., certificate store paths like LocalMachine\My, references to Win32 CryptoAPI, and event log channels) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. Troubleshooting sections and configuration examples often default to Windows-centric approaches, and PowerShell/C++ error codes are used without cross-platform alternatives.
Recommendations
  • Ensure Linux certificate store paths and management tools are described alongside Windows equivalents, not as afterthoughts.
  • Provide troubleshooting guidance for Linux clusters, including log locations and certificate management commands (e.g., using openssl or Linux-specific logs).
  • Include Linux/macOS error codes and diagnostic steps where C++/Windows error codes are given.
  • Clarify when a feature or configuration is Windows-only, and provide Linux alternatives or note limitations.
  • Balance example ordering so Linux and Windows are equally represented, or explicitly state platform applicability.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS shell instructions. PowerShell is presented as the exclusive scripting option for command-line operations, and is mentioned before any Linux-friendly alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI/Bash.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (add, remove, scale, configure placement properties, etc.).
  • Explicitly state that PowerShell examples are cross-platform (if true), or provide guidance for Linux/macOS users on how to use PowerShell Core or Azure CLI.
  • Where possible, provide Bash scripts or instructions for Linux/macOS environments.
  • Mention Azure CLI as an alternative in introductory sections and throughout the document.
  • Clarify any limitations or prerequisites for PowerShell usage on non-Windows platforms.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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 GUI tool typically used on Windows). No Linux/macOS CLI or tool alternatives are mentioned, and the PowerShell command is presented without cross-platform context. The overall guidance assumes Windows-centric patterns, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent CLI examples for Linux/macOS users, such as using Azure CLI or REST API where possible.
  • Clarify whether the PowerShell command can be run from PowerShell Core on Linux/macOS, or provide alternative commands.
  • Mention cross-platform tools or interfaces (e.g., Azure Portal, Service Fabric CLI) where relevant.
  • Add notes about Service Fabric Explorer accessibility from non-Windows platforms, or suggest alternatives.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters. However, there is a notable Windows bias: PowerShell is the only scripting example provided for certificate enrollment, and the Key Vault VM extension is discussed exclusively in its Windows variant. The documentation references Windows-specific certificate store concepts (e.g., 'LocalMachine', 'MY'), and the linking-on-renewal feature is described as 'Only Windows'. There are no explicit Linux/macOS examples or guidance for equivalent certificate provisioning or automation, and Windows terminology/tools are used throughout, often without mentioning Linux alternatives.
Recommendations
  • Add CLI/bash examples for certificate enrollment and provisioning, using Azure CLI or REST API, to complement PowerShell scripts.
  • Document the Key Vault VM extension for Linux (if available), or clarify limitations and provide Linux-specific guidance for certificate provisioning.
  • Include references to Linux certificate stores (e.g., /etc/ssl/certs) and explain how Service Fabric clusters on Linux nodes should manage certificates.
  • Where Windows-specific features (like linking-on-renewal) are discussed, explicitly state Linux/macOS limitations or alternatives.
  • Ensure that JSON ARM templates and deployment steps are annotated for cross-platform applicability, noting any OS-specific requirements.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page provides several examples and links to Azure PowerShell modules for managing Service Fabric managed clusters, with PowerShell mentioned before Azure CLI and other cross-platform tools. While Azure CLI and ARM/Bicep templates are referenced, PowerShell is emphasized in the best practices section and specific tasks, potentially creating friction for Linux/macOS users who may prefer CLI or other cross-platform utilities.
Recommendations
  • Add explicit Azure CLI examples for all tasks currently demonstrated with Azure PowerShell (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI alongside PowerShell in the best practices section, ensuring parity in guidance.
  • Where possible, provide code snippets or links for both PowerShell and CLI for common operations.
  • Clarify that Azure PowerShell is available cross-platform, but highlight CLI as a native option for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily references Az PowerShell cmdlets for managing Service Fabric resources, with explicit links to PowerShell modules. While the Azure CLI (az resource) is mentioned for deleting applications, PowerShell is presented first and more frequently. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for the recommended management operations.
Recommendations
  • Provide Azure CLI examples for all operations (e.g., unprovisioning application type versions, creating applications/services) alongside PowerShell examples.
  • Clarify that Azure CLI commands are cross-platform and highlight their usage for Linux/macOS users.
  • Ensure links to Azure CLI documentation are as prominent as PowerShell links.
  • Consider adding a note about the parity between PowerShell and Azure CLI for managing ARM-managed Service Fabric resources.
GitHub Create Pull Request
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides monitoring guidance for Azure Service Fabric clusters on both Windows and Linux, but there is a noticeable Windows bias. Windows-specific tools (such as EventStore APIs, Event Viewer, Diagnostics Agent) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. Some examples and tutorials focus on Windows/.NET, and Linux-specific instructions are often relegated to brief mentions or links. There are missing Linux-specific walkthroughs and examples, especially for cluster monitoring and event access.
Recommendations
  • Add Linux-specific examples and walkthroughs for cluster monitoring, event access, and log collection, similar to the Windows-focused tutorials.
  • Ensure Linux tools and patterns (such as LTTng, Syslog, and Linux agent configuration) are described in detail and given equal prominence to Windows tools.
  • Provide sample code and configuration snippets for Linux clusters, including how to access Service Fabric events and logs.
  • Where Windows tools are mentioned (e.g., Event Viewer, Diagnostics Agent), immediately reference the Linux equivalents and link to relevant guides.
  • Expand tutorials to include Linux application monitoring and diagnostics, not just .NET/Windows scenarios.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily discusses data serialization in the context of Azure Service Fabric, which is 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. PowerShell and Visual Studio are Windows-first tools, and their exclusive mention creates friction for Linux/macOS users.
Recommendations
  • Add examples or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), which are available on Linux/macOS.
  • Mention Visual Studio Code as a cross-platform IDE alternative for application management.
  • Clarify which upgrade methods are Windows-only and provide Linux/macOS alternatives where possible.
  • Include explicit guidance for Linux/macOS users in the 'Next steps' section.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for Service Fabric application upgrades exhibits a notable Windows bias. PowerShell is the only command-line example provided, and all upgrade-related tooling references (such as Start-ServiceFabricApplicationUpgrade and Update-ServiceFabricService) are PowerShell cmdlets. There are no examples or instructions for Linux/macOS users (e.g., using sfctl or REST APIs), and Windows-specific tools (like http.sys) are referenced without Linux equivalents. The 'Next steps' section also prioritizes Visual Studio and PowerShell, both Windows-centric tools, with no mention of cross-platform alternatives.
Recommendations
  • Add equivalent examples using sfctl (the cross-platform Service Fabric CLI) for Linux/macOS users wherever PowerShell examples are shown.
  • Mention and link to REST API documentation for application upgrades as a platform-agnostic alternative.
  • Clarify when features or limitations (such as http.sys or certificate handling) are Windows-specific, and provide Linux/macOS guidance if applicable.
  • In the 'Next steps' section, include tutorials or references for upgrading applications using sfctl or REST APIs.
  • Where possible, present cross-platform examples first or in parallel with Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates notable Windows bias. All code examples use Windows containers (nanoserver), Windows-specific commands (cmd, echo, ping, set, exit), and reference Windows container compatibility. Querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux equivalents or CLI tools. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add examples using Linux containers (e.g., Ubuntu or Alpine images) with equivalent shell commands.
  • Provide guidance for querying deployment status using cross-platform tools, such as Azure CLI or REST APIs, or document Linux-compatible alternatives.
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, include relevant code snippets.
  • Present examples for both Windows and Linux environments, or explicitly state if the feature is Windows-only.
  • Avoid referencing Windows container version compatibility exclusively; mention Linux container considerations if applicable.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation contains a notable Windows bias in its guidance for authoring and validating manifest XML files. It explicitly recommends opening the Service Fabric XSD schema in Visual Studio using a Windows file path ("C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd") and does not mention Linux or cross-platform alternatives for schema validation or authoring. Additionally, PowerShell is referenced as a way to create service instances, with no mention of Linux equivalents (e.g., Azure CLI, Bash scripts).
Recommendations
  • Provide instructions or examples for validating manifest XML files on Linux/macOS, such as using xmllint, VS Code with the XML extension, or cross-platform editors.
  • Mention the location of the ServiceFabricServiceModel.xsd schema on Linux clusters, or clarify if it is only available on Windows.
  • When referencing PowerShell for service creation, also mention Azure CLI or REST API alternatives that are available cross-platform.
  • Where file paths are given, provide Linux/macOS equivalents if applicable, or clarify platform limitations.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation covers Service Fabric application security in a cross-platform context, but exhibits mild Windows bias. Windows-specific features (e.g., AD accounts, gMSA, BitLocker) are mentioned before or more prominently than Linux equivalents. Some sections (e.g., disk encryption, user accounts) provide Windows-only examples or reference Windows tools, while Linux guidance is missing or relegated to TODOs.
Recommendations
  • Add explicit Linux examples for disk encryption (e.g., using Azure Disk Encryption with Linux VMSS, or referencing Linux encryption tools).
  • Provide parity in user account configuration: clarify how Linux clusters handle service user accounts, and add examples for Linux service principals.
  • When referencing Windows-specific features (e.g., BitLocker, gMSA), clearly indicate their platform scope and provide Linux alternatives or links where possible.
  • Ensure that Linux and Windows examples are presented together or alternately, rather than Windows-first.
  • Complete the TODO for 'Encrypt disks on Linux clusters?' with actionable guidance.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation for restoring backups in Azure Service Fabric is heavily biased towards Windows and PowerShell usage. All command-line examples use PowerShell syntax and require the Microsoft.ServiceFabric.Powershell.Http module, which is Windows-centric. There are no examples or guidance for Linux/macOS users (e.g., using Bash, curl, or cross-platform Service Fabric CLI). Windows tools and patterns are mentioned exclusively and presented first, with no mention of Linux equivalents or alternative workflows.
Recommendations
  • Provide equivalent examples using Bash/curl for REST API calls, suitable for Linux/macOS users.
  • Clarify whether the PowerShell module is required for all platforms, or suggest cross-platform alternatives (e.g., Azure CLI, Service Fabric CLI, or direct REST API usage).
  • Add explicit instructions for Linux/macOS environments, including certificate handling and authentication steps.
  • Indicate platform requirements and limitations for each method (PowerShell module, Service Fabric Explorer, REST API).
  • Consider reordering or grouping examples by platform, or clearly labeling Windows-only steps.
GitHub Create Pull Request
Service Fabric Health monitoring in Service Fabric ...s/service-fabric/service-fabric-health-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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. The text mentions REST as an option but does not demonstrate its usage. This creates friction for Linux/macOS users, as PowerShell is not natively available on those platforms and Service Fabric clusters can run on Linux nodes.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and supported on Linux/macOS.
  • Provide REST API example(s) for health reporting and querying, as REST is platform-agnostic.
  • Clarify in the example section that PowerShell is Windows-specific, and link to Linux/macOS alternatives.
  • Ensure future documentation includes both Windows and Linux/macOS usage patterns where applicable.
GitHub Create Pull Request
Service Fabric Understanding periodic backup configuration ...-fabric-backuprestoreservice-configure-periodic-backup.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation page for configuring periodic backups in Azure Service Fabric is mostly platform-neutral, focusing on REST API usage and JSON configuration. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Integrated Windows Authentication are mentioned, with no reference to Linux or SMB/CIFS equivalents. Windows authentication patterns are described first and exclusively, potentially creating friction for Linux users wishing to use file shares. There are no explicit Linux examples or guidance for configuring file shares from Linux nodes.
Recommendations
  • Add examples and guidance for configuring file share backup storage from Linux-based Service Fabric clusters, including SMB/CIFS mount instructions and authentication options.
  • Clarify whether Linux clusters can use file share backup storage and, if so, provide sample paths and authentication methods relevant to Linux.
  • Mention any limitations or differences for Linux clusters regarding file share backup storage.
  • Consider including both Windows and Linux file share path formats and authentication patterns in examples.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 equal prominence. In the cluster upgrade section, only PowerShell commands are provided for manual upgrades, with no Linux shell (bash) or cross-platform alternatives. Windows registry and Windows Update settings are discussed for VM configuration, with no mention of Linux equivalents or guidance for disabling updates on Linux VMs. Windows-specific configuration appears before Linux in some sections.
Recommendations
  • Provide bash or Azure CLI examples for manual cluster upgrades alongside PowerShell, or clarify if Linux users should use different methods.
  • Include guidance for disabling automatic updates on Linux VMs (e.g., using cloud-init or OS-specific package manager settings).
  • When discussing VM configuration, mention both Windows and Linux settings, or clearly indicate when a step is Windows-only.
  • Ensure Linux examples and references are given equal prominence and ordering as Windows examples, especially in sections not inherently Windows-specific.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Placement Policies ...ce-manager-advanced-placement-rules-placement-policies.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page consistently provides PowerShell examples for configuring Service Fabric placement policies, without offering equivalent Linux/macOS CLI or scripting examples (such as Azure CLI or Bash). Windows/PowerShell commands are presented alongside C# code, but Linux-friendly alternatives are absent. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, where possible.
  • Include Bash scripting or REST API examples to demonstrate cross-platform management.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide guidance for non-Windows users.
  • Explicitly mention any limitations or differences for Linux/macOS cluster management, if applicable.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides numerous PowerShell-based examples and instructions for scaling operations, such as using `Disable-ServiceFabricNode`, `Get-ServiceFabricNode`, and `Remove-ServiceFabricNodeState`. These commands are specific to Windows environments and PowerShell, with no equivalent Linux CLI or script examples provided. Additionally, Windows/PowerShell instructions are presented first and exclusively in several critical scaling workflows, creating friction for Linux users. While the page mentions Linux clusters in the 'Next steps' section, the main scaling guidance lacks Linux parity.
Recommendations
  • Add equivalent Linux CLI or script examples for scaling operations, such as using Service Fabric CLI (`sfctl`) or REST API calls.
  • Clearly indicate when PowerShell commands are Windows-only and provide alternative instructions for Linux clusters.
  • Include Linux-specific guidance for cluster scaling, node management, and state cleanup.
  • Ensure that both Windows and Linux workflows are covered equally in critical operational sections, not just in 'Next steps'.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for Service Fabric networking, but there is a notable Windows bias. PowerShell and Windows-specific tools are referenced more frequently and often appear first. Some examples and explanations (such as dynamic port range checks and client API usage) are Windows-centric or reference Windows tools (e.g., netsh, PowerShell) without Linux equivalents. ARM template samples and DevOps sections also highlight Windows scenarios. However, Linux support is acknowledged and linked, and most best practices are generally applicable.
Recommendations
  • Provide Linux CLI (az CLI, bash) equivalents alongside PowerShell examples, especially for port range checks and cluster management.
  • Add explicit Linux-focused ARM template samples and links, similar to the Windows sample provided.
  • Clarify when guidance is Windows-only and offer Linux alternatives or note when Linux does not require certain steps (e.g., ephemeral port range).
  • Balance the order of presentation so Linux and Windows examples are equally prominent.
  • Expand DevOps/API guidance to include Linux-compatible tools and workflows.
GitHub Create Pull Request
Service Fabric Node types and virtual machine scale sets ...les/service-fabric/service-fabric-cluster-nodetypes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page describes Azure Service Fabric node types and their relationship to virtual machine scale sets. While it mentions both Linux and Windows node types in the extension configuration, the JSON example and property table default to Windows-centric patterns (e.g., Windows-style file paths like 'D:\\SvcFab', certificate store references, and RDP-related next steps). Linux-specific guidance, examples, or parity for remote connection and file paths are missing. The 'Next steps' section links to PowerShell scripts for Windows tasks (RDP port and admin credentials), but does not mention Linux equivalents.
Recommendations
  • Add Linux-specific examples for file paths (e.g., '/var/svcfab') and certificate storage.
  • Provide guidance or links for remote SSH connection to Linux nodes, alongside RDP instructions for Windows.
  • Include Linux admin credential change instructions or scripts, not just Windows/PowerShell.
  • Clarify in property tables which settings are Windows-only and which are Linux-only.
  • Balance 'Next steps' with Linux-focused operational tasks and documentation.
GitHub Create Pull Request
Service Fabric Service Fabric Cluster Resource Manager - Application Groups ...ice-fabric-cluster-resource-manager-application-groups.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 mention of Linux-compatible CLI tools (such as Azure CLI, Bash, or REST API) or cross-platform scripting. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
  • Add Azure CLI examples for all operations shown (creation, update, querying, removal of application capacity).
  • Mention REST API endpoints or provide sample REST calls for managing Application Groups.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), and if so, provide guidance; otherwise, offer alternatives.
  • Include Bash or shell script examples where possible, or link to cross-platform tools.
  • Explicitly state platform requirements for each example/tool used.
GitHub Create Pull Request
Service Fabric Describe a cluster by using Cluster Resource Manager ...ce-fabric-cluster-resource-manager-cluster-description.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows-specific (ClusterManifest.xml, PowerShell) and cross-platform (ClusterConfig.json) configuration examples. However, Windows-centric examples (XML format, PowerShell commands) are consistently presented first and more prominently. PowerShell is the only CLI example given, with no Linux shell or CLI parity. The XML configuration is shown before the JSON configuration, and the infrastructure example is explicitly labeled as <WindowsServer>, with no mention of Linux clusters or their configuration specifics.
Recommendations
  • Add explicit Linux cluster configuration examples, such as <Linux> sections in ClusterManifest.xml or references to Linux node setup.
  • Provide CLI examples using Azure CLI or Bash for Linux users, alongside PowerShell.
  • Clarify any differences in cluster setup or resource management for Linux-based Service Fabric clusters.
  • Ensure JSON configuration examples are given equal prominence and placement to XML/Windows examples.
  • Mention Linux/macOS support status for Service Fabric clusters and link to relevant platform-specific documentation.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
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'), without offering equivalent Linux/macOS CLI examples. The example is presented early and exclusively, which may create friction for Linux users seeking parity.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, e.g., 'sfctl partition health --partition-id ...'.
  • Mention cross-platform management tools and clarify which commands are available on which OS.
  • Where PowerShell is used, provide alternative commands or note if PowerShell Core is supported on Linux/macOS.
  • Ensure examples and instructions are not Windows-centric unless the feature is Windows-only.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides PowerShell examples for configuring move cost, but does not offer equivalent Linux/bash/CLI examples. PowerShell is primarily a Windows tool, and its exclusive use creates friction for Linux/macOS users. The C# examples are cross-platform, but administrative scripting is often done via CLI tools, and only Windows-centric options are shown.
Recommendations
  • Add Azure CLI or REST API examples for configuring move cost, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell examples are supported on Linux/macOS (via PowerShell Core), or provide bash equivalents if possible.
  • Reorder examples so that cross-platform options (Azure CLI, REST API, C#) are shown before or alongside PowerShell.
  • Clarify any platform limitations for Service Fabric management commands.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides detailed PowerShell examples for managing node tags and service requirements, but does not offer equivalent CLI/bash or Linux-native examples. PowerShell is a Windows-centric tool, and its exclusive use here creates friction for Linux/macOS users. No mention is made of Service Fabric CLI or REST API usage for these tasks, despite REST APIs being referenced earlier.
Recommendations
  • Add examples using Service Fabric CLI (sfctl) for node tag management and service configuration, which is cross-platform and works on Linux/macOS.
  • Provide REST API sample requests for adding/removing node tags and setting service tag requirements, as REST APIs are mentioned as a supported mechanism.
  • Clarify which PowerShell commands are available on Linux (if any), or note their Windows-only nature.
  • Consider including bash or shell script examples where appropriate.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not mention or provide equivalent CLI or scripting examples for Linux/macOS users. The PowerShell API is highlighted as a primary method for dynamic configuration, and no Linux-native tools or cross-platform alternatives (such as Azure CLI or REST API) are referenced. This creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI or REST API examples for configuring service sensitivity and maximum load, if supported.
  • Clarify whether PowerShell examples are usable on Linux/macOS (via PowerShell Core), or provide guidance for cross-platform usage.
  • Mention any limitations or alternatives for Linux/macOS users, such as using JSON/XML manifests or C# SDK.
  • Consider providing bash or shell script examples if applicable.
GitHub Create Pull Request
Service Fabric Manage Azure Service Fabric app load using metrics ...ric/service-fabric-cluster-resource-manager-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. PowerShell commands are shown before any mention of cross-platform alternatives, and there is no guidance for Linux users on how to perform these tasks. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform.
  • Provide Bash script examples or reference REST API usage for metric operations.
  • Explicitly mention which tools are available on Linux/macOS and provide links or instructions for installation.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide guidance for Linux/macOS users.
  • Ensure that documentation sections using PowerShell are supplemented with cross-platform alternatives.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) without mentioning Linux equivalents or cross-platform tooling. The linked instructions for scaling standalone clusters point to a Windows Server-specific guide, and there are no examples or guidance for Linux-based Service Fabric deployments, which are possible but not addressed.
Recommendations
  • Include examples and instructions for scaling Service Fabric standalone clusters deployed on Linux machines, if supported.
  • Reference cross-platform tools (such as Service Fabric CLI or REST API) alongside PowerShell, and provide usage examples for both Windows and Linux environments.
  • Clarify in the documentation whether standalone clusters are supported on Linux, and if not, explicitly state this to avoid confusion.
  • If Linux is supported, add links to Linux-specific scaling guides or sections within the documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mention of Azure CLI equivalents or Linux/macOS-friendly approaches. Application packaging is described via Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no examples or guidance for Linux users, and Windows tools are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide guidance for packaging Service Fabric applications using cross-platform tools (e.g., dotnet CLI, sfctl, or manual zip commands).
  • Mention and link to Linux/macOS-compatible tooling and workflows.
  • Clarify which steps are Windows-only and offer alternatives where possible.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there is a notable Windows bias: Windows-specific tools and processes (e.g., PowerShell, Visual Studio, Windows services/executables) are mentioned first or exclusively in several sections. Examples and links for creating standalone clusters are Windows-only, and Linux standalone clusters are explicitly not supported. PowerShell is often referenced before CLI, and Windows-specific executables (FabricHost.exe, Fabric.exe) are described as core components. While Linux support is acknowledged, Linux-specific instructions, examples, and tools are less prominent or missing.
Recommendations
  • Provide Linux-first or Linux-parity examples and instructions alongside Windows ones, especially for cluster creation, management, and health monitoring.
  • Highlight CLI usage equally or before PowerShell, as CLI is cross-platform.
  • Add explicit guidance for Linux users where features are supported, including links to Linux documentation and tools.
  • Clarify Windows-only limitations early and consistently, and provide alternatives or workarounds for Linux users where possible.
  • Include Linux-specific troubleshooting, monitoring, and diagnostic tools and workflows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or instructions for accessing Service Fabric events on Linux-based clusters, nor are Linux-native tools or patterns mentioned. Windows tools and patterns are discussed first and exclusively, creating friction for Linux users.
Recommendations
  • Add information about how Service Fabric events are logged and accessed on Linux clusters, including any differences in event channels or monitoring tools.
  • Mention Linux-native logging mechanisms (e.g., syslog, journald) if applicable, and provide examples or references for integrating Service Fabric diagnostics with these tools.
  • Clarify whether the Azure diagnostics agent and EventStore REST APIs are supported and configured differently on Linux clusters.
  • Ensure parity in examples and instructions for both Windows and Linux environments.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page frequently references Windows Server clusters and provides links and instructions specifically for securing standalone clusters on Windows. There are no equivalent examples, links, or instructions for securing standalone Linux clusters, nor are Linux-specific security patterns or tools mentioned. Windows security (Kerberos) is discussed, but Linux authentication options are not. While Azure-hosted clusters are mentioned (which can be Linux or Windows), standalone cluster guidance is Windows-only.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and any Linux-specific authentication options.
  • Include Linux examples and instructions alongside Windows examples, especially for node-to-node and client-to-node security.
  • Mention Linux tools and patterns (e.g., OpenSSL for certificate creation, Linux account management) where relevant.
  • Clarify which security scenarios apply equally to Linux and Windows, and which are Windows-specific.
  • Provide parity in recommendations for Linux clusters, not just Windows clusters.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation generally avoids OS-specific bias in most upgrade scenarios, but in the 'Upgrading OS images for cluster nodes' section, it only references patching Windows operating systems and links exclusively to Windows-specific instructions. Additionally, the 'Patch Orchestration Application (POA)' is described as a solution for Windows OS patching, with no mention of Linux equivalents or guidance for clusters running Linux nodes. In other sections, both PowerShell and Azure CLI are mentioned together, but PowerShell is listed first, which may indicate a subtle 'windows_first' ordering bias.
Recommendations
  • Add explicit guidance or links for upgrading or patching Linux-based Service Fabric cluster nodes, if supported.
  • Clarify whether Patch Orchestration Application (POA) or similar solutions exist for Linux clusters, or state if it is Windows-only.
  • When mentioning management tools, alternate the order of PowerShell and Azure CLI, or mention Azure CLI first in some cases to balance perceived bias.
  • If certain features (like OS patching) are Windows-only, clearly state this to avoid confusion for Linux users.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. All command-line examples are in PowerShell, with no equivalent Linux (bash/CLI) examples or references to Linux-native tools. Windows tools and patterns are mentioned first and exclusively in example sections, creating friction for Linux users who may not be familiar with PowerShell or lack access to it.
Recommendations
  • Add equivalent bash/CLI examples for Service Fabric operations, such as scaling services, creating/removing instances, and updating configurations.
  • Reference Linux-native tools or Service Fabric CLI where appropriate, alongside PowerShell examples.
  • Clarify which commands are platform-specific and provide guidance for Linux users on how to achieve the same tasks.
  • Consider reordering examples so that platform-neutral or Linux examples are presented alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
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 or scripting examples. Windows tools and patterns (e.g., ApplicationManifest.xml, Visual Studio) are mentioned before Linux alternatives, and Linux-specific limitations are described without offering Linux-native workflows or parity in examples. There are no Linux CLI (e.g., Bash, Azure CLI) examples for managing DNS service or setting DNS names, and enabling DNS service via portal is only available for Windows clusters.
Recommendations
  • Add Azure CLI or Bash examples for setting DNS names and managing DNS service, especially for Linux clusters.
  • Explicitly document Linux-native workflows for cluster and service management, including how to enable DNS service on Linux clusters (e.g., via ARM templates or CLI).
  • Where PowerShell is used, provide equivalent Linux command-line instructions or scripts.
  • Clarify which steps are Windows-only and which are cross-platform, and ensure Linux users are guided through their supported scenarios.
  • Mention Linux-friendly editors (e.g., VS Code) alongside Visual Studio when discussing ApplicationManifest.xml editing.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location in C:\Program Files\...), and mentions Visual Studio as a packaging tool without Linux alternatives. There are no explicit Linux/macOS examples or guidance, and the directory structure example uses a Windows-style executable (.exe). However, the content does not explicitly state that the process is Windows-only, and Service Fabric supports Linux clusters and non-Windows workloads.
Recommendations
  • Add explicit Linux/macOS guidance for packaging guest executables, including references to cross-platform tools (e.g., CLI, VS Code, or other IDEs).
  • Provide Linux file path examples for schema files and directory structure.
  • Clarify that guest executables can be any platform-supported binary (not just .exe), and show examples for Linux binaries.
  • Mention Linux deployment scenarios and provide links to Linux-specific documentation where relevant.
  • Ensure parity in sample links and instructions for Linux users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page primarily describes Azure Service Fabric hosting lifecycle concepts in a platform-neutral manner, but the 'Next steps' section and some linked references emphasize PowerShell for deployment/removal tasks, which is traditionally Windows-centric. There are no explicit Linux/bash examples or references to Linux-native tools, and the only advanced example for downloading a ServicePackage in advance links to a PowerShell cmdlet. This creates friction for Linux/macOS users, who may need to use Service Fabric CLI or REST APIs instead.
Recommendations
  • Add Linux/bash examples alongside PowerShell for deployment and removal tasks.
  • Mention Service Fabric CLI (sfctl) and REST API options for Linux/macOS users.
  • Provide links to Linux/macOS-specific documentation or tools where applicable.
  • Clarify when PowerShell is cross-platform (PowerShell Core) vs. Windows-only.
  • Ensure that advanced scenarios (like downloading ServicePackages) include Linux-compatible instructions.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail, while Linux-native workflows are only briefly referenced (e.g., sfctl and install.sh) without concrete examples. There are no explicit Linux/macOS command-line examples, and the guidance assumes familiarity with Windows tooling.
Recommendations
  • Add explicit Linux/macOS command-line examples using sfctl and install.sh, including sample commands for passing parameters.
  • Reorder sections or provide parallel examples so that Linux-native tools (sfctl, bash scripts) are presented alongside or before Windows/PowerShell equivalents.
  • Clarify when a tool or script is Windows-only (e.g., Deploy-FabricApplication.ps1) and provide Linux alternatives.
  • Expand on the Jenkins/script task example to show a concrete Linux shell script for token replacement.
  • Where Visual Studio is referenced, note cross-platform alternatives or clarify if the workflow is Windows-only.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page for Service Fabric application and service manifest examples exhibits mild Windows bias. Windows-specific concepts (such as local admin accounts, NetworkService, Setup.bat, and EXE-based entry points) are referenced throughout, and PowerShell is mentioned as the primary tool for service creation. There is no explicit mention of Linux equivalents, nor are Linux-specific examples or guidance provided. However, the XML manifest format itself is cross-platform, and the examples are not strictly Windows-only.
Recommendations
  • Add explicit notes or examples for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) for SetupEntryPoint.
  • Clarify how user accounts and principals map to Linux (e.g., use of system users, groups, and service accounts).
  • Mention Linux tools (such as Azure CLI or Bash) for application/service creation, alongside PowerShell.
  • Where Windows-specific terms are used (e.g., NetworkService), provide Linux equivalents or note differences.
  • Ensure that references to executables (e.g., VotingWeb.exe) are accompanied by guidance for Linux (e.g., dotnet binaries or other formats).
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell-based deployment examples and references Windows command-line patterns (e.g., RDP, ping from C:\ prompt), without offering equivalent Azure CLI or Bash examples for Linux/macOS users. All deployment steps use PowerShell, and Windows-centric terminology and tools are mentioned first or exclusively. No Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps, especially for template deployment and resource creation.
  • Include Bash shell command examples for common tasks (e.g., ping, SSH access) instead of only Windows CMD/RDP.
  • Mention Linux/macOS-compatible tools and workflows (e.g., SSH instead of RDP, Azure CLI instead of PowerShell).
  • Clarify that Service Fabric clusters can be managed from Linux/macOS and provide links or sections for cross-platform guidance.
  • Where possible, show both Windows and Linux command-line examples side-by-side.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides conceptual information about Service Fabric hosting models, but operational examples and tooling references are heavily skewed toward Windows/PowerShell. The only CLI example is PowerShell, and all links to command references are for PowerShell modules. There are no Linux/macOS CLI examples (e.g., Azure CLI, Bash), nor are Linux-native tools or patterns mentioned. This creates friction for Linux/macOS users who may need to perform equivalent operations.
Recommendations
  • Add Azure CLI examples for creating services with ServicePackageActivationMode, especially for Linux/macOS users.
  • Include Bash or shell script examples where applicable.
  • Reference cross-platform tools and APIs (such as Azure CLI or REST API) alongside PowerShell, not just as secondary mentions.
  • Clarify which operations can be performed from Linux/macOS and provide guidance or links for those users.
  • Consider reordering examples so that cross-platform approaches are shown first or equally with Windows/PowerShell.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric container application manifest examples demonstrates a notable Windows bias. The examples and explanations are based on the 'Windows Server 2016 Container Sample', and Windows-specific tools and patterns (such as 'winver' for OS build detection and Windows file paths like 'c:\VolumeTest\Data') are referenced exclusively or before Linux equivalents. There is no mention of Linux-specific patterns, file paths, or commands, nor are Linux-based container samples or manifest examples provided. While some features (like certificate handling) mention both Windows and Linux outcomes, the overall guidance and examples are Windows-centric.
Recommendations
  • Include Linux-based container manifest examples, such as referencing the Linux sample repo or showing Linux file paths (e.g., '/mnt/data').
  • When describing OS build detection, mention Linux equivalents (e.g., 'cat /etc/os-release' or 'uname -r') alongside 'winver'.
  • Provide guidance or notes for Linux users where behaviors or configuration differ (e.g., volume mounting, certificate formats, isolation modes).
  • Balance examples and explanations so that Linux and Windows users can both follow along and see relevant patterns.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows (HTTP.sys) and cross-platform (Kestrel) options for hosting ASP.NET Core services in Azure Service Fabric. However, Windows-specific tools and patterns (such as HTTP.sys, Windows HTTP Server API, netsh) are discussed in detail and often before their Linux equivalents. HTTP.sys is clearly marked as Windows-only, but the documentation sometimes presents Windows-centric approaches first and references Windows tools without mentioning Linux alternatives. PowerShell or Windows command-line tools are referenced for endpoint configuration, but Linux equivalents (such as firewall or port management) are not discussed.
Recommendations
  • Ensure Linux parity by providing explicit Linux/macOS guidance for endpoint configuration, port management, and firewall setup.
  • When referencing Windows tools (e.g., netsh), mention that Linux users do not need to perform these steps, or provide Linux/macOS alternatives where relevant.
  • Present cross-platform options (Kestrel) before Windows-only options (HTTP.sys) to reinforce Linux support.
  • Clarify any OS-specific limitations or requirements in each section, especially when discussing configuration or deployment steps.
  • Add troubleshooting and deployment notes for Linux/macOS Service Fabric clusters where applicable.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page for 'Replica soft delete for enhanced data protection in Service Fabric' primarily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and command references exclusively in PowerShell syntax. There is no mention of Linux or cross-platform equivalents, nor are CLI or REST API examples provided. The documentation assumes familiarity with Windows tooling and does not address how Linux/macOS users can perform equivalent operations or whether these APIs are accessible via other means.
Recommendations
  • Add examples using Azure CLI or REST API if available, to demonstrate cross-platform usage.
  • Clarify whether the PowerShell APIs are supported on Linux/macOS (via PowerShell Core), and provide guidance for those environments.
  • Mention or link to FabricClient API usage in non-Windows environments, including sample code or commands.
  • Explicitly state any platform limitations if the feature or APIs are Windows-only, to avoid confusion.
  • Provide parity in documentation by showing Linux/macOS workflows alongside Windows/PowerShell examples.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides detailed examples for reporting health in Azure Service Fabric using PowerShell, including command-line snippets and configuration, but does not offer equivalent examples for Linux/macOS environments. PowerShell is presented as the primary CLI method, with no mention of cross-platform alternatives (such as Bash, Azure CLI, or REST via curl). The REST API is mentioned but not demonstrated with practical, platform-neutral examples. This creates friction for Linux/macOS users, who may not have access to PowerShell or Windows-specific Service Fabric tools.
Recommendations
  • Add equivalent CLI examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Demonstrate REST API usage with curl or HTTPie, including sample requests and responses.
  • Clarify which PowerShell commands are available cross-platform (via PowerShell Core) and which are Windows-only.
  • Mention any Linux-native Service Fabric tools or SDKs, if available.
  • Reorder sections to present REST and platform-neutral methods before Windows/PowerShell-specific examples.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides explicit PowerShell instructions for using the Fault Analysis Service but does not mention or provide examples for Linux/macOS users (e.g., Bash, CLI, or REST API usage). It references the Service Fabric PowerShell module and SDK, which are Windows-centric tools, without discussing cross-platform alternatives.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI, Bash, or REST API to support Linux/macOS users.
  • Clarify whether the Fault Analysis Service APIs can be accessed from non-Windows environments, and provide guidance if so.
  • If PowerShell Core (cross-platform) is supported, mention this explicitly and provide installation instructions for Linux/macOS.
  • Link to or document any cross-platform SDKs or tools that can be used to interact with the Fault Analysis Service.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux, frequently references Windows tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-centric instructions for VHD creation and conversion. Linux-native alternatives for creating and converting VHDs are not mentioned or are referenced after Windows tools. This creates friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
  • Mention Linux/macOS alternatives for extracting and manipulating VHD files, such as using tar, qemu-img, or other open-source utilities.
  • Present Linux-native workflows before or alongside Windows/Hyper-V instructions, especially in sections where Windows tools are currently referenced first.
  • Clarify which steps are Windows-specific and provide equivalent Linux/macOS guidance where possible.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation is focused on Linux VMs and provides extensive Azure CLI and PowerShell examples for managing Run Commands. However, PowerShell examples are given equal or greater prominence than Azure CLI, despite PowerShell being a Windows-centric tool. Several notes and examples reference Windows-specific tools (e.g., New-AzStorageBlobSASToken, PowerShell script URIs, Windows parameter handling), and in some cases, Windows terminology or patterns are described before their Linux equivalents. REST API and ARM template examples use PowerShell script syntax (Write-Host, .ps1) even in Linux contexts, and some explanations default to Windows behaviors before clarifying Linux differences.
Recommendations
  • Prioritize Azure CLI examples and explanations, as CLI is more native to Linux environments.
  • Where PowerShell is used, clarify its cross-platform support and provide Bash or shell script alternatives.
  • In REST and ARM template examples, use Linux shell script syntax (e.g., 'echo Hello World!' or '.sh' files) instead of PowerShell (.ps1) for Linux VM scenarios.
  • When discussing parameter handling, describe Linux behaviors first, then Windows, or clearly separate the two.
  • Reduce references to Windows-specific tools (e.g., New-AzStorageBlobSASToken) or provide Linux-native alternatives (such as Azure CLI commands for generating SAS tokens).
  • Ensure all examples and notes are tailored for Linux users, especially in sections where Windows terminology or tools are used.
GitHub Create Pull Request
Virtual Machines Create and upload a Red Hat Enterprise Linux VHD for use in Azure ...les/virtual-machines/linux/redhat-create-upload-vhd.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides step-by-step instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, throughout the guide, Windows-centric tools and workflows (notably Hyper-V Manager) are consistently presented first and in greater detail. References to Windows tools (e.g., Hyper-V Manager, PowerShell convert-vhd cmdlet) appear before Linux equivalents, and the VM creation workflow often assumes Hyper-V as the starting point, even for Linux VMs. Linux-native hypervisors (KVM, VMware) are covered, but their sections are secondary and sometimes reference steps from the Hyper-V workflow, reinforcing Windows as the default environment.
Recommendations
  • Reorder sections so Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, reflecting the primary audience for RHEL.
  • Provide Linux-native disk conversion instructions (e.g., qemu-img) before Windows/Hyper-V tools.
  • Avoid referencing Hyper-V Manager as the default VM creation tool for Linux VMs; instead, highlight virt-manager, virsh, or VMware Workstation/ESXi.
  • Clarify that PowerShell and Hyper-V tools are optional for users on Windows, and provide equivalent Linux/macOS commands wherever possible.
  • Ensure that all steps referenced from Hyper-V sections are fully explained in Linux-native hypervisor sections, rather than requiring cross-referencing.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux coverage for Azure Compute Gallery, but there is a notable Windows bias in several areas. PowerShell examples and references are frequent and often appear before or alongside CLI examples, with some links and examples specifically referencing Windows workflows (e.g., Sysprep, Windows VHD upload). Windows tools and terminology (such as Sysprep, PowerShell, Windows-specific upload instructions) are mentioned more prominently or before Linux equivalents. While Linux is supported and referenced, the documentation tends to default to Windows-first patterns and tools.
Recommendations
  • Ensure Linux CLI examples are presented before or equally alongside PowerShell examples.
  • Provide explicit Bash/Linux shell examples for all PowerShell commands.
  • Where Windows tools (e.g., Sysprep) are mentioned, ensure Linux equivalents (e.g., waagent) are described with equal prominence and detail.
  • Add links to Linux-specific workflows and troubleshooting guides where Windows-specific links are provided.
  • Review FAQ and scenario sections to ensure Linux scenarios are described with the same depth as Windows scenarios.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides multiple PowerShell examples for resizing VMs, including detailed scripts for both standalone VMs and VMs in availability sets. PowerShell is a Windows-centric tool, and its examples are more extensive and appear before Azure CLI examples. The Terraform section references a Windows VM quickstart and highlights Windows-specific code. While Azure CLI examples are present and cross-platform, the prominence and depth of PowerShell content, along with references to Windows tools and examples, indicate a Windows-first bias. Linux-specific examples or parity in scripting depth are missing.
Recommendations
  • Expand CLI examples to match the depth and scenarios covered in PowerShell (e.g., availability sets, error handling).
  • Add explicit Bash shell examples for Linux users, including how to run Azure CLI commands in Bash.
  • Provide Terraform examples for azurerm_linux_virtual_machine alongside Windows examples.
  • Ensure that Linux VM scenarios are referenced equally in code samples and explanations.
  • Consider reordering sections so that cross-platform tools (Azure CLI, Terraform) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Linux and Windows examples in CLI and REST sections, but PowerShell sections are heavily Windows-centric, with all PowerShell VM creation examples defaulting to Windows VMs (using Set-AzVMOperatingSystem -Windows). Windows-specific constructs (e.g., RDP port, Windows credential prompts) are used in PowerShell examples, and Linux VM creation in PowerShell is not shown. In several places, Windows terminology and tools (PowerShell, Windows credential prompts) are presented before or instead of Linux equivalents. However, CLI and REST examples are generally neutral or Linux-first.
Recommendations
  • Add PowerShell examples for creating Linux VMs (using Set-AzVMOperatingSystem -Linux) alongside Windows examples.
  • Clarify in PowerShell sections that both Linux and Windows VMs can be created, and provide parameter variations for Linux.
  • Where possible, avoid defaulting to Windows-specific constructs (e.g., RDP port, Windows credential prompts) in generic VM creation examples.
  • Ensure parity in example coverage for both Linux and Windows across all scripting tabs (CLI, PowerShell, REST).
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides parity for both Linux and Windows in most areas, especially in Azure CLI and ARM template examples. However, there is a notable bias in the PowerShell sections, where only Windows-based examples are provided (e.g., using Windows images, Windows-specific parameters, and RDP security rules). Additionally, in some PowerShell code, the Windows scenario is shown first or exclusively, and Windows-centric tools and patterns (like RDP port rules) are used without Linux equivalents. The overall structure tends to present Windows/PowerShell before Linux in some places.
Recommendations
  • Add PowerShell examples for Linux VMs, including using Linux images and Linux-specific configuration (e.g., SSH port rules instead of RDP).
  • Where PowerShell is shown, provide both Windows and Linux variants, or clearly indicate which OS the example applies to.
  • In PowerShell network security group examples, include SSH (port 22) rules for Linux, not just RDP (port 3389) for Windows.
  • When listing deployment methods or examples, alternate the order or present Linux and Windows equally, rather than defaulting to Windows/PowerShell first.
  • Review all code snippets and ensure that Linux users can follow along without needing to translate Windows-specific steps.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell) are listed before Linux equivalents (Eclipse, Yeoman). There are no exclusive Windows examples or tools, and Linux parity is generally acknowledged.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Add links to Linux quickstarts and documentation alongside Windows quickstarts.
  • Ensure that example workflows and tool references are balanced between Windows and Linux.
  • Consider linking to the Linux development guide in the 'Next steps' section.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias in some sections where Windows-specific tools (IIS, Mirantis Container Runtime) and Windows scenarios (IIS lift and shift) are mentioned before or more prominently than Linux equivalents. Windows container runtimes are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) are described in depth, while Linux scenarios are less emphasized.
Recommendations
  • Add more Linux-specific scenarios (e.g., Apache/Nginx lift and shift, common Linux workloads) alongside Windows scenarios.
  • Provide parity in listing container runtimes for Linux (e.g., mention containerd, Podman if supported) as is done for Windows.
  • Ensure Linux examples and tutorials are referenced equally and not only after Windows examples.
  • Clarify when features or scenarios are Windows-only to avoid confusion.
  • Consider alternating the order of Linux and Windows examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in greater detail, which may give the impression of a Windows-first bias. The CLI examples are present and sufficient for Linux/macOS users, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
  • Present cross-platform CLI (sfctl) examples before PowerShell examples to emphasize Linux/macOS parity.
  • Explicitly note that sfctl works on all platforms and is recommended for non-Windows users.
  • Balance the level of detail and explanation between PowerShell and CLI sections.
  • Consider adding a short note at the top of the deployment section clarifying that both Windows (PowerShell) and cross-platform (sfctl) options are available.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides example commands for Azure CLI, Azure PowerShell, and ARM templates. While the Azure CLI and ARM templates are cross-platform, the PowerShell examples are Windows-centric and are presented with equal prominence as CLI examples. The ARM template section references both Linux and Windows getting started articles, but does not provide explicit Linux-specific examples or highlight Linux workflows. In some sections, Windows tooling (PowerShell) is mentioned before Linux-friendly alternatives (CLI), and there is no explicit parity check for Linux/macOS users in PowerShell sections.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add explicit Linux/macOS notes or examples where PowerShell is referenced, clarifying CLI as the preferred method for those platforms.
  • Where ARM templates are shown, provide a brief Linux-specific deployment example (e.g., using Azure CLI or Bicep on Linux).
  • Consider adding a table or section summarizing platform compatibility for each method.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all command-line examples, but consistently presents PowerShell examples immediately after CLI and before ARM templates. PowerShell is a Windows-centric tool, and its inclusion (with detailed examples) may create friction for Linux/macOS users who do not use PowerShell. However, Azure CLI is cross-platform and all tasks can be completed using it, so Linux/macOS users are not blocked. The documentation does not reference Windows-only tools or patterns, nor does it omit Linux/macOS equivalents.
Recommendations
  • Consider explicitly stating that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add brief notes clarifying that PowerShell examples are primarily for Windows users, while Azure CLI works on all platforms.
  • If possible, show Azure CLI examples first, or clarify that the order is not indicative of platform preference.
  • Ensure screenshots and UI instructions are not Windows-specific (they are currently Azure Portal, which is platform-neutral).
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation covers both Windows and Linux VM deployment methods for the Qualys Cloud Agent and provides parallel links for each OS where relevant. However, in several sections, Windows examples or links are listed before Linux equivalents, which may subtly reinforce a Windows-first perspective.
Recommendations
  • Alternate the order of Windows and Linux examples/links in each section, or present them in alphabetical order (Linux, then Windows) for parity.
  • Explicitly state that all deployment methods are supported on both Windows and Linux at the beginning of the relevant sections.
  • Where possible, provide combined instructions or tables that show both Windows and Linux commands side-by-side.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions, and no Linux container image examples or references are provided. The configuration examples and descriptions focus on Windows images and do not demonstrate parity for Linux-based containers, nor do they clarify whether the cleanup features apply equally to Linux containers.
Recommendations
  • Add examples and references to Linux container images (e.g., 'docker.io/library/alpine', 'ubuntu') in configuration and explanations.
  • Clarify whether the image cleanup features apply to both Windows and Linux containers, and note any differences.
  • Include sample settings or scenarios for Linux container images in the 'ContainerImagesToSkip' parameter.
  • Explicitly mention Linux support in the introductory and settings sections if applicable.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral manner, but the Management subsystem section specifically mentions PowerShell cmdlets as a primary management interface, without referencing Linux/macOS equivalents (such as Azure CLI or REST APIs). Windows security is also mentioned alongside X509 certificates in the Transport subsystem, but not Linux authentication mechanisms. These examples and tool references are presented before any cross-platform alternatives, creating a mild Windows bias.
Recommendations
  • Mention Azure CLI and REST API as cross-platform management options alongside PowerShell cmdlets.
  • Clarify that Service Fabric management can be performed from Linux/macOS using CLI or API tools.
  • When discussing security, explicitly note that X509 certificates are supported on all platforms, and clarify Windows security is an additional option for Windows environments.
  • Provide links or references to Linux/macOS management documentation or examples.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page presents Service Fabric cluster settings in a platform-neutral way, but there are subtle signs of Windows bias. Windows terminology (e.g., 'MY' certificate store, 'LocalMachine' store location, NTLM authentication) is used throughout, and Windows-specific defaults are sometimes mentioned before Linux equivalents. Some parameters reference Windows tools or concepts (e.g., certificate store names, NTLM, Windows Defender Firewall) without always clarifying Linux alternatives or differences. However, Linux-specific settings are present, and the page is not exclusively Windows-focused.
Recommendations
  • Where Windows-specific terms (e.g., 'MY', 'LocalMachine', NTLM') are used, clarify Linux equivalents or note differences.
  • Add explicit Linux/macOS guidance for certificate management, authentication, and firewall configuration where Windows tools are referenced.
  • When listing parameters with platform-specific defaults, present Linux and Windows values equally (e.g., 'default is FALSE (Linux) and TRUE (Windows)').
  • Link to Linux-specific documentation or examples for relevant settings.
  • Review guidance for any implicit Windows assumptions and ensure Linux parity in explanations.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric upgrade tutorials (Visual Studio and PowerShell) are mentioned before any Linux or cross-platform alternatives. PowerShell is a Windows-first tool, and no Linux CLI or cross-platform upgrade guidance is referenced.
Recommendations
  • Add links or references to Linux/macOS upgrade workflows, such as using Azure CLI or Service Fabric CLI (sfctl).
  • Explicitly mention cross-platform tools and approaches for application upgrades, ensuring parity with Windows examples.
  • Reorder 'Next steps' to avoid listing Windows tools first, or group platform-specific guidance together.
  • Clarify that PowerShell and Visual Studio are Windows-centric, and provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page is generally cross-platform and describes Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows-specific tools and patterns (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in some sections, and Windows terminology is used before Linux equivalents. Linux support is acknowledged, but Windows is often the default or primary context.
Recommendations
  • When describing node infrastructure, clarify that Linux nodes use different service management mechanisms (e.g., systemd) instead of Windows services, and mention relevant Linux processes/tools.
  • When referencing executable files, note that Linux uses ELF binaries and not EXE/DLL files, and provide examples or terminology for Linux equivalents.
  • In sections referencing auto-start Windows services (e.g., FabricHost.exe), add a note about how this works on Linux (e.g., systemd units, service scripts).
  • Ensure that examples and descriptions are equally balanced between Windows and Linux, or explicitly state differences where relevant.
  • Consider providing Linux-first or Linux-parallel examples where possible, especially in technical sections.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ minor_windows_tools
Summary
The documentation references both Azure CLI and Azure PowerShell for creating and managing Virtual Machine Scale Sets, but Azure PowerShell (a Windows-centric tool) is mentioned equally alongside Azure CLI. Windows-specific scenarios (activation, updates) are listed before Linux equivalents in the networking section. However, Linux is acknowledged (e.g., package managers), and most examples use Azure CLI, which is cross-platform. No critical migration steps are Windows-only, but minor ordering and tool parity issues exist.
Recommendations
  • Ensure Linux-specific migration scenarios (such as package manager access) are given equal prominence and detail as Windows scenarios.
  • Where Azure PowerShell is referenced, provide equivalent Bash/Azure CLI examples first, or clarify cross-platform support.
  • Explicitly mention that Azure CLI is fully cross-platform and recommend it as the default for non-Windows users.
  • Consider adding links or examples for Linux-specific troubleshooting (e.g., outbound connectivity for apt/yum).
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. In the 'Configure rolling upgrades with MaxSurge' section, the PowerShell example is presented immediately after the CLI example, and both are given equal prominence. However, the CLI example uses Azure CLI, which is cross-platform, and the PowerShell example is Windows-centric. There are no Linux-specific tools or shell examples (e.g., Bash scripting), but the Azure CLI example is sufficient for Linux/macOS users. The ordering of examples (CLI first, then PowerShell) is appropriate, but the presence of PowerShell may create minor friction for Linux/macOS users if they are unclear about which tools to use.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Explicitly state that PowerShell examples are for Windows users, and Azure CLI is suitable for Linux/macOS.
  • Consider adding a Bash shell example for invoking Azure CLI commands, or note that Azure CLI commands can be run in Bash or other shells.
  • Ensure that all screenshots and instructions in the Portal section are platform-neutral.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides a conceptual overview of orchestration modes for Azure Virtual Machine Scale Sets and is largely platform-neutral. However, there is a minor bias in the 'Managed Identity' row of the comparison table, where the link for configuring User Assigned Identity points to a Windows VMSS-specific guide. Additionally, the Azure Site Recovery feature is noted as supported 'via PowerShell' for Flexible orchestration, which may imply a Windows-centric tool, though PowerShell is cross-platform. All examples and commands use Azure CLI or Resource Graph, which are platform-agnostic. No critical sections are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Replace or supplement the User Assigned Identity link with a platform-neutral or Linux-specific guide, or clarify that the process is similar for Linux VMSS.
  • Clarify that Azure Site Recovery via PowerShell is supported on Linux/macOS as well, or provide Bash/Azure CLI alternatives if available.
  • Continue to use Azure CLI and Resource Graph for examples, and ensure any links or references are not Windows-specific unless the feature is Windows-only.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific guidance. However, in deployment and troubleshooting sections, PowerShell examples are presented first and in greater detail than Azure CLI equivalents, despite Linux users typically favoring Azure CLI or shell scripting. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI, which may create friction for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples in deployment and troubleshooting sections, as CLI is more relevant for Linux users.
  • Expand Azure CLI troubleshooting guidance to match the detail provided for PowerShell.
  • Clarify that PowerShell examples are primarily for Windows users, and highlight Azure CLI as the preferred method for Linux environments.
  • Consider adding Bash scripting examples for common operations, if relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) give more detailed PowerShell usage. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or at least side-by-side, to avoid implicit Windows-first bias.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and managing resources.
  • Add explicit notes clarifying that Azure CLI commands work cross-platform (Linux, macOS, Windows).
  • Where possible, include Bash shell script snippets for complex CLI operations.
  • Review for any PowerShell-only guidance and provide CLI alternatives.
GitHub Create Pull Request
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but there is evidence of Windows bias. PowerShell examples and Windows-specific extension types (ApplicationHealthWindows) are frequently shown alongside or before Linux equivalents. In several code samples, Windows tools and patterns (PowerShell, Add-AzVmssExtension, ApplicationHealthWindows) are mentioned, sometimes before Linux tools. The CLI and REST examples are neutral, but PowerShell is given equal or greater prominence than Bash, and Windows extension types are referenced in multiple places. The documentation does not omit Linux examples, but Windows-specific terminology and tools are often foregrounded.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with Linux shown first in some sections.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows, and provide explicit Linux-focused extension install examples (e.g., az vmss extension set with ApplicationHealthLinux).
  • Add explicit notes or tables summarizing which commands and extension types are for Linux vs Windows, to avoid confusion.
  • Where PowerShell is used, ensure Bash/Linux alternatives are always present and equally detailed.
  • Review ordering of examples and terminology to avoid defaulting to Windows-first language.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI (bash-style) and Azure PowerShell examples for creating instant access snapshots, but PowerShell is presented as a primary example alongside CLI. The CLI example uses bash syntax, which is Linux/macOS-friendly, but PowerShell is listed second and is Windows-centric. There are no Linux-specific tools or commands (such as direct REST API calls or references to Linux-native scripting), but the CLI coverage is sufficient for Linux/macOS users. The documentation avoids Windows-only tools and does not mention Windows patterns or tools before Linux equivalents, but PowerShell is still prominent.
Recommendations
  • Ensure Azure CLI examples are always listed first, as they are cross-platform.
  • Consider adding explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Optionally, provide REST API or Python SDK examples for advanced Linux/macOS users.
  • Clarify that PowerShell is optional and primarily for Windows users.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major extension management tasks, but consistently lists PowerShell examples immediately after CLI, and sometimes with more detailed output. There is a slight 'Windows-first' ordering in some sections, and PowerShell is given parity with CLI despite Linux users overwhelmingly preferring CLI. No Linux-specific tools (e.g., Bash scripts, cloud-init) are referenced for extension management, and troubleshooting/log paths are Linux-appropriate. No critical Windows-only tools or patterns are present, and all examples are valid for Linux VMs.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in all sections, as CLI is the primary cross-platform tool for Linux users.
  • Explicitly state that Azure PowerShell is available on Linux, but CLI is recommended for Linux VM management.
  • Add a short Bash script example for extension management using the Azure CLI to reinforce Linux-native workflows.
  • Where possible, reference Linux-native automation tools (e.g., cloud-init, Bash scripting) in the context of VM extension management.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a subtle Windows bias in some areas. PowerShell examples are shown with Windows as the default OS type, and Windows terminology (Sysprep) is mentioned before Linux equivalents. In the PowerShell section, Windows is the primary example, while Linux is only referenced as an alternative. However, CLI and REST examples default to Linux, and Linux-specific guidance is linked early in the 'Before you begin' section. Overall, Linux users can complete all tasks, but Windows is sometimes prioritized in examples and terminology.
Recommendations
  • In PowerShell examples, show Linux as the default OS type or provide parallel Linux and Windows examples.
  • When referencing OS-specific steps, mention Linux and Windows equally, rather than defaulting to Windows terminology.
  • Ensure that CLI and PowerShell sections consistently show both Linux and Windows examples, or alternate which OS is shown first.
  • Add explicit notes clarifying parity between Linux and Windows where relevant.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation provides both Windows and Linux examples and covers both OSes in detail. However, there are several areas where Windows tools and PowerShell are mentioned first or exclusively, such as using PowerShell for checksum generation, validator examples, and generalization commands. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less prominent. Some sections use Windows tools or patterns before Linux equivalents, and PowerShell is often referenced for tasks that could be done with cross-platform tools.
Recommendations
  • When describing tasks like generating SHA256 checksums, mention Linux/macOS commands (e.g., 'sha256sum') alongside or before PowerShell equivalents.
  • Ensure Linux validator examples are as prominent and detailed as Windows examples, including shell script usage and inline commands.
  • Where possible, use cross-platform tools (e.g., Azure CLI) in examples before platform-specific tools (e.g., PowerShell).
  • For sections like generalization, provide Linux command examples with equal detail and visibility as Windows Sysprep examples.
  • Consider alternating the order of Windows and Linux examples to avoid always presenting Windows first.
  • Clarify when a feature is Windows-only (e.g., WindowsRestart customizer), and provide Linux alternatives or explicitly state the lack thereof.
GitHub Create Pull Request
Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of a PowerShell section may create friction for Linux/macOS users, as PowerShell is not natively installed on those platforms. No Linux-specific tools or commands (such as Bash scripting or references to native Linux utilities) are mentioned, but the Azure CLI is cross-platform and sufficient for Linux users.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Optionally, add a note that PowerShell is available on Linux/macOS, but Azure CLI is more commonly used.
  • Ensure that CLI examples are always shown first and are comprehensive.
  • Consider adding Bash script examples for automation, if relevant.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before fully explaining Linux-specific mechanisms. No Windows/PowerShell examples are given except for a single PowerShell command for base64 encoding cloud-init, which is contextually relevant for Azure users but lacks a Linux equivalent. All technical guidance, tools, and examples are Linux-centric.
Recommendations
  • Move Windows Server 2016 discussion to a background or context section, or clarify its relevance to Linux VM time sync.
  • Provide a Linux shell equivalent for the PowerShell base64 encoding example (e.g., 'base64 cloud-config.txt') for parity.
  • Ensure that Linux-specific guidance is presented before or independently of Windows references.
  • Consider minimizing Windows documentation links unless directly relevant to Linux VM time sync.
GitHub Create Pull Request
Virtual Machines Upgrade Gen1 VMs to Trusted launch ...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for upgrading Gen1 VMs to Trusted launch. However, Windows-specific tools (MBR2GPT.exe, Defrag, PowerShell) are described in detail and appear first, with Linux instructions following. Windows disk conversion and troubleshooting steps are more extensive, while Linux disk conversion is not covered (because most Marketplace Linux images already meet requirements). Azure CLI and ARM template examples are cross-platform, but PowerShell is shown first and used for template deployment. Overall, Linux users can complete the task, but Windows tools and patterns are emphasized.
Recommendations
  • Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
  • For ARM template deployment, provide Azure CLI examples alongside PowerShell.
  • Expand Linux troubleshooting guidance for disk layout issues, even if rare, to match Windows detail.
  • Clarify that Azure CLI and ARM templates are fully cross-platform and recommend them for Linux users.
  • Consider adding links or references to Linux disk conversion tools (e.g., gdisk, parted) for custom images.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides parity for both Linux and Windows VMs, with explicit statements that the feature applies to both. CLI and ARM template instructions are platform-neutral. However, PowerShell instructions are given equal prominence as CLI, and PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there). Additionally, in some sections (e.g., Portal and PowerShell tabs), Windows terminology (RDP) is mentioned before Linux (SSH), and PowerShell is listed before ARM template, which may subtly prioritize Windows patterns.
Recommendations
  • Clarify that PowerShell instructions are applicable on both Windows and Linux, or provide Bash/Cloud Shell alternatives where relevant.
  • Consider listing CLI instructions before PowerShell, as CLI is more universally used across platforms.
  • When mentioning remote access, list SSH (Linux) and RDP (Windows) together, or alternate their order to avoid subtle Windows-first bias.
  • Add explicit notes or links for Linux users regarding PowerShell usage, or suggest Azure Cloud Shell as a cross-platform option.
  • Ensure screenshots and terminology are neutral or include both Linux and Windows examples where possible.
GitHub Create Pull Request
Virtual Machines FAQ for Trusted Launch ...b/main/articles/virtual-machines/trusted-launch-faq.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most operations, but PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI. In some cases, Windows-specific image examples are shown first, and PowerShell is given equal prominence to CLI, which may create a subtle Windows-first impression. However, Linux-specific instructions and tools (such as SBInfo for Secure Boot validation) are included where relevant, and Linux images are referenced in CLI/PowerShell commands. There are no critical omissions for Linux users.
Recommendations
  • Where possible, lead with Azure CLI examples (which are cross-platform) before PowerShell, especially in sections not inherently Windows-specific.
  • When demonstrating image queries, alternate or balance the use of Windows and Linux images as examples.
  • Continue to provide explicit Linux troubleshooting and validation steps, as done with the SBInfo tool.
  • Consider adding Bash scripting examples for common automation scenarios, where appropriate.
  • Clarify in introductory sections that both Linux and Windows are fully supported, and that all examples apply to both unless otherwise noted.
GitHub Create Pull Request
Virtual Machines Trusted Launch for Azure VMs .../blob/main/articles/virtual-machines/trusted-launch.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation covers Trusted Launch for both Linux and Windows VMs, but there are several subtle signs of Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are presented first in example lists. Windows-specific tools and features (like Windows Defender Credential Guard, HVCI, and Secure Boot references) are discussed in detail, with less depth for Linux equivalents. Some links and explanations (e.g., Secure Boot, vTPM, VBS) reference Windows documentation or features before Linux, and Windows driver installation is described as 'not requiring extra steps', while Linux installation is described as requiring workarounds.
Recommendations
  • Provide Linux-focused deployment examples alongside or before Windows examples, especially in sections listing ARM templates.
  • Expand explanations of Linux equivalents for security features (e.g., Secure Boot, attestation, kernel module validation) to match the depth given to Windows features.
  • Balance references to Windows tools with Linux tools (e.g., mention Linux attestation and boot integrity solutions).
  • Ensure that Linux-specific guidance (such as driver installation steps) is as clear and prominent as Windows guidance.
  • Where possible, link to Linux documentation or community resources for features like Secure Boot and vTPM.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. However, the PowerShell section is presented immediately after the CLI section, and the PowerShell example is detailed and uses Windows-centric terminology (e.g., PowerShell SDK objects). The CLI example uses a Linux image (Ubuntu2204), but there is no explicit Linux/macOS shell example or mention of Bash scripting. The documentation refers to SQL Server as a licensing example, which is Windows-centric, but this is not flagged as bias since SQL Server is also available on Linux. Overall, the documentation is slightly Windows-biased in its ordering and tooling focus, but Linux users can complete all tasks using the CLI and ARM templates.
Recommendations
  • Add explicit Bash or Linux/macOS shell examples for Azure CLI usage, clarifying that CLI commands work cross-platform.
  • Consider mentioning that PowerShell is available on Linux/macOS, or provide a Bash equivalent for any PowerShell-specific steps.
  • Ensure that CLI examples are shown first or equally with PowerShell, and clarify that both methods are supported on all OSes.
  • Add a note that ARM templates and Azure CLI are fully cross-platform and suitable for Linux/macOS users.
GitHub Create Pull Request