← Back to Dashboard
268
Pages Scanned
88
Pages Flagged
268
Changed Pages
32.8%
% Pages Flagged

Scan Information

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

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 268

Files Completed: 268

Problematic Pages

89 issues found
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
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily focused on Windows tooling, specifically Visual Studio and PowerShell, for configuring and upgrading Service Fabric applications. All examples and workflows are centered around Visual Studio (a Windows-only IDE) and PowerShell (with no mention of cross-platform alternatives or Linux/macOS equivalents). There are no examples or guidance for Linux/macOS users, nor are CLI or REST API alternatives discussed.
Recommendations
  • Add instructions and examples for upgrading Service Fabric applications using Azure CLI or REST API, which are cross-platform.
  • Include guidance for Linux/macOS users, such as using Service Fabric SDK tools or scripts available for those platforms.
  • Mention and link to documentation for non-Windows development environments (e.g., VS Code, CLI workflows) where applicable.
  • Clarify which steps are Windows-only and provide parity or alternatives for other OSes where possible.
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 provides management guidance for Service Fabric Explorer and ARM-managed clusters. It consistently recommends Az PowerShell cmdlets for resource operations, mentioning them before or instead of Azure CLI equivalents. While Azure CLI is referenced once for deleting applications, most examples and links are PowerShell-focused, which may create friction for Linux/macOS users who prefer or require CLI tools.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell cmdlet examples, especially for provisioning and deleting resources.
  • Mention both PowerShell and CLI options equally in best practices sections.
  • Clarify that Az PowerShell cmdlets are cross-platform, but highlight CLI usage for Linux/macOS users.
  • Add explicit examples for ARM template deployment using CLI tools.
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 validating manifest XML files, specifically recommending opening the schema file in Visual Studio using a Windows file path. The only explicit tool and workflow mentioned for schema validation is Windows/Visual Studio-centric, with no mention of cross-platform alternatives. Additionally, the PowerShell module is referenced before any Linux or cross-platform equivalents for service creation.
Recommendations
  • Provide instructions or examples for validating manifest XML files using cross-platform tools (e.g., xmllint, VS Code with XML extensions, or other schema validation tools available on Linux/macOS).
  • When referencing the Service Fabric PowerShell module, also mention the Service Fabric CLI (sfctl) or Azure CLI as cross-platform alternatives for managing services.
  • Where file paths or tooling are given, clarify if the guidance is Windows-specific and offer Linux/macOS equivalents if available.
  • Consider adding a note that Service Fabric development is supported on both Windows and Linux, and link to platform-specific setup guides.
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 Azure Service Fabric networking, but there is a notable Windows bias. PowerShell and Windows-specific tools are referenced more frequently, and Windows examples or terminology often appear before Linux equivalents. Some explanations (e.g., client API usage, DevOps tasks) focus on PowerShell, and sample ARM templates link to Windows-specific resources. Linux is mentioned, but often as an afterthought or secondary option.
Recommendations
  • Provide Linux CLI (az CLI or bash) examples alongside PowerShell, especially for cluster management and networking tasks.
  • Reference Linux ARM template samples equally, not just Windows ones.
  • Clarify when instructions or port requirements differ for Linux clusters (e.g., ephemeral ports section).
  • Expand explanations of DevOps and client API usage to include Linux tooling (e.g., Azure CLI, REST, bash scripts).
  • Ensure Linux and Windows guidance appear together, or alternate which is presented first.
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 ⚠️ missing_linux_example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent CLI or Linux/macOS instructions. No Linux tools or cross-platform alternatives are mentioned, and the only command-line guidance is Windows-centric.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for bypassing Infrastructure Service, if available.
  • Clarify whether the PowerShell command can be run using Azure Cloud Shell (which supports PowerShell on Linux/macOS), or if it is strictly for Windows environments.
  • Mention any cross-platform tools or approaches for managing Service Fabric Infrastructure Service.
  • Explicitly state if certain operations are only supported via PowerShell, and suggest workarounds or alternatives for Linux/macOS users.
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 examples and links primarily 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 are referenced, PowerShell is emphasized in the best practices and example links, which may create friction for Linux/macOS users who prefer CLI or scripting tools native to their platforms.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell examples for all recommended actions (e.g., deleting NodeTypes, restarting/reimaging scale sets).
  • Mention Azure CLI before or equally with PowerShell in best practices to highlight cross-platform support.
  • Clarify that Azure PowerShell is available cross-platform, but also link to CLI documentation for parity.
  • Add sample commands for ARM/Bicep deployments and management where relevant.
  • Ensure that references to 'Node blade on the Azure portal' are supplemented with CLI/ARM/Bicep alternatives for automation scenarios.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation references PowerShell cmdlets and administrative APIs as the primary means for managing Service Fabric clusters, without mentioning Linux equivalents such as Azure CLI or REST API usage. The mention of 'Windows security' as a transport security option, while not inherently biased, is not balanced by mentioning Linux-compatible authentication mechanisms.
Recommendations
  • Include Azure CLI examples or references for cluster and application management tasks alongside PowerShell.
  • Clarify that management operations can also be performed using REST APIs or Azure CLI, which are cross-platform.
  • Mention Linux-compatible authentication mechanisms (e.g., X509 certificates) more prominently when discussing security.
  • Add a note or section highlighting cross-platform management options for Service Fabric clusters.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides general information about Azure Service Fabric node types and VM scale sets, but several sections and examples show a Windows bias. The JSON extension snippet uses a Windows-style data path (D:\\SvcFab) and certificate store references, with no Linux equivalent shown. The 'Next steps' section links to PowerShell scripts for Windows-centric tasks (RDP port range, admin username/password changes) without Linux/SSH alternatives. While the extension type 'ServiceFabricLinuxNode' is mentioned, practical Linux usage examples and guidance are missing.
Recommendations
  • Add Linux-specific examples for configuring Service Fabric nodes, including file paths and certificate stores.
  • Include guidance or links for Linux/macOS users on how to remotely connect to scale set instances (e.g., SSH instead of RDP).
  • Provide parity in 'Next steps' by including Linux/SSH-based instructions for changing admin credentials and port ranges.
  • Clarify where Windows-specific instructions apply and offer alternatives for Linux clusters.
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 a PowerShell-centric deployment guide as the next step. While .NET and REST options are mentioned, PowerShell is presented first and most prominently. There are no explicit Linux/macOS command-line examples (such as Bash or Azure CLI), nor is there mention of cross-platform tooling for cluster management.
Recommendations
  • Add examples using Azure CLI or Bash scripts for retrieving cluster manifests and deploying applications, to provide parity for Linux/macOS users.
  • Include links to cross-platform tools or documentation (e.g., Azure CLI, Service Fabric CLI) alongside PowerShell references.
  • Ensure that deployment and management instructions are not solely tied to Visual Studio or PowerShell, but also reference other supported environments.
  • Clarify which tools are cross-platform and which are Windows-only, to help users select appropriate options.
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 Service Fabric partition health, using Windows-style paths and commands (e.g., 'PS C:\Users\User > Get-ServiceFabricPartitionHealth'). No equivalent Linux or cross-platform CLI example is given. The example and command syntax are Windows-centric, and the documentation implicitly assumes Windows as the primary environment for management tasks.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS environments.
  • Mention cross-platform management tools and clarify which commands are available on Linux/macOS.
  • Provide guidance or links for Linux/macOS users to achieve similar tasks, such as querying partition health.
  • Consider showing both Windows and Linux examples side-by-side to improve parity.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page on upgrading Azure Service Fabric clusters exhibits mild Windows bias. While most upgrade concepts are platform-neutral, several sections reference Windows-specific tools (PowerShell) and Windows OS patching, with no explicit mention of Linux equivalents or examples. In particular, the 'Upgrading OS images for cluster nodes' section links only to Windows patching guidance, and throughout, PowerShell is mentioned before Azure CLI, with no Linux-specific guidance or examples.
