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 251-275 of 718 flagged pages
Service Fabric Migrate from Azure Cloud Services to Service Fabric ...ic/cloud-services-to-service-fabric-migration-guide.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. PowerShell is the only command-line example provided for cluster setup and application deployment, with no Azure CLI or Bash equivalents. Visual Studio (Windows-only) is presented as the primary development environment, and the instructions for preparing the development environment reference Windows specifically. There are no explicit Linux/macOS instructions or examples for cluster management, deployment, or development. Windows-specific migration scenarios (IIS, Windows Containers) are discussed, but Linux alternatives are not addressed.
Recommendations
  • Add Azure CLI and Bash examples for cluster creation, node type addition, and application deployment alongside PowerShell.
  • Include instructions for setting up the development environment on Linux/macOS, referencing cross-platform tools like VS Code and .NET CLI.
  • Provide parity in migration guides for Linux-based workloads, including ASP.NET Core on Linux and containerization with Linux containers.
  • Explicitly mention platform support and limitations for Service Fabric Managed Clusters, including Linux compatibility.
  • Reorder examples so that cross-platform tools (Azure CLI, VS Code, .NET CLI) are shown before or alongside Windows-specific tools.
  • Add troubleshooting steps relevant to Linux/macOS environments.
GitHub Create Pull Request
Service Fabric X.509 Certificate-based Authentication in a Service Fabric Cluster ...ticles/service-fabric/cluster-security-certificates.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows terminology (e.g., certificate stores like LocalMachine\My), Windows API references (Win32 CryptoAPI, CertGetCertificateChain), and troubleshooting steps (event logs, CAPI2 logging) are presented first and in detail, while Linux equivalents are mentioned briefly or parenthetically (e.g., 'Linux equivalent path, /var/lib/sfcerts'). There are no explicit Linux/macOS command-line examples, and troubleshooting guidance is focused on Windows tools and logs.
Recommendations
  • Provide Linux/macOS-specific examples for certificate storage, management, and troubleshooting (e.g., using OpenSSL, Linux file paths, systemd journal logs).
  • Include explicit instructions or references for Linux/macOS users on how to locate, install, and validate certificates in Service Fabric clusters.
  • Add troubleshooting steps for Linux clusters, such as where to find Service Fabric logs, how to enable verbose logging, and how to diagnose certificate issues using Linux-native tools.
  • Reference cross-platform APIs and tools where possible, or clarify platform-specific differences in configuration and behavior.
  • Ensure that examples and explanations are presented in a platform-neutral order, or provide parallel examples for both Windows and Linux/macOS.
GitHub Create Pull Request
Service Fabric Configure managed identity support in an existing Service Fabric cluster ...existing-cluster-enable-managed-identity-token-service.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references viewing upgrade policy settings via PowerShell and the Azure portal, but does not mention or provide examples for Linux/macOS command-line tools (such as Azure CLI or Bash). The order of tool references and lack of Linux-specific guidance may create friction for non-Windows users.
Recommendations
  • Add explicit instructions and examples for performing cluster upgrades and viewing upgrade policies using Azure CLI and Bash, which are cross-platform.
  • Mention Linux/macOS compatibility for all steps, and clarify which tools are available on all platforms.
  • Provide parity in troubleshooting steps, ensuring error investigation can be performed using cross-platform tools.
  • Avoid referencing PowerShell or Windows tools first unless they are the only option; otherwise, present cross-platform options equally.
GitHub Create Pull Request
Service Fabric Manage certificates in a Service Fabric cluster ...vice-fabric/cluster-security-certificate-management.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 notable Windows bias. PowerShell is the only scripting language shown for certificate enrollment automation, and Windows-specific tooling (such as the Key Vault VM extension for Windows and S-channel APIs) is referenced exclusively or explained in detail. There are no Linux/macOS equivalents or examples for certificate provisioning, automation, or troubleshooting. Windows patterns (e.g., certificate store locations, ACLing, linking on renewal) are described first and in depth, while Linux approaches are absent.
Recommendations
  • Add Linux/macOS examples for certificate enrollment, provisioning, and automation (e.g., using Azure CLI, Bash scripts, or Python SDK).
  • Reference and link to the Key Vault VM extension for Linux, and explain any differences in behavior or configuration.
  • Describe certificate store locations and access control mechanisms for Linux (e.g., /etc/ssl/certs, file permissions) alongside Windows registry/store details.
  • Provide troubleshooting steps and FAQs relevant to Linux/macOS environments.
  • When discussing features that are Windows-only (e.g., S-channel, CERT_RENEWAL_PROP_ID), clearly note their platform specificity and suggest Linux alternatives if available.
