Service Fabric

407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2475 issues found
Showing 1101-1125 of 2475 flagged pages
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides numerous PowerShell-based deployment examples and references Windows-centric tools (e.g., RDP, 'C:\' paths, PowerShell commands) without offering equivalent Linux/macOS CLI (Azure CLI) or SSH examples. Windows tools and patterns are mentioned first and exclusively, and there are no Linux/macOS-specific instructions or parity for key deployment steps.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all deployment steps.
  • Include SSH instructions for accessing VMs, in addition to RDP.
  • Use platform-neutral file paths and terminology where possible.
  • Explicitly note any differences or requirements for Linux/macOS users.
  • Provide sample ARM template deployment commands for Linux/macOS environments.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
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 in Service Fabric, with explicit Windows paths and commands. No equivalent Linux or cross-platform CLI examples (such as Bash, Azure CLI, or REST with curl) are provided. PowerShell is presented as the primary scripting interface, and Windows-centric patterns (e.g., PS C:\> prompts) are used throughout. REST is mentioned but not exemplified, and there is no guidance for Linux/macOS users on how to perform similar tasks.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting, especially for REST endpoints.
  • Include sample REST calls using curl or HTTPie, showing how to report health from Linux/macOS environments.
  • Clarify which PowerShell commands are available cross-platform (PowerShell Core), and provide notes or alternatives for Linux/macOS users.
  • Reorder sections so that REST or cross-platform approaches are presented before or alongside PowerShell.
  • Explicitly mention any limitations or requirements for Linux/macOS users, and provide links to relevant tools or 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 →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish), which are Windows-centric. All examples and instructions reference Visual Studio and its UI, with no mention of Linux/macOS equivalents or CLI-based workflows. The only alternative deployment methods mentioned are ARM templates and PowerShell cmdlets, but these are referenced briefly and without example parity. There are no Linux/macOS-specific instructions or examples, and the documentation implicitly assumes a Windows development environment.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to manage service configuration and deployment without Visual Studio.
  • Provide CLI-based examples (using Azure CLI, Service Fabric CLI, or PowerShell Core where cross-platform) for creating and deploying applications with StartupServices.xml.
  • Clarify which features are Visual Studio/Windows-only and offer alternative workflows for non-Windows environments.
  • Include screenshots or instructions for Linux/macOS development tools (e.g., VS Code, command-line workflows).
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation covers both Windows-only (HTTP.sys) and cross-platform (Kestrel) web servers for ASP.NET Core in Service Fabric. However, it gives extensive coverage to HTTP.sys, a Windows-only technology, including detailed examples and endpoint configuration instructions. Windows-specific tools like netsh are mentioned, and Windows platform limitations are called out. Kestrel, the cross-platform option, is also well documented and recommended for Linux scenarios, but Windows tools and patterns (such as HTTP.sys and netsh) are presented first and in greater detail. There are no explicit Linux/macOS-specific examples or troubleshooting tips, and some configuration guidance (e.g., endpoint registration) is Windows-centric.
Recommendations
  • Add explicit Linux/macOS examples and troubleshooting tips, especially for Service Fabric clusters running on Linux.
  • Clarify which steps and configurations are Windows-only versus cross-platform, and highlight Linux compatibility in relevant sections.
  • Present Kestrel (the cross-platform option) before HTTP.sys in examples and guidance, or clearly indicate when Windows-only features are being discussed.
  • Include notes or links to Linux-specific Service Fabric documentation where available.
  • Avoid mentioning Windows tools (e.g., netsh) without Linux equivalents or alternatives.
