Service Fabric

810
Total Pages
600
Linux-Friendly Pages
210
Pages with Bias
25.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

718 issues found
Showing 676-700 of 718 flagged pages
Service Fabric Configure a Service Fabric managed cluster to use a NAT gateway ...s/service-fabric/how-to-managed-cluster-nat-gateway.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example commands for ARM templates, Azure CLI, Azure PowerShell, and Azure portal. While Azure CLI is cross-platform, Azure PowerShell examples are given in detail and are presented before the Azure portal steps. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is a Windows-centric tool, though it is available on Linux. The ordering and depth of PowerShell examples may create a perception of Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • If PowerShell is shown, mention that Azure PowerShell is available on Linux and macOS, or provide equivalent Bash/CLI examples.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally cross-platform.
  • Add a note or section for Linux/macOS users to highlight any platform-specific considerations.
GitHub Create Pull Request
Service Fabric Use a Public IP address prefix in a Service Fabric managed cluster ...vice-fabric/how-to-managed-cluster-public-ip-prefix.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying a public IP prefix in a Service Fabric managed cluster. However, the PowerShell example is given equal prominence to the CLI, and PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users. The CLI example is cross-platform, but there is a subtle bias in listing PowerShell as a primary method and linking to PowerShell-specific guides. No Linux-specific tools or shell examples are provided, and there is no explicit mention of Linux/macOS compatibility.
Recommendations
  • Clearly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • List Azure CLI examples before PowerShell examples to reduce Windows-first perception.
  • Add a note clarifying that PowerShell examples are primarily for Windows users.
  • Consider providing bash shell script examples for ARM template deployment for Linux users.
  • Link to documentation on using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric releases ...ocs/blob/main/articles/service-fabric/release-notes.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure Service Fabric releases demonstrates a mild Windows bias. Several sections, especially in releases 8.x, 9.x, and earlier, reference Windows-specific configuration properties (e.g., 'windowsConfiguration.enableAutomaticUpdates'), Windows-only tools (Web Platform Installer, Visual Studio), and update/patching patterns. Windows configuration options are often mentioned before Linux equivalents, and some features/tools are described as available for Windows clusters with Linux support mentioned as an add-on or afterthought. However, there is evidence of Linux support and parity in recent releases, including explicit mentions of Ubuntu support and Linux configuration options.
Recommendations
  • When describing configuration properties (such as VM scale set OS updates), always mention both Windows and Linux equivalents, or clarify if a feature is Windows-only.
  • For tooling and SDK installation, include Linux/macOS instructions and alternatives alongside Windows tools (e.g., avoid referencing Web Platform Installer without listing Linux package managers or CLI options).
  • If a feature is available on both platforms, present Linux and Windows options side-by-side, rather than listing Windows first.
  • Highlight Linux-specific improvements and support in the same detail as Windows features.
  • Ensure that all code samples, configuration snippets, and operational guidance include Linux/macOS variants where applicable.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by recommending Visual Studio (a Windows-centric tool) and referencing a local Windows file path for schema validation. The only tool-specific guidance is for Windows, with no mention of Linux/macOS alternatives for editing or validating manifest files. However, the manifest examples themselves are platform-neutral XML, and most content is conceptual.
Recommendations
  • Add instructions for validating manifest XML schema on Linux/macOS, such as using VS Code, xmllint, or other cross-platform editors.
  • Mention cross-platform locations or methods for accessing the ServiceFabricServiceModel.xsd schema (e.g., via NuGet package or GitHub), not just the Windows SDK path.
  • Include references to Linux/macOS-compatible development environments and tools alongside Visual Studio.
  • If PowerShell or Windows-specific deployment tools are mentioned elsewhere, ensure CLI or REST API alternatives are documented.
GitHub Create Pull Request
Service Fabric Add a node type to an Azure Service Fabric cluster ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/virtual-machine-scale-set-scale-node-type-scale-out.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias: file paths in configuration examples use Windows-style (e.g., 'D:\\SvcFab'), and the only link for standalone cluster scaling refers specifically to Windows Server. There are no explicit Linux/macOS examples, nor are Linux file paths or tools mentioned. However, the main instructions are Azure-centric and not OS-specific.
Recommendations
  • Provide configuration examples using Linux-style file paths (e.g., '/var/svcfab') alongside Windows paths.
  • Clarify whether the steps and configuration apply equally to Linux-based Service Fabric clusters.
  • Include links or instructions for scaling standalone clusters on Linux, if supported.
  • Explicitly mention OS differences, if any, in node type configuration or management.
