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 1476-1500 of 2475 flagged pages
Service Fabric Monitor Azure Service Fabric ...main/articles/service-fabric/monitor-service-fabric.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
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 are several areas where Windows tools and patterns are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some examples and tutorials focus on Windows or .NET, and certain features (like EventStore APIs) are Windows-only. Linux-specific guidance is present but less detailed, and Linux configuration steps are sometimes referenced as separate links rather than integrated alongside Windows instructions.
Recommendations
  • Ensure Linux examples and tools are presented alongside Windows ones, not just referenced via links.
  • Where Windows tools (e.g., Event Viewer, ETW) are mentioned, explicitly describe Linux equivalents (e.g., LTTng, Syslog) in the same section.
  • Provide Linux-focused tutorials and sample code, especially for application monitoring and logging.
  • Clarify when features are Windows-only and offer alternative approaches for Linux users.
  • Balance the order of presentation so Linux and Windows are equally visible in lists and explanations.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation prioritizes Windows-centric tools (PowerShell and Visual Studio) in both structure and detail. Parameters for PowerShell and Visual Studio are discussed first and in greater depth, with SFCTL (the cross-platform CLI) covered later. Most examples and parameter tables focus on PowerShell, with Linux/macOS users needing to adapt or refer to a separate section. There are no direct Linux shell examples, and the workflow for non-Windows users is less prominent.
Recommendations
  • Reorganize the documentation to present SFCTL (Service Fabric CLI) parameters and workflows alongside or before PowerShell/Visual Studio, highlighting its cross-platform nature.
  • Provide explicit Linux/macOS shell examples (e.g., bash commands) for common upgrade scenarios using SFCTL.
  • Ensure parameter tables and explanations are parallel for all tools, not just PowerShell/Visual Studio.
  • Add a summary table or section at the top that helps users quickly identify which tool/command to use based on their OS.
  • Where PowerShell has a code example, provide an equivalent SFCTL example.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Initializer CodePackages in Service Fabric provides only Windows container examples, uses Windows-specific images (nanoserver:1809), and references Windows paths and commands (cmd, C:\ paths, ping, type). There is no mention of Linux containers, Linux-compatible images, or equivalent Linux command examples. The ApplicationManifest and ServiceManifest examples are exclusively Windows-focused, and the 'Next steps' section does not link to Linux container guidance.
Recommendations
  • Add a parallel example using Linux containers (e.g., mcr.microsoft.com/linux/base images) with Linux shell commands.
  • Include guidance on using Initializer CodePackages with Linux containers, specifying differences in paths, commands, and volume mounts.
  • Clarify whether Initializer CodePackages are supported for Linux containers and, if so, provide Linux-specific documentation.
  • If Initializer CodePackages are Windows-only, explicitly state this limitation at the top of the article.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page primarily references PowerShell cmdlets (Az PowerShell, AzSF PowerShell) for management operations, with no explicit mention of Linux/macOS alternatives or CLI equivalents. While the Azure CLI (az resource) is mentioned once, the overall guidance and examples are PowerShell-centric, which may create friction for Linux/macOS users who typically use Azure CLI or bash scripts.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, especially for common operations like creating or deleting applications and services.
  • Explicitly mention that the Azure CLI can be used on Linux/macOS for ARM resource management, and provide links to relevant documentation.
  • Where possible, include bash script examples or cross-platform instructions alongside PowerShell examples.
  • Clarify in each section whether the instructions are cross-platform or Windows-specific.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for RunToCompletion semantics in Service Fabric presents code examples and guidance exclusively for Windows containers and Windows-specific tools. All container examples use Windows images and Windows command syntax, and querying deployment status is described only via PowerShell and C# APIs, with no mention of Linux equivalents. There is no guidance or example for Linux containers or cross-platform usage, despite Service Fabric supporting Linux containers.
Recommendations
  • Add equivalent Linux container examples using popular Linux base images (e.g., Ubuntu, Alpine) and 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 Linux tools (e.g., Azure CLI, Bash scripts) or cross-platform approaches.
  • Present examples for both Windows and Linux containers, or explicitly state if the feature is Windows-only.
  • Avoid using Windows-specific terminology (e.g., cmd, PowerShell) without mentioning Linux alternatives.
