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 701-718 of 718 flagged pages
Service Fabric Create a Linux container app on Service Fabric in Azure ...e-fabric/service-fabric-quickstart-containers-linux.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on deploying Linux containers and uses Linux-centric commands and tools throughout. However, in the 'Clean up resources' section, Windows certificate management is described first and in more detail than the Linux/macOS equivalents, with a direct link to the MMC snap-in instructions. The Linux and Mac instructions are brief and lack direct links or step-by-step guidance. Additionally, PowerShell is mentioned as a Service Fabric management option in the 'Configure your environment' section, but is not used in examples.
Recommendations
  • Provide equally detailed instructions and direct links for certificate removal on Linux (e.g., using certutil or manual file removal) and macOS (Keychain Access).
  • When listing management tools, mention Linux/macOS options first or in parallel, and avoid putting Windows tools before their Linux equivalents.
  • Add step-by-step guidance for certificate management on Linux and macOS, similar to the Windows MMC instructions.
  • If mentioning PowerShell, clarify its cross-platform availability or provide Linux/macOS alternatives.
GitHub Create Pull Request
Service Fabric Create a Linux Service Fabric cluster in Azure ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Path Example Windows File Path Windows Certificate Path
Summary
The documentation is focused on deploying a Linux Service Fabric cluster using Azure CLI and templates, and does not provide Windows-specific examples for the main task. However, several example commands use Windows-style file paths (e.g., C:\MyCertificates\MyCertificate.pem), which may confuse Linux/macOS users. There is a clear separation between Linux and Windows cluster creation, with a link to a separate Windows tutorial, and no PowerShell or Windows-only tools are used in the main instructions.
Recommendations
  • Provide Linux/macOS file path examples (e.g., /home/user/MyCertificates/MyCertificate.pem) alongside or instead of Windows-style paths.
  • Add a note clarifying that file paths should be adapted to the user's OS.
  • Ensure all CLI examples are OS-agnostic or provide both Windows and Linux/macOS variants where file paths are involved.
GitHub Create Pull Request
Service Fabric Azure Service Fabric versions ...ain/articles/service-fabric/service-fabric-versions.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows information and tables before Linux, both in navigation and in detail. Windows OS versions are listed with lifecycle details, while Linux equivalents are only provided for Ubuntu and are placed after the Windows section. There are references to Windows-specific upgrade procedures and links, with Linux equivalents not always equally highlighted. The overall structure and ordering favor Windows users, though Linux information is present and reasonably complete.
Recommendations
  • Present Windows and Linux sections in parallel, or default to a neutral order (e.g., alphabetical) rather than Windows first.
  • Ensure upgrade procedures and links are equally highlighted for Linux, not just Windows.
  • Provide lifecycle tables for other supported Linux distributions if applicable, not just Ubuntu.
  • Review all cross-references and ensure Linux parity in guidance and linked documentation.
  • Add a summary table at the top comparing Windows and Linux support/features for quick reference.
GitHub Create Pull Request
Service Fabric Configure a Service Fabric managed cluster to use a NAT gateway ...s/service-fabric/how-to-managed-cluster-nat-gateway.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example commands for ARM templates, Azure CLI, Azure PowerShell, and Azure portal. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and its example is more detailed and multi-step than the CLI example. The PowerShell example is given equal prominence to the CLI, and both are listed before the Azure portal steps. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there explicit mention of Linux/macOS compatibility for the CLI commands. The documentation does not reference Windows-only tools, but the inclusion and detail of PowerShell may signal a slight Windows bias.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add Bash shell script examples for Linux users, especially for multi-step operations.
  • Note any platform-specific differences or requirements for Azure CLI and PowerShell.
  • Consider listing CLI examples before PowerShell to reflect cross-platform parity.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS (if true), or provide alternatives if not.