GitHub Create Pull Request
Service Fabric Fault Analysis Service overview .../service-fabric/service-fabric-testability-overview.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides usage instructions for C# (via the Microsoft.ServiceFabric NuGet package) and PowerShell (via the Service Fabric SDK and PowerShell module). There are no Linux/macOS CLI examples or references to cross-platform tools such as Azure CLI or REST APIs. PowerShell, which is traditionally Windows-centric, is mentioned as the primary scripting interface, and no Linux-specific guidance is given.
Recommendations
  • Add examples for using the Fault Analysis Service via Azure CLI or REST API, if available, to support Linux/macOS users.
  • Clarify whether PowerShell Core (cross-platform) is supported, and provide installation instructions for Linux/macOS if so.
  • Include guidance for invoking Fault Analysis Service actions from non-Windows environments, such as using Python SDKs or other cross-platform tools.
  • Explicitly state any platform limitations if the Fault Analysis Service is only accessible via Windows tools.
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-only example for bypassing Infrastructure Service, and references Service Fabric Explorer (a Windows-centric tool) without mentioning Linux/macOS alternatives. No Linux CLI or cross-platform examples are given for critical operations, and Windows tooling is implicitly assumed.
Recommendations
  • Add equivalent Linux/macOS command-line examples (e.g., using sfctl or Azure CLI) for cluster operations.
  • Clarify whether Service Fabric Explorer is available cross-platform or suggest alternatives for Linux/macOS users.
  • Explicitly state platform requirements for commands and tools, and provide guidance for non-Windows users.
  • Where possible, link to cross-platform documentation or tools for Service Fabric management.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL). The PowerShell and Visual Studio sections are more detailed and appear first, with SFCTL (the cross-platform CLI) covered later. There are more explicit parameter examples for PowerShell, and Windows tools are referenced more frequently. Linux users may need to scroll or search to find relevant CLI information, and the structure may imply Windows as the default environment.
Recommendations
  • Reorganize the page to present cross-platform tools (SFCTL) before or alongside Windows-specific tools (PowerShell, Visual Studio).
  • Provide equivalent parameter examples for SFCTL, including sample command lines and JSON payloads.
  • Clarify early in the article that SFCTL is the recommended cross-platform tool for Linux/macOS users.
  • Add a summary table mapping parameters across PowerShell, Visual Studio, and SFCTL for easy comparison.
  • Ensure all examples and descriptions are equally detailed for SFCTL as for PowerShell/Visual Studio.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides general guidance for upgrading Azure Service Fabric clusters, but exhibits Windows bias in several areas. References to PowerShell and Windows-specific patching tools (Patch Orchestration Application) are made without equivalent Linux examples or guidance. The section on OS image upgrades links only to Windows patching documentation, and PowerShell is mentioned as a management tool alongside Azure CLI, but Linux-native tools or workflows are not described. The order of mention and lack of Linux-specific guidance creates friction for Linux/macOS users.
Recommendations
  • Add explicit Linux cluster upgrade guidance, including links to Linux patching documentation and relevant tools.
  • Provide Azure CLI examples for all management tasks, and clarify which commands are cross-platform.
  • Mention Linux support and differences where applicable, especially in sections about OS image upgrades and certificate management.
  • Ensure that references to PowerShell are balanced with Azure CLI or Bash examples.
  • Link to Linux-specific Service Fabric documentation where available.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for on-demand backup in Azure Service Fabric is heavily focused on PowerShell-based workflows and commands, with all CLI examples using PowerShell syntax and modules. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, curl), and the prerequisite steps assume a Windows environment. The REST API is referenced, but only invoked via PowerShell, not with cross-platform tools.
Recommendations
  • Add equivalent examples using Bash/curl or Azure CLI for REST API calls, so Linux/macOS users can follow along.
  • Clarify whether the Microsoft.ServiceFabric.Powershell.Http module is required for all scenarios, or if REST API calls can be made directly from any platform.
  • Provide guidance for connecting to Service Fabric clusters from Linux/macOS, including certificate handling and authentication.
  • Mention any cross-platform tools (such as Azure CLI or Service Fabric CLI) that can be used for backup operations.
  • Explicitly state platform requirements if certain steps are Windows-only, and offer alternatives where possible.
GitHub Create Pull Request
Service Fabric Cluster Resource Manager - Management Integration ...fabric-cluster-resource-manager-management-integration.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example (Get-ServiceFabricPartitionHealth) for querying health information, but does not include equivalent examples for Linux or cross-platform CLI tools. This may create friction for Linux/macOS users who do not use PowerShell or Windows environments.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl), which is cross-platform and works on Linux/macOS.
  • Where possible, provide both PowerShell and CLI (sfctl) commands side by side.
  • Clarify in the example sections that the shown PowerShell commands are for Windows, and link to documentation for Linux/macOS management tools.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions PowerShell cmdlets as a primary management interface for Service Fabric, with no reference to Linux or cross-platform CLI equivalents. Windows security is mentioned as a transport option alongside X509 certificates, but Linux alternatives are not discussed. The management subsystem section leads with Windows tooling (PowerShell), suggesting Windows-first bias.