GitHub Create Pull Request
Service Fabric Application lifecycle in Service Fabric ...service-fabric/service-fabric-application-lifecycle.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for the Service Fabric application lifecycle consistently references PowerShell cmdlets and Windows-centric tooling (e.g., PowerShell commands, .NET APIs) throughout critical lifecycle operations (deploy, upgrade, remove, cleanup). While REST API alternatives are mentioned, Linux-native CLI tools (such as sfctl or Azure CLI) are not referenced in the main procedural steps, and PowerShell examples are shown first or exclusively. This creates friction for Linux/macOS users, who must infer or search for equivalent commands.
Recommendations
  • Add explicit examples and procedural steps using sfctl (Service Fabric CLI) and Azure CLI for all major lifecycle operations (deploy, upgrade, remove, cleanup).
  • Where PowerShell cmdlets are referenced, provide Linux/macOS equivalents alongside, not just REST API links.
  • Ensure that CLI and REST API options are presented before or alongside PowerShell examples, not after.
  • Include sample command blocks for sfctl and Azure CLI in relevant sections.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the right approach.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides links to application upgrade tutorials using Visual Studio and PowerShell, both of which are primarily Windows-centric tools. There are no explicit Linux/macOS examples or equivalent upgrade instructions for those platforms. The serialization guidance is .NET-focused, but does not reference Linux-specific workflows or tools.
Recommendations
  • Add links or sections for upgrading Service Fabric applications using Linux/macOS tools, such as Azure CLI or REST APIs.
  • Provide examples or tutorials for application upgrades on Linux-based Service Fabric clusters.
  • Clarify which upgrade methods are cross-platform and which are Windows-only.
  • Mention alternative development environments (e.g., VS Code, CLI) for non-Windows users.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation covers Azure Service Fabric application security in a generally platform-neutral manner, but several sections show Windows bias. Windows-specific features (e.g., Active Directory, gMSA, BitLocker) are mentioned before or instead of Linux equivalents. Disk encryption is only referenced via a PowerShell/Windows link, and Linux disk encryption is listed as a TODO. Some examples and guidance (e.g., running services under user accounts) focus on Windows scenarios, with less detail for Linux. Linux-specific tools and patterns are rarely mentioned, and Linux parity is incomplete in some critical areas.
Recommendations
  • Add Linux-specific examples and guidance for disk encryption, referencing Azure documentation for encrypting disks on Linux VMSS clusters.
  • Ensure parity in sections about running services under user accounts: clarify how this works on Linux clusters, including any limitations or differences.
  • Where Windows tools (e.g., PowerShell, BitLocker, gMSA) are mentioned, provide equivalent Linux tools or note if no equivalent exists.
  • Review all examples and ensure both Windows and Linux scenarios are covered, especially for certificate management, user accounts, and startup scripts.
  • Remove or resolve TODOs regarding Linux disk encryption, providing actionable guidance.
