← Back to Dashboard
231
Pages Scanned
80
Pages Flagged
231
Changed Pages
34.6%
% Pages Flagged

Scan Information

Started At: 2026-02-01 00:00:11

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

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 231

Files Completed: 231

Problematic Pages

80 issues found
Service Fabric Azure Service Fabric reverse proxy ...articles/service-fabric/service-fabric-reverseproxy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric reverse proxy is Windows-focused, as the reverse proxy is explicitly stated to be unavailable for Linux clusters. All examples, configuration guidance, and usage scenarios assume a Windows environment, with no Linux equivalents or workarounds provided.
Recommendations
  • Clearly state at the top of the documentation that reverse proxy is not supported on Linux clusters and link to any alternative approaches for Linux users.
  • Provide guidance or references for Linux users on how to achieve similar service discovery and HTTP routing, if possible, using other Service Fabric features or third-party tools.
  • Update related documentation to clarify platform support for reverse proxy and suggest migration paths or alternatives for Linux clusters.
GitHub Create Pull Request
Service Fabric Standalone Service Fabric clusters overview ...-fabric/service-fabric-standalone-clusters-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_only ⚠️ missing_linux_example
Summary
Although the introduction claims Service Fabric clusters can run on both Windows Server and Linux, the documentation later states that Linux isn't yet supported for standalone clusters. All examples, operating system lists, and security options are Windows-centric, with no Linux instructions or parity. This creates confusion for Linux users and makes the documentation effectively Windows-only.
Recommendations
  • Clarify at the top of the page that standalone Service Fabric clusters are currently Windows-only, and Linux support is not available.
  • Remove or update the description to avoid implying Linux support where it does not exist.
  • Add a section explaining the roadmap or alternatives for Linux users, if applicable.
  • Ensure that all examples and instructions are clearly marked as Windows-specific to avoid misleading Linux/macOS users.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, without mentioning equivalent Linux/macOS command-line options or tools. The use of PowerShell cmdlets and lack of cross-platform instructions creates friction for non-Windows users managing Service Fabric clusters.