Recommendations
  • Add references to cross-platform management tools, such as Azure CLI or REST APIs, where applicable.
  • Clarify whether PowerShell cmdlets are available on Linux/macOS (via PowerShell Core), or provide Linux-specific examples.
  • Mention Linux-compatible security mechanisms in the transport subsystem (e.g., use of X509 certificates, Kerberos, etc.).
  • Ensure examples and tooling references are balanced between Windows and Linux environments.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides PowerShell and C# examples exclusively for configuring Service Fabric Application Groups, with no mention of Linux-compatible CLI tools (such as sfctl) or Bash examples. All command-line instructions use PowerShell cmdlets, which are native to Windows, and there is no guidance for Linux/macOS users on how to perform equivalent operations.
Recommendations
  • Add examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS, for all PowerShell command scenarios.
  • Explicitly mention that PowerShell commands are Windows-specific and provide alternative instructions for Linux/macOS users.
  • Include Bash or shell script examples where appropriate.
  • Clarify any limitations or differences in feature support between Windows and Linux Service Fabric clusters, if relevant.
GitHub Create Pull Request
Service Fabric Secure an Azure Service Fabric cluster ...cles/service-fabric/service-fabric-cluster-security.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page presents security scenarios for Azure Service Fabric clusters, but consistently references Windows Server clusters and Windows-specific security mechanisms (such as Windows authentication and Windows certificate services) before or instead of Linux equivalents. There are explicit links and instructions for securing standalone clusters on Windows, but no corresponding guidance or links for standalone Linux clusters. The concept of Linux clusters is briefly mentioned, but practical examples, instructions, or references are missing.
Recommendations
  • Add explicit sections or links for securing standalone Linux Service Fabric clusters, including certificate setup and client authentication.
  • Provide Linux-specific examples for certificate generation and management (e.g., using OpenSSL instead of Windows certificate services).
  • Clarify which security mechanisms are available or recommended for Linux clusters, and highlight any differences.
  • Ensure parity in guidance for both Windows and Linux, including references to relevant tools and templates for Linux environments.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page provides Service Fabric manifest examples and explanations. While the XML manifests themselves are cross-platform, there are subtle signs of Windows bias: Windows tools and concepts (such as 'Setup.bat', 'VotingWeb.exe', and references to 'Administrators' and 'NetworkService' accounts) are used in examples, and PowerShell is mentioned as a deployment tool. Linux equivalents (such as shell scripts, Linux user/group concepts, or Linux deployment tools) are not provided or referenced.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) in SetupEntryPoint and EntryPoint.
  • Mention Linux user/group concepts and how Service Fabric handles them on Linux clusters.
  • Reference Linux deployment tools (e.g., Azure CLI or sfctl) in addition to PowerShell.
  • Clarify any platform-specific differences in manifest usage, especially for user accounts and script execution.
  • Consider showing both Windows and Linux file naming conventions and executable formats in example manifests.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Events ...es/service-fabric/service-fabric-diagnostics-events.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Service Fabric Events references Windows-specific logging mechanisms (ETW/Windows Event logs) and the Windows Azure diagnostics agent as primary ways to access events. There are no explicit examples or guidance for accessing Service Fabric events on Linux clusters, nor are Linux-native tools or patterns mentioned. The ordering and language suggest Windows as the default environment, creating friction for Linux users.
Recommendations
  • Add explicit guidance and examples for accessing Service Fabric events on Linux clusters, including supported logging mechanisms and monitoring tools.
  • Mention Linux-native equivalents (such as syslog, journald, or Azure Monitor integration for Linux nodes) alongside Windows tools.
  • Clarify which event access methods are cross-platform and which are Windows-only.
  • Provide sample commands or configuration snippets for Linux environments where possible.