GitHub Create Pull Request
Service Fabric Deploy an application to a managed cluster using Azure Resource Manager ...bric/how-to-managed-cluster-app-deployment-template.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets (New-AzResourceGroupDeployment, Get-AzResource, Remove-AzServiceFabricManagedClusterApplication) with no mention of Azure CLI or Bash equivalents. The application packaging workflow is described using Visual Studio, a Windows-centric tool, and file paths use Windows conventions. There are no Linux/macOS-specific instructions or examples, and Windows tools and patterns are presented exclusively and first.
Recommendations
  • Add Azure CLI examples for deployment, upgrade, and deletion steps alongside PowerShell commands.
  • Include instructions for packaging the application using cross-platform tools (e.g., dotnet CLI, zip utilities) rather than only Visual Studio.
  • Show file path examples using both Windows and Linux/macOS conventions.
  • Explicitly mention that the workflow can be performed on Linux/macOS and provide guidance for those platforms.
  • Reference cross-platform editors (e.g., VS Code) for editing templates and packaging applications.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias by referencing Windows-specific tools and patterns, such as the Key Vault VM extension for Windows, and using terminology like 'certificate store name on the nodes, e.g.: "MY"' which is a Windows convention. The linked extension documentation is Windows-specific, and there is no mention of Linux/macOS equivalents or instructions for Linux-based Service Fabric clusters. Examples and references to certificate stores and installation methods are Windows-centric, with no Linux parity guidance.
Recommendations
  • Add explicit instructions and examples for deploying certificates and secrets on Linux-based Service Fabric clusters.
  • Reference and link to the Key Vault VM extension for Linux (if available), or provide alternative Linux-compatible methods for certificate management.
  • Clarify certificate store conventions for Linux (e.g., file paths, store names) and provide examples.
  • Ensure that both Windows and Linux approaches are presented side-by-side or in parallel sections.
  • Avoid using Windows-specific terminology without explanation or Linux equivalents.
GitHub Create Pull Request
Service Fabric Deploy app with a user-assigned managed identity ...vice-fabric-application-user-assigned-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references PowerShell in the link for managing user-assigned managed identities, and does not mention or link to Linux/macOS CLI alternatives. The only external tool mentioned is PowerShell, suggesting a Windows-first approach. No explicit Linux/macOS examples or parity guidance are provided.
Recommendations
  • Include links to Azure CLI and/or REST API documentation for managing user-assigned managed identities, which are cross-platform.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or other non-Windows tools.
  • Provide example commands for both PowerShell and Azure CLI where relevant.
  • Review all external links to ensure Linux/macOS users are not directed exclusively to Windows-centric tooling.
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-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 demonstrates a notable Windows bias by exclusively providing PowerShell examples for critical steps such as obtaining the Service Principal ID and assigning roles. No equivalent Azure CLI, Bash, or Linux/macOS instructions are offered. The PowerShell commands are presented first and as the only option for command-line interaction, which may create friction for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for service principal retrieval and role assignment.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or Bash, and provide those instructions.
  • Reorder examples so that platform-neutral (ARM template) or CLI instructions are shown before or alongside PowerShell.
  • Include a note clarifying cross-platform support and linking to Azure CLI documentation.
GitHub Create Pull Request
Service Fabric Configure and use applications with managed identity on a Service Fabric managed cluster ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/how-to-managed-cluster-application-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell in the context of managing user-assigned identities and links to a PowerShell-specific guide, without mentioning or providing equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). No Linux/macOS tools or patterns are discussed, and Windows tooling is implicitly prioritized.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for managing user-assigned identities.
  • Reference cross-platform documentation (e.g., Azure CLI guides) when linking to how-to guides.
  • Explicitly state that all steps can be performed on Linux/macOS and provide relevant command-line examples.
  • Add a section or note clarifying tool parity and platform support.
