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 1501-1525 of 2475 flagged pages
Service Fabric Azure Service Fabric standalone cluster scaling ...ce-fabric/service-fabric-cluster-scaling-standalone.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 on scaling Azure Service Fabric standalone clusters exhibits Windows bias by exclusively referencing PowerShell cmdlets (e.g., Get-ServiceFabricClusterManifest, Start-ServiceFabricClusterConfigurationUpgrade) and linking to Windows Server-specific guides. There are no Linux-specific examples, tools, or instructions provided, nor is it clarified whether Linux-based standalone clusters are supported or how to scale them.
Recommendations
  • Add examples and instructions for scaling standalone clusters running on Linux, including relevant command-line tools (e.g., bash scripts, sfctl, or REST API usage).
  • Clarify whether standalone Service Fabric clusters can be deployed and scaled on Linux, and if not, explicitly state this limitation.
  • Provide parity in documentation by including Linux-specific guidance or links alongside Windows/PowerShell instructions.
  • Mention cross-platform tools (such as sfctl) where applicable, and show how to use them for cluster scaling operations.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-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 upgrading Azure Service Fabric clusters shows mild Windows bias. While most upgrade instructions are platform-neutral, sections such as 'Upgrading OS images for cluster nodes' and references to Patch Orchestration Application (POA) link only to Windows-specific guidance. Additionally, PowerShell is mentioned alongside Azure CLI for cluster management tasks, but Linux-specific tools or examples are not provided. The documentation does not explicitly state whether Linux-based Service Fabric clusters are supported or provide parity guidance for Linux users.
Recommendations
  • Add explicit guidance and links for upgrading OS images on Linux-based Service Fabric clusters, if supported.
  • Provide Linux/macOS-specific examples for certificate management, port opening, and node property configuration using Azure CLI or relevant tools.
  • Clarify whether Patch Orchestration Application (POA) or similar solutions exist for Linux clusters, and link to relevant documentation.
  • Where PowerShell is mentioned, ensure Azure CLI examples are equally prominent and platform-neutral.
  • State cluster OS support matrix early in the article to clarify applicability.
GitHub Create Pull Request
Service Fabric Azure Service Fabric application resource model ...ervice-fabric/service-fabric-concept-resource-model.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 demonstrates a notable Windows bias. All deployment and deletion examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzResource) without any Azure CLI or Bash equivalents. The application packaging step is described using Visual Studio, a Windows-centric tool, with no mention of cross-platform alternatives. No Linux/macOS-specific instructions or examples are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add Azure CLI examples for deployment and deletion alongside PowerShell cmdlets.
  • Provide instructions for packaging applications using cross-platform tools (e.g., dotnet CLI, SF tooling) instead of only Visual Studio.
  • Mention and show Bash or shell commands for uploading files to Azure Blob Storage (e.g., using az storage blob upload).
  • Clearly indicate which steps are cross-platform and which are Windows-specific, and provide alternatives where possible.
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-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references the Service Fabric SDK schema file using a Windows file path and does not mention Linux or cross-platform equivalents. The overall structure and examples (such as .exe files) are Windows-centric, and there is no explicit mention of Linux tooling, file paths, or packaging non-Windows executables. However, the content does not explicitly exclude Linux, and Service Fabric does support Linux clusters.
Recommendations
  • Add references to Linux file paths for the Service Fabric SDK schema, or clarify if/where it is available on Linux.
  • Include examples using Linux-compatible executables (e.g., ELF binaries, .sh scripts) alongside .exe examples.
  • Mention cross-platform or Linux-specific tooling for packaging and deploying guest executables, if available.
  • Clarify any platform-specific limitations or requirements for guest executables on Linux clusters.
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-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 provides PowerShell-based examples and references for managing Service Fabric services, with no equivalent CLI or Linux-native examples. It assumes the use of PowerShell and Windows tooling for service creation and management, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for service creation and management, especially for specifying ServicePackageActivationMode.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples.
  • Clarify whether PowerShell Core (cross-platform) is supported, or if examples are Windows PowerShell-specific.
  • Where possible, provide bash or shell script equivalents for common operations.
  • Link to Linux/macOS-specific guidance if available.
