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 626-650 of 718 flagged pages
Service Fabric Service Fabric Backup and Restore ...ric/service-fabric-reliable-services-backup-restore.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for 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-specific tools and APIs (e.g., kernel32, .NET's Directory.Move) are referenced for file operations and workarounds, but Linux/macOS file system considerations are not discussed. No Linux or bash examples are provided for backup/restore testing or automation, and Windows-centric terminology (PowerShell, kernel32) appears before any mention of cross-platform approaches.
Recommendations
  • Provide equivalent Linux/macOS instructions for testing backup and restore, such as using Service Fabric CLI (sfctl) or REST APIs.
  • Include bash or shell script examples for backup/restore operations alongside PowerShell examples.
  • Discuss file system limitations and workarounds for Linux/macOS (e.g., path length, permissions) in addition to Windows-specific issues.
  • Reference cross-platform tools and APIs before or alongside Windows-specific ones.
  • Clarify which APIs and methods are platform-agnostic and which are Windows-only.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, primarily through its extensive coverage of HTTP.sys (a Windows-only web server), references to Windows-specific tools (netsh), and frequent mentions of Windows APIs. While Kestrel (cross-platform) is recommended and well-documented, HTTP.sys sections lack Linux/macOS alternatives and do not clarify that those features are unavailable on non-Windows platforms. Windows-specific instructions and examples (such as endpoint registration and port sharing) are presented before or instead of Linux equivalents, and troubleshooting/configuration scenarios often assume Windows capabilities.
Recommendations
  • Clearly mark Windows-only sections and features, and provide equivalent Linux/macOS guidance or alternatives where possible.
  • Add explicit Linux/macOS examples for service hosting, endpoint configuration, and troubleshooting, especially for Kestrel.
  • Where Windows tools (like netsh) are referenced, suggest cross-platform alternatives or clarify their absence on Linux/macOS.
  • Reorder examples so that cross-platform (Kestrel) instructions appear before Windows-only (HTTP.sys) instructions.
  • Add a summary table or section comparing feature parity and limitations between Windows and Linux/macOS Service Fabric deployments.
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-01-12 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 by exclusively referencing PowerShell-based administrative APIs (e.g., Remove-ServiceFabricReplica, Restore-ServiceFabricReplica) and showing command output screenshots from Windows environments. There is no mention of Linux/macOS equivalents, CLI alternatives, or cross-platform usage patterns. All example commands and API references are Windows-centric, and the documentation does not clarify how Linux users should perform these operations.
Recommendations
  • Add equivalent examples using Service Fabric CLI (sfctl) for Linux/macOS users.
  • Explicitly document how to perform replica soft delete and restore operations on Linux clusters, including any differences in tooling or workflow.
  • Include screenshots or output examples from Linux environments where relevant.
  • Clarify whether the PowerShell APIs are available cross-platform, and if not, provide alternative instructions.
  • Reorder examples to present cross-platform or CLI methods before or alongside PowerShell commands.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All code examples and configuration references are tailored for Windows environments, such as using Windows certificate stores (StoreLocation.LocalMachine, StoreName="My") and thumbprint-based certificate lookup, with only a brief note about Linux certificate location and format. There are no Linux-specific code samples or configuration patterns, and Windows terminology and tools are used exclusively throughout the main content. The page also presents Windows/C# content before mentioning Java/Linux alternatives.
Recommendations
  • Provide parallel Linux-specific code examples, especially for certificate handling (e.g., loading PEM files from /var/lib/sfcerts).
  • Include configuration samples that demonstrate Linux-compatible certificate settings.
  • Clarify any platform-specific differences in APIs, certificate management, and deployment steps.
  • Balance the order of presentation so Linux guidance is not secondary or relegated to notes.
  • Reference cross-platform tools and patterns where possible, or clearly indicate platform limitations.
GitHub Create Pull Request
Service Fabric Add and remove node types of a Service Fabric managed cluster ...abric/tutorial-managed-cluster-add-remove-node-type.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows, with all examples using Azure PowerShell and no mention or examples of equivalent Linux/macOS workflows (e.g., Azure CLI or Bash). Prerequisites and instructions assume PowerShell usage, which is native to Windows, and do not provide guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all tasks (adding/removing node types), as CLI is cross-platform and works natively on Linux/macOS.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with installation links for each platform.
  • Explicitly state that the tutorial works on Linux/macOS and provide any platform-specific notes if necessary.
  • Consider showing CLI/Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Service Fabric Azure Service Fabric reverse proxy diagnostics ...ice-fabric/service-fabric-reverse-proxy-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through references to Windows-specific tools and terminology (e.g., 'Windows Azure Diagnostics', 'ERROR_WINHTTP_TIMEOUT', 'winHttpError'), and by mentioning Windows-centric workflows (Visual Studio) in the 'Next steps' section. There are no explicit Linux/macOS troubleshooting examples, nor are cross-platform log collection methods or tools discussed. Windows error codes and APIs are referenced in diagnostic payloads without Linux equivalents or translation.
Recommendations
  • Add equivalent Linux/macOS troubleshooting examples, including common error codes and diagnostic patterns for those platforms.
  • Mention and document cross-platform log collection methods (e.g., using Linux diagnostics agents, Azure Monitor, or open-source tools).
  • Clarify whether the error codes (e.g., ERROR_WINHTTP_TIMEOUT) are relevant only to Windows nodes, and provide Linux equivalents if available.
  • Include instructions for viewing and interpreting logs on Linux/macOS clusters, such as using command-line tools or alternative IDEs.
  • Rephrase 'Windows Azure Diagnostics' to 'Azure Diagnostics' and specify Linux support where applicable.
  • Provide parity in 'Next steps' for Linux/macOS users, such as links to Linux-compatible monitoring tools or documentation.
GitHub Create Pull Request
Service Fabric Azure Service Fabric set up reverse proxy ...es/service-fabric/service-fabric-reverseproxy-setup.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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. Standalone cluster instructions and references are consistently tied to Windows Server, with links and examples focused on Windows-specific configuration files and upgrade guides. There are no explicit Linux/macOS examples or guidance for standalone clusters, and the documentation refers to Windows Server guides for key configuration steps. Azure-hosted cluster instructions are platform-neutral, but standalone cluster support is Windows-centric.
Recommendations
  • Provide explicit instructions and examples for configuring reverse proxy on standalone clusters running Linux (if supported).
  • Reference Linux/macOS equivalents for configuration and upgrade steps, including links to relevant documentation.
  • Clarify platform support for standalone clusters and indicate if Linux is not supported, or provide parity where possible.
  • Ensure that references to upgrade/configuration guides include both Windows and Linux versions, or state platform limitations.
GitHub Create Pull Request
Service Fabric Azure Service Fabric CLI- sfctl chaos .../articles/service-fabric/service-fabric-sfctl-chaos.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation for 'sfctl chaos' demonstrates a Windows bias primarily through its use of Windows-specific terminology and references, such as 'Windows file time' and linking to .NET's DateTime.ToFileTimeUtc method. There are no explicit Linux/macOS examples or references, and the documentation does not clarify how Linux/macOS users should specify time arguments or handle platform differences. The CLI itself is cross-platform, but the documentation assumes a Windows-centric context.
Recommendations
  • Provide equivalent Linux/macOS instructions or examples, especially for time formatting and conversion.
  • Clarify whether 'Windows file time' is required on all platforms, and offer guidance/tools for Linux/macOS users to generate compatible values.
  • Include references to cross-platform date/time conversion utilities (e.g., Python, shell commands) for Linux/macOS users.
  • Add explicit notes or examples showing usage on Linux/macOS, including any differences in behavior or prerequisites.
GitHub Create Pull Request
Service Fabric Azure Service Fabric CLI- sfctl node ...n/articles/service-fabric/service-fabric-sfctl-node.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is largely platform-neutral, focusing on the sfctl CLI, which is cross-platform. However, there is a notable Windows bias in the 'remove-state' command section, where guidance and links are provided only for standalone clusters running on Windows Server, with no mention of Linux equivalents or instructions for Linux clusters.
Recommendations
  • Add equivalent guidance and links for managing node state in standalone Service Fabric clusters running on Linux.
  • Clarify whether the described procedures and links are applicable to Linux clusters, and if not, provide Linux-specific instructions.
  • Ensure that any references to platform-specific documentation (such as adding/removing nodes) include both Windows and Linux versions, or explicitly state platform limitations.
GitHub Create Pull Request
Service Fabric Learn Azure Service Fabric terminology ...es/service-fabric/service-fabric-technical-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 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. Key infrastructure concepts (such as the node definition) reference Windows-specific tools and patterns (e.g., auto-start Windows service, FabricHost.exe) without mentioning Linux equivalents or patterns. Executable file types are described as EXE/DLL, which are Windows-centric, and Windows containers are mentioned before Docker containers on Linux. There is a lack of explicit Linux examples or terminology in critical sections, and Windows tools/patterns are presented first or exclusively.
Recommendations
  • Explicitly describe Linux equivalents for node management (e.g., systemd services, Linux process patterns) alongside Windows services.
  • When discussing executables, mention Linux binary formats (e.g., ELF) and clarify how Service Fabric handles them.
  • Present Docker containers on Linux before or alongside Windows containers to avoid Windows-first ordering.
  • Add examples or explanations for Linux-specific deployment and operational steps where Windows tools are referenced.
  • Ensure terminology and examples are platform-neutral or provide parity between Windows and Linux/macOS.
GitHub Create Pull Request
Service Fabric Integrate API Management with Service Fabric in Azure ...abric/service-fabric-tutorial-deploy-api-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is strongly oriented toward Windows environments. It assumes the use of a Windows Service Fabric cluster, references Windows-specific development tools (Visual Studio), and provides step-by-step instructions for creating and deploying .NET services using Visual Studio. There are no equivalent instructions or examples for Linux clusters, Linux development environments, or cross-platform tooling. PowerShell is used for scripting and certificate handling, with no Bash or Linux alternatives shown. Linux users are left to infer or adapt steps, which may create significant friction.
Recommendations
  • Add explicit instructions for setting up a Linux Service Fabric cluster, including links to relevant tutorials.
  • Provide examples for developing and deploying Service Fabric services using cross-platform tools (e.g., VS Code, CLI, Java, or .NET Core on Linux).
  • Include Linux/macOS equivalents for certificate handling and base64 encoding (e.g., using openssl and base64 commands).
  • Show Bash scripts alongside PowerShell for template deployment and resource management.
  • Clarify which steps are Windows-specific and offer alternatives for Linux/macOS users.
  • Reference Linux development environment setup guides and Service Fabric SDK installation for Linux.
GitHub Create Pull Request
Service Fabric How to view Azure Service Fabric entities' aggregated health ...bric/service-fabric-view-entities-aggregated-health.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides detailed PowerShell examples for querying Service Fabric health, with no equivalent examples for Linux/macOS command-line environments (e.g., Bash, CLI). PowerShell is a Windows-centric tool, and its usage is shown before REST API alternatives. There is no mention of Linux-native tools, nor are there instructions for running PowerShell cross-platform. This creates friction for Linux/macOS users, who must rely on REST API or .NET SDK without command-line parity.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation instructions or usage notes if PowerShell is required.
  • Include Bash/cURL examples for REST API calls to demonstrate how Linux/macOS users can perform equivalent queries.
  • Reorder sections so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell.
  • Clarify any platform-specific limitations or requirements for Service Fabric tooling.
GitHub Create Pull Request
Service Fabric Configure secure Azure Service Fabric cluster connections ...rvice-fabric-visualstudio-configure-secure-connections.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, focusing on Visual Studio and PowerShell for configuring secure connections to Azure Service Fabric clusters. Certificate installation instructions and command-line tooling are exclusively Windows-centric, with no mention of Linux/macOS equivalents or cross-platform alternatives. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Add instructions for installing .pfx certificates on Linux/macOS, such as using OpenSSL or system-specific certificate stores.
  • Include examples of connecting to Service Fabric clusters using cross-platform tools (e.g., Azure CLI, Service Fabric CLI) where possible.
  • Provide guidance for editing publish profiles and resolving certificate parameters on Linux/macOS systems.
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives or references.
  • Mention cross-platform IDEs (such as VS Code) if supported, or explicitly state Windows-only requirements.
GitHub Create Pull Request
Service Fabric Troubleshoot with system health reports ...understand-and-troubleshoot-with-system-health-reports.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. All command-line examples use PowerShell syntax and Windows-style paths (e.g., 'PS C:\>'), with no mention of Linux or macOS equivalents. There is no reference to Service Fabric CLI (sfctl), Bash, or cross-platform tools. The only instructions for clearing health reports and querying cluster/application/service/partition/replica health are given as PowerShell cmdlets, and links to further instructions also point to Windows/PowerShell-specific documentation. This creates friction for Linux/macOS users and may prevent them from easily following the troubleshooting steps.
Recommendations
  • Add equivalent examples using sfctl (Service Fabric CLI), which is cross-platform and works on Linux/macOS.
  • Explicitly mention that all PowerShell commands can be run on Windows, and provide Bash/sfctl alternatives for Linux/macOS.
  • Where possible, use generic API references (e.g., REST API, .NET SDK) and show how to invoke them from different platforms.
  • Reorder examples so that cross-platform tools (sfctl, REST API) are shown first or alongside PowerShell.
  • Update links to include Linux/macOS documentation and troubleshooting guides.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows file paths (e.g., 'D:\\SvcFab') in configuration examples, omitting Linux-specific paths or considerations. The 'Next steps' section links to a standalone cluster scaling guide that is explicitly for Windows Server, with no mention of Linux equivalents. There are no Linux/macOS-specific instructions, examples, or notes, and Windows conventions (such as drive letters) are used by default.
Recommendations
  • Include Linux-specific configuration examples, such as using '/var/svcfab' for dataPath instead of 'D:\\SvcFab'.
  • Add notes or sections clarifying differences when deploying on Linux-based clusters, including any required changes to ARM templates or Service Fabric extension properties.
  • Provide links to Linux/macOS standalone cluster scaling documentation, or clarify if such functionality is not supported.
  • Ensure that all examples are either cross-platform or presented in both Windows and Linux formats.
GitHub Create Pull Request
Service Fabric Use Application Gateway in a Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-application-gateway.md
Medium Priority View Details →
Scanned: 2026-01-10 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 command examples for critical steps (e.g., getting the Service Principal and assigning roles), with no equivalent CLI or Bash examples for Linux/macOS users. Windows/PowerShell tooling is referenced exclusively and presented first, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI equivalents for all PowerShell commands (e.g., az ad sp show, az role assignment create).
  • Explicitly mention that steps can be performed on Linux/macOS using Azure CLI or Bash.
  • Provide example scripts for Linux/macOS environments alongside PowerShell examples.
  • Consider reordering examples so that cross-platform (CLI) options are shown first or side-by-side with PowerShell.
GitHub Create Pull Request
Service Fabric Use Azure DDoS Protection in a Service Fabric managed cluster ...rvice-fabric/how-to-managed-cluster-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-01-10 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 notable Windows bias by providing only Azure PowerShell examples for key steps (service principal lookup, role assignment), mentioning PowerShell before Azure CLI, and omitting equivalent Linux/macOS-friendly CLI commands. No Bash or Azure CLI examples are given for tasks that can be performed cross-platform, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, especially for service principal lookup and role assignment.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI.
  • Present CLI/Bash examples before or alongside PowerShell to improve parity.
  • Include notes or links to cross-platform tooling for ARM template deployment and role assignment.
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-10 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 Windows bias by providing only PowerShell examples for ARM template deployment, referencing RDP (a Windows-specific remote access protocol) for admin access, and omitting equivalent Linux/macOS command-line instructions (such as Azure CLI or Bash). Windows tools and patterns are mentioned exclusively or before Linux alternatives, making it harder for non-Windows users to follow the guide.
Recommendations
  • Add Azure CLI examples for ARM template deployment, showing Linux/macOS compatible commands.
  • Mention SSH as an alternative to RDP for VM access, and clarify admin username/password usage for Linux-based VMs.
  • Present deployment options for both Windows and Linux/macOS users side-by-side, or in parallel sections.
  • Explicitly state that the instructions apply to both Windows and Linux, or note any platform-specific differences.
  • Include Bash script examples for template deployment where appropriate.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page references provisioning IP tags using a PowerShell module (Az.Network) and links to a PowerShell-specific example, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or REST API). This creates a bias towards Windows environments and tools.
