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 326-350 of 718 flagged pages
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows PowerShell examples first and in greater detail, with multiple PowerShell commands listed for deployment, management, and upgrade scenarios. The CLI (sfctl) examples are provided second, but without explicit mention of Linux or macOS usage, and PowerShell is the only shell-specific example. Windows-specific tools (PowerShell cmdlets) are emphasized, and the 'Isolation' Compose directive is noted as 'only for Windows'. There are no explicit Linux/macOS shell examples or guidance for those platforms.
Recommendations
  • Add explicit Linux/macOS shell examples using sfctl, including installation and usage notes for those platforms.
  • Clarify that sfctl is cross-platform and provide links or instructions for Linux/macOS users.
  • Balance the order of examples: present CLI (sfctl) examples before or alongside PowerShell to avoid Windows-first bias.
  • Mention any platform-specific limitations or differences (e.g., 'Isolation' directive) in a dedicated section.
  • Include troubleshooting or environment setup notes for Linux/macOS users.
GitHub Create Pull Request
Service Fabric Enable disk encryption for Linux clusters ...c/service-fabric-enable-azure-disk-encryption-linux.md
Medium 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 page for enabling disk encryption for Linux clusters in Azure Service Fabric shows a notable Windows bias. PowerShell commands are presented first and in greater detail, with explicit references to Windows filesystem paths (e.g., c:\certificates), and the use of PowerShell-specific cmdlets throughout. While Azure CLI examples are provided, they are often secondary and some instructions (such as certificate handling) assume Windows conventions. There is limited guidance for Linux-native tooling or shell environments, and Linux-specific patterns (e.g., bash scripting, Linux file paths) are not demonstrated.
Recommendations
  • Provide Linux-native command examples (e.g., bash scripts) alongside or before PowerShell examples.
  • Use Linux file path conventions (e.g., /home/user/certificates) in Linux-focused documentation.
  • Include instructions for certificate generation and management using Linux tools (e.g., openssl) rather than only PowerShell.
  • Clarify when commands are platform-agnostic (Azure CLI) and when they are Windows-specific (PowerShell), and recommend CLI for cross-platform use.
  • Add troubleshooting and validation steps using Linux commands (e.g., lsblk, cryptsetup status) where appropriate.
GitHub Create Pull Request
Service Fabric Package an existing executable to Azure Service Fabric ...abric/service-fabric-guest-executables-introduction.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools and paths (e.g., Visual Studio, C:\Program Files), mentioning Windows tooling before any cross-platform alternatives, and omitting explicit Linux/macOS instructions or examples. There is no mention of Linux packaging workflows, nor are Linux/macOS equivalents for the Service Fabric SDK installation path or packaging tools provided.
Recommendations
  • Include Linux/macOS-specific instructions for packaging and deploying guest executables to Service Fabric.
  • Provide examples using cross-platform command-line tools (e.g., Azure CLI, Service Fabric CLI) rather than focusing on Visual Studio.
  • Document the installation path and usage of Service Fabric SDK on Linux/macOS.
  • Add sample directory structures and file paths using Linux conventions (e.g., /opt/servicefabric/schemas/).
  • Ensure that all referenced samples and quickstarts are compatible with Linux/macOS and clearly indicate platform support.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting activation and deactivation life cycle ...les/service-fabric/service-fabric-hosting-lifecycle.md
Medium Priority View Details →
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 page demonstrates a moderate Windows bias. PowerShell is referenced as the primary tool for deploying and removing applications, and the only explicit tooling example for downloading a ServicePackage in advance links to a PowerShell cmdlet. No Linux or cross-platform CLI examples are provided, and Windows-centric tools are mentioned before any Linux alternatives (which are absent).
Recommendations
  • Include equivalent Linux/macOS instructions and examples, such as using Azure CLI or Service Fabric CLI (sfctl) for deployment and management tasks.
  • Provide links to documentation for Linux/macOS tooling, not just PowerShell.
  • When referencing tools or commands, present cross-platform options first or side-by-side, rather than defaulting to Windows/PowerShell.
  • Clarify which steps or commands are platform-specific and offer alternatives for other platforms.