Recommendations
  • Add explicit references and links to Linux patching/upgrading guidance for Service Fabric clusters, if supported.
  • Provide Linux-specific examples (e.g., using Bash or Azure CLI on Linux/macOS) alongside PowerShell examples.
  • Clarify whether Service Fabric cluster upgrade and management features are supported on Linux, and if so, include relevant instructions.
  • When mentioning tools, list Azure CLI before or alongside PowerShell, and note cross-platform compatibility.
  • If certain features (like Patch Orchestration Application) are Windows-only, explicitly state this to avoid confusion.
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 demonstrates mild Windows bias. Windows terminology (e.g., 'Administrators', 'NetworkService', 'Setup.bat', 'VotingWeb.exe') is used throughout, and references to running scripts or executables (such as .bat files) are Windows-centric. The only mention of tooling is the 'ServiceFabric PowerShell module', with no Linux CLI or cross-platform alternatives. User and group examples reference Windows system groups and accounts, and there is no explicit guidance for Linux deployments or examples using Linux conventions.
Recommendations
  • Add Linux-specific examples (e.g., using shell scripts like Setup.sh instead of Setup.bat, and referencing Linux user/group conventions).
  • Mention cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl) alongside PowerShell.
  • Clarify which elements or features are supported on Linux clusters and provide guidance for Linux users where applicable.
  • Where possible, use neutral terminology for user/group names and executable formats (e.g., .exe vs. .out or generic names).
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_first ⚠️ windows_tools
Summary
The documentation provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits Windows bias in several areas. PowerShell is the only scripting example given for certificate enrollment, and the Key Vault VM extension is discussed exclusively in its Windows variant, with explicit notes about Windows-specific behaviors (such as 'linkOnRenewal'). Windows terminology and tooling (certificate stores, ACLing, S-channel, etc.) are used throughout, and Linux equivalents are not mentioned or provided. The documentation assumes Windows as the default platform for VM extensions and certificate handling, with no guidance for Linux-based clusters or cross-platform scenarios.
Recommendations
  • Provide equivalent Linux examples for certificate enrollment and provisioning, such as using Azure CLI or Bash scripts.
  • Mention and document the Key Vault VM extension for Linux, including its schema and behavioral differences.
  • Clarify which steps, tools, and mechanisms are Windows-specific and which are cross-platform, especially regarding certificate stores and ACLing.
  • Add troubleshooting and FAQ entries relevant to Linux clusters.
  • Where PowerShell is used, offer Azure CLI or Bash alternatives for parity.
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 a thorough overview of X.509 certificate-based authentication in Service Fabric clusters, but exhibits Windows bias in several areas. Windows-specific terminology (e.g., certificate stores like LocalMachine\My), Windows API references (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting instructions (event logs, CAPI2 logging) are presented first or exclusively. Linux equivalents are mentioned briefly (e.g., /var/lib/sfcerts), but lack detailed guidance or parity in examples and troubleshooting steps.
Recommendations
  • Expand Linux-specific guidance for certificate storage, retrieval, and troubleshooting (e.g., provide detailed instructions for accessing Service Fabric logs and certificate stores on Linux).
  • Include Linux/macOS equivalents for Windows API references and tools (e.g., OpenSSL commands, Linux certificate validation methods, log locations).
  • Present examples for both Windows and Linux environments side-by-side, ensuring Linux examples are not omitted or relegated to parenthetical notes.
  • Clarify any differences in certificate handling between Windows and Linux Service Fabric nodes, especially for cluster upgrades and certificate rotation.
  • Add troubleshooting steps and error codes relevant to Linux/macOS, including how to diagnose certificate issues on non-Windows platforms.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides step-by-step instructions and code samples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI example provided, with no equivalent Bash, Azure CLI, or Linux/macOS shell instructions. The PowerShell examples are prominent and used for critical operations (add, remove, scale, configure placement properties), and are mentioned before or instead of cross-platform alternatives. This creates friction for Linux/macOS users, who must either use the Portal or ARM templates, but lack CLI parity.
Recommendations
  • Add Azure CLI examples for all PowerShell operations (add, remove, scale, configure placement properties, etc.), since Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
  • Where possible, include Bash shell or Azure CLI scripts alongside PowerShell, or clarify if certain operations are only possible via PowerShell.
  • Review the order of examples to avoid always presenting Windows/PowerShell first; consider alternating or grouping by platform.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.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 Initializer CodePackages in Service Fabric presents only Windows container examples, uses Windows-specific images (nanoserver), Windows paths (C:\), and Windows commands (cmd, echo, type, ping). There is no mention of Linux container support, nor are Linux examples or equivalents provided. The page assumes familiarity with Windows container creation and does not address Linux scenarios.
Recommendations
  • Add examples for Linux containers, using Linux-compatible images and commands.
  • Clarify whether Initializer CodePackages are supported for Linux containers in Service Fabric.
  • If supported, provide Linux path and volume mount examples alongside Windows examples.
  • Mention Linux container version compatibility and relevant documentation links.
  • If Initializer CodePackages are Windows-only, explicitly state this in the introduction.
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 covers monitoring Azure Service Fabric clusters on both Windows and Linux, but there is a noticeable Windows bias. Windows-specific tools (e.g., Event Log, Event Viewer, Diagnostics Agent) are mentioned first or in more detail, while Linux equivalents are referenced later or with less explanation. Some examples and tutorials focus on .NET applications, which are cross-platform, but the monitoring setup and event channels are described with Windows patterns first. Linux-specific instructions and tools are often referenced as 'different configuration' or linked out, rather than explained inline. The EventStore APIs are noted as Windows-only, but Linux alternatives are not clearly described. Overall, Linux users can complete the tasks, but may face friction due to less direct guidance.
Recommendations
  • Provide Linux-specific examples and instructions inline, not just as links.
  • When describing monitoring tools or event channels, present Windows and Linux approaches side-by-side.
  • Clarify Linux equivalents for Windows tools (e.g., Event Viewer vs. Syslog/LTTng) and provide sample commands or screenshots.
  • Expand Linux cluster monitoring tutorials to match the detail of Windows-focused tutorials.
  • Explicitly note when features are Windows-only and offer Linux alternatives or workarounds.
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_first ⚠️ missing_linux_example
Summary
The documentation frequently references PowerShell cmdlets for Service Fabric operations, often listing them before or alongside .NET API and REST methods. There is little to no mention of Linux-specific tools or CLI equivalents (such as sfctl or Azure CLI), and no explicit Linux/macOS usage examples. This creates friction for non-Windows users, as PowerShell is primarily a Windows-centric tool and Service Fabric supports Linux clusters as well.
Recommendations
  • Add examples using sfctl (Service Fabric CLI) and Azure CLI for each operation, especially for deploy, upgrade, remove, and maintenance tasks.
  • Explicitly mention Linux/macOS support and provide guidance for those environments.
  • Where PowerShell is referenced, also provide the equivalent sfctl or REST command, and clarify which tools are cross-platform.
  • Consider reordering examples so that cross-platform tools (sfctl, REST, Azure CLI) are listed before or alongside PowerShell.
  • Add a section or note about managing Service Fabric applications on Linux clusters, including any differences or limitations.
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 primarily discusses deploying custom Windows images in Service Fabric Managed Clusters, with Windows terminology and PowerShell examples featured. While there is a brief reference to Linux custom image creation, the main workflow, examples, and tooling are Windows-centric, and PowerShell is used for role assignment without a Linux CLI equivalent. Linux users may need to infer or adapt steps.
Recommendations
  • Provide explicit Linux/CLI examples for role assignment (e.g., using Azure CLI instead of only PowerShell).
  • Clarify that custom images can be Linux-based, and include sample ARM template snippets for Linux images.
  • Balance references to Windows and Linux documentation and tools throughout the page.
  • Add a section or note for Linux users outlining any differences or considerations when deploying Linux custom images.
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 presents RunToCompletion semantics for Service Fabric containers and guest executables, but all code examples and walkthroughs are Windows-centric. Windows container images (nanoserver), Windows-specific commands (cmd, echo, ping, set), and PowerShell tools are used exclusively. No Linux container examples, Linux shell commands, or Linux querying methods are provided, and Windows terminology appears first throughout.
Recommendations
  • Add equivalent Linux container examples (e.g., using Ubuntu or Alpine images) with Linux shell commands.
  • Provide sample ServiceManifest.xml and ApplicationManifest.xml for Linux containers.
  • Include instructions for querying deployment status using Linux tools (e.g., Azure CLI, Bash scripts) or cross-platform methods.
  • Clarify which aspects are Windows-only and which are cross-platform, to help Linux/macOS users understand applicability.
  • Consider presenting Linux and Windows examples side-by-side for parity.
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 provides some Windows-specific examples and references (e.g., Active Directory, gMSA, BitLocker, PowerShell disk encryption), often mentioning Windows tools or features before Linux equivalents. Linux-specific guidance is sometimes missing or relegated to TODO comments, especially for disk encryption and user account management. While the page covers both Windows and Linux clusters in some sections, there is a notable tendency to prioritize Windows scenarios and omit Linux parity in critical areas.
Recommendations
  • Add explicit Linux examples and instructions for disk encryption (currently only a TODO comment).
  • Provide parity for user account management on Linux clusters, including how to run services under different accounts and secure resources.
  • Ensure that all PowerShell or Windows tool references are accompanied by Linux equivalents (e.g., Bash, CLI, or relevant Linux tools).
  • Mention Linux options alongside Windows ones, rather than after or as an afterthought.
  • Clarify which features are Windows-only and provide alternative guidance for Linux where possible.
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 for advanced Service Fabric application upgrade topics heavily relies on PowerShell cmdlets for examples and instructions, with no mention of Linux/macOS equivalents or cross-platform CLI tools. All command-line examples are PowerShell-based, and references to Visual Studio are made without alternatives for non-Windows environments. There is no guidance for Linux users on how to perform these tasks using Azure CLI, REST API, or other cross-platform tools.
Recommendations
  • Add Azure CLI or REST API examples alongside PowerShell cmdlets for all upgrade operations.
  • Explicitly mention whether PowerShell cmdlets can be used on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • Include references to cross-platform tools or scripts for Service Fabric management.
  • Provide alternatives to Visual Studio for packaging and upgrading applications, such as using the Service Fabric CLI (sfctl) or other build tools.
  • Clarify which features or steps are Windows-only and which are cross-platform.
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 ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page for Service Fabric application upgrade exhibits Windows bias by providing only PowerShell examples, referencing Windows-specific tools (http.sys), and lacking equivalent Linux CLI or SDK examples. Additionally, upgrade tutorials are linked for Visual Studio and PowerShell, both Windows-centric, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Add CLI or SDK-based examples for application upgrades that work on Linux/macOS (e.g., Azure CLI, Service Fabric CLI, REST API, or Python SDK).
  • Include explicit notes about cross-platform support and limitations, clarifying which features are Windows-only and which are available on Linux clusters.
  • Provide links or sections for Linux/macOS users, such as 'Upgrading your Application Using Service Fabric CLI' or 'Upgrading your Application Using REST API'.
  • Mention Linux-specific considerations (such as certificate handling, port management, and health checks) where relevant.
  • Ensure that examples and tutorials are not exclusively Windows-first; alternate between platforms or provide parity.
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 provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. No Linux/macOS equivalents (such as CLI or cross-platform tools) are mentioned or linked. The serialization guidance is focused on C# and .NET, which are cross-platform, but the upgrade workflow examples are Windows-first.
Recommendations
  • Add links or sections for upgrading applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and commonly used on Linux/macOS.
  • Mention and provide examples for upgrading Service Fabric applications from Linux/macOS environments.
  • Clarify which upgrade methods are Windows-only and suggest alternatives for Linux/macOS users.
  • Consider including a note about cross-platform support for .NET Core/.NET 5+ serialization if relevant.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page presents upgrade parameters for Service Fabric applications, but gives primary focus to Windows-centric tools (PowerShell and Visual Studio) before mentioning cross-platform options (SFCTL and REST). The parameter tables and explanations are structured with PowerShell and Visual Studio examples first, and only later describe SFCTL (the CLI used on Linux/macOS). While all major options are covered, the ordering and example emphasis create a Windows-first impression.
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL and REST) are presented before or alongside Windows-specific tools (PowerShell and Visual Studio).
  • Provide parameter tables and examples for SFCTL and REST in parallel with PowerShell/Visual Studio, rather than after them.
  • Add explicit notes clarifying which tools are cross-platform and which are Windows-only.
  • Include sample upgrade commands for SFCTL in the main parameter sections, not just in the 'Next steps'.
  • Consider a summary comparison table showing parameter mappings across PowerShell, Visual Studio, SFCTL, and REST.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for on-demand backup in Azure Service Fabric is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, and the prerequisite is to install a PowerShell module. There are no CLI, Bash, or Linux-native examples, nor any mention of how to perform these operations from Linux/macOS. The use of PowerShell-specific modules and commands creates friction for non-Windows users, and the documentation does not clarify cross-platform alternatives.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API calls with curl for Linux/macOS users.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is supported on PowerShell Core (pwsh) on Linux/macOS, and provide installation instructions if so.
  • If REST API is the recommended cross-platform method, provide explicit curl or HTTP request examples for Linux/macOS.
  • Indicate any platform limitations and guide Linux/macOS users to supported tooling.
  • Consider reordering examples so that cross-platform methods (REST API, CLI) are presented before or alongside PowerShell.
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 ⚠️ missing_linux_example
Summary
The documentation page primarily describes backup configuration for Azure Service Fabric, which is a cross-platform technology. However, in the 'File share' backup storage section, only Windows-style file share paths (\\StorageServer\BackupStore) and Integrated Windows Authentication are mentioned. There are no examples or guidance for Linux-based file shares (e.g., NFS, SMB on Linux), nor is there discussion of Linux authentication patterns. The documentation does not provide Linux-specific examples or parity for file share backup configuration.
Recommendations
  • Add examples for configuring file share backup storage using Linux-based file shares (e.g., NFS, SMB on Linux).
  • Include guidance for authentication to file shares from Linux nodes, such as using mount options, credentials, or Kerberos.
  • Clarify whether Linux Service Fabric clusters can use file share backup storage, and if so, provide relevant configuration details.
  • Mention any limitations or differences for Linux clusters regarding file share backup storage.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for restoring backups in Azure Service Fabric is heavily biased towards Windows, with all command-line examples provided exclusively in PowerShell. The prerequisite explicitly requires installation of a PowerShell module, and all REST API usage is demonstrated via PowerShell scripts. There are no Linux/macOS shell (bash/curl) examples, nor any mention of cross-platform tools or workflows. This creates friction for Linux/macOS users who may wish to automate or script these operations.