GitHub Create Pull Request
Service Fabric Service Fabric Azure Resource Manager deployment guardrails ...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists Windows Server cluster creation as the first 'Next steps' link, placing Windows before Linux. However, the main content is platform-neutral and does not provide OS-specific examples or instructions.
Recommendations
  • Present Linux and Windows cluster creation links in parallel or in alphabetical order to avoid implying priority.
  • Explicitly state that the guidance applies equally to both Windows and Linux deployments, if true.
  • Ensure future examples and troubleshooting steps include both Windows and Linux-specific instructions where relevant.
GitHub Create Pull Request
Service Fabric Plan an Azure Service Fabric cluster deployment ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally treats Windows and Linux equally in terms of cluster support, but in the 'Next steps' section, the link to creating a Windows cluster is listed before the Linux cluster link. No examples, tools, or patterns are given that are Windows-specific, and there are no PowerShell-heavy or Windows-only instructions. However, the ordering of links could subtly signal a Windows-first bias.
Recommendations
  • List the Linux and Windows cluster creation links together, or alternate their order in different documentation sections.
  • Explicitly state that all configuration and deployment steps apply equally to both Windows and Linux clusters where relevant.
  • If examples or code snippets are added in future, ensure parity by providing both Windows and Linux versions.
GitHub Create Pull Request
Service Fabric Upgrade the configuration of an Azure Service Fabric cluster ...-fabric/service-fabric-cluster-config-upgrade-azure.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell-based methods before Azure CLI equivalents and referencing PowerShell-specific commands (Set-AzServiceFabricSetting, Remove-AzServiceFabricSetting) prominently. While Azure CLI options are mentioned, PowerShell is given precedence, which may create friction for Linux/macOS users who typically use CLI tools.
Recommendations
  • List Azure CLI methods before or alongside PowerShell methods to avoid implying preference for Windows tools.
  • Provide explicit examples for both Azure CLI and PowerShell commands, ensuring parity in instructions for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS environments.
  • Avoid referencing PowerShell-specific commands without also providing CLI equivalents.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally presents Windows and Linux parity, but there is a slight Windows bias: Windows container scenarios and tools (IIS, Windows Server, Mirantis Container Runtime) are described in more detail, and Windows examples or links are often listed before Linux equivalents. The IIS lift-and-shift scenario is Windows-specific, and references to Windows container images and tools are more prominent than Linux alternatives. There is no evidence of missing Linux examples, but Windows-centric tools and patterns are mentioned first or exclusively in some sections.
Recommendations
  • Ensure Linux examples and tutorials are listed before or alongside Windows equivalents, not after.
  • Add equivalent Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift) to balance the IIS example.
  • Mention Linux container runtimes and tools (e.g., Podman, containerd) where relevant, not just Docker.
  • Provide parity in detail for both Windows and Linux container orchestration and deployment workflows.
  • Highlight Linux-specific capabilities or challenges in Service Fabric where applicable.
GitHub Create Pull Request
Service Fabric Create a Linux container app on Service Fabric in Azure ...e-fabric/service-fabric-quickstart-containers-linux.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Example In Cleanup
Summary
The documentation is strongly focused on Linux, with all main examples and instructions using Linux tools and workflows. However, in the 'Clean up resources' section, Windows certificate removal is described first and in more detail than macOS or Ubuntu, and the Windows-specific Certificates MMC snap-in is mentioned. This is a minor instance of Windows bias in an otherwise Linux-centric guide.
Recommendations
  • Provide equally detailed instructions for removing certificates on Ubuntu and macOS, possibly with step-by-step screenshots or commands.
  • List Linux/macOS certificate removal instructions before Windows, or present all platforms in parallel for parity.
  • Ensure that any references to Windows tools are matched with equivalent Linux/macOS instructions throughout the documentation.