GitHub Create Pull Request
Service Fabric Azure Service Fabric hosting model ...rticles/service-fabric/service-fabric-hosting-model.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell command-line examples for service creation and management, referencing Windows-centric tools and modules (e.g., Service Fabric PowerShell cmdlets), and omitting equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform REST usage). Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, making it less accessible for users on Linux or macOS.
Recommendations
  • Add Azure CLI examples for service creation and management, which are cross-platform.
  • Include Bash or shell script equivalents for common operations.
  • Explicitly mention REST API usage with sample curl commands for Linux/macOS users.
  • Clarify which tools and commands are available on Linux/macOS, and provide links to relevant documentation.
  • Reorder examples so that cross-platform or REST approaches are presented before or alongside PowerShell.
  • Add a note about Service Fabric CLI (sfctl), which is supported on Linux/macOS.
GitHub Create Pull Request
Service Fabric Azure Service Fabric image store connection string ...fabric/service-fabric-image-store-connection-string.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references PowerShell and Visual Studio as primary tools for deployment and verification, both of which are traditionally Windows-centric. The 'Next steps' section links only to PowerShell-based deployment instructions, and there are no explicit Linux/macOS CLI or scripting examples. While .NET and REST APIs are mentioned as alternatives for retrieving the cluster manifest, these are listed after PowerShell and lack concrete Linux usage guidance.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Azure CLI, Bash scripts, or cross-platform tools for deployment and manifest retrieval.
  • Provide links to documentation pages that cover Linux/macOS workflows for Service Fabric, including application deployment and cluster management.
  • Mention and demonstrate how to use REST API calls from Bash/cURL or other cross-platform tools.
  • Include parity in 'Next steps' by linking to Linux/macOS deployment guides alongside PowerShell instructions.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned first and in more detail, with explicit references to PowerShell cmdlets and scripts. While sfctl and Jenkins (cross-platform tools) are mentioned, their usage is less detailed and appears after Windows tools. There are no explicit Linux/macOS command-line examples or workflows, and the documentation assumes familiarity with Windows tooling.
Recommendations
  • Add explicit Linux/macOS command-line examples for creating applications, such as using sfctl and bash scripts.
  • Provide step-by-step instructions for parameter substitution using Linux tools (e.g., sed, envsubst) alongside Windows/PowerShell examples.
  • Clarify which tools and scripts are cross-platform and which are Windows-only.
  • Ensure that references to Windows tools (PowerShell, Visual Studio) are balanced with equivalent Linux/macOS workflows.
  • Consider reordering examples so that cross-platform tools (sfctl, Jenkins) are presented before or alongside Windows-specific tools.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific concepts such as running services as local admin accounts, using system groups like 'Administrators', and mentions ServiceFabric PowerShell modules for service creation. Examples use Windows-style batch scripts (Setup.bat) and executables (.exe), with no mention of Linux shell scripts or Linux/macOS user/group management. Windows terminology and tools are presented first and exclusively, with no Linux equivalents or cross-platform notes.
Recommendations
  • Add Linux/macOS equivalents for user/group management and service accounts, including examples using Linux system users and groups.
  • Provide examples of using shell scripts (e.g., Setup.sh) in addition to batch files for SetupEntryPoint.
  • Mention Linux-compatible tools (such as CLI commands) for managing Service Fabric applications, not just PowerShell.
  • Clarify which features and manifest elements are cross-platform and which are Windows-only, ideally with platform compatibility tables.
  • Include notes or links to documentation for deploying Service Fabric applications on Linux clusters.
GitHub Create Pull Request
Service Fabric Azure Service Fabric container application manifest examples ...abric/service-fabric-manifest-example-container-app.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing the Windows Server 2016 Container Sample as the basis for all manifest examples, using Windows-specific paths (e.g., 'c:\VolumeTest\Data'), and mentioning Windows tools (e.g., 'winver' command) for OS build identification. There is no mention of Linux container samples, nor are Linux-specific patterns, file paths, or OS build identification methods provided. While some notes acknowledge Linux (e.g., certificate handling), practical Linux examples and instructions are absent.
Recommendations
  • Include Linux-based container sample manifests and reference them alongside Windows samples.
  • Provide Linux-specific file path examples (e.g., '/mnt/VolumeTest/Data') in volume bindings.
  • Document how to obtain the OS build/version on Linux (e.g., 'cat /etc/os-release' or 'uname -r') for image overrides.
  • Clarify any differences in Service Fabric manifest configuration or runtime behavior between Windows and Linux clusters.
  • Ensure all features (e.g., volume drivers, certificate import) are described with both Windows and Linux usage notes and examples.