Recommendations
  • Include equivalent instructions for Linux/macOS users, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) if available.
  • Clarify whether the PowerShell command is required or if cross-platform alternatives exist.
  • Add notes or links to cross-platform tooling for cluster management tasks.
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: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page on describing Azure Service Fabric apps and services shows mild Windows bias. It references Windows file paths (e.g., 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd'), recommends using Visual Studio (a Windows-centric tool) for schema validation, and mentions the ServiceFabric PowerShell module for service creation before any Linux equivalents. There are no explicit Linux/macOS examples or tooling recommendations, and Windows terminology appears first in several places.
Recommendations
  • Add equivalent instructions for Linux/macOS users, such as how to locate schema files on those platforms.
  • Recommend cross-platform editors (e.g., VS Code) for XML schema validation and intelli-sense.
  • Mention Linux CLI tools (e.g., Azure CLI, sfctl) for service creation alongside PowerShell.
  • Provide examples or notes for Linux/macOS file paths and environment setup.
  • Ensure that references to Windows tools are balanced with Linux/macOS alternatives where possible.
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 references PowerShell and Visual Studio as primary tools for application upgrade walkthroughs, both of which are traditionally Windows-centric. PowerShell is available on Linux/macOS, but Service Fabric PowerShell modules and Visual Studio are most commonly used on Windows. No explicit Linux/macOS CLI or cross-platform upgrade example is provided, and the documentation does not mention Linux-native tools or workflows.
Recommendations
  • Add equivalent upgrade walkthroughs using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Clarify whether PowerShell examples work on Linux/macOS, or provide Bash/shell alternatives where appropriate.
  • Mention cross-platform development environments (e.g., VS Code) or provide links to documentation for upgrading applications from non-Windows systems.
  • Explicitly state platform requirements for each tool or example, so users know if a Windows environment is required.
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 ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but Windows examples and tools (such as PowerShell and Windows Defender) are often presented first or exclusively. Some sections, like Windows Defender and security baselines, are Windows-specific, but these are appropriately marked. However, in sections like certificate encryption, Windows/PowerShell examples precede Linux/openssl examples, and Windows-specific tooling is referenced more frequently.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Clearly label Windows-only sections and provide equivalent Linux guidance or explicitly state when no Linux equivalent exists.
  • Where possible, reference cross-platform tools and patterns before platform-specific ones.
  • Expand Linux-specific security baseline recommendations (e.g., CIS benchmarks, Linux antimalware options) to match Windows coverage.
  • Ensure that all code samples and configuration steps are available for both platforms, or link to Linux/macOS equivalents.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation references PowerShell cmdlets and Windows security as primary management and security mechanisms, without mentioning Linux equivalents (such as Azure CLI, Bash, or Linux security integration). Windows tools and patterns are mentioned first and exclusively in key management sections, creating friction for Linux/macOS users seeking parity.
Recommendations
  • Include Azure CLI and REST API examples for management tasks alongside PowerShell cmdlets.
  • Clarify whether management operations (provision, deploy, patch, upgrade) can be performed using cross-platform tools, and provide links or examples.
  • Mention Linux-compatible security mechanisms (such as X509 certificates) before or alongside Windows security.
  • Add a note on platform support for Service Fabric management and clarify any Windows-only limitations.
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 ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation consistently provides PowerShell examples for managing Service Fabric Application Groups, with no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for users operating Service Fabric clusters on Linux or from non-Windows environments. The C# SDK examples are cross-platform, but operational/command-line instructions are Windows-centric.
Recommendations
  • Add equivalent Azure CLI or REST API examples for all PowerShell commands shown, especially for creating, updating, and querying application groups.
  • Explicitly mention which commands/tools are available on Linux/macOS and provide links to relevant cross-platform documentation.
  • If certain features are only available via PowerShell, clearly state this limitation and suggest alternatives or workarounds for Linux users.
  • Consider including Bash script examples or instructions for using Service Fabric CLI (sfctl), if applicable.
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 command-line examples exclusively using PowerShell cmdlets for managing node tags and service tag requirements in Azure Service Fabric. There are no equivalent examples for Linux/macOS users, such as Bash, CLI, or REST API usage. This creates friction for users operating Service Fabric clusters on non-Windows environments.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service tag requirements.
  • Include REST API sample requests for tag operations, as these are platform-agnostic.
  • Explicitly mention how Linux/macOS users can perform these tasks, and provide links to relevant cross-platform tools or documentation.
  • Clarify whether PowerShell Core (cross-platform) is supported, and if so, provide usage notes.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric hosting activation and deactivation life cycle exhibits moderate Windows bias. The only explicit example for deploying or managing Service Fabric applications refers to PowerShell, a Windows-centric tool. The 'Next steps' section links specifically to PowerShell-based deployment/removal instructions, with no mention of Linux equivalents (such as Service Fabric CLI or REST API). There are no examples or references to Linux/macOS workflows, tools, or commands, and no mention of cross-platform deployment patterns.
Recommendations
  • Include Linux/macOS deployment examples using Service Fabric CLI (sfctl) or REST API alongside PowerShell instructions.
  • Add references or links to documentation for Linux/macOS Service Fabric node management.
  • Clarify which steps or tools are cross-platform and which are Windows-specific.
  • Where PowerShell is referenced, provide equivalent CLI commands for Linux users.
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 ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page on Azure Service Fabric Events primarily references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent. There are no explicit examples or guidance for accessing or configuring Service Fabric events on Linux clusters, nor are Linux-native logging tools or patterns mentioned. This may create friction for Linux users seeking parity.
Recommendations
  • Add explicit documentation or examples for accessing Service Fabric events on Linux clusters, including references to Linux-native logging mechanisms (e.g., syslog, journald, or custom log files).
  • Clarify whether the described diagnostics agent and event logging mechanisms apply to both Windows and Linux clusters, or provide Linux-specific alternatives if not.
  • Include Linux-focused guidance or links to relevant documentation for configuring diagnostics and accessing events on Linux-based Service Fabric clusters.
  • Ensure that any references to monitoring tools or agents are inclusive of both Windows and Linux environments, or clearly state platform limitations.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page provides several examples and deployment instructions using PowerShell commands and Windows file paths, with Windows-centric terminology and tooling presented first or exclusively. Linux equivalents are mentioned only briefly and lack detailed examples, which may create friction for Linux/macOS users.
Recommendations
  • Include equivalent Linux/macOS deployment instructions, such as using Azure CLI or Service Fabric CLI (sfctl), alongside PowerShell examples.
  • Provide Linux file path references and clarify differences in certificate storage (e.g., /var/lib/sfcerts) with concrete examples.
  • Add explicit Linux/macOS code snippets for common tasks (e.g., application deployment, endpoint configuration) to ensure parity.
  • Where PowerShell is used, note the Linux/macOS alternative and link to relevant documentation.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is notably Windows-centric, focusing exclusively on Visual Studio workflows and referencing Windows-specific tools and patterns (e.g., F5/Ctrl+F5, right-click->Publish, Visual Studio project templates). There are no examples or guidance for Linux/macOS users or for cross-platform Service Fabric development and deployment. The only alternative deployment methods mentioned are ARM and PowerShell cmdlets, but these are referenced briefly and not demonstrated. The documentation assumes use of Visual Studio, which is primarily a Windows tool, and omits any mention of Linux-compatible workflows, such as using Service Fabric CLI (sfctl) or cross-platform editors.
Recommendations
  • Add equivalent instructions and examples for deploying Service Fabric applications using Linux/macOS tools, such as sfctl, Azure CLI, or VS Code.
  • Clarify which features are Visual Studio-specific and provide alternative cross-platform workflows where possible.
  • Include sample commands for Linux/macOS environments for tasks like building, deploying, and managing Service Fabric applications.
  • Reference cross-platform Service Fabric SDKs and document how StartupServices.xml fits into non-Visual Studio workflows, if supported.
  • Explicitly state any limitations or lack of support for StartupServices.xml outside Visual Studio, and guide Linux/macOS users to supported alternatives.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page provides a comprehensive overview of certificate management in Azure Service Fabric clusters, but exhibits a moderate Windows bias. PowerShell is the only scripting language shown for programmatic certificate enrollment, and the Key Vault VM extension is described exclusively in its Windows variant. The documentation references Windows-specific certificate store locations and behaviors (such as ACLing and S-channel linking), and Windows-centric terminology and examples appear before or instead of Linux equivalents. There is little to no mention of Linux/macOS-specific certificate provisioning or automation approaches, and no Bash/CLI examples are provided.
Recommendations
  • Add equivalent Bash/Azure CLI examples for certificate enrollment and management, especially for tasks currently shown only in PowerShell.
  • Clarify whether the Key Vault VM extension and Service Fabric VM extension have Linux support, and if so, provide Linux-specific instructions and examples.
  • Discuss certificate store locations and ACLing approaches for Linux nodes, if supported.
  • Explicitly note any limitations or differences for Linux/macOS clusters, and link to relevant documentation.
  • Where Windows-specific features (like S-channel linking) are discussed, state their applicability and alternatives for Linux environments.
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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation exhibits a moderate Windows bias. Windows-specific tools, APIs, and troubleshooting steps are mentioned first or exclusively (e.g., references to the Windows certificate store, Win32 CryptoAPI, CAPI2 logging, and error codes). Linux equivalents are only briefly mentioned or omitted, and there are no concrete Linux/macOS command examples or troubleshooting guidance. This may create friction for Linux users configuring or diagnosing Service Fabric clusters.
Recommendations
  • Provide explicit Linux/macOS equivalents for certificate storage paths, management commands, and troubleshooting steps (e.g., show how to check certificates in /var/lib/sfcerts, use OpenSSL, or relevant Linux logs).
  • When referencing Windows-specific APIs or logs (e.g., Win32 CryptoAPI, CAPI2 logging), add parallel guidance for Linux (e.g., OpenSSL verification, syslog, journalctl, or Service Fabric logs on Linux).
  • Include Linux/macOS-specific error messages and common troubleshooting steps.
  • Where possible, show both Windows and Linux examples side-by-side, especially for certificate installation, validation, and cluster manifest configuration.
  • Clarify any platform-specific limitations or differences in Service Fabric certificate handling.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referring to 'custom windows images' throughout, providing only PowerShell examples for role assignment, and mentioning Windows/PowerShell tools before their Linux equivalents. Although there are references to Linux custom image creation and Azure CLI, no Linux-specific command examples or workflows are provided for key steps such as role assignment.
Recommendations
  • Clarify that Service Fabric Managed Cluster supports both Windows and Linux node types if applicable.
  • Provide Linux-specific examples for role assignment (e.g., using Azure CLI or Bash).
  • Include ARM template examples for both Windows and Linux images, or clarify any OS-specific differences.
  • Present Linux and Windows workflows in parallel, rather than focusing on Windows terminology and examples.
  • Ensure references to documentation for both Windows and Linux image creation are equally prominent.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides detailed PowerShell examples for managing Service Fabric managed cluster node types but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). All command-line automation is shown using PowerShell, which is primarily a Windows tool, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (adding, removing, scaling node types, etc.).
  • Explicitly state that PowerShell examples can be run cross-platform (if true), or provide installation guidance for PowerShell on Linux/macOS.
  • Where possible, provide Bash or shell script equivalents, or reference Azure CLI documentation for equivalent tasks.
  • Clarify in each section that users can choose between PowerShell and Azure CLI, and link to relevant Azure CLI documentation.
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 for Azure PowerShell modules when describing best practices for managing Service Fabric managed clusters. PowerShell is a Windows-centric tool, and its examples are listed before Azure CLI and other cross-platform options. While Azure CLI and ARM templates are mentioned, actionable examples and direct links for critical operations (delete, restart, reimage) are given only for PowerShell, with no equivalent CLI or Linux-native command examples.
Recommendations
  • Add Azure CLI examples and links for all critical operations (delete NodeType, restart, reimage) alongside PowerShell examples.
  • Ensure that CLI and Bicep/ARM template usage is described with parity to PowerShell, including direct documentation links.
  • Explicitly state that all recommended tools (CLI, ARM, Bicep, Portal) are cross-platform and suitable for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (CLI, ARM, Bicep) are listed before or alongside PowerShell.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page predominantly references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for managing Service Fabric resources, with no mention of Linux/macOS equivalents or CLI alternatives. This creates friction for non-Windows users, as PowerShell is a Windows-native tool, and the Azure CLI (which is cross-platform) is only briefly mentioned for deletion operations. There are no Linux/macOS-specific instructions or examples.
Recommendations
  • Include Azure CLI examples for all operations (create, delete, scale) alongside PowerShell cmdlets, as Azure CLI is cross-platform.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell must be used, and provide installation guidance.
  • Where possible, provide ARM template examples for resource management, as these are platform-agnostic.
  • Clarify which tools are required for each OS and provide parity in instructions.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for Initializer CodePackages in Service Fabric provides only Windows container examples, exclusively referencing Windows container images, Windows file paths, and Windows command-line tools (cmd, echo, type, ping). There are no Linux container or cross-platform examples, and the example assumes familiarity with Windows container development. This creates friction for Linux/macOS users who may wish to use Initializer CodePackages with Linux containers.