GitHub Create Pull Request
Service Fabric Import certificates into a container ...s/service-fabric/service-fabric-securing-containers.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-specific details (such as PFX handling, environment variables, and ACLs) are explained first and in greater depth. The only code example provided is C# code for importing a PFX certificate, which is directly relevant to Windows. Linux handling is described briefly, with no code samples or practical import instructions. Windows tools and patterns (PFX, ACLs, X509Store) are mentioned exclusively, while Linux equivalents (PEM, OpenSSL, file permissions) are not covered.
Recommendations
  • Provide equivalent Linux code samples (e.g., using OpenSSL or Linux certificate stores) for importing PEM certificates and private keys.
  • Describe Linux file permission management for certificate files, analogous to the Windows ACL discussion.
  • Present Windows and Linux instructions/examples in parallel, rather than focusing on Windows first.
  • Mention Linux-specific tools and patterns (such as openssl, chmod, etc.) where appropriate.
  • Clarify differences in certificate handling between platforms, including security implications.
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The only concrete deployment example uses Windows PowerShell (New-ServiceFabricApplication), and the Service Fabric SDK schema location is referenced using a Windows file path. Linux-specific details are limited to a brief mention of the certificate store location, and no Linux/macOS CLI examples (such as Azure CLI or Bash) are provided. Windows tools and patterns are mentioned first and more prominently.
Recommendations
  • Add Linux/macOS deployment examples using Azure CLI or Bash scripts alongside PowerShell examples.
  • Reference Linux file paths for SDK/schema locations in addition to Windows paths.
  • Explicitly mention cross-platform tools and workflows where possible, and clarify any platform-specific differences.
  • Ensure that all examples and instructions are applicable to both Windows and Linux clusters, or clearly indicate platform limitations.
GitHub Create Pull Request
Service Fabric Configure autoscaling for Service Fabric managed cluster nodes ...les/service-fabric/how-to-managed-cluster-autoscale.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 significant Windows bias. All command-line examples use PowerShell cmdlets (e.g., New-AzResourceGroup, New-AzResourceGroupDeployment, Remove-AzResource), which are native to Windows and require either Windows or PowerShell Core on Linux/macOS. There are no equivalent Azure CLI or bash examples provided for Linux/macOS users. The troubleshooting section also references PowerShell modules exclusively. The documentation assumes familiarity with Windows tooling and does not mention Linux-native alternatives or provide guidance for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along without installing PowerShell.
  • Explicitly mention that PowerShell Core can be installed on Linux/macOS, or recommend Azure CLI as the preferred cross-platform tool.
  • Reorder examples so that Azure CLI (cross-platform) is shown first, or at least in parallel with PowerShell.
  • Include troubleshooting steps using Azure CLI and reference Linux/macOS compatibility.
  • Clarify any OS-specific limitations or requirements, especially in the context of autoscale metrics and deployment tooling.
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-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 demonstrates a notable Windows bias by providing only Azure PowerShell examples for critical steps, such as retrieving the Service Principal and assigning roles. There is no mention of equivalent Azure CLI commands, which are cross-platform and preferred by many Linux/macOS users. The PowerShell examples are presented first and exclusively, with no alternative instructions for non-Windows environments.
Recommendations
  • Add Azure CLI command examples alongside PowerShell for all steps involving resource management and role assignments.
  • Explicitly mention that Azure CLI is supported and provide links to CLI documentation.
  • Where possible, present CLI and PowerShell examples side-by-side, or indicate which tools are cross-platform.
  • Clarify that ARM templates and Azure Portal are platform-agnostic, and encourage their use for users on Linux/macOS.
GitHub Create Pull Request
Service Fabric Add Azure Dedicated Host to a Service Fabric managed cluster (SFMC) ...rvice-fabric/how-to-managed-cluster-dedicated-hosts.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 demonstrates a notable Windows bias by exclusively providing PowerShell-based examples for all command-line operations, such as authentication, resource group creation, and role assignment. There are no CLI (az) or Bash/Linux/macOS shell equivalents, and PowerShell is assumed as the default automation tool. This creates friction for Linux and macOS users who typically use Azure CLI and Bash. Additionally, Windows-centric terminology (e.g., RDP admin credentials) is presented without Linux alternatives.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all resource management and deployment steps.
  • Include Bash shell script snippets for Linux/macOS users.
  • Mention SSH as an alternative to RDP for VM access, and clarify admin credential requirements for Linux VMs.
  • Explicitly state that all steps can be performed from Linux/macOS and provide links to cross-platform tooling.
  • Reorder examples so that CLI and PowerShell are presented together, or CLI first, to avoid Windows-first impression.