GitHub Create Pull Request
Service Fabric Configure networking modes for container services ...cles/service-fabric/service-fabric-networking-modes.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific configuration steps (such as NSG rules for DNS, network recreation on VM reboot, and mixing networking modes) are described in detail, while Linux limitations are only briefly mentioned. Examples and instructions often focus on Windows clusters, with Linux support or differences relegated to notes or not covered in equivalent detail. There are no Linux-specific configuration examples, and some features (like mixing networking modes) are explicitly unsupported on Linux but not explained further.
Recommendations
  • Provide explicit Linux configuration examples, especially for networking setup and service manifests.
  • Clarify Linux-specific limitations and offer guidance or workarounds for Linux users.
  • Balance the presentation order: present Windows and Linux instructions side-by-side or in parallel sections.
  • Include troubleshooting tips for Linux clusters, similar to those given for Windows (e.g., handling network resets).
  • Expand on why certain features (like mixing networking modes) are unsupported on Linux and suggest alternatives.
GitHub Create Pull Request
Service Fabric Start and stop cluster nodes .../service-fabric/service-fabric-node-transition-apis.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets alongside managed API calls, but does not mention or provide examples for Linux or macOS equivalents. All sample code is in C# and assumes usage of the .NET FabricClient, with no mention of cross-platform CLI tools or REST APIs. PowerShell is referenced before any Linux alternatives, and there are no bash, shell, or Linux-native instructions or code samples.
Recommendations
  • Add equivalent Linux/macOS instructions, such as using Azure CLI, REST API, or Service Fabric CLI (sfctl) where applicable.
  • Provide bash or shell script examples for common node operations.
  • Explicitly mention cross-platform tools and how Linux/macOS users can perform the same tasks.
  • Reorder references so that platform-neutral or cross-platform methods are presented before Windows-specific tools.
  • Include notes about platform compatibility for all APIs and tools mentioned.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (Visual Studio, PowerShell) are mentioned first and in more detail than Linux equivalents. The Linux development section is shorter and less prominent, with fewer tool examples (Eclipse, Yeoman) and no direct Linux command-line or deployment examples. The quickstart link points to a .NET/Windows-focused guide, and there are no Linux/macOS-specific walkthroughs or parity in example depth.
Recommendations
  • Provide Linux/macOS examples alongside Windows ones, especially in quickstart and deployment sections.
  • Mention Linux tools (e.g., Bash, CLI, VS Code) with equal prominence and detail as Windows tools.
  • Link to Linux/macOS quickstart guides directly from the overview page.
  • Ensure that all critical workflows (development, deployment, monitoring) have step-by-step instructions for both Windows and Linux/macOS.
  • Balance the order of tool mentions (e.g., alternate Windows and Linux first in different sections).
GitHub Create Pull Request
Service Fabric Package an Azure Service Fabric app ...articles/service-fabric/service-fabric-package-apps.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. All command-line and scripting examples use Windows-specific tools (PowerShell, tree, msbuild.exe), and file paths are shown in Windows format. There are no Linux/macOS equivalents or alternative instructions for common tasks such as packaging, validating, or compressing Service Fabric applications. Visual Studio is presented as the primary IDE, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users, who must infer or research equivalent commands and workflows.
Recommendations
  • Provide Linux/macOS equivalents for all command-line examples (e.g., use 'find' or 'ls' instead of 'tree', and show bash/zsh commands).
  • Document how to package and validate Service Fabric applications using cross-platform .NET CLI tools (e.g., 'dotnet build'), or clarify if msbuild is available on Linux/macOS.
  • Include instructions for compressing packages using common Linux/macOS utilities (e.g., 'zip', 'tar').
  • Mention and provide examples for using Service Fabric CLI (sfctl), which is cross-platform, for deployment and validation tasks.
  • Clarify any platform-specific limitations or requirements for Service Fabric tooling.
  • Reorder examples so that cross-platform or Linux/macOS instructions are presented alongside or before Windows-specific ones.