Recommendations
  • Add equivalent bash/curl examples for REST API calls, demonstrating how to trigger restore and track progress from Linux/macOS.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all operations, or if REST API calls can be made directly from any platform.
  • Mention cross-platform alternatives or note any limitations for Linux/macOS users.
  • Include guidance on certificate handling for REST API calls from Linux/macOS (e.g., using OpenSSL or curl options).
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 detailed step-by-step instructions for scaling Service Fabric clusters, but the manual scaling sections rely exclusively on PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning Linux equivalents or cross-platform alternatives. Windows/PowerShell tooling is referenced first and exclusively in critical operational steps, while Linux users are left to infer possible approaches. No Bash, CLI, or REST API examples are provided for Linux environments, and the documentation does not clarify whether these PowerShell commands are available or supported on Linux clusters.
Recommendations
  • Add equivalent instructions and examples for Linux clusters, using Bash, Azure CLI, or REST API where appropriate.
  • Clarify whether PowerShell commands are supported on Linux clusters, and if not, provide alternative workflows.
  • Include cross-platform guidance for manual scaling operations, ensuring Linux users can follow the same procedures.
  • Present examples for both Windows and Linux environments side-by-side, or clearly indicate platform-specific steps.
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 Resource Manager templates, but PowerShell is presented as a separate section, and manual upgrade instructions are PowerShell-only. Windows-specific registry keys and template properties are discussed in detail, while Linux equivalents are not mentioned. The documentation references both Windows and Linux clusters, but operational examples and upgrade instructions are heavily Windows-oriented.
Recommendations
  • Add Linux-specific operational examples, such as Bash or shell commands for manual cluster upgrades.
  • Include information about disabling automatic updates on Linux VM scale sets (e.g., using cloud-init or relevant Linux configuration).
  • Provide parity for registry/configuration guidance for Linux hosts, or clarify when steps are Windows-only.
  • When showing PowerShell examples, also provide Bash/Linux equivalents where applicable.
  • Clarify which steps are Windows-specific and which are cross-platform.
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 guidance for key security tasks, but Windows-specific tools and examples (e.g., PowerShell, Windows Defender, Windows security baselines) are often presented first or exclusively. Windows-specific recommendations and tooling (PowerShell, Windows Defender, DSC) are prominent, while Linux equivalents are less detailed or referenced later. Some sections (e.g., Windows Defender, security baselines) are Windows-only, but this is acknowledged. Linux examples are present for certificate generation and secret encryption, but Windows examples are shown first.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Expand Linux-specific guidance for security baselines and endpoint protection (e.g., recommend common Linux security tools or practices).
  • Where Windows tools (PowerShell, DSC, Defender) are mentioned, provide equivalent Linux tools or explicitly state if no direct equivalent exists.
  • Clarify when a section is Windows-only and provide links to Linux alternatives where relevant.
  • Ensure Linux guidance is as detailed as Windows guidance, especially for certificate management and secret encryption.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides a comprehensive reference for Service Fabric cluster settings, covering both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows terminology and tools (such as certificate store names like 'My', 'LocalMachine', and references to NTLM authentication) are used throughout, often without explicit Linux equivalents or clarifications. Windows-specific features (e.g., Windows Update, NTLM, log file paths) are mentioned more frequently and sometimes without clear Linux alternatives. In some places, Windows defaults are listed first or exclusively, even when Linux is supported.