GitHub Create Pull Request
Service Fabric Develop .NET Core applications with Visual Studio Code ...ervice-fabric-develop-csharp-applications-with-vs-code.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux instructions for opening VS Code with elevated privileges, but Windows instructions are consistently presented before Linux equivalents. All other steps and examples are OS-agnostic, leveraging VS Code's integrated terminal and cross-platform commands. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
  • Present Linux and Windows instructions in parallel or in the order matching the stated cross-platform intent.
  • Explicitly confirm that all subsequent steps (build, deploy, debug) are identical across platforms, or note any differences.
  • Where possible, use neutral language (e.g., 'terminal window' instead of 'command window on Windows') and clarify any platform-specific terminology.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric container application on Linux ...-fabric/service-fabric-get-started-containers-linux.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is generally Linux-focused, but there are a few instances of Windows bias. The most notable is the instruction to 'Open a PowerShell window' for Docker commands, which is not appropriate for Linux users. There are also references to Windows-specific concepts (e.g., named pipes for Docker daemon communication) and some minor ordering bias (Windows selector appears before Linux). However, all critical steps and examples are provided for Linux, and Linux tools are used throughout.
Recommendations
  • Replace 'Open a PowerShell window' with 'Open a terminal window' or 'Open a shell' for Linux instructions.
  • Ensure all command-line examples use Linux shell syntax and terminology.
  • Where Windows-specific concepts are mentioned (e.g., named pipes), clarify the Linux equivalent (e.g., unix domain sockets) and provide Linux-specific instructions first.
  • Consider listing Linux before Windows in selectors and examples, especially on Linux-focused pages.
  • Audit for any lingering references to Windows tools or patterns and replace with Linux equivalents.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, primarily in the 'Next steps' section. It lists Windows-centric tools (Visual Studio and PowerShell) for application upgrades, with no mention of Linux/macOS equivalents or cross-platform alternatives. The main content is platform-neutral, focusing on .NET APIs and serialization concepts, but the guidance for upgrade workflows assumes Windows environments.
Recommendations
  • Add instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI.
  • Include references to Linux/macOS-compatible development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Provide parity in example workflows for application upgrades on Linux/macOS, not just PowerShell and Visual Studio.
  • Clarify which features and APIs are cross-platform, and note any platform-specific limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric versions ...ain/articles/service-fabric/service-fabric-versions.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows information and tables before Linux equivalents, both in navigation and in the order of sections. Windows OS support details are more extensive and appear first, while Linux support is covered later and with less detail. There are no Windows-only examples or tools, and Linux parity is generally maintained in the version tables.
Recommendations
  • Present Windows and Linux sections in parallel or alternate their order to avoid implicit prioritization.
  • Ensure Linux OS support tables are as detailed as Windows ones (e.g., include more distributions if supported).
  • Add explicit navigation aids for Linux users at the top of the page.
  • Review and balance the depth of OS lifecycle information for both platforms.
GitHub Create Pull Request
Service Fabric Service Fabric Azure Resource Manager deployment guardrails ...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists Windows Server cluster creation as the first 'Next steps' link, placing Windows before Linux. However, the main technical content is platform-neutral and does not use Windows-specific tools or examples.
Recommendations
  • List Linux and Windows cluster creation links in parallel or alphabetical order, or clarify that both platforms are supported equally.
  • Explicitly mention that the ARM template examples and mitigation steps apply to both Windows and Linux clusters.
  • If there are platform-specific differences in guardrails or error messages, provide examples for both Windows and Linux.
GitHub Create Pull Request
Service Fabric Create an Azure Load Balancer rule for a cluster ...n/articles/service-fabric/create-load-balancer-rule.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 creating Azure Load Balancer rules. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its section is given equal prominence. There is a slight Windows bias in that PowerShell is featured as the only alternative to Azure CLI, with no mention of Linux/macOS-specific tools or workflows (e.g., Bash, scripting, or REST API usage). The CLI example appears first, which is positive, but the PowerShell section may imply Windows-centric workflows for users seeking alternatives.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS.
  • Add explicit Bash shell examples or mention that the Azure CLI commands work identically on Linux/macOS.
  • Consider including REST API or ARM template examples for users who prefer declarative or non-shell approaches.
  • If PowerShell is included, note that PowerShell Core is available cross-platform, or provide guidance for Linux/macOS users.
  • Avoid implying that PowerShell is a required or preferred alternative to Azure CLI.