GitHub Create Pull Request
Service Fabric Service Fabric project creation next steps ...ric/service-fabric-project-creation-next-step-tasks.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page shows a notable Windows bias. Tutorials and walkthroughs are exclusively for Windows (e.g., 'C# Reliable Services service on Windows', 'Windows container application'), with no mention of Linux equivalents or cross-platform options. Deployment scripts are referenced with PowerShell, a Windows-centric tool, and the 'Next steps' section highlights creating a Windows cluster, omitting Linux cluster creation. There are no examples, instructions, or links for Linux/macOS users, making it unclear how to proceed on non-Windows platforms.
Recommendations
  • Add Linux/macOS equivalents for all walkthroughs and tutorials, or clearly indicate cross-platform support.
  • Include deployment instructions and scripts for Linux (e.g., Bash, CLI) alongside PowerShell.
  • Provide links to documentation for creating Linux clusters and managing Service Fabric on Linux.
  • Ensure examples and sample applications are labeled with platform compatibility.
  • Present Windows and Linux options side-by-side, or clarify platform requirements at the start of each section.
GitHub Create Pull Request
Service Fabric Change ReliableDictionaryActorStateProvider settings ...e-actors-reliabledictionarystateprovider-configuration.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Visual Studio (Windows-only) as the primary tool for generating configuration files, mentioning PowerShell commands without Linux equivalents, and using Windows-style file paths in examples. Linux-specific instructions are minimal and relegated to notes, with no Linux/macOS configuration workflows or command-line examples provided.
Recommendations
  • Include instructions for generating and editing settings.xml files on Linux/macOS, such as using the Service Fabric CLI (sfctl) or other cross-platform tools.
  • Provide Linux/macOS equivalents for PowerShell commands, e.g., show how to view the cluster manifest using sfctl or other Linux-native tools.
  • Add sample file paths using Linux conventions (e.g., /var/log/SharedLog.Log) alongside Windows paths.
  • Present Linux/macOS examples and workflows alongside or before Windows examples to ensure parity.
  • Clarify which steps are platform-specific and provide guidance for both environments.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias, primarily through its extensive coverage of HTTP.sys, which is Windows-only, and references to Windows-specific tools and APIs (such as netsh and the Windows HTTP Server API). HTTP.sys usage is described in detail, but it is explicitly unavailable on Linux/macOS. While Kestrel, the cross-platform web server, is covered and recommended for Linux, the documentation often presents Windows-specific options (HTTP.sys) first or in greater depth, and does not provide Linux/macOS-specific troubleshooting, configuration, or parity examples. There are no PowerShell-only examples, but Windows-centric patterns and tools are mentioned without Linux equivalents.
Recommendations
  • Clearly mark Windows-only sections at the top and direct Linux/macOS users to relevant Kestrel sections.
  • Provide explicit Linux/macOS configuration and deployment examples, especially for ServiceManifest.xml, port assignment, and firewall configuration.
  • Add troubleshooting tips for Linux/macOS environments (e.g., SELinux, iptables, systemd integration).
  • Balance the order of presentation so that cross-platform (Kestrel) options are shown first or in parallel with Windows-only options.
  • Where Windows tools (e.g., netsh) are mentioned, provide Linux/macOS alternatives or note their irrelevance.
  • Include a summary table mapping features and limitations for both platforms.
GitHub Create Pull Request
Service Fabric Change FabricTransport settings ...service-fabric-reliable-actors-fabrictransportsettings.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows certificate store concepts (e.g., 'LocalMachine', 'My'), using Windows-centric certificate subject names (e.g., 'WinFabric-Test-SAN1-Alice'), and omitting concrete Linux configuration examples. Although there is a brief note about PEM certificates for Linux, all XML configuration samples and attribute values are tailored to Windows environments, with no equivalent Linux instructions or examples provided.
Recommendations
  • Add explicit Linux configuration examples, including sample XML with Linux-appropriate values for certificate store location and format.
  • Clarify how parameters like 'CertificateStoreLocation' and 'CertificateStoreName' should be set on Linux nodes (e.g., file paths, environment variables, or other mechanisms).
  • Provide Linux-specific guidance for certificate subject names and thumbprints, including how to obtain and reference them.
  • Ensure that Linux instructions are presented alongside Windows instructions, not only as a side note.