Recommendations
  • Add a parallel example using Linux containers (e.g., Ubuntu or Alpine images) with Linux file paths and shell commands (bash, echo, cat, sleep).
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance for Linux users.
  • Where possible, use cross-platform patterns or explicitly note platform limitations.
  • If Initializer CodePackages are Windows-only, state this clearly at the top of the page.
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 generally covers both Windows and Linux clusters for Azure Service Fabric monitoring, but there is a noticeable Windows-first bias in several sections. Windows tools and patterns (such as Event Log/Event Viewer, Diagnostics Agent, and ETW providers) are mentioned before their Linux equivalents, and some examples or tutorials focus primarily on Windows or .NET applications. Linux-specific instructions and tools are referenced, but often as secondary notes or links, and there is a lack of explicit Linux example walkthroughs or parity in some areas.
Recommendations
  • Ensure that Linux monitoring tools and configuration steps are presented with equal prominence and detail as Windows equivalents.
  • Provide explicit Linux example walkthroughs for common monitoring scenarios, including sample code and configuration steps.
  • Where Windows tools (e.g., Event Viewer, Diagnostics Agent) are mentioned, immediately follow with Linux equivalents (e.g., Syslog, Linux platform diagnostics) and clarify differences.
  • Add tutorials or links for monitoring non-.NET applications and Linux-native workloads on Service Fabric.
  • Review and update references to ensure Linux and cross-platform tools are not only mentioned but demonstrated.
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 ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page on RunToCompletion semantics in Service Fabric demonstrates a notable Windows bias. All code examples use Windows container images and Windows-specific shell commands (cmd, set, exit, etc.), with no mention or example of Linux containers or Linux shell equivalents. Querying deployment status is described only via PowerShell and C# APIs, with no Linux CLI or cross-platform alternatives. The introductory note and example code are explicitly Windows-focused, and Linux parity is not addressed.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands (bash, echo, exit, etc.).
  • Clarify whether RunToCompletion semantics are supported for Linux containers and, if so, provide Linux-specific guidance.
  • Include instructions for querying deployment status using cross-platform tools (e.g., Azure CLI, REST API) or Linux-native commands if available.
  • Explicitly state any limitations or differences for Linux container support, if applicable.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., Copy-ServiceFabricApplicationPackage, Register-ServiceFabricApplicationType) alongside .NET APIs and REST operations. PowerShell examples and commands are frequently mentioned before or in preference to cross-platform alternatives, and there is little explicit mention of Linux/macOS workflows or CLI parity. While REST APIs and .NET APIs are referenced (which are cross-platform), the documentation implicitly assumes familiarity with Windows tooling and does not provide Linux-specific examples or guidance.
Recommendations
  • Add explicit examples using Service Fabric CLI (sfctl), which is cross-platform and recommended for Linux/macOS users.
  • Where PowerShell cmdlets are mentioned, also provide equivalent sfctl or Azure CLI commands.
  • Include notes or sections clarifying differences or additional steps for Linux/macOS environments, especially for deployment and lifecycle management.
  • Ensure that links to CLI documentation are prominent and not only included as a general reference.
  • Consider reordering examples so that cross-platform tools (sfctl, REST API) are presented before or alongside PowerShell cmdlets.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell, but does not mention or provide examples for Linux/macOS command-line tools, Service Fabric CLI (sfctl), or REST API usage. This creates friction for Linux/macOS users who cannot use PowerShell natively and may rely on cross-platform tools.
Recommendations
  • Add examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Mention REST API options for interacting with the Fault Analysis Service, if available.
  • Clarify which tools are supported on which platforms and provide parity in instructions for Linux/macOS users.
  • Consider adding a table or section comparing usage across Windows, Linux, and macOS environments.
GitHub Create Pull Request
Service Fabric Learn about Azure Service Fabric application security ...ric/service-fabric-application-and-service-security.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation covers Service Fabric application security in a generally cross-platform manner, but several sections show Windows bias. Examples and references often focus on Windows tools and patterns (e.g., Active Directory, gMSA, BitLocker) with Linux equivalents either missing or relegated to TODOs. Windows-specific features are sometimes described before Linux options, and some security configuration examples (e.g., disk encryption) only link to Windows/PowerShell guides, leaving Linux users without clear guidance.
Recommendations
  • Provide explicit Linux examples and instructions alongside Windows ones, especially for disk encryption and service account management.
  • Add links to Linux-specific documentation where only Windows/PowerShell guides are referenced (e.g., encrypting disks on Linux clusters).
  • When mentioning Windows tools (e.g., BitLocker, gMSA), clarify their platform specificity and offer Linux alternatives or note limitations.
  • Ensure that examples and walkthroughs are balanced between Windows and Linux, or clearly indicate platform applicability.
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 page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all command-line examples using PowerShell and the Microsoft.ServiceFabric.Powershell.Http module. There are no CLI, Bash, or Linux-native instructions, nor any mention of cross-platform alternatives. The use of PowerShell and related modules is presented as the default and only method, which may create friction for Linux/macOS users who typically use Bash, Azure CLI, or REST APIs directly.
Recommendations
  • Add equivalent examples using Azure CLI (az sf cluster, az rest) or Bash/cURL for REST API calls.
  • Clarify whether the PowerShell module is required on all platforms, and if so, provide installation instructions for Linux/macOS (e.g., via PowerShell Core).
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users.
  • Where REST API is referenced, provide direct cURL or HTTP request examples instead of only PowerShell.
  • Reorder examples so that REST API or cross-platform methods are shown before or alongside PowerShell.
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 operations using PowerShell commands (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState), but does not offer equivalent Linux CLI or bash examples. The manual scaling sections consistently reference PowerShell as the primary tool, and do not mention Linux alternatives or cross-platform Service Fabric CLI usage. Windows/PowerShell instructions are presented first and exclusively, creating friction for Linux users who may not have access to PowerShell or may prefer bash/CLI workflows.
Recommendations
  • Add equivalent Linux/Bash/Service Fabric CLI examples for all PowerShell commands (e.g., show how to disable nodes, check node status, and remove node state using Linux tools or the Service Fabric CLI).
  • Explicitly mention cross-platform tools (such as Service Fabric CLI or REST API) where possible, and clarify which instructions are platform-specific.
  • Where PowerShell is referenced, provide a note or link to Linux instructions, or indicate if the operation can be performed via the Service Fabric CLI or REST API.
  • Reorder examples so that cross-platform or Linux instructions are presented alongside or before Windows/PowerShell examples, where appropriate.
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 code examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. All CLI/script examples use PowerShell, which is primarily a Windows tool. There are no Linux shell (bash/CLI) equivalents or guidance for Linux users. The PowerShell examples are presented for both instance-based and partition-based scaling, and appear before any mention of Linux compatibility. While the text notes that resource monitoring is supported for containerized applications on Linux, practical configuration examples and tooling guidance are Windows-centric.
Recommendations
  • Add equivalent CLI examples for Linux environments, such as using Azure CLI, Bash scripts, or REST API calls.
  • Explicitly document how Linux users can perform the same auto scaling configuration tasks, including any required tools or commands.
  • Clarify any limitations or differences in auto scaling configuration between Windows and Linux clusters.
  • If PowerShell is required for certain operations, state this clearly and provide alternatives or workarounds for Linux users.
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 demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets, with no mention of Linux or cross-platform CLI equivalents. The documentation references Windows-centric tools and patterns (PowerShell, Visual Studio) exclusively or before alternatives, and does not provide guidance for Linux/macOS users or Service Fabric clusters managed from non-Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform and supported on Linux/macOS.
  • Explicitly mention how Linux/macOS users can perform the same upgrade operations, including any differences in tooling or workflow.
  • Where PowerShell cmdlets are referenced, provide a parallel example using sfctl or Azure CLI, or link to relevant documentation for those tools.
  • Clarify any platform-specific limitations, and indicate when a feature or command is Windows-only.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page presents PowerShell and Visual Studio (Windows-centric tools) first and in more detail, with extensive parameter tables and examples. SFCTL (cross-platform CLI, especially for Linux/macOS) is covered later and with less detail. There are no explicit Linux/macOS command-line examples or walkthroughs in the main body, and the parameter tables for PowerShell/Visual Studio are much more comprehensive than for SFCTL. The 'Next steps' section lists Windows upgrade tutorials before Linux equivalents.
Recommendations
  • Present SFCTL (cross-platform CLI) examples and parameter tables alongside PowerShell/Visual Studio, not after them.
  • Provide explicit Linux/macOS command-line examples for SFCTL in the main documentation body.
  • Balance the detail level of SFCTL documentation to match that of PowerShell/Visual Studio, including parameter explanations and example usages.
  • Consider listing cross-platform tools (SFCTL, REST API) before or alongside Windows-specific tools in introductory sections.
  • In 'Next steps', alternate or group Linux/macOS and Windows tutorials to avoid implicit prioritization.
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 demonstrates a notable Windows bias. The only code example provided uses PowerShell, a Windows-centric tool, with no equivalent Linux or cross-platform CLI example. References to Windows-specific technologies (e.g., http.sys, Windows HTTP Server API) are present, and upgrade instructions link to Visual Studio and PowerShell tutorials, both Windows-focused, without mention of Linux alternatives. No Linux or cross-platform CLI (such as Azure CLI or Service Fabric CLI) examples or guidance are provided.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) or Azure CLI for Linux/macOS users.
  • Include notes or sections clarifying how Linux/macOS users can perform application upgrades, especially for clusters running on Linux nodes.
  • Where Windows-specific tools or APIs are mentioned (e.g., http.sys), clarify their applicability and provide Linux alternatives or limitations.
  • Balance tutorial links by including Linux/macOS upgrade guides if available.