GitHub Create Pull Request
Service Fabric Delete a Service Fabric cluster in Azure ...rvice-fabric/service-fabric-tutorial-delete-cluster.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing on Windows clusters in the tutorial series, referencing Windows-specific management and monitoring tools, and providing PowerShell examples (which are Windows-centric, though available cross-platform). There is no mention of Linux clusters, and all cluster creation and management examples assume a Windows environment. Linux-specific guidance, such as for Linux-based Service Fabric clusters or Linux node patching, is absent.
Recommendations
  • Include explicit instructions and examples for creating, managing, and deleting Linux-based Service Fabric clusters.
  • Balance references to Windows tools (e.g., Service Fabric Explorer, Windows patching) with Linux equivalents or note differences.
  • Add Linux-specific sections or callouts, especially for cluster node management and diagnostics.
  • Clarify when instructions apply to both Windows and Linux clusters, or provide parallel workflows.
  • Reference documentation for Linux cluster patching and diagnostics where available.
GitHub Create Pull Request
Service Fabric Enable Disk Encryption for Service Fabric managed cluster nodes ...abric/how-to-managed-cluster-enable-disk-encryption.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. The introduction and most examples are explicitly for Windows, with ARM template and PowerShell commands shown exclusively or first. Linux support is mentioned only in passing, with no Linux-specific instructions, verification steps, or troubleshooting guidance. The use of PowerShell and references to Windows tools dominate, and Azure CLI is only briefly mentioned for Key Vault creation and update, not for deployment or verification. There are no examples for Linux users on how to deploy, verify, or troubleshoot disk encryption for Service Fabric managed clusters.
Recommendations
  • Add explicit Linux-focused sections, including deployment and verification steps for disk encryption on Linux-based Service Fabric managed cluster nodes.
  • Provide Azure CLI examples for all steps, not just Key Vault creation and update, including deployment and verification.
  • Include troubleshooting tips and verification commands for Linux environments (e.g., using SSH, Linux-native tools, or Azure CLI).
  • Clarify which instructions apply to both Windows and Linux, and highlight any differences.
  • Reference Linux documentation and provide links to Linux-specific guides where appropriate.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell commands for all deployment and management steps, with no mention of Azure CLI, Bash, or Linux/macOS-compatible workflows. All code examples and instructions assume a Windows environment, creating friction for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or REST API.
  • Provide Bash script samples or instructions for Linux users where appropriate.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
GitHub Create Pull Request
Service Fabric Upgrading Azure Service Fabric managed clusters ...cles/service-fabric/how-to-managed-cluster-upgrades.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing only Windows-based Service Fabric cluster versions in its examples and omitting Linux equivalents. The REST API output exclusively references Windows environments, and there are no examples or guidance for Linux-based clusters or their upgrade process. This may cause confusion or friction for users managing Linux clusters.
Recommendations
  • Include examples of Linux-based Service Fabric cluster versions in the REST API output section.
  • Explicitly mention Linux support and provide instructions or examples for upgrading Linux clusters.
  • Clarify whether upgrade procedures differ for Linux clusters and link to relevant documentation if so.
  • Ensure that references to supported versions and operating systems include both Windows and Linux, or state any limitations.
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-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 demonstrates a notable Windows bias: it only provides a PowerShell command for adding VM extensions, omits CLI or Linux/macOS instructions, and uses Windows-specific extension types (e.g., KeyVaultForWindows). Examples and tooling references are Windows-centric, with no parity for Linux users.
Recommendations
  • Add Azure CLI and/or REST API examples for adding VM extensions, which are cross-platform.
  • Include examples of Linux-compatible VM extensions (e.g., KeyVaultForLinux) in ARM template samples.
  • Explicitly mention how Linux/macOS users can perform equivalent operations, including any differences in extension types or setup.
  • Reorder examples or provide parallel examples for both Windows and Linux to avoid Windows-first presentation.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides PowerShell examples for command-line operations (add, remove, scale, configure properties), but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or cross-platform scripting). PowerShell is Windows-centric, and its use is assumed throughout, creating friction for users on other platforms. Additionally, Windows tools and patterns (e.g., drive letters, PowerShell cmdlets) are referenced without Linux alternatives or context.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell cmdlets can be run on Linux/macOS (via PowerShell Core), or provide Bash script equivalents where possible.
  • Where drive letters or Windows-specific concepts are referenced (e.g., diskLetter), clarify behavior on Linux-based node types or note any differences.
  • Ensure that examples and instructions do not assume a Windows environment; include notes or sections for Linux/macOS users where relevant.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