Recommendations
  • Include Azure CLI examples for provisioning IP tags, as CLI is cross-platform and widely used on Linux/macOS.
  • Reference REST API methods for advanced users who may prefer scripting outside of PowerShell.
  • Explicitly state that the process can be completed on Linux/macOS and provide links to relevant documentation.
  • Reorder examples so that cross-platform tools (CLI, REST) are mentioned before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Deploy application secrets to a Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-application-secrets.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (such as the Key Vault VM extension for Windows) and certificate store names (e.g., 'MY'), and links to Windows-focused documentation. There are no explicit Linux/macOS examples or guidance, and Linux equivalents for certificate installation and management are not mentioned, making it harder for non-Windows users to follow the instructions.
Recommendations
  • Add explicit instructions and examples for Linux-based Service Fabric clusters, including how to install certificates and manage secrets using Linux tools.
  • Reference the Key Vault VM extension for Linux and provide a link to its documentation.
  • Clarify certificate store naming conventions for Linux and macOS environments.
  • Present cross-platform guidance side-by-side, or clearly indicate platform-specific steps.
  • Include PowerShell, CLI, and bash examples where relevant.
GitHub Create Pull Request
Service Fabric Configure maintenance control for Service Fabric managed cluster ...e-fabric/how-to-managed-cluster-maintenance-control.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides PowerShell-based examples for all resource creation, deployment, and status checking steps, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows/PowerShell tooling is assumed throughout, and Linux/macOS users are not given alternative commands or guidance.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that the steps can be performed from any OS using Azure CLI, and provide Bash script snippets where appropriate.
  • Include a note or section on platform compatibility, clarifying that the process is not Windows-specific and listing supported tools for Linux/macOS.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown first or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Add a virtual machine scale set extension to a Service Fabric managed cluster node type ...ervice-fabric/how-to-managed-cluster-vmss-extension.md