GitHub Create Pull Request
Service Fabric Restoring backup in Azure Service Fabric ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-backup-restore-service-trigger-restore.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation for restoring backups in Azure Service Fabric is heavily focused on PowerShell-based workflows, with all CLI examples using PowerShell syntax and Windows-specific modules. There is no mention of Linux/macOS equivalents, nor are cross-platform REST API examples provided using tools like curl or Azure CLI. The documentation assumes the use of Windows tooling and does not address how Linux/macOS users can perform the same operations.
Recommendations
  • Provide REST API examples using cross-platform tools such as curl or httpie.
  • Include instructions for using Azure CLI where possible, as it is cross-platform.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required or if REST API calls can be made directly from any OS.
  • Add a section explicitly addressing Linux/macOS workflows for backup restore, including certificate handling and authentication.
  • If PowerShell is required, mention PowerShell Core (pwsh) compatibility on Linux/macOS, or provide alternatives.
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 provides code examples in C# and PowerShell only, with no mention of Linux-native tools, Bash, or cross-platform CLI usage. PowerShell is featured as the only command-line example, and is shown before any Linux alternatives (which are absent). There is no guidance for Linux/macOS users on how to perform equivalent operations, despite Service Fabric supporting Linux clusters.
Recommendations
  • Add Azure CLI examples for placement policy configuration, as Azure CLI is cross-platform.
  • Include Bash or shell script examples where applicable.
  • Clarify whether PowerShell examples are usable on Linux (via PowerShell Core), or provide alternative instructions for Linux environments.
  • Explicitly mention any differences or limitations when configuring placement policies on Linux clusters.
  • Consider reordering examples so that cross-platform methods (e.g., Azure CLI) are shown 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 describes periodic backup configuration for Azure Service Fabric, and while most of the content is platform-neutral, the only on-premises backup storage example provided is for Windows file shares using Windows authentication patterns (UNC paths, Integrated Windows Authentication, username/password). There is no mention of Linux-compatible storage options (such as NFS or SMB mounts from Linux), nor are Linux authentication patterns or examples provided for on-premises clusters.
Recommendations
  • Add examples for configuring backup storage using Linux-compatible file shares, such as NFS mounts, and document any requirements or limitations.
  • Clarify whether file share backup storage supports Linux nodes and, if so, provide Linux-specific configuration guidance (e.g., mounting SMB/CIFS shares on Linux, using Kerberos or other authentication methods).
  • If Service Fabric on Linux does not support file share backup, explicitly state this to avoid confusion.
  • Ensure that any references to authentication methods (e.g., Integrated Windows Authentication) are accompanied by Linux alternatives or a note about platform support.
GitHub Create Pull Request
Service Fabric Azure Service Fabric infrastructure as Code Best Practices ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-best-practices-infrastructure-as-code.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Service Fabric clusters, but PowerShell is given a dedicated section and is used for cluster upgrade operations without Linux/macOS equivalents. Windows-specific tools and registry settings are mentioned for VM upgrade configuration, with no Linux alternatives or parity. Windows configuration details are presented before Linux, and some upgrade instructions are Windows-centric.
Recommendations
  • Provide Bash or Linux shell equivalents for cluster upgrade operations currently shown only in PowerShell.
  • Include Linux-specific VM configuration guidance, such as disabling automatic updates, alongside Windows registry and osProfile settings.
  • Clarify which steps are Windows-only and offer Linux alternatives or explicitly state when Linux users should use different procedures.
  • Balance example order so that Linux and Windows instructions are presented with equal prominence.
  • For sections mentioning registry keys or Windows-specific configuration, add notes or links for Linux system management best practices.
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: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides several examples and references that prioritize Windows tools and patterns, such as PowerShell and Windows-specific ARM templates, before or instead of Linux equivalents. Some explanations and port usage are described primarily in the context of Windows (e.g., netsh commands, PowerShell APIs), and references to Linux are less detailed or appear after Windows examples. There are sections where Linux-specific guidance is minimal or missing, especially regarding command-line examples and tooling.
Recommendations
  • Provide Linux CLI (az, bash) examples alongside or before PowerShell examples for cluster management and networking tasks.
  • Include references to Linux-specific ARM templates and sample configurations, not just Windows-focused ones.
  • Clarify when port ranges or networking rules differ for Linux clusters, and provide explicit Linux guidance (e.g., how to check ephemeral ports on Linux).
  • Mention Linux equivalents for Windows tools (e.g., netstat or ss instead of netsh), and provide Linux-specific troubleshooting steps.
  • Balance references to Windows and Linux in introductory and summary sections to avoid Windows-first impression.
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 guidance on Azure Service Fabric node types and VM scale sets, but exhibits some Windows bias. The JSON snippet uses a Windows-style dataPath (D:\\SvcFab) without a Linux equivalent, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks and tools. There are no explicit Linux examples or guidance for connecting to Linux nodes or managing Linux-specific configurations.
Recommendations
  • Provide Linux-specific examples for configuration, such as using a Linux-style dataPath (e.g., /var/svcfab) in the extension snippet.
  • Include guidance or links for SSH access to Linux nodes, analogous to the RDP/PowerShell instructions for Windows.
  • Add parity in 'Next steps' for Linux users, such as scripts or documentation for changing SSH port ranges and admin credentials on Linux VMs.
  • Clarify when instructions are Windows-only and offer Linux alternatives where possible.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides several code examples for configuring and managing Service Fabric clusters, with a notable emphasis on Windows-centric tools and patterns. PowerShell is the only CLI/scripting example shown for service creation and updates, and the XML configuration examples use <WindowsServer> as the infrastructure type. There is no mention of Linux-specific configuration, tools, or command-line examples, even though Service Fabric supports Linux clusters. JSON-based configuration examples are present, which are cross-platform, but the lack of Linux CLI or configuration context creates friction for Linux users.
Recommendations
  • Add equivalent Bash/CLI examples for service creation and updates (e.g., using sfctl for Linux).
  • Include Linux-specific configuration examples, such as using <Linux> in ClusterManifest.xml, or clarify when examples are Windows-only.
  • When showing PowerShell, also provide Linux/Bash alternatives where possible.
  • Clarify in the text when examples are cross-platform versus Windows-specific.
  • If certain features or configuration options are only available on Windows, explicitly state this.
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 ⚠️ missing_linux_example
Summary
The documentation provides a health report example using PowerShell (Get-ServiceFabricPartitionHealth) with a Windows-style command prompt, but does not offer equivalent Linux/macOS CLI examples or mention cross-platform tooling. The rest of the content is platform-neutral and focuses on Service Fabric concepts.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users, e.g., 'sfctl partition health --partition-id ...'.
  • Explicitly mention that Service Fabric management commands can be run on Linux/macOS using sfctl, and link to relevant cross-platform tooling documentation.
  • Where PowerShell is used, clarify if the command is Windows-only, and provide alternative instructions for other platforms.
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 ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides PowerShell examples for creating and updating Service Fabric services, but does not offer equivalent Linux shell (e.g., Bash/CLI) examples. PowerShell is primarily a Windows tool, and its exclusive use in examples creates friction for Linux/macOS users. There is no mention of Service Fabric CLI (sfctl) or Bash alternatives, which are available for cross-platform usage.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which works on Linux/macOS, for all PowerShell commands shown.
  • Explicitly mention cross-platform tooling and provide guidance for Linux/macOS users.
  • Reorder examples so that CLI/Bash and PowerShell are presented together or in parallel, rather than PowerShell-only.
  • Clarify any platform-specific limitations if certain features are only available via PowerShell.
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 frequently references Windows Server clusters and provides links and instructions specifically for securing standalone clusters on Windows. While it mentions that Azure clusters and standalone clusters on Windows can use certificate or Windows security, there is little to no explicit guidance or examples for standalone Linux clusters. The documentation does state that the concept of creating secure clusters is the same for Linux and Windows, but does not provide Linux-specific instructions, examples, or references.
Recommendations
  • Add explicit instructions and examples for securing standalone Linux Service Fabric clusters, including certificate management and configuration steps.
  • Provide links to Linux-specific documentation or resources where available.
  • Clarify any differences or limitations for Linux clusters compared to Windows clusters, especially in sections that currently only reference Windows Server.
  • Ensure that examples and guidance are presented in a way that is platform-neutral or that both platforms are covered equally.