GitHub Create Pull Request
Service Fabric Configure network settings for Service Fabric managed clusters ...es/service-fabric/how-to-managed-cluster-networking.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 exhibits a notable Windows bias, primarily through the exclusive use of PowerShell for command-line examples, frequent references to Windows-specific tools (such as Remote Desktop Connection), and explicit mention of Windows clusters in RDP/NAT sections. There are no CLI/bash examples or guidance for Linux/macOS users, and Windows terminology and screenshots are used without Linux equivalents.
Recommendations
  • Provide Azure CLI (az) and/or Bash examples alongside PowerShell commands for all resource management and deployment steps.
  • Include instructions and screenshots for connecting to Linux-based nodes (e.g., using SSH) in sections discussing remote access and NAT rules.
  • Clarify when steps or features apply to both Windows and Linux clusters, and note any differences.
  • Reference cross-platform tools (e.g., VS Code, SSH clients) where appropriate, not just Windows-only tools.
  • Reorder examples so that platform-neutral or cross-platform approaches are presented first, or side-by-side.
GitHub Create Pull Request
Service Fabric Add a managed identity to a Service Fabric managed cluster node type ...ed-identity-managed-cluster-virtual-machine-scale-sets.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 demonstrates a notable Windows bias by providing only PowerShell-based command-line examples for resource creation, role assignment, and deployment. There are no equivalent examples using Bash, Azure CLI, or Linux/macOS-native tools. Additionally, VM image properties in the ARM template examples exclusively reference Windows Server images, with no mention of Linux-based node types or images. This prioritization of Windows tools and patterns creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all resource creation, role assignment, and deployment steps.
  • Include Bash script snippets for template deployments and identity management.
  • Show ARM template examples using Linux VM images (e.g., Ubuntu) in addition to Windows Server.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS environments.
  • Clarify that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide alternatives.
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-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 demonstrates a moderate Windows bias. Azure PowerShell is referenced and linked as the primary example for cluster management tasks (deleting NodeTypes, restarting/reimaging scale sets), with no equivalent Linux/macOS command-line examples (e.g., Azure CLI or sfctl) shown for these operations. PowerShell-based workflows are described first and in detail, while Linux-friendly tools are only listed in a utility table and not exemplified in the main guidance.
Recommendations
  • Add explicit Azure CLI and sfctl command examples for all major management tasks (deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
  • When referencing PowerShell, always mention that equivalent operations can be performed with Azure CLI or sfctl, and provide links.
  • In best practices, present Azure CLI and sfctl examples before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify platform compatibility for each tool in the utility table (e.g., note that Azure CLI and sfctl are cross-platform).
GitHub Create Pull Request
Service Fabric Introduction to the Service Fabric Infrastructure Service .../articles/service-fabric/infrastructure-service-faq.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 Missing Linux Example
Summary
The documentation provides a PowerShell-only example for bypassing the Infrastructure Service, with no equivalent Linux/macOS command or guidance. The use of PowerShell and Service Fabric Explorer (a GUI tool typically used on Windows) further reinforces a Windows-centric approach, while Linux users are left without clear instructions for performing the same operation.
Recommendations
  • Add equivalent CLI examples for Linux/macOS environments, such as using Azure CLI, Bash, or REST API.
  • Clarify whether the PowerShell command can be run from Azure Cloud Shell (which supports both Bash and PowerShell) or provide alternative instructions.
  • Mention cross-platform tools or interfaces for managing Service Fabric clusters, and link to relevant documentation.
  • Explicitly state platform requirements for Service Fabric Explorer and suggest alternatives if available.
GitHub Create Pull Request
Service Fabric Deploy a Service Fabric managed cluster using the Azure portal ...es/service-fabric/quickstart-managed-cluster-portal.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 is heavily focused on using the Azure portal GUI for all steps, which is platform-neutral. However, the cluster created uses Windows Server 2019-Datacenter VMs exclusively, and there is no mention of Linux-based clusters or how to access/manage the cluster from Linux/macOS clients. Instructions for importing certificates and accessing Service Fabric Explorer implicitly assume Windows certificate stores and browsers, with no guidance for Linux/macOS users. No PowerShell or CLI examples are given, but the lack of Linux parity in cluster OS and client instructions creates friction for non-Windows users.
Recommendations
  • Explicitly mention whether Linux-based managed clusters are supported, and provide instructions if so.
  • Add guidance for importing and using client certificates on Linux and macOS (e.g., using OpenSSL, browser certificate stores, etc.).
  • Include notes or examples for accessing Service Fabric Explorer from Linux/macOS browsers.
  • If possible, provide parity for cluster OS selection (Windows and Linux) and document the differences.
  • Clarify any limitations for non-Windows users in the quickstart prerequisites.
GitHub Create Pull Request
← Previous Page 11 of 29 Next →