GitHub Create Pull Request
Service Fabric Describing Azure Service Fabric apps and services ...ic/service-fabric-application-and-service-manifests.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools and paths (Visual Studio, C:\Program Files\...), and suggesting the use of Visual Studio for schema validation. There is no mention of Linux/macOS equivalents or cross-platform alternatives for authoring or validating manifest files. Additionally, the only tooling example given is for Windows, and Windows file paths are used exclusively.
Recommendations
  • Include instructions for validating XML schema on Linux/macOS, such as using xmllint, VS Code, or other cross-platform editors.
  • Mention cross-platform locations for Service Fabric SDK files, or provide guidance for locating schema files on non-Windows systems.
  • Provide examples or references for editing manifests using editors available on Linux/macOS.
  • Avoid using Windows paths exclusively; use environment variables or generic paths where possible.
GitHub Create Pull Request
Service Fabric Service Fabric Azure Resource Manager deployment guardrails ...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a minor Windows bias by listing the Windows Server cluster creation link before the Linux equivalent in the 'Next steps' section. The main technical content is platform-neutral, focusing on Azure Resource Manager templates and Service Fabric concepts without OS-specific commands or tooling.
Recommendations
  • List Linux and Windows cluster creation links in parallel or alphabetically to avoid implicit prioritization.
  • Explicitly state that the guidance applies equally to both Windows and Linux clusters where relevant.
  • If examples or troubleshooting steps are added in future, ensure parity by providing both Windows and Linux versions.
GitHub Create Pull Request
Service Fabric Overview of Azure Service Fabric ...ain/articles/service-fabric/service-fabric-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows development tools (Visual Studio, PowerShell, .NET SDK) are mentioned before Linux equivalents, and the quickstart link points to a .NET (Windows-centric) guide. Linux tooling (Eclipse, Yeoman, Java SDK) is referenced, but less prominently and after Windows tools. No explicit Linux/macOS examples or walkthroughs are provided, and there is no direct parity in example depth or visibility.
Recommendations
  • Provide Linux/macOS quickstart links alongside the Windows/.NET quickstart.
  • Present Linux and Windows development environments with equal prominence and detail.
  • Include example workflows for both PowerShell (Windows) and Bash/CLI (Linux/macOS) where relevant.
  • List Linux tools and patterns before or alongside Windows tools to avoid ordering bias.
  • Ensure all referenced guides (e.g., quickstart) have Linux/macOS equivalents easily discoverable.
GitHub Create Pull Request
Service Fabric Create a Linux container app on Service Fabric in Azure ...e-fabric/service-fabric-quickstart-containers-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Example In Cleanup
Summary
The documentation is strongly Linux-focused throughout, with all main instructions and examples using Linux commands, tools, and patterns. However, in the 'Clean up resources' section, Windows-specific instructions (Certificates MMC snap-in) are mentioned first when describing how to remove certificates, with Mac and Ubuntu following. The mention of PowerShell is only in passing as an alternative management tool, and no PowerShell examples are provided.
Recommendations
  • When listing platform-specific instructions (such as removing certificates), present Linux/macOS instructions first or in parallel with Windows, to reinforce the Linux focus.
  • Consider grouping platform-specific cleanup instructions under clear subheadings (Windows, Mac, Ubuntu) for parity.
  • If mentioning PowerShell as a management tool, also mention Linux equivalents (bash scripts, CLI) with equal prominence.
  • Ensure that any platform-specific tooling is described with parity, and avoid listing Windows tools before Linux/macOS tools in Linux-focused 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
Low 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 mild Windows bias, primarily through its reference to PowerShell in the link for managing user-assigned managed identities and the absence of Linux/macOS-specific command-line examples. The only external tool mentioned is PowerShell, with no mention of Azure CLI or Bash alternatives. No explicit OS-specific instructions are provided, but the documentation assumes familiarity with Windows-centric tooling and patterns.
Recommendations
  • Include Azure CLI and Bash examples alongside or before PowerShell references, especially for identity management tasks.
  • When linking to external resources, provide both PowerShell and Azure CLI/Bash documentation links.
  • Explicitly state that the ARM template and manifest editing steps are OS-agnostic, and clarify any platform-specific requirements.
  • Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