GitHub Create Pull Request
Service Fabric Upgrade an Azure Service Fabric standalone cluster ...ce-fabric/service-fabric-cluster-upgrade-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for upgrading an Azure Service Fabric standalone cluster exhibits moderate Windows bias. References and links are primarily to Windows Server-specific upgrade guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md'), and the Patch Orchestration Application is described only for Windows. There are no Linux-specific instructions, examples, or mentions of Linux equivalents, which may create friction for users managing Service Fabric clusters on Linux.
Recommendations
  • Add explicit guidance or links for upgrading Service Fabric clusters on Linux, if supported.
  • Include Linux-specific examples and configuration instructions alongside Windows examples.
  • Clarify whether certain features (e.g., Patch Orchestration Application) are Windows-only, and provide Linux alternatives or note their absence.
  • Ensure that references to upgrade guides and configuration documentation include both Windows and Linux versions, if available.
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 page provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI examples (such as Azure CLI or Bash scripts) are provided. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and there is no explicit guidance for Linux users on how to perform these tasks.
Recommendations
  • Add Azure CLI examples for service creation and metric management, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets or instructions for Linux users where relevant.
  • Explicitly mention cross-platform tools and workflows, clarifying which commands are available on Linux/macOS.
  • If PowerShell is required, note that PowerShell Core is available on Linux/macOS and provide usage instructions for those platforms.
GitHub Create Pull Request
Service Fabric Service sensitivity ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides PowerShell-based examples for configuring service sensitivity and maximum load, and references the PowerShell API for dynamic operations. There are no equivalent examples or guidance for Linux/macOS users (e.g., Azure CLI, REST API, or cross-platform scripting), and PowerShell is a Windows-centric tool in the context of Service Fabric. This creates friction for non-Windows users.
Recommendations
  • Add Azure CLI or REST API examples for all operations currently shown with PowerShell.
  • Explicitly state whether these operations can only be performed with PowerShell or if cross-platform alternatives exist.
  • If PowerShell Core (cross-platform) is supported, clarify this and provide installation guidance for Linux/macOS users.
  • Provide guidance or links for Linux/macOS users on how to perform equivalent tasks.
GitHub Create Pull Request
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for scaling Azure Service Fabric standalone clusters demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific instructions. There are no Linux or cross-platform examples, nor is there mention of Linux tooling or procedures for scaling standalone clusters on non-Windows environments.
Recommendations
  • Include equivalent Linux instructions or examples, such as using Service Fabric CLI (sfctl) or REST APIs for cluster management.
  • Clarify whether standalone clusters can be run and managed on Linux, and if so, provide guidance for those scenarios.
  • If PowerShell is required, note any cross-platform support or alternatives for Linux/macOS users.
  • Add links to Linux-specific documentation or explicitly state if scaling standalone clusters is only supported on Windows.
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
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides upgrade guidance for Azure Service Fabric clusters and generally presents platform-neutral instructions. However, in sections about managing certificates and opening application ports, PowerShell is mentioned before Azure CLI, and no explicit Linux/macOS command examples are provided. The OS image upgrade section links only to Windows-specific patching guidance, suggesting a Windows-first approach and omitting Linux node upgrade details. References to NTLM settings and FileStoreService also imply Windows-centric scenarios without clarifying Linux applicability.
Recommendations
  • Provide explicit Azure CLI examples alongside PowerShell, especially for certificate management and port configuration, and clarify cross-platform compatibility.
  • Include guidance or links for upgrading OS images on Linux-based Service Fabric clusters, if supported.
  • Clarify which features or steps are Windows-only and which apply to Linux clusters to avoid confusion.
  • Where Windows-specific tools or terminology (e.g., NTLM, FileStoreService) are used, note their relevance or alternatives for Linux 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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides code examples for scaling Service Fabric services primarily using PowerShell and C#, both of which are most commonly associated with Windows environments. There are no equivalent Linux shell (bash/CLI) examples, and Windows-centric tools (PowerShell cmdlets) are referenced first and exclusively. This creates friction for Linux users, who may not use PowerShell or may prefer bash/CLI commands. The documentation does mention platform differences in logging, but does not provide Linux-specific operational guidance or examples for scaling tasks.
Recommendations
  • Include equivalent Linux CLI (bash/az CLI) examples for all PowerShell commands shown.
  • Explicitly mention how Linux users can perform the same scaling operations (e.g., using Azure CLI, REST API, or Service Fabric CLI).
  • Where PowerShell cmdlets are referenced, add links or notes about Linux alternatives.
  • Consider reordering examples so that Windows and Linux approaches are presented side-by-side, or Linux examples are not always secondary.
  • Add a section or callout for Linux-specific operational considerations beyond logging (e.g., service management, scaling commands).
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 for the Azure Service Fabric application resource model demonstrates a notable Windows bias. All command-line deployment and management examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without mentioning or providing equivalent Azure CLI commands. The application packaging workflow is shown using Visual Studio, a Windows-centric tool, with no alternative for Linux/macOS users. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add Azure CLI equivalents for all PowerShell deployment and management commands (e.g., az deployment group create, az resource show, az resource delete).
  • Provide instructions for packaging Service Fabric applications using cross-platform tools (such as dotnet CLI or SFCTL) instead of only Visual Studio.
  • Include screenshots or steps for Linux/macOS environments where relevant (e.g., zipping application packages, uploading to Azure Storage via CLI or portal).
  • Clearly indicate which steps are platform-agnostic and which require Windows-specific tooling, offering alternatives where possible.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides several examples and instructions using Windows-centric tools and patterns, such as PowerShell commands and ApplicationManifest.xml (Visual Studio), without offering equivalent Linux-friendly alternatives. While the page notes Linux support is limited, it does not provide Linux-specific guidance for tasks like setting DNS names or managing services, and Windows methods are presented first and in more detail.
Recommendations
  • Add Linux-specific instructions for setting DNS names, such as using CLI commands (az CLI, sfctl) or editing YAML/JSON manifests for containerized services.
  • Include examples for Linux users, such as using Bash scripts or Linux-native tools to manage Service Fabric services.
  • Clarify which steps are Windows-only and which are applicable to Linux clusters, especially in sections about ApplicationManifest.xml and PowerShell.
  • Provide guidance on managing DNS service for Linux clusters outside the Azure portal, since portal support is unavailable.
  • Consider reordering examples so that Linux and Windows approaches are presented with equal prominence.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only PowerShell-based examples for reporting and querying Service Fabric health, with no equivalent Linux/macOS CLI or REST API examples. It references PowerShell cmdlets and omits cross-platform alternatives, which may create friction for users managing Service Fabric clusters from Linux or macOS environments.
Recommendations
  • Add equivalent examples using 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.
  • Explicitly mention that PowerShell cmdlets are Windows-only and provide guidance for Linux/macOS users.
  • Where APIs are referenced, link to documentation showing usage from multiple platforms.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page references PowerShell as the primary example for interacting with Service Fabric clusters and retrieving the cluster manifest. It mentions Visual Studio (a Windows-centric tool) for publishing, and links to PowerShell-based deployment guides. There are no Linux/macOS CLI or script examples, nor are cross-platform alternatives (such as Azure CLI, Bash, or Linux tools) mentioned. This creates friction for users on non-Windows platforms.