GitHub Create Pull Request
Service Fabric Manage apps for multiple environments ...e-fabric-manage-multiple-environment-app-configuration.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, with a noticeable preference for Windows/PowerShell tools. PowerShell is mentioned first and in detail, and Visual Studio (a Windows-centric IDE) is referenced for parameter management. Linux tools (sfctl) are mentioned, but not as prominently or with as much detail. There are no explicit Linux/macOS examples or workflows, and the scripting examples (Deploy-FabricApplication.ps1) are Windows-specific.
Recommendations
  • Provide Linux/macOS-specific examples, such as using sfctl and shell scripts for parameter management.
  • Include guidance for managing parameters using cross-platform tools and editors (e.g., VS Code, CLI).
  • Ensure parity in example detail and order: mention sfctl and Linux workflows before or alongside PowerShell.
  • Add sample shell scripts (e.g., install.sh) for Linux users, similar to the PowerShell examples.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right workflow.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides extensive PowerShell examples and references Windows-specific tools and patterns (such as the Key Vault VM extension for Windows, S-channel, and certificate store locations like 'LocalMachine'). Windows terminology and mechanisms (ACLing, certificate linking, S-channel) are discussed in detail, while Linux/macOS equivalents are not mentioned or are missing. The PowerShell example is the only programmatic enrollment script shown, and Windows-specific features (like certificate linking) are explained without Linux alternatives.
Recommendations
  • Add equivalent Linux/macOS examples for certificate enrollment and management (e.g., using Azure CLI, Bash, or Python SDK).
  • Clarify which mechanisms (such as Key Vault VM extension) are available or not available on Linux, and provide guidance for Linux users.
  • Discuss certificate provisioning and rotation on Linux nodes, including how Service Fabric clusters on Linux VMs handle certificates.
  • Provide troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • Where Windows-specific features are discussed (e.g., S-channel, certificate linking), explicitly note their absence or alternatives on Linux.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page primarily references Windows tools and patterns (e.g., certificate stores like LocalMachine\My, Win32 CryptoAPI, CAPI2 logging, and Windows event logs) when discussing certificate management, troubleshooting, and configuration. Linux equivalents are mentioned only briefly or parenthetically, and there are no concrete Linux/macOS-specific troubleshooting steps or examples. Windows terminology and APIs are presented first and in detail, while Linux is referenced as an aside (e.g., 'or the Linux equivalent path, /var/lib/sfcerts').
Recommendations
  • Provide explicit Linux/macOS examples for certificate storage, retrieval, and troubleshooting (e.g., using OpenSSL, viewing logs, certificate file locations).
  • Document Linux/macOS-specific paths, commands, and log locations alongside Windows examples, not just as parentheticals.
  • Include troubleshooting steps for Linux clusters, such as how to check certificate permissions, validate certificate chains, and interpret relevant logs.
  • Clarify which APIs or behaviors are platform-specific (e.g., Win32 CryptoAPI, CAPI2 logging) and offer Linux/macOS alternatives where possible.
  • Add a table or section summarizing differences and equivalents between Windows and Linux certificate management in Service Fabric.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page primarily focuses on deploying custom Windows images in Azure Service Fabric Managed Clusters. Windows terminology and PowerShell examples are used, and Windows-specific tools and patterns are mentioned first or exclusively. While there is a brief reference to Linux custom image creation, the main guidance, examples, and tooling are Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS CLI examples alongside PowerShell commands, especially for role assignment and image management.
  • Clarify which steps are OS-agnostic and which are Windows-specific, and add explicit guidance for Linux custom images where relevant.
  • Include links to Linux documentation and examples for creating and managing custom images, and for assigning roles using Azure CLI.
  • Ensure ARM template examples and image references are equally applicable to Linux images, and explicitly mention Linux support where possible.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container image management .../articles/service-fabric/container-image-management.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in cleanup settings, but does not mention Linux container base images or provide examples relevant to Linux containers. There are no explicit Linux-specific examples or guidance, and Windows images are referenced first and exclusively.