GitHub Create Pull Request
Service Fabric Service Fabric Backup and Restore ...ric/service-fabric-reliable-services-backup-restore.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Service Fabric Backup and Restore demonstrates a moderate Windows bias. The only explicit tooling example for testing backup and restore uses the PowerShell cmdlet 'Start-ServiceFabricPartitionDataLoss', with no mention of Linux/macOS equivalents or cross-platform alternatives. Windows/PowerShell tools are referenced exclusively, and there are no CLI or bash examples. Additionally, the workaround for long file paths references Windows-specific kernel32 APIs. The documentation does not provide guidance for Linux/macOS users on how to perform equivalent operations, nor does it mention Service Fabric CLI (sfctl), which is cross-platform.
Recommendations
  • Include equivalent Linux/macOS instructions for testing backup and restore, such as using the Service Fabric CLI (sfctl) or REST API.
  • Provide bash or shell script examples alongside PowerShell examples.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones.
  • Clarify which APIs and tooling are available on Linux/macOS clusters and provide links to relevant documentation.
  • For file path limitations, discuss Linux/macOS filesystem behaviors and workarounds, not just Windows kernel32 APIs.
GitHub Create Pull Request
Service Fabric Configure Azure Service Fabric Reliable Services ...bric/service-fabric-reliable-services-configuration.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-centric tools and workflows (e.g., PowerShell, Visual Studio) are mentioned first or exclusively, with no Linux equivalents or examples provided. Configuration file paths and security certificate instructions are primarily Windows-oriented, and Linux-specific instructions are minimal or relegated to notes. There are no Linux/macOS command-line examples, nor guidance for editing cluster manifests or settings on non-Windows platforms.
Recommendations
  • Provide Linux/macOS equivalents for all command-line instructions (e.g., show how to view the cluster manifest using Service Fabric CLI or REST API, not just PowerShell).
  • Include examples of editing configuration files and paths using Linux conventions (e.g., use /var/log/servicefabric/SharedLog.Log instead of f:\SharedLog.Log).
  • Offer guidance for developing and debugging Service Fabric applications on Linux/macOS, including alternatives to Visual Studio (e.g., VS Code, CLI tools).
  • Expand certificate configuration instructions for Linux, including command-line steps for PEM certificate management and integration.
  • Reorder examples so that Windows and Linux instructions are presented with equal prominence, or in parallel sections.
GitHub Create Pull Request
Service Fabric Secure service remoting communications with C# ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-reliable-services-secure-communication.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on C# service remoting security in Azure Service Fabric, with all code examples and configuration patterns tailored to Windows environments. Windows certificate store concepts (StoreLocation, StoreName) are used throughout, and Linux-specific instructions are limited to a brief note about certificate file placement, with no Linux-oriented code or configuration examples. The page does not provide parity for Linux users running C# services, omitting details on how to configure certificates or settings for Linux clusters.
Recommendations
  • Add explicit C# code and configuration examples for Linux clusters, showing how to reference PEM-formatted certificates and any differences in API usage or configuration.
  • Document the process for installing and referencing certificates on Linux nodes, including directory structure, file permissions, and mapping to Service Fabric APIs.
  • Clarify which settings (e.g., StoreLocation, StoreName) are ignored or replaced on Linux, and provide Linux-specific equivalents or guidance.
  • Present Windows and Linux instructions/examples side-by-side or in parallel sections, rather than focusing solely on Windows.
  • Include troubleshooting tips for common Linux certificate issues in Service Fabric.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily featured for command-line examples, with no mention of Linux/macOS equivalents (such as Bash, CLI, or cross-platform tools). Windows-specific tools and patterns (PowerShell cmdlets, Windows-style paths, and examples) are presented before REST or API options. There is no guidance for Linux users on how to perform health reporting tasks from non-Windows environments, nor are alternative CLI examples (e.g., Azure CLI, Bash) provided.