Recommendations
  • Add examples using Azure CLI or REST API for retrieving the cluster manifest and configuring the ImageStoreConnectionString, demonstrating usage on Linux/macOS.
  • Include references to cross-platform deployment workflows, such as using Bash scripts or Azure CLI, alongside PowerShell and Visual Studio.
  • Clarify which steps are platform-agnostic and which are Windows-specific, helping users on Linux/macOS understand their options.
  • Link to documentation for Linux/macOS Service Fabric SDK usage where relevant.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides a broad overview of Azure Service Fabric, covering both Windows and Linux support. However, there is a noticeable Windows bias: Windows-specific tools and processes (e.g., PowerShell cmdlets, Visual Studio, Windows services like FabricHost.exe) are mentioned first or exclusively in several sections. Examples and links for cluster creation and management often default to Windows, with Linux equivalents either omitted or referenced only in passing. Some features (e.g., standalone clusters) are explicitly called out as Windows-only, but Linux users are left without guidance or examples for equivalent tasks.
Recommendations
  • Ensure Linux equivalents are mentioned alongside Windows tools (e.g., Bash scripts, Linux CLI usage) and provide direct links to Linux-specific documentation where available.
  • Present examples for both Windows and Linux platforms in parallel, rather than defaulting to Windows-first ordering.
  • Clarify in each section which features are Windows-only and provide alternative guidance or workarounds for Linux users where possible.
  • Expand the 'Next steps' section to include Linux cluster creation and management guides.
  • Add explicit examples and walkthroughs for Linux environments, especially for common tasks like cluster creation, management, and health monitoring.
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 on the Azure Service Fabric hosting model provides conceptual information applicable to all platforms, but operational examples and tooling references are heavily biased toward Windows and PowerShell. The only command-line example for creating a service uses PowerShell syntax, and all linked operational references (e.g., querying, reporting health, restarting code packages) point to PowerShell cmdlets. There are no CLI or Linux-native examples (such as Azure CLI, Bash, or REST via curl), nor is there guidance for users on Linux or macOS clusters. The C# example is cross-platform, but the overall pattern prioritizes Windows tooling and omits Linux parity.
Recommendations
  • Add Azure CLI or REST API examples for service creation and management tasks, especially for operations currently shown only with PowerShell.
  • Explicitly mention cross-platform management options, such as using Azure CLI, REST, or SDKs from Linux/macOS.
  • Where PowerShell is referenced, clarify if the operation can be performed from Linux/macOS (e.g., via Azure CLI or REST), and provide equivalent examples.
  • Include a short section or note on managing Service Fabric clusters from non-Windows environments, with links to relevant documentation.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page exhibits a moderate Windows bias by prioritizing PowerShell and Visual Studio workflows, mentioning Windows-centric tools and scripts first, and lacking explicit Linux/macOS command examples. While sfctl and Jenkins are referenced (which are cross-platform), the examples and guidance are skewed toward Windows users, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS command-line examples for creating Service Fabric applications, such as using sfctl from bash or zsh.
  • Include sample shell scripts (e.g., install.sh) for parameter substitution and deployment on Linux/macOS.
  • Clarify which tools and scripts are cross-platform and provide parity guidance (e.g., alternatives to Deploy-FabricApplication.ps1 for Linux).
  • Reorder examples to present cross-platform or Linux/macOS options before or alongside Windows/PowerShell examples.
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 demonstrates a notable Windows bias: it references the Windows Server 2016 Container Sample as the basis for its examples, frequently mentions Windows-specific tools (such as 'winver' for OS build detection), and describes container volume mounts using Windows-style paths (e.g., 'c:\VolumeTest\Data'). There is no mention of Linux container samples, Linux path formats, or Linux-specific configuration patterns. While some notes acknowledge Linux (e.g., certificate handling differences), the examples and guidance are overwhelmingly Windows-centric.
Recommendations
  • Include equivalent Linux-based manifest examples, referencing the Linux container sample repository if available.
  • Show volume mount examples using Linux path formats (e.g., '/mnt/data') alongside Windows paths.
  • When describing OS build detection, mention the Linux equivalent (e.g., 'cat /etc/os-release' or 'uname -r') for determining OS version.
  • Clarify which manifest elements or features are cross-platform and which are Windows-only.
  • Provide links to Linux container documentation and samples in the introduction and feature tables.
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 comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core integration with Azure Service Fabric. However, there is a notable Windows bias in several areas: HTTP.sys (a Windows-only technology) is discussed in detail and presented first in some sections, with explicit mention that it only works on Windows. There are no explicit Linux/macOS-specific examples or troubleshooting notes, and some configuration patterns (such as Endpoint registration and port sharing) are described primarily in the context of Windows tools and APIs (e.g., netsh, HTTP.sys kernel driver). While Kestrel is recommended for cross-platform scenarios, Linux users may find the documentation less tailored to their environment, especially regarding ServiceManifest.xml configuration, port management, and deployment nuances.
Recommendations
  • Add explicit Linux/macOS examples for ServiceManifest.xml configuration, deployment, and troubleshooting (e.g., how to manage ports and firewall rules on Linux nodes).
  • Clearly separate Windows-only sections (HTTP.sys) from cross-platform guidance, and consider presenting Kestrel (cross-platform) examples before HTTP.sys (Windows-only) examples.
  • Include notes or links to Linux/macOS-specific Service Fabric documentation, especially for common tasks like endpoint configuration, port assignment, and debugging.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux/macOS equivalents or clarify that these steps are not required on non-Windows platforms.
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_tools ⚠️ missing_linux_example
Summary
The documentation page for Replica soft delete in Service Fabric is heavily focused on PowerShell-based APIs and tools (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica), with no mention of Linux CLI equivalents or cross-platform usage patterns. All command and API examples reference PowerShell cmdlets, and there is no guidance for Linux/macOS users on how to perform these operations using Service Fabric CLI (sfctl) or REST APIs. This creates friction for non-Windows users, even though Service Fabric itself is cross-platform.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for all PowerShell cmdlets mentioned (e.g., remove replica, restore replica, get replica status).
  • Explicitly state whether the new APIs (such as Restore Replica) are available via sfctl or REST, and provide usage examples.
  • Clarify any platform limitations (if any) for these APIs, and if there are none, ensure Linux/macOS users are guided on how to perform the same tasks.
  • Where screenshots or command outputs are shown, include cross-platform examples or note any differences.
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_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page for Service Fabric reliable services app manifest examples demonstrates a moderate Windows bias. It references Windows-specific tools and patterns, such as .bat scripts for setup and mentions the ServiceFabric PowerShell module for service creation. The examples and explanations assume Windows conventions (e.g., NETWORKSERVICE account, .exe executables, .bat scripts) and do not provide Linux equivalents or guidance for cross-platform scenarios. Linux-specific details, such as shell script usage or Linux service accounts, are missing.
Recommendations
  • Add Linux-specific examples, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint, and explain how to configure working folders and permissions for Linux deployments.
  • Mention and provide examples for using Linux service accounts (e.g., 'sfuser') and clarify differences in account types and permissions between Windows and Linux clusters.
  • Reference Linux-compatible deployment tools (such as Azure CLI or Service Fabric CLI) alongside PowerShell, and provide command examples for both platforms.
  • Explicitly state which manifest elements and patterns are cross-platform, and note any Windows-only features or behaviors.
  • Where .exe or .bat files are referenced, include parallel examples for Linux (.sh, ELF binaries) and clarify platform-specific requirements.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation mentions both Windows and Linux support for Service Fabric, but Windows development tools (Visual Studio, PowerShell, .NET SDK) are listed before Linux equivalents (Eclipse, Yeoman, Java SDK). The quickstart link points to a .NET/Windows-focused guide, and Windows development is described first. There are no explicit Linux examples or Linux-first instructions, and PowerShell is referenced as the main automation tool for Windows, with no Linux CLI or shell alternatives mentioned.