Recommendations
  • Where certificate store names or NTLM authentication are referenced, clarify Linux equivalents or note Linux limitations.
  • Add explicit notes or columns indicating Linux-specific behaviors, defaults, or paths where they differ from Windows.
  • Where Windows-only features are mentioned (e.g., Windows Update, NTLM), clearly mark them as Windows-only and provide Linux alternatives or state if not applicable.
  • Ensure Linux terminology (e.g., certificate locations, user accounts, log paths) is included alongside Windows terminology.
  • Review parameter defaults and guidance for parity, ensuring Linux defaults are documented where they differ.
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 provides code examples for configuring Service Fabric placement policies using C# and PowerShell. All CLI examples use PowerShell, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are consistently shown alongside C# code, with no Linux-first or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for each placement policy configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for configuring placement policies, with example requests.
  • Clarify whether PowerShell examples are only applicable to Windows clusters, and provide guidance for Linux-based Service Fabric clusters.
  • Consider including Bash scripts or references to Service Fabric SDK tools available on Linux/macOS.
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 PowerShell and C# examples exclusively for managing Service Fabric Application Groups, without offering equivalent Linux/bash/CLI examples. It assumes the use of PowerShell cmdlets, which are native to Windows, and does not mention cross-platform tools or workflows. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer bash/CLI interfaces.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Mention whether PowerShell cmdlets are available cross-platform (via PowerShell Core) or if there are limitations.
  • Provide bash or shell script equivalents, or reference REST API usage for Linux/macOS users.
  • Clarify platform requirements for Service Fabric management tools and link to cross-platform options if available.
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 a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation also presents PowerShell examples before C# code, reinforcing Windows-first patterns. No mention is made of Azure CLI, REST API, or bash scripting alternatives, which would be relevant for cross-platform parity.
Recommendations
  • Add Azure CLI or REST API examples for configuring and updating move cost, as these are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention whether PowerShell examples are supported on Linux (via PowerShell Core), or clarify if they are Windows-only.
  • Consider providing bash or shell script equivalents where possible, or link to documentation covering Linux/macOS workflows.
  • Reorder examples so that cross-platform options (CLI, REST API) are presented before or alongside PowerShell.
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_first ⚠️ missing_linux_example
Summary
The documentation provides detailed examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all PowerShell examples are Windows-centric, and there are no equivalent Linux shell or CLI examples. The documentation does not mention or demonstrate Linux-native tools or commands for configuring auto scaling, despite Service Fabric supporting Linux containers. Additionally, PowerShell examples are presented alongside C# and manifest examples, but no Linux-first or cross-platform CLI guidance is given.
Recommendations
  • Add Azure CLI or Bash shell examples for configuring scaling policies, especially for Linux-based Service Fabric clusters.
  • Explicitly mention which steps or commands are cross-platform, and clarify any Windows-specific limitations.
  • Provide guidance or links for Linux users on how to perform equivalent operations (e.g., using REST APIs, Azure CLI, or SDKs on Linux/macOS).
  • Consider including a table or section summarizing cross-platform support and differences.
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 ⚠️ windows_tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json), but the Windows-specific XML example is consistently presented first and referenced more often. The only explicit platform mention is <WindowsServer> in the XML example, and PowerShell examples are included for service creation and updates, but no Linux shell or CLI equivalents are given. There is no explicit Linux/macOS example or guidance, and the Windows terminology (e.g., 'WindowsServer') is used without clarifying Linux support.
Recommendations
  • Present Linux/cross-platform examples (ClusterConfig.json) before or alongside Windows examples.
  • Clarify that Service Fabric standalone clusters can run on Linux, and provide explicit Linux configuration examples (e.g., referencing <Linux> infrastructure in ClusterManifest.xml if supported).
  • Add Azure CLI or Bash examples for service creation and updates, or reference relevant cross-platform tools.
  • Avoid using Windows terminology exclusively (such as <WindowsServer>) without mentioning Linux equivalents or applicability.
  • Include a short section or note about Linux/macOS support and any platform-specific differences.
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 app load using 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. Additionally, PowerShell examples are presented 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 platform-agnostic tools.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used.
  • Explicitly mention which tools are Windows-only and provide alternatives for Linux/macOS users.
  • Consider including Bash script examples or references to REST API usage for metric management.
  • Clarify any prerequisites or limitations for Linux/macOS users in the relevant sections.
  • Where possible, link to documentation on using Service Fabric tools on Linux clusters.
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_first ⚠️ missing_linux_example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not include equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. The C# API is platform-neutral, but operational examples (service creation/update) are Windows-centric.
Recommendations
  • Add Azure CLI or Bash script examples for service creation and updates, where possible.
  • Clarify whether PowerShell Core (cross-platform) is supported, or if only Windows PowerShell is valid.
  • Mention any Linux/macOS-compatible tooling for Service Fabric management.
  • If PowerShell is required, explicitly state its platform support and alternatives for Linux users.
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 Linux/bash/CLI 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 API being referenced earlier.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and commonly used on Linux/macOS.
  • Include REST API request examples for adding/removing node tags and updating service tag requirements.
  • Explicitly mention which PowerShell commands are available on Linux (if any), or clarify if they are Windows-only.
  • Consider providing bash or shell script snippets for Linux users where applicable.
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 on scaling Azure Service Fabric standalone clusters demonstrates Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to a Windows Server-specific guide for scaling standalone clusters. There are no Linux-specific examples, tools, or instructions, and the guidance assumes the use of Windows-based Service Fabric clusters and management tools.
Recommendations
  • Add equivalent Linux instructions and examples for scaling standalone Service Fabric clusters, including relevant CLI commands (e.g., sfctl) or scripts.
  • Clarify whether standalone Service Fabric clusters can be managed on Linux, and if so, provide parity in documentation for Linux environments.
  • Reference Linux-compatible tools and workflows alongside PowerShell examples, or explicitly state if only Windows is supported for standalone cluster management.
  • Update links and guidance to include Linux-specific scaling procedures if available.
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 for securing an Azure Service Fabric cluster presents security scenarios and technologies applicable to both Azure-hosted clusters and standalone Windows clusters. However, it repeatedly mentions standalone clusters as 'running on Windows' and provides links and guidance only for Windows Server clusters, with no equivalent instructions or links for standalone Linux clusters. Windows security (Kerberos) is discussed, but Linux authentication mechanisms are not mentioned. Certificate creation guidance references Windows Server certificate services and Windows tools, with no Linux-specific alternatives or examples. The concept of Linux clusters is acknowledged, but practical guidance is missing.
Recommendations
  • Add explicit guidance and links for securing standalone Linux Service Fabric clusters, including certificate setup and authentication options.
  • Provide Linux-specific examples for certificate creation and management (e.g., using OpenSSL or Linux CA tools).
  • Clarify which security scenarios and technologies are supported on Linux clusters, and highlight any differences.
  • Include references to Linux authentication mechanisms if applicable, or state their absence.
  • Ensure parity in example coverage and instructions for both Windows and Linux standalone clusters.
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_tools ⚠️ windows_first
Summary
The documentation page provides numerous PowerShell examples and references to Windows-specific tools (e.g., PowerShell cmdlets like Update-ServiceFabricService and New-ServiceFabricService) without equivalent Linux CLI or scripting examples. Windows tools and patterns are mentioned first and exclusively in code samples, creating friction for Linux users. The only explicit Linux mention is in the 'Choosing a platform' section, which discusses implementation differences, but does not provide Linux-specific operational guidance or examples.
Recommendations
  • Add equivalent Linux CLI examples (e.g., using sfctl or REST API) alongside PowerShell samples for all service management operations.
  • Explicitly mention Linux-compatible tools and workflows where PowerShell is referenced.
  • Where possible, provide code samples in Bash or cross-platform scripting languages.
  • Clarify any platform-specific limitations or differences in operational procedures.
  • Ensure Linux instructions are given equal prominence and not only in a dedicated section.
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 covers both Windows and Linux usage of Azure Service Fabric, but there is a notable Windows bias. Windows-specific tools (PowerShell, Visual Studio) and terminology (Windows service, FabricHost.exe) are mentioned first or exclusively in several sections. Examples and instructions often default to Windows, with Linux equivalents referenced later or not at all. Standalone clusters are only supported on Windows, and this is clearly stated. CLI and REST API options are mentioned, but PowerShell is often listed first. There are few explicit Linux command examples or Linux-focused workflows.
Recommendations
  • Provide Linux-specific examples and workflows alongside Windows instructions, especially for cluster management and health monitoring.
  • List CLI commands (sfctl) and REST API options before or equally with PowerShell, to improve parity for Linux/macOS users.
  • Clarify which tools and steps are cross-platform, and which are Windows-only, to reduce ambiguity.
  • Add links or references to Linux development environments and tools where appropriate.
  • Highlight Java programming model and Linux container support more prominently in relevant sections.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page references Windows-specific upgrade guides and tools (e.g., Patch Orchestration Application for Windows), and links to upgrade/configuration instructions with 'windows-server' in their URLs. There is no mention of Linux-specific upgrade instructions, examples, or tools, nor is Linux parity addressed. The page assumes Windows as the default platform for Service Fabric standalone clusters, which may create friction for Linux users.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric standalone clusters running on Linux, if supported.
  • Provide Linux-specific examples and configuration instructions alongside Windows instructions.
  • Clarify whether Service Fabric standalone clusters are Windows-only or if Linux is supported, to set expectations for users.
  • If Linux is not supported, state this clearly to avoid confusion.
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 notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. Application packaging instructions reference Visual Studio (a Windows-centric tool) and do not mention cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools are presented first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell examples.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling, or manual zip commands) instead of only Visual Studio.
  • Include Bash or shell script examples for relevant steps, such as uploading to blob storage.
  • Explicitly note that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
  • Reorder examples so that cross-platform tools are presented before or alongside Windows tools.
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 for 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 clusters, nor are Linux-native tools or patterns mentioned. Windows tools and approaches are discussed first and exclusively, creating friction for Linux users.
Recommendations
  • Add explicit guidance for accessing Service Fabric events on Linux clusters, including supported logging mechanisms (e.g., stdout, syslog, or Azure Monitor integration for Linux).
  • Mention Linux-native monitoring tools or patterns alongside Windows tools, such as using Azure Monitor with Linux clusters or exporting logs to Linux-friendly formats.
  • Clarify which features or approaches are Windows-only and provide Linux alternatives where available.
  • Include example workflows or commands for Linux environments, ensuring parity with Windows examples.
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 exhibits mild Windows bias. It references Windows file paths (e.g., Service Fabric SDK schema location), mentions Visual Studio as a packaging/deployment tool, and does not provide Linux/macOS equivalents or examples. There are no explicit PowerShell examples, but Windows tools and patterns are mentioned first or exclusively. The application package structure and manifest files are described generically, but the lack of Linux-specific guidance or examples may create friction for non-Windows users.
Recommendations
  • Add examples or instructions for packaging and deploying guest executables using Linux/macOS tools (e.g., CLI, VS Code, or cross-platform SDK usage).
  • Mention the location of schema files or SDK installation paths for Linux/macOS, if available.
  • Provide sample directory structures and file paths using both Windows and Linux conventions.
  • Clarify whether Visual Studio is required, or if cross-platform alternatives exist.
  • Link to Linux/macOS-specific Service Fabric documentation or guides, if available.
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
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation covers both Windows and Linux clusters, but there is a notable Windows-first bias. PowerShell examples are provided for setting DNS names, with no Linux CLI or scripting equivalents. Enabling DNS service via the Azure portal is only available for Windows clusters, and this is mentioned, but Linux users are left to infer their workflow from ARM template instructions. There are no Linux-specific command-line examples (e.g., Azure CLI, Bash, or REST API) for common tasks, and the ApplicationManifest.xml workflow is presented in a way that assumes Visual Studio, which is Windows-centric.
Recommendations
  • Add Azure CLI or Bash scripting examples for Linux users, especially for tasks currently only shown with PowerShell.
  • Explicitly document the Linux workflow for enabling DNS service (e.g., using ARM templates or REST API), including step-by-step instructions.
  • Where Visual Studio is referenced, mention cross-platform alternatives (e.g., VS Code, nano, vim) for editing manifest files.
  • When showing command-line examples, provide Linux equivalents alongside or immediately after Windows/PowerShell examples.
  • Clarify any limitations for Linux users up front, and provide links to relevant Linux-specific guidance where available.
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. While Service Fabric is cross-platform, the exclusive use of PowerShell in the example creates friction for Linux/macOS users, who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using the Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include REST API examples for health reporting and querying, as these are platform-agnostic.
  • Mention PowerShell as one option, but ensure Linux/macOS-friendly alternatives are presented alongside or before it.
  • Clarify which tools are available on each platform, and link to relevant installation guides.
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 page for the Azure Service Fabric hosting model presents PowerShell as the primary CLI example for creating services, with no Linux CLI (such as Azure CLI or Bash) equivalents. Windows/PowerShell tools are referenced first and exclusively in command-line instructions, and there is no mention of Linux-specific management patterns or tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for commands currently shown only in PowerShell.
  • Clarify which management tools are cross-platform and provide guidance for Linux/macOS users.
  • Mention or link to any available Bash scripts or REST API usage examples for Linux users.
  • Explicitly state PowerShell's cross-platform availability if relevant, or note any limitations for Linux/macOS users.
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 presents Service Fabric container application manifest examples based on Windows Server 2016 containers, with explicit references to Windows-specific tools (e.g., 'winver' for OS build detection) and Windows file paths (e.g., 'c:\VolumeTest\Data'). Linux equivalents are not mentioned, and Linux-specific guidance or examples are missing. While some sections acknowledge Linux (e.g., certificate handling), the overall focus and examples are Windows-centric, creating friction for Linux users.
Recommendations
  • Provide equivalent Linux-based manifest examples, including sample paths and OS build detection methods (e.g., 'cat /etc/os-release' or 'uname -r').
  • Clarify which features and manifest settings are cross-platform and which are Windows-only.
  • Add guidance for Linux container image tagging and compatibility, similar to the Windows 'ImageOverrides' section.
  • Include Linux file path examples alongside Windows paths in volume binding.
  • Reference Linux-specific documentation or Service Fabric samples where available.
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 extensive PowerShell-based deployment instructions and command examples, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. Windows tools and patterns (e.g., RDP, PowerShell, Windows file paths) are referenced exclusively or before any Linux alternatives. This creates friction for Linux/macOS users, who must translate instructions or find their own equivalents.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment steps.
  • Include Bash shell command alternatives for template deployments.
  • Mention SSH as a remote access method in addition to RDP, especially for Linux-based clusters.
  • Use platform-neutral file paths or clarify when Windows paths are used.
  • Explicitly state that the instructions apply to both Windows and Linux clusters, or provide Linux-specific guidance where relevant.
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 on Azure Service Fabric hosting activation and deactivation life cycle is generally platform-neutral in its conceptual explanations. However, there is evidence of Windows bias in the 'Next steps' section, which only links to PowerShell-based deployment instructions. Additionally, the only example for downloading a ServicePackage in advance references a PowerShell cmdlet, without mentioning Linux equivalents or cross-platform tools. No Linux-specific commands, tools, or guidance are provided, and PowerShell is implicitly presented as the default or primary method for operational tasks.
Recommendations
  • Add links to Linux/macOS deployment instructions using Service Fabric CLI (sfctl) or REST API, alongside PowerShell.
  • Provide examples for downloading ServicePackages in advance using cross-platform tools (e.g., sfctl, curl, or REST API), not just PowerShell.
  • Clarify which operational steps are platform-agnostic and which require platform-specific tooling.
  • In 'Next steps', include links to documentation for Linux/macOS users, not just PowerShell.
  • Where possible, mention both Windows and Linux tools in parallel, or note any platform limitations.
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 ⚠️ missing_linux_example
Summary
The documentation provides detailed coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Service Fabric. However, HTTP.sys is discussed first and in greater depth, with Windows-specific concepts (like netsh, Windows HTTP Server API, and kernel driver) explained extensively. Windows tools and patterns (e.g., ServiceManifest.xml Endpoint configuration for HTTP.sys, netsh usage) are mentioned without Linux equivalents. There are no explicit Linux/macOS-specific examples or guidance, and some sections (e.g., endpoint configuration, port assignment) focus on Windows behaviors before cross-platform considerations. While Kestrel is recommended for Linux, Linux-specific troubleshooting, deployment, or configuration details are missing.
Recommendations
  • Reorder sections to discuss Kestrel (cross-platform) before HTTP.sys (Windows-only), emphasizing Linux/macOS parity.
  • Add explicit Linux/macOS examples and guidance for Service Fabric Reliable Services with ASP.NET Core, including deployment, port configuration, and troubleshooting.
  • Clarify that HTTP.sys is Windows-only earlier in the document and highlight Kestrel as the default for Linux/macOS scenarios.
  • Provide Linux/macOS-specific notes for ServiceManifest.xml endpoint configuration, firewall handling, and certificate management.
  • Include links or references to Linux/macOS development environment setup and debugging tools.
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 provides detailed examples for health reporting in Service Fabric using PowerShell, which is Windows-centric, and shows PowerShell examples before REST. There are no equivalent Linux/bash or cross-platform CLI examples for health reporting, nor is there guidance for Linux users on how to perform these tasks outside of PowerShell. The REST API is mentioned but not demonstrated with concrete examples, and the PowerShell examples dominate the practical guidance.
Recommendations
  • Add equivalent examples using Azure CLI or bash scripts for health reporting, especially for Linux/macOS users.
  • Provide explicit guidance on using REST APIs with curl or similar tools, including sample requests and responses.
  • Clarify which tools are cross-platform and which are Windows-only, and recommend alternatives for Linux/macOS users.
  • Consider including a section on using Service Fabric SDKs or tools on Linux, if supported.
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' demonstrates notable Windows bias. All command-line/API examples reference PowerShell cmdlets (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), and there is no mention of Linux equivalents or cross-platform CLI usage. The documentation assumes the use of Windows tooling and APIs, with no guidance for Linux/macOS users on how to perform equivalent operations. This creates friction for non-Windows users, though workarounds may exist via FabricClient APIs or REST endpoints.
Recommendations
  • Add examples using cross-platform Service Fabric CLI (sfctl) where possible, alongside PowerShell examples.
  • Clarify whether the new APIs (e.g., Restore-ServiceFabricReplica) are accessible via sfctl or REST, and provide usage instructions for Linux/macOS users.
  • Explicitly state platform support for the administrative APIs and tools, and link to relevant Linux/macOS documentation.
  • If PowerShell is required, note any limitations for Linux users and suggest alternatives.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell example for deploying applications, which is Windows-centric. Windows file paths and certificate store names are referenced first, with Linux equivalents mentioned later and only briefly. There are no Linux CLI (e.g., Bash or sfctl) deployment examples, and Windows terminology/tools (like PowerShell) are presented before Linux alternatives.