Medium Priority View Details →
Scanned: 2026-01-10 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. The only CLI example provided is for PowerShell (Add-AzServiceFabricManagedNodeTypeVMExtension), with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The VM extension example uses 'KeyVaultForWindows', a Windows-specific extension type, without referencing Linux equivalents or cross-platform options. Windows-centric tools and patterns are mentioned exclusively and appear first, while Linux support is not addressed.
Recommendations
  • Add Azure CLI and/or Bash examples for adding VM scale set extensions to Service Fabric managed cluster node types.
  • Explicitly mention and provide examples for Linux-compatible VM extensions (e.g., KeyVaultForLinux) in ARM templates.
  • Clarify cross-platform support for Service Fabric managed clusters and extensions, including any OS-specific requirements or limitations.
  • Reorder examples to present cross-platform or Linux options alongside or before Windows-specific ones.
  • Include a table or section comparing extension types and their OS compatibility.
GitHub Create Pull Request
Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure placement properties), but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). PowerShell is a Windows-centric tool, and its usage is presented as the sole scripting option. There is no mention of cross-platform alternatives, and PowerShell examples are given before or instead of any Linux-friendly options. This creates friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all operations currently shown only with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant, and clarify any differences in usage.
  • Provide Bash or REST API examples where appropriate.
  • In each section, present cross-platform options (Azure CLI, REST) before or alongside PowerShell, not after.
  • Include notes or links to cross-platform tooling documentation for Service Fabric management.