GitHub Create Pull Request
Service Fabric Use a Public IP address prefix in a Service Fabric managed cluster ...vice-fabric/how-to-managed-cluster-public-ip-prefix.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying a public IP prefix in a Service Fabric managed cluster. However, the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash scripting, Linux-specific notes), and the ordering of examples places PowerShell immediately after CLI, which may suggest parity but still reflects a Windows-first mindset by including PowerShell as a primary method.
Recommendations
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add explicit Bash or shell script examples for Linux/macOS users, if relevant.
  • Note that PowerShell Core is available on Linux/macOS, but most users on those platforms will prefer Azure CLI.
  • Consider reordering examples to present CLI first, then PowerShell, and explicitly mention platform compatibility.
  • Add a short section or note for Linux/macOS users to confirm that all steps are supported and provide links to platform-specific guidance if needed.
GitHub Create Pull Request
Service Fabric Azure Service Fabric releases ...ocs/blob/main/articles/service-fabric/release-notes.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for Azure Service Fabric releases shows a mild Windows bias. Several release notes and key announcements reference Windows-specific configuration properties (e.g., 'windowsConfiguration.enableAutomaticUpdates'), Windows Server support, and Windows tools (such as Web Platform Installer and Visual Studio). These references often appear before or without equivalent Linux/macOS details. However, the page also mentions Linux support and features, and does not include command-line or scripting examples that would further increase bias.
Recommendations
  • When mentioning configuration properties (such as 'windowsConfiguration.enableAutomaticUpdates'), also include Linux equivalents or clarify if not applicable.
  • Ensure that announcements about OS support (e.g., Windows Server 2022, Ubuntu 20.04) are presented in parallel, not with Windows first.
  • Where Windows-specific tools (WebPI, Visual Studio) are referenced, add information about Linux/macOS alternatives (e.g., CLI, VS Code, package managers).
  • Explicitly mention Linux/macOS support for features and releases where applicable.
  • Consider adding a summary table or section that highlights cross-platform compatibility for each release.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools and paths (Visual Studio, C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd) as the primary method for schema validation and IntelliSense. No Linux or cross-platform alternatives are mentioned for authoring or validating manifest files. Additionally, the only tooling guidance is Windows-centric and appears early in the article.
Recommendations
  • Include instructions or examples for validating and editing manifest XML files on Linux/macOS, such as using VS Code, JetBrains Rider, or command-line tools like xmllint.
  • Mention the location of Service Fabric SDK schemas on Linux/macOS installations, if available.
  • Provide cross-platform guidance for authoring manifests, such as using platform-agnostic editors or CLI tools.
  • Avoid referencing Windows paths and tools exclusively; offer parity for non-Windows environments.
GitHub Create Pull Request
Service Fabric Plan an Azure Service Fabric cluster deployment ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally maintains OS neutrality throughout most of the content, mentioning both Windows and Linux as supported platforms for Service Fabric clusters. However, in the 'Next steps' section, the link to 'Create a Service Fabric cluster running Windows' is presented before the link to the Linux equivalent, indicating a subtle 'windows_first' bias. No examples or tooling are specific to Windows or PowerShell, and Linux is not omitted from any critical instructions.
Recommendations
  • Present links to Windows and Linux cluster creation in parallel or alphabetically, rather than listing Windows first.
  • Where possible, alternate the order of OS mentions throughout documentation to avoid implicit prioritization.
  • Explicitly state that all configuration steps and templates apply equally to both Windows and Linux clusters, unless otherwise noted.
GitHub Create Pull Request
Service Fabric Service Fabric cluster capacity planning considerations ...cles/service-fabric/service-fabric-cluster-capacity.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools and patterns (such as Patch Orchestration Application and standalone clusters hosted in Windows), and by providing instructions for Windows before Linux equivalents. There is a lack of explicit Linux/macOS examples or guidance for non-Windows environments, especially regarding cluster configuration and maintenance tasks.
Recommendations
  • Include explicit instructions and examples for Linux/macOS environments, especially for standalone clusters (e.g., how to upgrade cluster settings on Linux).
  • Mention Linux equivalents for Windows-specific tools (such as alternatives to Patch Orchestration Application for automating OS updates).
  • Provide parity in documentation structure by listing Linux/macOS procedures alongside Windows procedures, rather than Windows-first.
  • Clarify which steps or tools are cross-platform and which are Windows-only, to help users identify relevant guidance.