Recommendations
  • Add Linux/macOS deployment examples using sfctl or Bash scripts alongside PowerShell examples.
  • Mention Linux file paths and certificate store locations earlier and more prominently.
  • Clarify cross-platform differences in endpoint/certificate handling and deployment commands.
  • Provide parity in tooling references (e.g., show both PowerShell and sfctl for application deployment).
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation is heavily focused on Visual Studio workflows, which are Windows-centric, and repeatedly references PowerShell as the tool for creating service instances. There are no examples or guidance for Linux/macOS users, nor are cross-platform tools or CLI alternatives mentioned. The documentation implicitly assumes Windows as the primary development environment for Service Fabric applications.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage Service Fabric applications and service configuration using cross-platform tools like Azure CLI or Service Fabric CLI.
  • Include examples for deploying and configuring Service Fabric applications on Linux clusters, or clarify if StartupServices.xml is not supported outside Visual Studio/Windows.
  • Mention alternative editors (e.g., VS Code) and workflows for non-Windows environments, if applicable.
  • If StartupServices.xml is strictly a Visual Studio feature, add a clear note stating its Windows-only scope to reduce confusion.
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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for the Fault Analysis Service overview in Azure Service Fabric presents usage examples and tooling primarily for C# and PowerShell, with explicit instructions for PowerShell (a Windows-centric tool) and no mention of Linux or cross-platform CLI alternatives. There is no guidance for Linux/macOS users on how to interact with the Fault Analysis Service, such as using Azure CLI, REST APIs, or Service Fabric CLI (sfctl).
Recommendations
  • Add examples for using the Fault Analysis Service with Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Include instructions for invoking Fault Analysis Service APIs via REST, which is platform-agnostic.
  • Clarify that PowerShell is Windows-specific and provide Linux/macOS alternatives where possible.
  • Reorder examples so that cross-platform options (e.g., sfctl, REST) are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