GitHub Create Pull Request
Service Fabric Service Fabric Explorer blocking operations ...ged-cluster-service-fabric-explorer-blocking-operation.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page predominantly references PowerShell cmdlets (e.g., Remove-AzResource, AzSF PowerShell cmdlet) for managing Service Fabric resources. There is no mention of Linux/macOS equivalents, such as Bash/CLI commands, nor are cross-platform instructions provided. The examples and guidance assume the use of Windows-centric tools, creating friction for users on Linux or macOS.
Recommendations
  • Include Azure CLI examples for each operation alongside PowerShell cmdlets, as Azure CLI is cross-platform.
  • Explicitly state which commands/tools are supported on Linux/macOS and provide links to relevant documentation.
  • Add Bash script examples for common operations, or clarify how Linux/macOS users can perform these tasks.
  • Reorder examples so that cross-platform tools (e.g., Azure CLI) are presented before or alongside Windows-specific tools.
GitHub Create Pull Request
Service Fabric Add application cert to a cluster in PowerShell ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/scripts/service-fabric-powershell-add-application-certificate.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is exclusively focused on Azure PowerShell, providing only PowerShell script examples and instructions. There are no Bash, Azure CLI, or Linux/macOS-specific examples or guidance. Windows-centric terminology (e.g., certificate store paths like LocalMachine\My) is used, and all tooling references are for PowerShell, which is native to Windows. This creates friction for Linux/macOS users who may prefer or require Bash/Azure CLI workflows.
Recommendations
  • Add equivalent Azure CLI and/or Bash script examples for each major step (certificate creation, upload, VMSS update).
  • Include notes on cross-platform compatibility of PowerShell Core, and clarify if scripts work on Linux/macOS PowerShell.
  • Mention Linux certificate store paths and how to handle certificates on Linux VMSS nodes.
  • Provide links to Linux/macOS-specific documentation or troubleshooting guides.
  • Reorder or parallelize examples so Linux/Azure CLI options are presented alongside PowerShell/Windows options.
GitHub Create Pull Request
← Previous Page 26 of 29 Next →