GitHub Create Pull Request
Service Fabric Use a Public IP address prefix in a Service Fabric managed cluster ...vice-fabric/how-to-managed-cluster-public-ip-prefix.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying a public IP address prefix in a Service Fabric managed cluster. However, PowerShell (a Windows-centric tool) is given its own dedicated section and example, while Linux/macOS equivalents (such as Bash scripting or explicit Linux CLI usage) are not mentioned. The ordering of examples places Azure CLI first, which is cross-platform, but the inclusion and prominence of PowerShell may suggest a slight Windows bias. There are no Linux-specific instructions or notes, and no mention of macOS.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Add explicit Bash shell examples for Linux/macOS users, especially for template deployment.
  • Note any platform-specific differences or prerequisites for Azure CLI and PowerShell.
  • Consider mentioning cross-platform compatibility in the requirements section.
  • If PowerShell is shown, consider showing Bash or Linux shell equivalents for parity.
GitHub Create Pull Request
Service Fabric Plan an Azure Service Fabric cluster deployment ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally maintains OS neutrality, but in the 'Next steps' section, the link to creating a Windows cluster is listed before the Linux equivalent. No examples, tools, or instructions are specific to Windows or PowerShell, and Linux is mentioned as a supported OS throughout. No critical steps are Windows-only.
Recommendations
  • List Windows and Linux cluster creation links side-by-side or alternate their order to avoid implicit prioritization.
  • Continue to ensure examples and instructions are OS-agnostic or provide both Windows and Linux variants where appropriate.
  • Explicitly mention Linux support in any sections discussing templates, scripts, or tooling if relevant.
GitHub Create Pull Request
Service Fabric Create an Azure Service Fabric container application on Linux ...-fabric/service-fabric-get-started-containers-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is primarily focused on Linux, but there are minor instances of Windows bias. Notably, the instructions for logging into Docker and building the image suggest opening a PowerShell window, which is a Windows-specific tool. Additionally, the example commands are sometimes shown with Windows conventions (e.g., PowerShell), and Windows tools are mentioned before their Linux equivalents in some places. However, the majority of the content, tooling, and examples are Linux-centric, and Linux users can complete all tasks without significant friction.
Recommendations
  • Replace 'Open a PowerShell window' with 'Open a terminal window' or specify both PowerShell (Windows) and terminal (Linux/macOS) options.
  • Ensure all command examples use cross-platform syntax (e.g., bash) and avoid Windows-specific conventions unless explicitly needed.
  • If referencing Windows tools or patterns, always provide the Linux/macOS equivalent first or alongside.
  • Review for any other subtle Windows-first language and adjust to prioritize Linux/macOS context, given the article's focus.
GitHub Create Pull Request
Service Fabric Reliable Collection object serialization ...c-reliable-services-reliable-collections-serialization.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-specific tools (Visual Studio and PowerShell) in the 'Next steps' section, with no mention of Linux/macOS equivalents or cross-platform alternatives. The examples and technical content are platform-neutral C#, but the upgrade guidance and tooling references prioritize Windows environments.
Recommendations
  • Add instructions or links for upgrading applications using cross-platform tools such as Azure CLI or Service Fabric CLI.
  • Include guidance for Linux/macOS users on how to perform upgrades and serialization tasks outside of Visual Studio and PowerShell.
  • Explicitly mention platform compatibility for the code samples and APIs, clarifying if/when they are usable on Linux/macOS.
  • Provide parity in 'Next steps' by listing Linux/macOS-friendly tutorials and troubleshooting guides.