Medium 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 both Windows Server and Linux, the documentation page only provides details and examples for Windows environments. The 'Supported operating systems' section explicitly states that Linux isn't yet supported for standalone clusters, and all security and scaling guidance is Windows-centric. Linux-specific instructions, examples, or parity are missing throughout.
Recommendations
  • Clarify in the introduction that standalone clusters are currently Windows-only, despite the general Service Fabric platform supporting Linux.
  • Remove or revise statements implying Linux support for standalone clusters unless Linux support is imminent.
  • Add a section outlining Linux support status and roadmap, if relevant.
  • If Linux support is planned, provide equivalent Linux examples, tools, and instructions alongside Windows guidance.
  • Ensure that future updates include Linux-specific guidance as soon as support is available.
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
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 references Azure CLI, Azure PowerShell, and ARM templates for creating Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or mention Linux tools. Azure PowerShell is mentioned alongside Azure CLI, but PowerShell is a Windows-centric tool. Windows-specific scenarios (Windows VM activation, Windows updates) are listed before Linux equivalents (Linux package managers) in the networking section. No explicit Linux/macOS command examples or parity guidance is provided.
Recommendations
  • Provide explicit bash/Linux command examples alongside Azure PowerShell, especially for VM creation and migration steps.
  • Mention Azure CLI as the primary cross-platform tool, and clarify PowerShell is optional for Windows users.
  • List Linux scenarios (e.g., package manager access) before or alongside Windows scenarios in relevant sections.
  • Add references or links to Linux-specific migration considerations or troubleshooting guides.
  • Ensure all example commands are shown in both Azure CLI and PowerShell formats, or clarify which are cross-platform.
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: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-specific tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as primary or sole options for creating and converting VHDs. Windows/Hyper-V steps are described in detail, with Linux-native alternatives either missing or not given equal prominence. This creates friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, KVM).
  • Provide parity examples for extracting and manipulating VHDs on Linux/macOS, not just Windows/WSL.
  • Mention cross-platform alternatives before or alongside Windows tools, rather than after.
  • Clarify which steps are Windows-specific and offer Linux/macOS equivalents wherever possible.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page provides detailed PowerShell examples for resizing Azure VMs, including multiple scripts and explanations. Azure CLI and Terraform examples are also present, but PowerShell (a Windows-centric tool) is given more prominence, detail, and appears before CLI examples. There are no explicit Linux shell (bash) or macOS-specific instructions, and the Terraform example references a Windows VM quickstart. The page does not provide parity for Linux users in terms of example scripts or guidance.
Recommendations
  • Add bash shell examples for resizing VMs using Azure CLI, explicitly noting compatibility with Linux/macOS terminals.
  • Provide Terraform sample code for azurerm_linux_virtual_machine alongside the Windows example.
  • Ensure CLI instructions are as detailed as PowerShell, including explanations for Linux/macOS users.
  • Clarify that PowerShell examples can be run cross-platform (via Azure Cloud Shell), but also provide native bash alternatives.
  • Reference Linux VM quickstart documentation in the Terraform section.
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
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation covers both Linux and Windows VM deployment with Trusted Launch, but there are signs of Windows bias. PowerShell examples are exclusively for Windows, and Windows-specific parameters (e.g., OS type, image publisher) are used in PowerShell sections without Linux equivalents. In some sections, Windows examples or terminology appear first or are more detailed. Linux-specific PowerShell examples are missing, and some PowerShell snippets default to Windows OS, even when the CLI examples use Linux images. However, Azure CLI and template sections provide Linux parity.
Recommendations
  • Add PowerShell examples for Linux Trusted Launch VMs, including Linux-specific parameters and images.
  • Ensure PowerShell snippets include both Windows and Linux variants, or clarify OS-specific applicability.
  • In PowerShell image definition examples, use Linux OS type and images alongside Windows examples.
  • Review ordering of examples to avoid consistently placing Windows first.
  • Add clarifying notes where PowerShell is Windows-only, and suggest CLI or template for Linux users.
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, but the PowerShell examples are significantly more detailed and complex, including full networking setup, while CLI examples are minimal. PowerShell is a Windows-centric tool, and its prominence and depth may create friction for Linux/macOS users. Additionally, PowerShell examples are consistently shown after CLI, but the CLI examples are less comprehensive. No Linux-specific tools or shell examples (e.g., Bash scripting) are provided, and the documentation does not mention cross-platform alternatives for PowerShell tasks.
Recommendations
  • Expand Azure CLI examples to include full VM/network setup, matching the detail of PowerShell examples.
  • Add Bash shell scripting examples for Linux/macOS users, especially for tasks like network configuration.
  • Clarify that PowerShell examples are primarily for Windows users and suggest CLI or Bash for Linux/macOS.
  • Ensure CLI examples are as comprehensive as PowerShell, covering all steps needed for VM creation.
  • Consider referencing cross-platform tools or workflows where possible.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are heavily focused on Windows-specific patterns (e.g., Set-AzVMOperatingSystem -Windows), and Windows VM creation steps are often shown or implied first in PowerShell sections. Linux parity is generally maintained in CLI and REST examples, but PowerShell sections default to Windows, and Linux-specific PowerShell instructions are missing.