GitHub Create Pull Request
Service Fabric Learn more about Azure Service Fabric ...icles/service-fabric/service-fabric-content-roadmap.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides a broad overview of Azure Service Fabric, which supports both Windows and Linux. However, there is notable Windows bias: Windows-specific tools (e.g., PowerShell, Visual Studio) are mentioned first or exclusively in several sections, and some examples reference Windows services and executables (e.g., FabricHost.exe) without clarifying Linux equivalents. Standalone cluster creation and upgrade instructions are Windows-only, and Linux standalone clusters are not yet supported, but this is clearly stated. CLI tools are mentioned, but PowerShell is often listed first. There are few explicit Linux examples or parity notes, and Linux-specific workflows are not illustrated.
Recommendations
  • Where possible, provide Linux-specific examples and workflows alongside Windows ones, especially for cluster management, health monitoring, and application lifecycle.
  • Mention Linux CLI tools (sfctl) and Bash usage equally with PowerShell, and avoid listing Windows tools first unless contextually appropriate.
  • Clarify differences in service management between Windows and Linux nodes, including which executables/services are used on Linux.
  • Add links to Linux-focused tutorials and documentation where Windows-only instructions are given.
  • Explicitly note feature parity or limitations for Linux throughout, not just in the standalone cluster section.
GitHub Create Pull Request
Service Fabric Azure Service Fabric DNS service ...n/articles/service-fabric/service-fabric-dnsservice.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 setting DNS names, but does not offer equivalent Linux CLI or scripting examples. Windows tools (PowerShell, Visual Studio) are mentioned for service configuration, while Linux-specific workflows are not covered. The limitations section notes Linux support is restricted, but the overall guidance and examples favor Windows users.
Recommendations
  • Add Linux CLI (e.g., Bash, Azure CLI) examples for configuring DNS names and services.
  • Include instructions for editing ApplicationManifest.xml and deploying from Linux environments (e.g., using VS Code or command-line tools).
  • Clarify any differences in workflow for Linux users, especially where portal or PowerShell methods are unavailable.
  • Provide guidance for enabling DNS service on Linux clusters via ARM templates, including any required steps or caveats.
GitHub Create Pull Request
Service Fabric Azure Service Fabric Docker Compose Deployment Preview ...ticles/service-fabric/service-fabric-docker-compose.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 provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This may create friction for Linux/macOS users, as PowerShell is primarily a Windows tool, and the CLI is cross-platform. There is no explicit mention of Linux/macOS-specific workflows or considerations, though the CLI examples are suitable for those platforms.
Recommendations
  • Present Service Fabric CLI (sfctl) examples before PowerShell, as CLI is cross-platform and more relevant to Linux/macOS users.
  • Explicitly state that sfctl is supported on Linux/macOS and provide installation instructions or a link for those platforms.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while sfctl is recommended for Linux/macOS.
  • Consider including a short section on Linux/macOS prerequisites or environment setup for Service Fabric Compose deployments.
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-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page on Azure Service Fabric hosting activation and deactivation life cycle is largely platform-neutral in its conceptual explanations. However, the 'Next steps' section directs users to deployment instructions specifically in PowerShell, and an example link for downloading a ServicePackage refers to a PowerShell cmdlet. This creates a subtle Windows bias by implying PowerShell as the primary or only supported tooling for deployment and management, without mentioning Linux or cross-platform alternatives (such as Azure CLI or REST APIs).
Recommendations
  • Add links or references to Linux/macOS-compatible deployment instructions, such as using Azure CLI or REST APIs for deploying and removing applications.
  • Clarify in the 'Next steps' section that PowerShell is one option, and provide parity guidance for Linux users.
  • Where PowerShell cmdlets are referenced, include equivalent commands or workflows for Linux environments, or explicitly state if PowerShell Core is supported cross-platform.
  • Consider mentioning any platform-specific limitations or supported tools for Service Fabric management.