Recommendations
  • Include examples of Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the ContainerImagesToSkip setting.
  • Clarify whether the cleanup features and settings apply equally to Linux containers, and provide guidance or examples for Linux container scenarios.
  • Add a note on cross-platform support, specifying any limitations or differences for Linux vs. Windows containers.
  • Ensure parity in documentation by referencing both Windows and Linux container images in explanations and examples.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for configuring Service Fabric managed cluster node types using the Azure Portal, ARM templates, and PowerShell. PowerShell is the only CLI method shown, with no mention of Azure CLI or Bash scripting alternatives. PowerShell examples are presented for all major operations (add, remove, scale, configure placement properties), and are often listed before or alongside portal and ARM template methods. This creates friction for Linux/macOS users, as PowerShell is less commonly used or installed on those platforms compared to Azure CLI.
Recommendations
  • Add Azure CLI examples for all operations currently demonstrated with PowerShell.
  • Explicitly state that PowerShell examples are cross-platform (if true), or provide guidance for Linux/macOS users on how to use PowerShell Core.
  • Where possible, provide Bash scripting examples or reference Azure CLI documentation for equivalent tasks.
  • Ensure that CLI examples are presented in a platform-neutral way, or alternate the order to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Initializer CodePackages in Service Fabric ...in/articles/service-fabric/initializer-codepackages.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
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-based examples, including Windows container images, Windows file paths, and Windows-specific commands (e.g., cmd, C:\ paths, type, ping). There are no Linux container or cross-platform examples, and the only complete example is explicitly for Windows containers. This creates friction for Linux users and those deploying on Linux-based Service Fabric clusters.
Recommendations
  • Add a parallel example using Linux containers (e.g., using Ubuntu or Alpine images) with Linux shell commands and file paths.
  • Clarify in the introduction whether Initializer CodePackages are supported for Linux containers and, if so, provide guidance or links.
  • If there are limitations for Linux support, explicitly state them and link to relevant documentation.
  • Ensure that examples and file paths are shown for both Windows and Linux where applicable, or note platform-specific differences.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page frequently references Az PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources, and these examples are presented before or instead of Azure CLI equivalents. While Azure CLI is mentioned once (az resource), PowerShell commands dominate, which may create friction for Linux/macOS users who typically use Azure CLI. No Linux-specific tools or examples are provided.
Recommendations
  • Provide Azure CLI command examples alongside PowerShell cmdlets for all operations (e.g., deleting, creating, scaling resources).
  • Clarify which commands are cross-platform and which are Windows-only.
  • Add explicit notes or tables showing parity between PowerShell and Azure CLI for each operation.
  • Consider referencing ARM template usage in a platform-neutral way.
GitHub Create Pull Request
Service Fabric RunToCompletion semantics and specifications ...blob/main/articles/service-fabric/run-to-completion.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates notable Windows bias. All code examples use Windows containers (nanoserver:1809) and Windows-specific commands (cmd, echo, ping, set, exit). The 'Query deployment status' section only references PowerShell and C# APIs, with no mention of Linux or cross-platform tooling. There are no examples or guidance for Linux containers or Linux-based workflows, despite Service Fabric supporting containers in general.
Recommendations
  • Add equivalent examples using Linux containers (e.g., Ubuntu or Alpine images) and Linux shell commands.
  • 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 CLI tools (e.g., Azure CLI, sfctl) or Linux shell commands.
  • Where possible, present both Windows and Linux examples, or note platform-specific limitations.
  • Update introductory notes to explicitly state if RunToCompletion is Windows-only, or highlight Linux support if available.
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 →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides best practice examples primarily using Azure PowerShell modules, with explicit links to PowerShell commands for cluster management tasks. While Azure CLI and ARM/Bicep are mentioned in a summary table, PowerShell is highlighted first in the best practices section and is the only example given for specific operations (delete, restart, reimage). There are no Linux/macOS-specific command examples or explicit parity for cross-platform tools in the main guidance.
Recommendations
  • Add Azure CLI command examples for deleting, restarting, and reimaging NodeTypes/VMSS, alongside PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider providing sample scripts or links for ARM/Bicep deployments relevant to the described operations.
  • Reorder examples so that cross-platform tools (Azure CLI, ARM/Bicep) are shown before or alongside PowerShell.
  • Clarify that PowerShell examples are also available on Linux/macOS, or provide alternative CLI syntax.
GitHub Create Pull Request
← Previous Page 45 of 99 Next →