GitHub Create Pull Request
Service Fabric Service Fabric application upgrade ...s/service-fabric/service-fabric-application-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation for Service Fabric application upgrades demonstrates a notable Windows bias. It provides only PowerShell-based examples and references to Windows-specific tools (e.g., http.sys), with no equivalent examples or guidance for Linux users. The upgrade process is described using Windows-centric commands, and Linux/CLI alternatives are not mentioned or linked. This creates friction for Linux/macOS users who may be managing Service Fabric clusters on those platforms.
Recommendations
  • Add equivalent examples using Azure CLI or REST API for application upgrades, especially for parameter preservation.
  • Explicitly mention Linux support for Service Fabric and link to relevant Linux documentation where available.
  • Clarify when features or commands are Windows-only (e.g., http.sys, PowerShell cmdlets) and provide Linux alternatives or workarounds.
  • Reorder sections or examples to present cross-platform or platform-neutral approaches first, followed by platform-specific guidance.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively uses PowerShell and Windows-centric tools (Microsoft.ServiceFabric.Powershell.Http module) for all command-line and API examples. There are no Linux/macOS CLI equivalents (such as Bash, curl, or Azure CLI) provided, and PowerShell is presented as the primary and only scripting environment. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls, so Linux/macOS users can follow along without PowerShell.
  • Mention and provide Azure CLI commands where possible, as Azure CLI is cross-platform.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide installation instructions if so.
  • Reorganize examples to show cross-platform approaches first, or at least in parallel with PowerShell.
  • Explicitly state if any steps are Windows-only, and provide alternatives or workarounds for other platforms.
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 →
Scanned: 2026-02-14 00:00
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 restoring backups in Azure Service Fabric is heavily biased toward Windows/PowerShell usage. All code examples use PowerShell, and the prerequisite is to install a Microsoft.ServiceFabric.Powershell.Http module. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, curl, or other cross-platform tools. The REST API is only shown via PowerShell scripts, and Windows authentication patterns (certificate thumbprints, PowerShellGet) are referenced. Service Fabric Explorer is mentioned, but no information is given about its availability or usage on Linux/macOS.
Recommendations
  • Add examples using Azure CLI or curl for REST API calls, which are cross-platform.
  • Document how to authenticate and connect to Service Fabric clusters from Linux/macOS (e.g., using certificates, REST calls).
  • Mention or link to any available Service Fabric tools or modules for Linux/macOS, or clarify if PowerShell Core is supported cross-platform.
  • Provide guidance for Linux/macOS users on installing and using PowerShell Core if that's required.
  • Clarify Service Fabric Explorer's platform support and usage for non-Windows users.
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 →
Scanned: 2026-02-14 00:00
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 featured prominently and used for upgrade operations without Linux/macOS alternatives. Windows-specific tools and registry settings are discussed in detail, while Linux equivalents (such as shell commands or Linux VM configuration) are missing or referenced only via external links. Windows configuration details (e.g., registry keys, Windows Update settings) are described before or instead of Linux approaches.
Recommendations
  • Include Linux/macOS shell (bash) examples for cluster upgrade operations, especially where only PowerShell is shown.
  • Add Linux-specific configuration guidance for disabling automatic updates on Linux VMSS nodes, analogous to the Windows registry and Windows Update settings.
  • Where PowerShell is used for cluster management, provide equivalent bash/CLI commands for Linux users, or clarify if such operations are Windows-only.
  • Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or clearly separate them by OS.
  • Explicitly note when a step or tool is Windows-only to avoid confusion for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric security best practices ...rvice-fabric/service-fabric-best-practices-security.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, including certificate creation and secret encryption. However, Windows examples (PowerShell commands, Windows Defender, Windows security baselines) are often presented first or in greater detail, and Windows-specific tools (PowerShell, Windows Defender, Azure Desired State Configuration) are referenced without Linux equivalents or with less emphasis. Some sections, such as Windows Defender and security baselines, are inherently Windows-focused, but overall, Linux guidance is present but less prominent.
Recommendations
  • Ensure Linux examples are given equal prominence and detail as Windows examples, especially in sections on certificate creation, secret encryption, and endpoint configuration.
  • Where Windows-specific tools (e.g., PowerShell, Windows Defender, DSC) are mentioned, provide clear Linux alternatives or explicitly state when no equivalent exists.
  • Consider alternating the order of Windows and Linux examples, or grouping them together for parity.
  • Add references to Linux security baselines and antivirus solutions where relevant, or clarify their absence.
  • Expand Linux-specific guidance for Azure Firewall rules, endpoint certificates, and managed identities if applicable.
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 →
Scanned: 2026-02-14 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 code examples in C# and PowerShell for configuring Service Fabric placement policies. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS CLI or scripting examples (such as Bash, Azure CLI, or REST API) are provided. All PowerShell examples are shown immediately after the C# code, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for each placement policy, as Azure CLI is cross-platform and widely used.
  • Mention REST API options for configuring placement policies, with example requests.
  • Explicitly note PowerShell's platform limitations and link to Linux/macOS-compatible tools.
  • Consider including Bash or Python SDK examples where relevant.
  • Clarify if certain configuration steps are only possible via PowerShell, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Azure Service Fabric networking best practices ...ice-fabric/service-fabric-best-practices-networking.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux guidance for Azure Service Fabric networking, but there are several areas where Windows-specific tools (e.g., PowerShell, netsh) and examples are mentioned first or exclusively. Some explanations reference Windows patterns or tools before Linux equivalents, and PowerShell is highlighted as the primary API client. ARM template samples and links are also Windows-focused. However, Linux support is acknowledged and included in key sections.