GitHub Create Pull Request
Service Fabric Define Service Configuration in StartupServices.xml for a Service Fabric Application ...service-fabric/service-fabric-startupservices-model.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Visual Studio workflows (Build/Rebuild/F5/Ctrl+F5/Publish) and references PowerShell modules for service creation, both of which are Windows-centric. There are no examples or guidance for Linux/macOS users, nor any mention of cross-platform tooling or workflows for Service Fabric application configuration. The page assumes Visual Studio usage, which is not available on Linux/macOS, and does not provide alternative approaches for those platforms.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to configure and deploy Service Fabric applications without Visual Studio.
  • Provide examples using cross-platform tools such as Azure CLI or Service Fabric CLI (sfctl), where applicable.
  • Clarify which aspects of StartupServices.xml are Visual Studio-specific and offer alternatives for non-Windows environments.
  • Mention any limitations or supported workflows for Linux/macOS users up front, so expectations are clear.
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-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 demonstrates a moderate Windows/PowerShell bias. It references PowerShell as the primary method for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. There are no explicit Linux/bash/CLI examples or references, and Windows/PowerShell tools are mentioned before other options. While .NET and REST are briefly mentioned, Linux users are left to infer their workflow, and no Linux-specific guidance or parity is provided.
Recommendations
  • Add Azure CLI or bash examples for retrieving the cluster manifest and managing the ImageStoreConnectionString.
  • Include links to Linux/macOS-compatible tools or documentation for Service Fabric management.
  • Balance the 'Next steps' section by referencing non-PowerShell deployment guides (e.g., Azure CLI, REST, or SDK-based workflows).
  • Clarify that PowerShell is not required and provide equivalent Linux-friendly instructions where possible.
GitHub Create Pull Request
Service Fabric Reliable services app manifest examples ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides Service Fabric application and service manifest examples, referencing Windows-specific tools and patterns (e.g., .bat files, Windows user accounts, PowerShell module usage) without offering equivalent Linux examples or clarifying cross-platform applicability. The examples and descriptions assume Windows conventions, such as running scripts via Setup.bat and referencing Windows system groups and accounts, but do not mention or demonstrate Linux-compatible alternatives (e.g., shell scripts, Linux user/group management, Linux deployment commands).
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as using .sh scripts instead of .bat for SetupEntryPoint, and clarify how user/group principals map to Linux environments.
  • Explicitly state which manifest features are supported on Linux clusters and provide guidance for Linux deployments (e.g., using Bash scripts, Linux user/group management).
  • When referencing PowerShell modules, also mention or link to CLI or Bash alternatives for Linux/macOS users.
  • Clarify any Windows-only limitations in the manifest features, and highlight cross-platform compatibility where applicable.
GitHub Create Pull Request
Service Fabric Replica soft delete for enhanced data protection in Service Fabric ...s/service-fabric/service-fabric-replica-soft-delete.md
Medium Priority View Details →
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 heavily references PowerShell APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and provides examples and links exclusively to PowerShell cmdlets. There is no mention of Linux or cross-platform equivalents, nor are FabricClient API usage examples shown for non-Windows environments. The focus on PowerShell and Windows tooling creates friction for Linux/macOS users, as Service Fabric supports cross-platform development but the documentation does not reflect this.
Recommendations
  • Add examples using FabricClient APIs in C# or other languages to demonstrate how to perform replica soft delete and restore operations programmatically, which is platform-agnostic.
  • Explicitly mention whether these operations can be performed from Linux/macOS environments, and if so, provide CLI or SDK-based instructions.
  • If there are Azure CLI or REST API equivalents for managing replicas, include those examples.
  • Clarify any limitations or differences for Linux clusters, if applicable.