Recommendations
  • Present Windows and Linux development options in parallel, rather than listing Windows first.
  • Provide links to both Windows and Linux quickstart guides in the 'Next steps' section.
  • Mention Linux CLI tools (e.g., Bash, Azure CLI) alongside PowerShell for automation.
  • Include examples or references for both .NET and Java development paths, and clarify cross-platform support.
  • Ensure that Linux-specific documentation is as discoverable and detailed as Windows documentation.
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 for 'Networking patterns for Azure Service Fabric' demonstrates a Windows bias by exclusively providing PowerShell-based deployment instructions and examples, referencing Windows command-line patterns (e.g., RDP, C:\ paths, ping commands in Windows syntax), and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). The examples and deployment workflows assume a Windows environment, which may create friction for users on other platforms.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Include Linux/macOS-specific notes for accessing VMs (e.g., using SSH instead of RDP, Linux ping syntax).
  • Clarify that Service Fabric clusters can be managed from Linux/macOS and link to relevant cross-platform tooling documentation.
  • Use generic file paths or show both Windows and Linux path formats in examples.
  • Explicitly state platform requirements or parity where applicable.
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 PowerShell examples for health reporting and cluster connection, but does not offer equivalent Linux/macOS CLI examples or mention cross-platform alternatives. PowerShell commands are shown first and exclusively for command-line usage, which may create friction for users on non-Windows platforms. REST and API methods are mentioned, but practical, platform-agnostic CLI examples are missing.
Recommendations
  • Add equivalent CLI examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that PowerShell commands are for Windows and provide guidance for Linux/macOS users.
  • Reorder examples so that REST and CLI methods are presented before or alongside PowerShell, emphasizing cross-platform options.
  • Include notes or links to documentation for Service Fabric CLI installation and usage on Linux/macOS.
GitHub Create Pull Request
Service Fabric Configure the upgrade of a Service Fabric application ...abric/service-fabric-visualstudio-configure-upgrade.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 is heavily focused on Windows-specific tools (Visual Studio and PowerShell) for configuring and upgrading Service Fabric applications. All examples and instructions reference Visual Studio dialogs and PowerShell cmdlets, with no mention of Linux/macOS alternatives or cross-platform CLI workflows. This creates friction for users on non-Windows platforms, as they are not provided guidance for performing upgrades outside of Windows environments.
Recommendations
  • Add equivalent instructions for upgrading Service Fabric applications using Azure CLI or Service Fabric CLI (sfctl), which are cross-platform.
  • Include examples of configuring upgrade parameters and health policies using command-line tools available on Linux/macOS.
  • Clarify which steps are Windows-only and provide links or references to Linux/macOS documentation where available.
  • If Visual Studio is required, explicitly state that these instructions are for Windows users and link to alternative workflows for other platforms.
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
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 provides Azure CLI, PowerShell, and ARM template examples for creating scale sets with Availability Zones. While the CLI and ARM template examples are cross-platform, PowerShell (Windows-only) is given equal prominence and detailed examples. The ARM template section links to both Linux and Windows quickstart guides, but the main walkthroughs and update instructions do not provide explicit Linux shell (bash) or macOS examples. Windows/PowerShell tooling is mentioned before Linux equivalents in some sections, and Linux-specific considerations (such as SSH keys or Linux admin users) are not highlighted outside the CLI example.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users, especially for update operations and scale set management.
  • Clarify in each section which commands are cross-platform and which are Windows-only.
  • Ensure Linux and Windows quickstart links are presented together and with equal prominence.
  • Consider adding notes or callouts for Linux-specific configuration steps (e.g., SSH keys, admin username conventions).
  • Where PowerShell is used, provide equivalent bash/CLI commands for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.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 provides both Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows) examples are often presented before CLI (Linux/macOS compatible) examples. In several sections, only PowerShell is shown for certain operations, or CLI examples are less detailed. Some verification steps use PowerShell exclusively, and there are places where Linux-specific guidance is missing or less emphasized.
Recommendations
  • Ensure that CLI examples are always present and as detailed as PowerShell examples for every operation.
  • Present CLI (cross-platform) examples before PowerShell examples to avoid implicit Windows prioritization.
  • Where PowerShell is used for querying or updating resources, provide equivalent CLI commands and highlight their parity.
  • Explicitly note that CLI commands work on Linux/macOS and Windows, and encourage their use for cross-platform scenarios.
  • Review all verification and troubleshooting steps to ensure Linux users are not left out or forced to use Windows tools.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are exclusively Windows-focused, with all sample code using Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows), and there are no PowerShell examples for Linux VM creation. Additionally, in the full parameter set, network security rules are configured for RDP (port 3389), which is Windows-specific, and the PowerShell code always prompts for a password (typical for Windows VMs). The CLI examples do mention Linux and SSH keys, but the PowerShell sections do not provide Linux parity. REST and Portal instructions do cover both OS types, but Windows examples and terminology often appear first or exclusively in PowerShell sections.
Recommendations
  • Add PowerShell examples for creating Linux VMs, including usage of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • In PowerShell networking examples, include security rules for SSH (port 22) alongside or instead of RDP (port 3389) when demonstrating Linux VM creation.
  • Ensure that both CLI and PowerShell tabs consistently show both Linux and Windows scenarios, or clearly indicate when an example is OS-specific.
  • In summary and instructional text, avoid implying that PowerShell is only for Windows VM creation; clarify its cross-platform capabilities.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
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 network setup and VM configuration. CLI examples are brief and do not cover equivalent advanced scenarios. PowerShell is a Windows-centric tool, and its prominence and depth here may disadvantage Linux/macOS users. Additionally, PowerShell examples are shown before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
  • Expand Azure CLI examples to include full VM creation workflows, including network setup, matching the detail of PowerShell examples.
  • Add Bash shell scripting examples for advanced scenarios, especially for users on Linux/macOS.
  • Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first impression.
  • Clarify that PowerShell examples are primarily for Windows users, and provide links to equivalent Linux/macOS guidance where possible.
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 towards Windows: Windows container runtimes are listed in more detail, Windows scenarios (such as IIS lift and shift) are described first and more extensively, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned. Linux is covered, but Windows examples and scenarios tend to appear first or receive more detail.
Recommendations
  • Ensure Linux scenarios (e.g., Apache/Nginx lift and shift, Linux-specific microservices) are described with equal detail and prominence as Windows scenarios.
  • List Linux and Windows container runtimes/tools in parallel, with equal detail and clarity.
  • Alternate the order of Linux and Windows examples in quickstart/tutorial links to avoid Windows-first presentation.
  • Provide Linux equivalents for Windows-specific scenarios (e.g., mention using Apache or NGINX containers for web apps on Linux).
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for Azure Service Fabric container image management shows mild Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions, and no Linux container image examples (e.g., Ubuntu, Alpine) are provided. The examples and descriptions focus on Windows images first, and there is no explicit mention of Linux-specific considerations or parity.
Recommendations
  • Include examples of Linux container images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting and explanations.
  • Clarify whether the cleanup features apply equally to Linux-based Service Fabric clusters and containers.
  • Add a note or section about Linux container image management, including any differences or additional settings relevant to Linux environments.
  • Provide parity in documentation by listing both Windows and Linux base images in examples and default behaviors.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows file paths (e.g., installation of schema definitions in 'C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd') and by mentioning Visual Studio as a primary tool for packaging and deploying guest executables. There are no explicit Linux/macOS examples, nor are Linux-specific tools or patterns discussed. However, the page does not state that Service Fabric guest executables are Windows-only, and it mentions that any type of code (Node.js, Java, C++) can be run, implying cross-platform support.