Recommendations
  • Add Linux CLI examples alongside PowerShell examples, especially for cluster management and networking tasks.
  • Where Windows tools (e.g., netsh) are referenced, provide equivalent Linux commands (e.g., 'ss', 'lsof', or 'netstat') for port range checks.
  • Balance the order of presentation so Linux and Windows are treated equally (e.g., mention Linux and Windows in parallel, not Windows first).
  • Include ARM template samples for Linux clusters with NSG configuration, not just Windows.
  • Clarify when guidance applies to both platforms, and explicitly note any platform-specific differences.
GitHub Create Pull Request
Service Fabric Change Azure Service Fabric cluster settings ...rvice-fabric/service-fabric-cluster-fabric-settings.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page covers Service Fabric cluster settings for both Azure-hosted and standalone clusters. However, there is evidence of Windows bias: Windows-specific terms (e.g., certificate store names like 'My', store locations like 'LocalMachine', NTLM authentication, and references to Windows Defender Firewall) are prevalent. Windows terminology and tools are often mentioned first or exclusively, with Linux equivalents rarely explained or referenced. Some parameters default to Windows values or behaviors, and Linux-specific guidance is minimal or absent. There are settings that reference Windows-only features (e.g., Windows Update, NTLM, Windows log directories) without clear Linux alternatives or parity explanations.
Recommendations
  • For parameters referencing Windows certificate stores (e.g., 'My', 'LocalMachine'), add explanations or examples for Linux equivalents (such as file paths or openssl usage).
  • Where NTLM authentication or Windows Defender Firewall is referenced, clarify Linux alternatives or note if the feature is Windows-only.
  • For settings with Windows-centric defaults, provide Linux-specific default values and guidance where applicable.
  • Add explicit Linux examples and explanations for customizing cluster settings, especially for standalone clusters.
  • Ensure that Linux-specific configuration paths, tools, and terminology are documented alongside Windows equivalents.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides general information about Azure Service Fabric node types and virtual machine scale sets, but several sections and examples show Windows bias. The JSON snippet uses a Windows-style file path (D:\SvcFab) as the default for dataPath, and the 'Next steps' section links to PowerShell scripts for changing RDP port ranges and admin credentials, which are Windows-specific tasks. There are no explicit Linux/macOS examples or guidance, and Windows tools/patterns (RDP, PowerShell) are mentioned exclusively.
Recommendations
  • Provide equivalent Linux/macOS examples, such as using SSH for remote connection instead of RDP.
  • Show Linux file path conventions (e.g., /var/svcfab) alongside Windows paths in configuration examples.
  • Include links to Bash or CLI scripts for cluster management tasks, not just PowerShell.
  • Clarify which tasks are Windows-only and which are cross-platform, and offer Linux guidance where possible.
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-14 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 only PowerShell and C# examples for managing Service Fabric Application Groups. PowerShell is a Windows-centric tool, and no Linux/macOS CLI (such as Bash, Azure CLI, or REST API) examples are given. There is no mention of Linux-compatible tooling or commands, which creates friction for users managing Service Fabric clusters from non-Windows environments.
Recommendations
  • Add Azure CLI examples for all operations shown (application creation, updating, querying load, removing capacity).
  • Include REST API examples for cross-platform management.
  • Explicitly mention whether PowerShell commands are supported on PowerShell Core (cross-platform) or only Windows PowerShell.
  • Provide guidance for Linux/macOS users on how to perform equivalent tasks.
  • Clarify any platform limitations if certain features are Windows-only.
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 →
Scanned: 2026-02-14 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 examples for configuring auto scaling in Azure Service Fabric using application manifests, C# APIs, and PowerShell. However, all CLI/script examples are PowerShell-based, with no equivalent Bash or Linux CLI examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented alongside C# and manifest examples without mention of Linux alternatives, and there is no guidance for Linux users on how to perform these tasks via Bash, Azure CLI, or REST APIs.
Recommendations
  • Add equivalent Bash or Azure CLI examples for configuring scaling policies, especially for Linux clusters.
  • Clarify which PowerShell commands (if any) are supported on Linux/macOS, or provide alternatives.
  • Explicitly mention REST API options for auto scaling configuration, if available.
  • Add notes or sections indicating how Linux users can perform these tasks, including links to relevant tools or documentation.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell examples for configuring service sensitivity and maximum load, but does not offer equivalent Linux/macOS CLI examples (e.g., Bash, Azure CLI). PowerShell is presented as the primary scripting interface, which may create friction for Linux/macOS users. Additionally, the PowerShell section precedes any mention of cross-platform tools, and there is no guidance for Linux users on how to perform these tasks.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for Linux/macOS users.
  • Clarify whether PowerShell Core (pwsh) can be used cross-platform, and provide instructions if so.
  • Mention any REST API or SDK alternatives that are platform-agnostic.
  • Reorder examples so that cross-platform options are presented alongside or before Windows-specific tools.
  • Explicitly state if certain operations are only possible via PowerShell on Windows, and suggest workarounds for Linux/macOS users.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific upgrade and configuration guides (e.g., 'service-fabric-cluster-upgrade-windows-server.md', 'service-fabric-cluster-config-upgrade-windows-server.md') and the Patch Orchestration Application for Windows, without mentioning Linux equivalents or providing Linux-specific guidance. This creates friction for Linux users seeking parity in upgrade and maintenance procedures.