GitHub Create Pull Request
Service Fabric Add custom Service Fabric health reports ...rticles/service-fabric/service-fabric-report-health.md
Medium Priority View Details →
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 extensive PowerShell examples and references, with no equivalent Linux shell or cross-platform CLI examples. Windows/PowerShell tools are mentioned first and exclusively in example sections, creating friction for Linux/macOS users who may not have access to PowerShell or Windows-specific Service Fabric tooling. REST API usage is briefly mentioned but not demonstrated with concrete examples, and there are no references to Linux-native tools or commands.
Recommendations
  • Add equivalent examples using Azure CLI or Bash scripts for health reporting, especially for sending health reports and querying health status.
  • Explicitly mention and demonstrate REST API usage with curl or other cross-platform tools, including sample requests and responses.
  • Clarify which PowerShell commands are available cross-platform (via PowerShell Core) and which are Windows-only, and provide alternatives where needed.
  • Consider referencing or linking to any Linux/macOS Service Fabric tooling or SDKs, if available.
  • Structure example sections so that REST or cross-platform methods are presented before or alongside Windows/PowerShell methods.
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-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 exhibits a moderate Windows bias. The manifest examples are explicitly based on a Windows Server 2016 container sample, and several instructions and comments reference Windows-specific tools and patterns (e.g., 'winver' for OS build detection, Windows file paths, and certificate handling in the Windows LocalMachine store). There is limited mention of Linux equivalents, and no Linux-specific manifest samples or guidance are provided, despite Service Fabric supporting Linux containers. The documentation does mention that certificates are exposed as PEM files on Linux, but overall, Linux users are left to infer how to adapt the examples.
Recommendations
  • Provide parallel manifest examples based on a Linux container sample, or clarify which elements differ for Linux deployments.
  • Include Linux-specific instructions for tasks such as OS build detection (e.g., using 'cat /etc/os-release' or 'uname -r'), volume mounting paths, and certificate installation.
  • Explicitly state which manifest elements or features are Windows-only and which are cross-platform.
  • Add links to Linux-focused Service Fabric container documentation where appropriate.
GitHub Create Pull Request
Service Fabric Service communication with the ASP.NET Core ...vice-fabric-reliable-services-communication-aspnetcore.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides comprehensive coverage of both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers for ASP.NET Core in Azure Service Fabric. However, Windows-specific tools and APIs (e.g., HTTP.sys, netsh, Windows HTTP Server API) are discussed in detail, often before or alongside Kestrel. HTTP.sys is clearly marked as Windows-only, but there are no explicit Linux/macOS usage examples or guidance. Kestrel is recommended for cross-platform scenarios, but Linux-specific instructions, troubleshooting, or parity notes are missing. Windows-centric configuration (e.g., ServiceManifest.xml endpoint registration for HTTP.sys) is explained, but Linux users may lack clarity on equivalent steps or limitations.
Recommendations
  • Add explicit Linux/macOS examples for Kestrel usage, including any OS-specific configuration steps, troubleshooting, or differences in Service Fabric integration.
  • Clarify which sections are Windows-only and which are cross-platform, especially when discussing endpoint configuration and port management.
  • Provide guidance or links for Linux/macOS users on how to debug, deploy, and configure ASP.NET Core services in Service Fabric clusters running on Linux.
  • Mention any limitations or differences for Linux Service Fabric clusters, such as the absence of HTTP.sys and how to handle scenarios where port sharing is needed.
GitHub Create Pull Request
Service Fabric Specifying Service Fabric service endpoints ...ce-fabric/service-fabric-service-manifest-resources.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 several examples and deployment instructions using PowerShell commands (e.g., New-ServiceFabricApplication) with Windows-style paths, and references to the Service Fabric SDK schema location in 'C:\Program Files\...'. While there is a brief mention of the Linux certificate store location, the majority of operational/deployment examples and tooling references are Windows-centric, with no Linux CLI or cross-platform equivalents provided.
Recommendations
  • Include equivalent Azure CLI or Service Fabric CLI (sfctl) commands for application deployment and parameter overrides, especially for Linux/macOS users.
  • Mention the location of the ServiceFabricServiceModel.xsd schema on Linux, or clarify if it is not applicable.
  • When referencing file paths or tools, provide both Windows and Linux/macOS equivalents where possible.
  • Add explicit notes or links to Linux/macOS deployment guidance, especially in sections that currently only show PowerShell/Windows examples.