Recommendations
  • Add Linux/macOS equivalents for file paths and installation locations (e.g., where the Service Fabric SDK and schema files are installed on Linux/macOS).
  • Include command-line examples using cross-platform tools (such as Azure CLI or PowerShell Core) and clarify which steps differ on Linux/macOS.
  • Mention alternative IDEs or editors (such as VS Code) and provide instructions for packaging and deploying guest executables without Visual Studio.
  • Explicitly state any platform limitations for Service Fabric guest executables if they exist.
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 Service Fabric CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. PowerShell examples are presented first and in greater detail, which may suggest a Windows-first approach. However, CLI examples are included and are cross-platform. No Linux-specific tools or patterns are missing, but the ordering and emphasis may create minor friction for Linux/macOS users.
Recommendations
  • Present CLI (sfctl) examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that sfctl works on Linux/macOS and provide installation instructions or a link.
  • Add a note clarifying that PowerShell commands are for Windows users, while sfctl is recommended for Linux/macOS.
  • Consider balancing the level of detail between PowerShell and CLI sections.
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 generally describes Service Fabric concepts in a cross-platform manner, but there are subtle signs of Windows bias. Windows-specific tools and processes (such as references to auto-start Windows services and EXE/DLL files) are mentioned before or more prominently than their Linux equivalents. The description of node startup references Windows services and executables without clarifying Linux equivalents or behaviors. However, the page does acknowledge Linux support in several places and does not present critical sections that are Windows-only.
Recommendations
  • Clarify how Service Fabric node processes are started and managed on Linux, including any differences from Windows (e.g., systemd services vs. Windows services).
  • When referencing executable formats (EXE/DLL), mention Linux equivalents (e.g., ELF binaries, .so files) to reinforce cross-platform support.
  • Where Windows-specific terms are used (such as FabricHost.exe as a Windows service), add a note or parallel explanation for Linux environments.
  • Ensure examples and terminology are presented in a platform-neutral order, or explicitly state differences for each OS where relevant.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence and detail, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of a dedicated PowerShell tab and example may signal a slight Windows bias, especially since Linux users are less likely to use PowerShell.
Recommendations
  • Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for cross-platform usage.
  • Add a note that Azure CLI works natively on Linux/macOS, while PowerShell requires installation and configuration on those platforms.
  • Consider including Bash or shell scripting examples for Linux users, if relevant.
  • Explicitly state platform compatibility for each tool in the documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides usage instructions for Spot Placement Score via Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is given its own section and is presented after the CLI, but both CLI and PowerShell are covered. There is a slight Windows bias in that PowerShell is called out specifically, and the ordering of examples (portal, REST, CLI, PowerShell) puts PowerShell before any Linux/macOS-specific shell scripting examples. However, Azure CLI is cross-platform and is documented with equal detail. No examples are missing for Linux/macOS users, and the REST API is platform-agnostic.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider adding a Bash shell script example for Linux/macOS users to demonstrate calling the REST API directly (e.g., with curl), especially for automation scenarios.
  • Explicitly state that PowerShell examples are for users who prefer PowerShell, and that equivalent functionality is available via CLI and REST API on all platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but there are subtle signs of Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and Linux-specific migration steps or examples (e.g., handling Linux package manager connectivity) are referenced only briefly and without concrete examples. There are no explicit Linux CLI or shell script examples, and the only command-line example shown uses Azure CLI, which is cross-platform, but does not demonstrate Linux-specific patterns or considerations.
Recommendations
  • Add explicit Linux migration scenarios and examples, such as handling Linux VM activation, package manager connectivity, and OS-specific extension installation.
  • Include Linux-focused CLI or shell script examples alongside Azure CLI and PowerShell references.
  • When listing outbound connectivity requirements, provide Linux scenarios with equal detail and order as Windows (e.g., mention Linux package manager access before or alongside Windows activation).
  • Ensure that any references to scripts or templates include both PowerShell and Bash examples where applicable.
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 both Azure CLI and PowerShell examples for configuring, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are included and shown alongside CLI and ARM template examples, which may indicate a slight Windows bias. In several sections, PowerShell is presented immediately after CLI, and before ARM template examples, which could be interpreted as a 'Windows first' ordering. All CLI examples use Azure CLI, which is cross-platform, and there are no exclusive Windows tools or patterns. No Linux-specific examples (such as Bash scripts) are provided, but the CLI commands are suitable for Linux/macOS users.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider adding a short Bash script example for Linux users, or clarify that the CLI examples are intended for all platforms.
  • Where PowerShell is shown, clarify that it is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Ensure ordering of examples does not consistently favor Windows/PowerShell over CLI/ARM template.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but in several places, Windows/PowerShell examples are presented before Linux equivalents. The PowerShell examples are detailed and use Windows-specific cmdlets (e.g., Add-AzVmssExtension, Update-AzVmssInstance), and the extension type defaults to ApplicationHealthWindows in some examples. While Linux is supported and shown, there is a slight preference for Windows/PowerShell tools and ordering, which may create minor friction for Linux users.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel tabs or with equal prominence, ideally listing Linux/Bash examples first in some sections.
  • Explicitly clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in extension configuration examples, and provide a Linux-specific example for the REST API payload.
  • Add more context or links for Linux users, such as troubleshooting tips specific to Linux environments.
  • Where possible, use generic or cross-platform CLI examples before platform-specific PowerShell ones.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
While the documentation is focused on a Linux-specific Azure VM extension, it provides both Azure PowerShell and Azure CLI deployment instructions. However, PowerShell examples and troubleshooting commands are presented before CLI equivalents, and PowerShell-specific warnings are included. This ordering and emphasis may create friction for Linux users, who are more likely to use Azure CLI or native Linux tools.
Recommendations
  • Present Azure CLI examples before PowerShell examples in all sections, as CLI is more commonly used on Linux.
  • Add explicit notes clarifying that PowerShell is optional and primarily for users on Windows or those who prefer it.
  • Where troubleshooting commands are shown, list Azure CLI commands first and ensure parity in troubleshooting guidance.
  • Consider removing PowerShell-specific warnings from the main flow, or move them to a dedicated section for Windows users.
  • Highlight Linux-native workflows and tools (e.g., bash scripting, systemd integration) where relevant.
GitHub Create Pull Request
Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page is focused on time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and link to Windows documentation before fully addressing Linux-specific mechanisms. All configuration, troubleshooting, and example commands are Linux-centric, with only a single PowerShell snippet shown for base64 encoding cloud-init data (which is relevant for Azure ARM template usage, not time sync itself). No Linux examples are missing, and no Windows tools are recommended for Linux VM management.
Recommendations
  • Move or minimize Windows Server 2016 time sync discussion to a background or context section, making it clear that the rest of the page is Linux-focused.
  • Add a brief note explaining why Windows time sync improvements are relevant to Linux VM users (e.g., because Azure hosts run Windows Server and this affects host time accuracy).
  • Consider providing a Linux shell command alternative for base64 encoding cloud-init data, since the PowerShell example may not be directly usable by Linux/macOS users.
  • Ensure that all actionable steps and examples remain Linux-centric and that any Windows references are clearly contextual/background.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit Linux shell (bash) example. The CLI example uses an Ubuntu image, but does not show Linux-specific shell usage or mention Linux tooling. The PowerShell section is detailed and uses Windows-centric SDK objects, while Linux users are expected to use the CLI or ARM templates without further guidance. The order of presentation (CLI, then PowerShell) is neutral, but the lack of explicit Linux shell examples and the presence of detailed PowerShell instructions indicate a mild Windows bias.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users, showing how to use az vm create and az vm list-skus in a Linux terminal.
  • Clarify that Azure CLI commands work on all platforms and provide notes or examples for Linux/macOS environments.
  • Reduce reliance on PowerShell SDK object manipulation, or provide equivalent scripting examples for Linux (e.g., using Azure CLI with jq or other Linux tools).
  • Consider presenting CLI and ARM template examples before PowerShell, or grouping them by platform.
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: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides parity for both Linux and Windows VMs in terms of feature applicability and CLI/PowerShell/Portal/ARM template instructions. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In some sections, RDP (Windows) is mentioned before SSH (Linux) when verifying VM access. Additionally, the template deployment steps use PowerShell for ARM template deployment, without mentioning Bash or cross-platform alternatives. The documentation does mention Linux-specific validation (SBInfo tool), but overall, Windows tools and patterns are slightly prioritized.
Recommendations
  • In ARM template deployment sections, provide Bash/az CLI examples for deploying templates, not just PowerShell.
  • When listing access methods, alternate or list SSH (Linux) before RDP (Windows) in some places.
  • Explicitly mention that all CLI and template steps work on Linux/macOS, and provide sample commands for Bash where PowerShell is shown.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for Linux/macOS users.
GitHub Create Pull Request