GitHub Create Pull Request
Service Fabric Create a Linux Service Fabric cluster in Azure ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Path Examples Windows File Path Patterns
Summary
The documentation is focused on deploying a Linux Service Fabric cluster using Azure CLI and Service Fabric CLI, with no PowerShell or Windows-specific tools used in the main instructions. However, several example file paths use Windows-style (e.g., C:\MyCertificates), and there is no mention of Linux/macOS file path equivalents. This may cause minor confusion for Linux/macOS users, but the overall workflow is cross-platform.
Recommendations
  • Provide Linux/macOS file path examples alongside Windows paths (e.g., ~/MyCertificates or /home/user/MyCertificates).
  • Add a note clarifying that file paths should be adapted to the user's OS.
  • Explicitly mention that Azure CLI and Service Fabric CLI are cross-platform and can be used on Linux/macOS.
  • Consider showing Linux/macOS shell commands (e.g., export VAR=value) if environment variables are set.
GitHub Create Pull Request
Service Fabric Azure Service Fabric versions ...ain/articles/service-fabric/service-fabric-versions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page presents Windows content first, including upgrade procedures and OS support tables, and references Windows-specific tools and lifecycle links before Linux equivalents. While Linux parity is generally maintained via tab selectors and parallel tables, Windows is consistently prioritized in structure and navigation. Some links and upgrade procedures are Windows-specific or default to Windows, with Linux guidance less prominent.
Recommendations
  • Present Windows and Linux tabs in a neutral order (e.g., alphabetical or randomized) or default to user's OS when possible.
  • Ensure upgrade procedures and links are available and equally prominent for Linux clusters.
  • Add Linux-specific lifecycle and support links alongside Windows equivalents in summary sections.
  • Review cross-references to ensure Linux guidance is not omitted or less visible than Windows guidance.
  • Consider a combined summary table for OS support, with clear separation for Windows and Linux, to avoid Windows-first presentation.
GitHub Create Pull Request
Service Fabric Service Fabric Azure Resource Manager deployment guardrails ...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists Windows Server cluster creation before Linux cluster creation in the 'Next steps' section, which may subtly prioritize Windows users. However, the main content is platform-neutral and does not provide OS-specific examples or instructions.
Recommendations
  • List Linux and Windows cluster creation links together or alternate their order to avoid implicit prioritization.
  • Explicitly state that the guidance applies equally to both Windows and Linux deployments where relevant.
  • Add platform-specific notes or examples if there are differences in deployment or troubleshooting steps.
GitHub Create Pull Request
Service Fabric Create an Azure Load Balancer rule for a cluster ...n/articles/service-fabric/create-load-balancer-rule.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for creating Azure Load Balancer rules. While the Azure CLI is cross-platform and presented first, the PowerShell section is given equal prominence and detail, despite being Windows-centric. There are no Linux/macOS-specific examples or mentions of platform differences, and PowerShell is described as a standard alternative rather than a Windows-only tool.
Recommendations
  • Clarify that PowerShell is primarily a Windows tool and mention cross-platform alternatives if available.
  • Add explicit notes that Azure CLI works on Linux/macOS and is the recommended method for non-Windows users.
  • Consider removing or de-emphasizing PowerShell instructions unless there is a unique capability not available in Azure CLI.
  • If PowerShell Core (cross-platform) is supported, specify compatibility and installation instructions for Linux/macOS.
GitHub Create Pull Request
Service Fabric Service Fabric Azure Resource Manager deployment guardrails ...ic/service-fabric-azure-resource-manager-guardrails.md
Low Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias by listing the Windows Server cluster creation guide before the Linux equivalent in the 'Next steps' section. No PowerShell-heavy examples, Windows-exclusive tools, or missing Linux examples are present in the main content, which is platform-neutral and focused on ARM templates.
Recommendations
  • List Linux and Windows cluster creation guides in parallel or alternate their order to avoid implying priority.
  • Explicitly state that all ARM template examples and guidance apply equally to both Windows and Linux clusters.
  • Where platform-specific instructions are given, ensure both Windows and Linux are covered with equal prominence.
GitHub Create Pull Request
← Previous Page 29 of 29 Next →