Recommendations
  • Add explicit PowerShell examples for creating Linux VMs, including Set-AzVMOperatingSystem -Linux usage and SSH authentication.
  • In PowerShell sections, clarify when examples are Windows-specific and provide Linux alternatives.
  • Ensure parity in PowerShell instructions for both OS types, similar to the CLI and REST sections.
  • Consider showing Linux examples first or equally in PowerShell sections, as is done in CLI.
  • Add notes or links to Linux PowerShell guidance where only Windows is shown.
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 Azure Service Fabric, but Windows development tools (Visual Studio, PowerShell, .NET SDK) are described before Linux equivalents (Eclipse, Yeoman, Java SDK). The quickstart link points to a .NET-based guide, which may be Windows-centric, though .NET Core is cross-platform. No explicit Linux examples or tools are missing, but Windows is presented first.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Include quickstart links for both Windows and Linux (e.g., .NET Core and Java quickstarts).
  • Clarify that .NET Core development is cross-platform and provide guidance for Linux/macOS users.
  • Consider linking to Linux-specific guides alongside Windows guides 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 toward Windows in the ordering and emphasis of examples and tools. Windows container runtimes and IIS scenarios are mentioned before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are detailed, while Linux only lists Docker. The IIS 'lift and shift' scenario is Windows-centric, but this is appropriate given IIS is a Windows-only technology. Linux examples are present and linked, but Windows examples and tools are sometimes listed first.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel or alternate order to avoid 'windows_first' bias.
  • Expand on Linux container runtime options if relevant (e.g., mention containerd or other alternatives if supported).
  • Clarify when scenarios are Windows-only (like IIS) to avoid confusion.
  • Add more Linux-centric scenarios or highlight Linux-specific advantages where appropriate.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides Azure Portal, Azure CLI, and Azure PowerShell examples for all attach/detach operations. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric, and its inclusion in every section (with full code samples) demonstrates a mild Windows bias. Additionally, PowerShell examples are consistently presented immediately after CLI, which may reinforce a Windows-first impression. However, there are no critical tasks that are Windows-only, and CLI parity is maintained throughout. No Linux/macOS-specific tools or shell examples are missing, but Bash or shell script examples are not explicitly shown.
Recommendations
  • Add explicit Bash/shell script examples for common attach/detach operations, or clarify that Azure CLI commands work identically on Linux/macOS.
  • Consider alternating the order of CLI and PowerShell examples, or explicitly state that CLI is cross-platform and recommended for Linux/macOS users.
  • Where possible, mention that PowerShell Core is available cross-platform, or clarify when examples are Windows PowerShell-specific.
  • Add a short note at the start of the 'Azure CLI' sections indicating that these commands are suitable for Linux/macOS/Windows.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_only ⚠️ missing_linux_example
Summary
The documentation explicitly states that the Service Fabric reverse proxy is not available for Linux clusters, and all examples and usage instructions are relevant only to Windows clusters. No Linux equivalents, workarounds, or alternative approaches are provided for Linux users.
Recommendations
  • Clearly indicate at the top of the page that the reverse proxy feature is Windows-only, to set expectations for Linux users.
  • Provide links or references to alternative service discovery and communication patterns for Service Fabric on Linux clusters, if available.
  • If possible, mention any roadmap or plans for Linux support, or direct users to feedback channels.
  • Ensure that related documentation pages (e.g., setup, diagnostics) also clarify platform limitations.
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, and these are mentioned before Linux equivalents. There are no explicit Linux container image examples or references, and the cleanup logic appears to prioritize Windows images. However, the documentation does not restrict usage to Windows containers and the settings themselves are generic.
Recommendations
  • Add examples of Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the ContainerImagesToSkip setting.
  • Clarify that the cleanup settings apply to both Windows and Linux containers, if applicable.
  • Mention any differences in image management between Windows and Linux nodes, if relevant.
  • Provide guidance or links for Linux container image management in Service Fabric clusters.
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 Docker Compose deployment on Azure Service Fabric. However, PowerShell is presented first and in greater detail, which may suggest a Windows-first approach. There are no explicit Linux/macOS shell or scripting examples, but the inclusion of sfctl (which is cross-platform) mitigates this bias.
Recommendations
  • Present the Service Fabric CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
  • Explicitly mention that sfctl can be used on Linux and macOS, and provide installation or usage notes for those platforms.
  • Optionally, add a short section or note confirming that all deployment operations can be performed from Linux/macOS using sfctl.
  • If possible, provide example shell commands (bash/zsh) for Linux/macOS users, especially for common tasks like checking deployment status.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a notable emphasis on Windows/PowerShell tooling. PowerShell is mentioned first for application creation, and Visual Studio (a Windows-centric IDE) is referenced for parameter file management. Linux tooling (sfctl) is mentioned, but not as prominently or with detailed examples. There is no explicit Linux/macOS bias, but Windows tools and patterns are presented first and in more detail.