GitHub Create Pull Request
Service Fabric Overview of Service Fabric and containers ...s/service-fabric/service-fabric-containers-overview.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page presents a generally balanced overview of Service Fabric container support for both Linux and Windows. However, there are subtle signs of Windows bias: Windows container scenarios (e.g., IIS lift and shift) are described in more detail and referenced first in some lists; Windows-specific tools (IIS, Mirantis Container Runtime, DockerEE) are mentioned, while Linux equivalents are not elaborated. The page also links to Windows tutorials and resources before Linux ones in several places. There is no explicit PowerShell example, but the focus on Windows tools and scenarios may create friction for Linux users.
Recommendations
  • Ensure Linux tutorials and resources are listed before or alongside Windows equivalents.
  • Provide Linux-specific container scenarios (e.g., Apache/Nginx lift and shift) to match the IIS example for Windows.
  • Mention Linux container runtime alternatives (e.g., containerd, Podman) if supported, not just Docker.
  • Balance the detail level in scenario descriptions for both platforms.
  • Include explicit Linux command-line examples or references where Windows tools are mentioned.
GitHub Create Pull Request
Service Fabric Develop .NET Core applications with Visual Studio Code ...ervice-fabric-develop-csharp-applications-with-vs-code.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally presents a cross-platform workflow, but in the 'Open the application in VS Code' section, Windows instructions are presented before Linux instructions. There are no exclusive Windows tools or missing Linux examples; both platforms are covered for all critical steps.
Recommendations
  • Present Linux and Windows instructions in parallel (side-by-side or in tabs), or alternate which platform is listed first.
  • Explicitly mention macOS if supported, or clarify its parity with Linux.
  • Ensure that all screenshots and instructions are clearly marked for the relevant platform if there are differences.
GitHub Create Pull Request
Service Fabric Monitor Linux cluster events in Azure Service Fabric ...ervice-fabric/service-fabric-diagnostics-oms-syslog.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is focused on Linux clusters and Syslog integration, but several configuration parameters and consumer/producer names reference Windows-centric tools (e.g., AzureWinFabCsv, AzureWinFabCrashDump, AzureTableWinFabEtwQueryable, WinFabLttProducer). These are listed before the Linux-specific SyslogConsumer, and no Linux-native equivalents or explanations are provided for these Windows-named components. However, the main instructions and examples are Linux-focused, and there are no PowerShell or Windows-only command examples.
Recommendations
  • Clarify the purpose of Windows-named consumer/producer instances in the configuration and whether they are required or optional for Linux clusters.
  • Provide Linux-native equivalents or explicitly state which components are relevant only for Windows clusters.
  • Reorder configuration examples to list Linux-relevant components first, or separate Windows and Linux configuration sections for clarity.
  • Add a note explaining the cross-platform nature of Service Fabric diagnostics and which settings apply to Linux clusters.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric container application on Linux ...-fabric/service-fabric-get-started-containers-linux.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is generally Linux-focused, as intended, but there are a few instances of Windows bias: the instructions for logging into Docker and building the image reference opening a PowerShell window, which is a Windows-specific tool. Additionally, the example commands are not always explicitly shown in a Linux shell context (e.g., 'Open a PowerShell window' instead of 'Open a terminal'). The 'Windows' option is listed before 'Linux' in the platform selector, and some references to Windows-specific patterns (such as named pipes) appear in generic configuration guidance.
Recommendations
  • Replace 'Open a PowerShell window' with 'Open a terminal window' or specify Linux shell usage.
  • Ensure all command-line examples use Linux shell syntax and context.
  • Move Linux before Windows in platform selectors when the page is Linux-focused.
  • Clarify any configuration instructions that mention Windows-specific tools or patterns, and provide Linux equivalents first or exclusively.
  • Audit for any lingering references to Windows tools (e.g., PowerShell, named pipes) and replace with Linux alternatives.
GitHub Create Pull Request
← Previous Page 28 of 29 Next →