Recommendations
  • Add links and references to Linux-specific Service Fabric upgrade and configuration documentation, if available.
  • Clarify whether the procedures described apply to both Windows and Linux standalone clusters, or specify any differences.
  • Include examples or guidance for Linux environments where relevant (e.g., patch orchestration, cluster configuration).
  • If Linux standalone clusters are not supported, explicitly state this to avoid confusion.
GitHub Create Pull Request
Service Fabric Scalability of Service Fabric services .../service-fabric/service-fabric-concepts-scalability.md
Medium Priority View Details →
Scanned: 2026-02-14 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 code examples and administrative instructions primarily using PowerShell, which is a Windows-centric tool. There are no equivalent Linux CLI or bash examples, nor are Linux-native tools or commands mentioned. Windows/PowerShell examples are consistently presented first and exclusively, creating friction for Linux users who may not have access to PowerShell or prefer bash/CLI tools. The section 'Choosing a platform' does acknowledge platform differences, but the practical guidance and examples remain Windows-focused.
Recommendations
  • Add equivalent Linux CLI/bash examples for administrative tasks (e.g., scaling services, creating/removing instances).
  • Mention and link to Linux-native Service Fabric tools or commands where available.
  • Present examples for both Windows and Linux platforms, or clarify when a command is Windows-only.
  • Consider providing platform-neutral guidance or highlighting cross-platform APIs where possible.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides code examples for managing Service Fabric metrics primarily in C# and PowerShell. PowerShell examples are given for service creation and metric configuration, but there are no equivalent CLI or Linux-native examples (such as Azure CLI or Bash). PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before any mention of cross-platform alternatives, and no Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI examples for service creation and metric configuration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention whether PowerShell commands can be run on PowerShell Core (pwsh) on Linux/macOS, or provide Bash scripting alternatives.
  • Include guidance for Linux users, such as using REST APIs or SDKs in Python/Java, where applicable.
  • Clarify any limitations or differences for Linux clusters versus Windows clusters in Service Fabric, if relevant.
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 →
Scanned: 2026-02-14 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 PowerShell and C# examples for configuring movement cost in Service Fabric, but does not include equivalent Linux/macOS command-line examples (such as Bash or CLI). PowerShell is presented first in each example section, which may create friction for Linux users. There is no mention of Linux-native tools or cross-platform CLI usage, and the documentation assumes familiarity with Windows-centric tooling.
Recommendations
  • Add Azure CLI or Bash examples for creating and updating Service Fabric services and move costs, if supported.
  • Explicitly mention whether PowerShell commands are cross-platform or Windows-only, and provide alternatives for Linux/macOS users.
  • Consider including references to Service Fabric REST APIs or SDKs usable from Linux environments.
  • Reorder examples so that cross-platform or Linux-native methods are presented alongside or before Windows-specific ones.
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 →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell examples for managing node tags and service requirements, but does not offer equivalent CLI or scripting examples for Linux/macOS users (such as Bash, Azure CLI, or REST API usage). PowerShell is primarily a Windows tool, and its prominence here creates friction for non-Windows users. The documentation mentions REST APIs but does not provide concrete examples or guidance for their use.
Recommendations
  • Add examples using Azure CLI or Bash scripts for managing node tags and service requirements.
  • Provide REST API sample requests and responses for relevant operations.
  • Clarify which PowerShell commands are cross-platform (if any), or explicitly note Windows-only limitations.
  • Consider including a table or section comparing available tooling for Windows, Linux, and macOS environments.
GitHub Create Pull Request
← Previous Page 60 of 99 Next →