Recommendations
  • Add explicit examples for Linux/macOS environments, such as using Bash, Azure CLI, or cross-platform .NET Core tools.
  • Clarify whether PowerShell examples work on PowerShell Core (pwsh) on Linux/macOS, and provide installation/setup instructions if so.
  • Include REST API examples with curl or other cross-platform tools, and show how to authenticate and send health reports from Linux.
  • Reorder examples so that cross-platform or REST approaches are presented before or alongside Windows/PowerShell methods.
  • Mention any limitations or requirements for Linux users (e.g., .NET Core support, Service Fabric CLI availability) and provide links to relevant resources.
GitHub Create Pull Request
Service Fabric Custom Image .../articles/service-fabric/how-to-deploy-custom-image.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by consistently referencing 'custom windows images' first, providing only PowerShell examples for role assignment, and mentioning Windows/PowerShell tools and patterns before their Linux equivalents. There are no Linux-specific command examples (e.g., Azure CLI or Bash), and the ARM template examples do not clarify Linux image usage. While links to Linux documentation exist, actionable steps and examples are Windows-centric.
Recommendations
  • Provide Azure CLI and Bash examples for role assignment and other operations alongside PowerShell.
  • Explicitly mention and show how to use Linux custom images in ARM templates, including image references and OS configuration differences.
  • Balance the narrative by referring to 'Windows and Linux images' together, rather than defaulting to Windows first.
  • Include Linux-specific troubleshooting tips and considerations for Service Fabric clusters.
  • Ensure that all referenced documentation links (e.g., finding marketplace images) are paired: one for Windows, one for Linux.
GitHub Create Pull Request
Service Fabric Set up IP tags on a Service Fabric managed cluster ...icles/service-fabric/how-to-managed-cluster-ip-tags.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation references provisioning IP tags using a PowerShell-specific Azure module and links to a PowerShell example, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI, ARM template, or REST API). This creates friction for non-Windows users who may not use PowerShell.
Recommendations
  • Include instructions and examples for provisioning IP tags using Azure CLI, which is cross-platform.
  • Reference ARM template and REST API methods for provisioning IP tags, not just PowerShell.
  • Add explicit notes or sections for Linux/macOS users to ensure parity.
  • Order examples so that cross-platform tools (CLI, ARM) are presented before or alongside Windows-specific tools.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays a Windows bias by referencing Windows-specific container images (microsoft/windowsservercore, microsoft/nanoserver) as defaults in the 'ContainerImagesToSkip' setting, and mentioning them before any Linux equivalents. There are no Linux container images (e.g., Ubuntu, Alpine) referenced as examples or defaults, nor is there guidance for Linux/macOS users. The examples and explanations focus on Windows images, which may lead Linux users to feel unsupported or unclear about best practices for their platforms.
Recommendations
  • Include Linux container images (e.g., ubuntu, alpine) in examples and defaults for 'ContainerImagesToSkip'.
  • Explicitly mention that the settings and cleanup apply equally to Linux-based images and provide examples.
  • Add a note clarifying platform support and any differences in behavior between Windows and Linux containers.
  • Provide parity in documentation by listing both Windows and Linux images in tables and examples.
GitHub Create Pull Request
Service Fabric Create a Service Fabric managed cluster (SFMC) with Ephemeral OS disks for node types ...ce-fabric/how-to-managed-cluster-ephemeral-os-disks.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for ARM template deployment and referencing RDP (a Windows-specific remote access protocol) for VM administration. There are no CLI or Bash examples for Linux/macOS users, nor are cross-platform tools like Azure CLI mentioned. The use of Windows tools and terminology is prevalent, and Linux alternatives are missing.
Recommendations
  • Add Azure CLI examples for ARM template deployment, showing equivalent steps for Linux/macOS users.
  • Include instructions for SSH access to VMs, alongside RDP, to support Linux/macOS administration.
  • Present cross-platform deployment methods first or in parallel, rather than focusing on PowerShell.
  • Explicitly mention that all steps can be performed from Linux/macOS and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
← Previous Page 14 of 29 Next →