GitHub Create Pull Request
Service Fabric Capacity planning and scaling for Azure Service Fabric ...bric/service-fabric-best-practices-capacity-scaling.md
Medium Priority View Details →
Scanned: 2026-02-13 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 several manual scaling instructions using PowerShell cmdlets (e.g., Disable-ServiceFabricNode, Get-ServiceFabricNode, Remove-ServiceFabricNodeState) without mentioning equivalent Linux/macOS commands or Service Fabric CLI usage. Windows/PowerShell-based workflows are described first and exclusively in step-by-step guides, while Linux alternatives are not presented, creating friction for non-Windows users.
Recommendations
  • Add equivalent instructions for Linux/macOS environments, using Service Fabric CLI (sfctl) or REST API where applicable.
  • Explicitly mention cross-platform tooling and provide examples for both PowerShell (Windows) and CLI/REST (Linux/macOS) in all procedural steps.
  • Clarify which commands are Windows-only and offer alternatives for Linux clusters.
  • Reorder examples so that platform-neutral or Linux instructions are presented alongside or before Windows-specific ones where possible.
GitHub Create Pull Request
Service Fabric Application upgrade: upgrade parameters ...abric/service-fabric-application-upgrade-parameters.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Windows/PowerShell and Visual Studio parameters and examples before Linux equivalents (SFCTL/CLI), with more detailed coverage and example formats for PowerShell and Visual Studio. The SFCTL section is present and covers Linux CLI usage, but is positioned after Windows tools and is less prominent. There are no Linux-specific examples or parity in example formatting (e.g., PowerShell has hashtable examples, SFCTL has JSON, but no direct comparison).
Recommendations
  • Reorder sections so that cross-platform tools (SFCTL/CLI) are presented before or alongside Windows tools.
  • Provide example command invocations for SFCTL in the same detail as PowerShell, including parameter formats and sample JSON.
  • Explicitly note which tools are cross-platform and which are Windows-only, to help users choose the right tool.
  • Add a comparison table showing parameter mapping between PowerShell and SFCTL for clarity.
  • Include Linux/macOS-specific notes or examples where relevant, especially for CLI usage.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page references Windows-centric tools and patterns, such as Visual Studio and PowerShell, in the 'Next steps' section. These are presented as primary upgrade methods, with no mention of Linux/macOS equivalents (e.g., CLI, Bash, cross-platform editors). The serialization discussion is tied to C# and .NET, which are cross-platform, but the upgrade guidance leans toward Windows workflows.
Recommendations
  • Add instructions or links for upgrading Service Fabric applications using Azure CLI or Bash scripts, which are cross-platform.
  • Mention cross-platform editors (such as VS Code) alongside Visual Studio.
  • Clarify whether PowerShell instructions are compatible with PowerShell Core on Linux/macOS, or provide Bash/CLI alternatives.
  • Explicitly note that Service Fabric development and upgrades can be performed on Linux/macOS, if applicable, and provide relevant guidance.
GitHub Create Pull Request
Service Fabric Deny assignment policy for Service Fabric managed clusters ...cles/service-fabric/managed-cluster-deny-assignment.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides examples and recommendations that prominently feature Azure PowerShell, including links to PowerShell modules for cluster management tasks. While Azure CLI and ARM/Bicep are mentioned, PowerShell is given as the primary example for key operations (delete, restart, reimage), and no explicit Linux/macOS command-line examples (such as Azure CLI usage) are provided for these tasks. The 'Best practices' section lists PowerShell before CLI, and PowerShell-specific links are used for critical actions.
Recommendations
  • Add explicit Azure CLI examples for deleting NodeTypes, restarting, and reimaging scale sets, alongside PowerShell examples.
  • Ensure that CLI and PowerShell are presented equally, or that CLI examples are shown first, as CLI is cross-platform.
  • Clarify that all recommended tools (Azure CLI, ARM templates, Bicep) are fully supported on Linux/macOS.
  • Where possible, provide links to CLI documentation for the same actions currently linked to PowerShell modules.