Recommendations
  • Present Linux/macOS tools (e.g., sfctl) before or alongside Windows/PowerShell examples.
  • Provide detailed examples for sfctl usage, including parameter passing, similar to the PowerShell example.
  • Include guidance for managing parameter files and deployments from Linux/macOS environments, not just Visual Studio.
  • Clarify cross-platform support for Service Fabric tooling and workflows.
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: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides examples and references primarily in C#, which is cross-platform, but in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives. There are no explicit Linux/macOS-specific examples or guidance, and no mention of Linux tooling for application upgrades.
Recommendations
  • Add references to Linux/macOS-compatible tools for application upgrades, such as Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell and Visual Studio.
  • Include examples or links for performing upgrades and serialization tasks on Linux/macOS environments.
  • Clarify that the C# code and serialization concepts are applicable on all supported platforms, not just Windows.
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 minor signs of Windows bias: Windows-specific executables and services (e.g., FabricHost.exe, Fabric.exe, FabricGateway.exe) are described first and in detail, and Windows terminology (EXE/DLL) is used for code packages. The mention of 'auto-start Windows service' for nodes and Windows containers appears before Linux equivalents. Linux support is acknowledged, but Windows patterns and terminology are more prominent.
Recommendations
  • Clarify when descriptions are Windows-specific and provide equivalent Linux details where relevant (e.g., how nodes are managed on Linux, what processes are involved).
  • Use neutral terminology for code packages (e.g., 'executables' instead of 'EXE/DLL files') and mention Linux binary formats.
  • When describing containers, mention Linux support equally and avoid listing Windows containers first.
  • Add explicit examples or notes for Linux environments where Windows-specific tools or services are referenced.
  • Ensure parity in describing development clusters and deployment models for Linux/macOS.
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 Template. Portal instructions are also present. However, PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash, shell scripting) are provided, but Azure CLI is cross-platform and covers most needs. The ordering of examples (CLI first, PowerShell second) is a minor bias, but no critical functionality is Windows-only.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing Bash shell scripting examples for common tasks, or clarify that Azure CLI commands are suitable for Linux/macOS.
  • If possible, add a short section or callout for Linux/macOS users, confirming that all tasks can be completed with Azure CLI.
  • Review the ordering of examples to ensure CLI and ARM Template are prioritized for cross-platform parity.
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
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is included alongside CLI and Portal, but CLI is shown before PowerShell. There is a slight bias toward Windows/PowerShell, as PowerShell is a Windows-centric tool, but the CLI example is cross-platform and appears first. No Windows-specific tools or patterns are mentioned exclusively, and Linux users can complete all tasks using Azure CLI or ARM templates.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell scripting examples for CLI usage, or clarifying that CLI commands work on Linux/macOS.
  • If possible, mention that PowerShell Core is available cross-platform, but traditional PowerShell is Windows-only.
  • Ensure that CLI and ARM template examples are always present and shown before PowerShell in future documentation.
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 (e.g., 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 CLI and PowerShell examples side-by-side or in parallel tabs, rather than consistently listing PowerShell first.
  • Ensure CLI examples are as detailed as PowerShell examples, especially for querying and updating resources.
  • Add explicit notes clarifying that Azure CLI works cross-platform (Linux/macOS/Windows), and PowerShell is available on Linux/macOS as well.
  • Where possible, provide Bash shell script examples for Linux users, especially in sections with only PowerShell code.
  • Review for any missing CLI equivalents and add them if absent.
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 custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there are several areas where Windows/PowerShell examples are presented first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in some code snippets and REST payloads. The PowerShell section is more verbose and detailed than the Bash example, and Windows-specific extension names/types are used in several places. Linux parity is generally good, but Windows bias is evident in ordering and emphasis.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail. Alternate the order of examples or present them side-by-side.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in all code snippets and REST payloads, and provide explicit Linux-focused examples.
  • Expand Bash/Python examples to match the detail and completeness of PowerShell examples, including troubleshooting and verification steps.
  • Where possible, use generic extension names/types in JSON and REST examples, or provide both Linux and Windows variants.
  • Review sample output and troubleshooting sections to ensure Linux commands and tools are as prominent as Windows/PowerShell equivalents.
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/shell) and Azure PowerShell examples for creating instant access snapshots, but PowerShell is presented as a primary option alongside CLI, and Windows-specific tooling (PowerShell) is given equal prominence. There are no Linux-specific notes or examples beyond Azure CLI, and the CLI examples use bash syntax, which is cross-platform but not explicitly labeled as Linux/macOS. The documentation does not mention Linux tools or patterns (e.g., shell scripting, automation with cron, etc.), nor does it provide troubleshooting or guidance for Linux users. PowerShell is presented before the Azure Portal and Resource Manager Template sections, which may subtly reinforce Windows-centric workflows.
Recommendations
  • Explicitly state that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Consider providing Linux/macOS-specific tips, such as using shell scripts for automation or integrating with cron.
  • Ensure that CLI examples use generic shell syntax and avoid Windows-specific environment variable patterns.
  • If possible, add troubleshooting or guidance for Linux users (e.g., common issues with az CLI on Linux).
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: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and the PowerShell section appears before the ARM template section. There is a slight 'windows_first' bias, as PowerShell is a Windows-centric tool, and its inclusion alongside CLI without mention of Bash or Linux-specific commands may create friction for Linux/macOS users. However, the CLI examples are present and fully functional for Linux/macOS users, and ARM templates are platform-agnostic.
Recommendations
  • Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Consider adding Bash shell script examples for Linux users, or clarifying that Azure CLI is the recommended tool for Linux/macOS.
  • In the 'Use Azure Resource Manager templates' section, clarify that both Linux and Windows images are supported, and link to both quick-create-template-linux.md and quick-create-template-windows.md equally.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation is primarily focused on Linux, as expected given the page title. However, there are several sections where Windows-oriented tools (PowerShell) are presented before their Linux equivalents (Azure CLI), and troubleshooting instructions reference Azure PowerShell before Azure CLI. PowerShell deployment examples are given first, despite Linux users typically preferring Azure CLI or shell scripting. There are no missing Linux examples, but the ordering and tool emphasis may create minor friction for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections, as CLI is the default for Linux users.
  • Explicitly note that PowerShell is optional and primarily for Windows users, while Azure CLI is cross-platform and recommended for Linux.
  • Add bash shell script examples for common deployment scenarios, if relevant.
  • In troubleshooting, show Azure CLI commands first, and clarify that PowerShell is an alternative for Windows users.
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 parity for both Linux and Windows throughout most sections, including CLI, REST, and portal instructions. However, there is mild Windows bias in the PowerShell examples, which default to Windows as the OS type, and in some cases, Windows is mentioned before Linux (e.g., in the PowerShell section). Additionally, PowerShell is a Windows-centric tool, and its examples are presented alongside CLI, but not prioritized over CLI. The CLI and REST examples default to Linux, balancing the bias. No critical Linux examples are missing, and all workflows are cross-platform.
Recommendations
  • In PowerShell examples, show Linux as the default OS type or provide both Linux and Windows variants equally.
  • Where possible, clarify that PowerShell can be used on Linux/macOS as well, or suggest cross-platform alternatives.
  • Ensure that OS-specific guidance and examples are presented in parallel (e.g., 'To create a Linux image, use ...; to create a Windows image, use ...') rather than defaulting to Windows.
  • Consider adding a note about PowerShell Core's cross-platform support for Linux/macOS users.
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 is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, including tools, commands, and configuration examples for ntpd, chronyd, systemd-timesyncd, and cloud-init. However, the introductory sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific content, which may create a perception of Windows-first bias. All practical examples and instructions are Linux-centric, with only a minor PowerShell snippet for base64 encoding cloud-init (which is relevant for Azure ARM template usage, not VM configuration).
Recommendations
  • Move or minimize Windows Server 2016 discussion in the introduction; focus on Linux host infrastructure and its impact on Linux VM time sync.
  • Provide a Linux shell alternative for the PowerShell base64 encoding example (e.g., `base64 cloud-config.txt`).
  • Ensure Linux-specific resources and links are presented before or alongside any Windows references.
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, PowerShell is presented as a primary option alongside CLI, despite PowerShell being more commonly used on Windows. The CLI example is shown first, which is positive, but the PowerShell section is equally prominent and detailed. There are no Linux-specific tools or shell examples (e.g., Bash scripting), and PowerShell is not flagged as Windows-only, which could cause confusion for Linux/macOS users who may not have PowerShell installed.
Recommendations
  • Clarify that PowerShell examples are primarily for Windows users, and note that PowerShell Core is available cross-platform but may require installation.
  • Add Bash shell scripting examples or note that Azure CLI is the recommended cross-platform tool.
  • Explicitly state that Azure CLI works natively on Linux/macOS and is the preferred method for non-Windows environments.
  • Consider adding a short section or note about PowerShell Core availability on Linux/macOS, with installation links.
GitHub Create Pull Request
Virtual Machines Share VM images in a compute gallery ...in/articles/virtual-machines/shared-image-galleries.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 Windows and Linux coverage for Azure Compute Gallery, but there are several signs of Windows bias. PowerShell examples and references appear frequently and often before CLI equivalents. Windows-specific tools (e.g., Sysprep) are mentioned before Linux equivalents (waagent). Some links and examples reference Windows paths or documentation first. However, Linux is supported and referenced throughout, and most tasks can be completed by Linux/macOS users.
Recommendations
  • Ensure that CLI and PowerShell examples are presented side-by-side or with equal prominence, rather than PowerShell first.
  • Where Windows tools (e.g., Sysprep) are mentioned, ensure Linux equivalents (e.g., waagent) are given equal detail and placement.
  • Review linked documentation to ensure Linux examples are as comprehensive as Windows examples.
  • Consider adding Bash or cross-platform scripting examples where appropriate.
  • Avoid referencing Windows documentation or tools first unless the feature is Windows-only.
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 VM vCore customization, but the PowerShell section is presented immediately after the CLI section and is detailed, potentially implying Windows as a primary platform. The CLI example uses Ubuntu as the image, but there are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is emphasized as a separate section. The documentation does not mention Linux-specific tools or patterns, nor does it provide parity for Linux/macOS users in terms of native shell scripting.
Recommendations
  • Add Bash shell examples for Linux/macOS users, especially for commands that can be run outside Azure CLI (e.g., using az commands in Bash scripts).
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider mentioning that PowerShell Core is available on Linux/macOS, but provide Bash examples as the default for non-Windows users.
  • Ensure that examples and instructions are not presented in a Windows-first order; alternate or combine CLI and PowerShell sections, or explicitly state platform applicability.
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 clear indications that Trusted launch applies to both. However, there is a mild Windows bias in the tooling examples: PowerShell is given its own section and is used for ARM template deployment and VM deallocation, while Linux-native tools (such as Bash or shell scripting) are not referenced for these tasks. Additionally, PowerShell examples are shown alongside CLI and portal, but the PowerShell section is not explicitly labeled as Windows-only, despite PowerShell Core being cross-platform. In some cases, PowerShell is used for tasks where Azure CLI or Bash could be equally applicable, and PowerShell is referenced first for ARM template deployment. The documentation does mention SSH for Linux and RDP for Windows, and includes a Linux-specific best practice (SBInfo tool), but overall, Windows tooling is slightly favored.
Recommendations
  • Add explicit Bash/shell scripting examples for ARM template deployment and VM deallocation/start, especially for Linux/macOS users.
  • Clarify that PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternative Bash/CLI commands where possible.
  • Ensure that CLI and Bash examples are presented before or alongside PowerShell, rather than PowerShell being the default for template deployment.
  • Where PowerShell is used, note its cross-platform support, or link to documentation for using PowerShell on Linux/macOS.
GitHub Create Pull Request