GitHub Create Pull Request
Service Fabric Architecture of Azure Service Fabric ...articles/service-fabric/service-fabric-architecture.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page describes the architecture of Azure Service Fabric in a platform-neutral way, but in the Management subsystem section, it specifically mentions 'PowerShell cmdlets' as a primary management interface, without mentioning Linux or cross-platform equivalents (such as Azure CLI or REST APIs). This creates a Windows-first impression and suggests Windows tooling is the default for management tasks, even though Service Fabric supports Linux clusters and cross-platform management.
Recommendations
  • Mention Azure CLI and REST API as cross-platform management options alongside PowerShell.
  • Clarify that management tasks can be performed from Linux/macOS using CLI or API, not just PowerShell.
  • Provide links or references to documentation for Linux management tools and examples.
  • Ensure examples and tooling references are balanced between Windows and Linux/macOS environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides general information about Azure Service Fabric node types and VM scale sets, but exhibits subtle Windows bias. The JSON snippet for the Service Fabric VM extension uses a Windows-style file path (D:\\SvcFab) as the default for 'dataPath', and certificate store references (x509StoreName) are Windows-centric. The 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-specific tasks and tools, without mentioning Linux equivalents or SSH guidance. Linux node type is referenced in the extension ('ServiceFabricLinuxNode'), but Linux-specific examples or guidance are missing.
Recommendations
  • Provide Linux-specific examples for connecting to cluster nodes (e.g., SSH instructions alongside RDP/PowerShell).
  • Clarify that 'dataPath' should use Linux-style paths when deploying Linux node types (e.g., /var/svcfab).
  • Add guidance for managing admin credentials and port ranges on Linux VMs (e.g., using Azure CLI or SSH).
  • Mention Linux certificate storage locations or alternatives to x509StoreName for Linux deployments.
  • Balance 'Next steps' links by including Linux-focused documentation or scripts.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric clusters ...icles/service-fabric/service-fabric-cluster-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides general guidance for upgrading Azure Service Fabric clusters, but exhibits mild Windows bias. Windows-specific tools (PowerShell) are mentioned alongside Azure CLI, but Linux equivalents (e.g., Bash, Linux-specific guidance) are not explicitly referenced. The section on OS image upgrades links only to Windows patching guidance, omitting Linux node patching. Windows terminology and tools are mentioned first or exclusively in some areas, and Linux/macOS users may need to infer their workflow.
Recommendations
  • Explicitly mention Linux/macOS support where applicable, especially for Service Fabric clusters running on Linux nodes.
  • Provide Linux-specific examples (e.g., Bash commands) alongside PowerShell and Azure CLI, or clarify that Azure CLI commands work cross-platform.
  • Add links or sections for patching/upgrading Linux node OS images in Service Fabric clusters, not just Windows.
  • Ensure that references to tools (PowerShell/Azure CLI) clarify their cross-platform availability, or provide parity in examples.
  • Review all guidance for assumptions that clusters are Windows-only, and clarify when guidance applies to both Windows and Linux clusters.
GitHub Create Pull Request
Service Fabric Networking patterns for Azure Service Fabric ...s/service-fabric/service-fabric-patterns-networking.md
Medium Priority View Details →
Scanned: 2026-02-13 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 only PowerShell-based deployment instructions and command-line examples, with no mention of Linux/macOS equivalents (such as Azure CLI or Bash). Windows tools and patterns (e.g., RDP, Windows directory paths, PowerShell syntax) are referenced exclusively and shown first. There are no Linux-specific examples or guidance, which creates friction for non-Windows users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all deployment steps, as Azure CLI is cross-platform.
  • Include Bash shell examples for template deployments where relevant.
  • Mention SSH as a method for accessing VMs/jump boxes, not just RDP.
  • Use generic directory paths or note differences for Linux/macOS users.
  • Clearly indicate that PowerShell is just one option, and provide links to Azure CLI documentation.
GitHub Create Pull Request
← Previous Page 61 of 99 Next →