Service Fabric
407
Total Pages
335
Linux-Friendly Pages
72
Pages with Bias
17.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2475 issues found
Showing 2276-2300 of 2475 flagged pages
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. It references Visual Studio as a primary tool for packaging and deploying guest executables and mentions the Service Fabric SDK schema location using a Windows file path. There are no explicit Linux/macOS examples or equivalent tooling mentioned, and the directory structure example uses a Windows executable (.exe), which may imply Windows-centric guidance. However, the content does not restrict the process to Windows and mentions running Node.js and Java, which are cross-platform.
Recommendations
- Add explicit Linux/macOS instructions for packaging and deploying guest executables, including command-line examples using Bash or cross-platform tools.
- Mention the location of Service Fabric SDK schema files on Linux/macOS, if available, or clarify if the SDK is Windows-only.
- Provide sample directory structures using cross-platform executable formats (e.g., .sh, .jar, or generic binaries) alongside .exe.
- Reference cross-platform IDEs or tools (e.g., VS Code, CLI utilities) in addition to Visual Studio.
- Clarify any Windows-specific requirements or limitations, and highlight Linux/macOS compatibility where applicable.
Create Pull Request
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, but Windows development tools (Visual Studio, PowerShell) are listed before Linux equivalents (Eclipse, Yeoman). There are no explicit examples or instructions favoring Windows, but the ordering subtly prioritizes Windows. No critical sections are Windows-only, and Linux support is clearly stated.
Recommendations
- Present Windows and Linux development options in parallel or alternate their ordering.
- Ensure quickstart and getting started links are available for both Windows and Linux (currently, the quickstart link points to a .NET/Windows page).
- Add explicit links to Linux quickstart and getting started guides in the 'Next steps' section.
- Where possible, provide sample commands/examples for both platforms.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides examples and configuration snippets for both Windows (ClusterManifest.xml under <WindowsServer>) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml with <WindowsServer>) is presented first and more prominently, and PowerShell examples are included without Linux CLI equivalents. There is a mild bias toward Windows tools and patterns, but Linux/standalone parity is generally maintained.
Recommendations
- Present Linux/standalone configuration examples (ClusterConfig.json) before or alongside Windows-specific examples.
- Include CLI examples for Linux/macOS users (e.g., Azure CLI, Bash scripts) where PowerShell examples are given.
- Clarify which examples apply to Windows-only deployments and which are cross-platform.
- Add explicit notes or links for Linux/macOS users about how to perform equivalent tasks.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page for Service Fabric reliable services app manifest examples shows mild Windows bias. It references Windows-specific tools (e.g., ServiceFabric PowerShell module), uses Windows-centric terminology (e.g., 'Setup.bat', 'exe'), and describes user accounts and groups in a way that aligns with Windows conventions (e.g., 'Administrators', 'NetworkService'). Linux equivalents or cross-platform guidance are not provided, and Windows tools are mentioned before any alternatives.
Recommendations
- Add Linux-specific examples or clarify cross-platform support for Service Fabric manifest features.
- Mention Linux deployment tools (e.g., CLI, Bash scripts) alongside PowerShell, or clarify if PowerShell is required on Linux.
- Provide guidance on user/group principals for Linux clusters, including mapping to Linux system users/groups.
- Include notes or examples for running setup scripts in Linux environments (e.g., using .sh files instead of .bat).
- Clarify any platform-specific limitations or behaviors for Service Fabric manifest elements.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias in the ordering and emphasis: Windows container runtimes and tools (Mirantis Container Runtime, DockerEE) are listed in detail, while Linux only mentions Docker. Windows scenarios (IIS lift and shift) are described before Linux scenarios, and Windows links are sometimes presented before Linux equivalents. The documentation references Windows-specific tools and patterns (IIS, Windows Server containers) more prominently.
Recommendations
- Ensure Linux and Windows examples/tutorials are presented in parallel or with equal prominence.
- Expand Linux-specific scenarios (e.g., NGINX, Apache, Linux-based microservices) to match Windows-specific examples like IIS.
- List Linux container runtimes and tools (e.g., containerd, Podman) if supported, not just Docker.
- When describing container capabilities, clarify which features are available on Linux vs. Windows.
- Avoid listing Windows tools or runtimes before Linux equivalents unless there is a technical reason.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. It references the Service Fabric SDK schema location using a Windows file path and mentions Visual Studio as a packaging/deployment tool before command-line utilities. There are no explicit Linux/macOS examples or references to cross-platform tools, and the directory structure example uses a Windows executable (.exe), which may imply Windows-centric workflows.
Recommendations
- Add explicit Linux/macOS examples for packaging and deploying guest executables, including references to cross-platform tools.
- Mention the location of Service Fabric SDK schema files on Linux/macOS, if available, or clarify if the SDK is Windows-only.
- Provide guidance for using command-line utilities on Linux/macOS, and ensure parity with Visual Studio instructions.
- Use neutral file extensions (e.g., .sh, .jar, .out) in directory structure examples, or clarify that .exe is just one possible format.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Service Fabric CLI (sfctl) examples for deploying Docker Compose files, but PowerShell commands are presented first and in greater detail. This may create a perception that Windows/PowerShell is the primary or preferred environment, even though cross-platform CLI alternatives are available. There is no explicit Linux/macOS bias, but the ordering and emphasis favor Windows users.
Recommendations
- Present Service Fabric CLI (sfctl) examples before or alongside PowerShell examples, as sfctl is cross-platform and works on Linux/macOS.
- Explicitly mention that sfctl is recommended for Linux/macOS users and provide installation instructions or a link.
- Ensure parity in the level of detail for both PowerShell and sfctl command examples.
- Add a note clarifying that PowerShell commands are for Windows users, while sfctl is suitable for all platforms.
Service Fabric
Node types and virtual machine scale sets
...les/service-fabric/service-fabric-cluster-nodetypes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides general information about Azure Service Fabric node types and VM scale sets, with some references to both Windows and Linux nodes. However, the JSON snippet example uses a Windows-style file path (D:\\SvcFab) for the dataPath property, and the 'Next steps' section links to PowerShell scripts for RDP port and admin credential changes, which are Windows-centric tasks. There are no explicit Linux/macOS examples or guidance for equivalent SSH access or Linux file paths, creating a mild Windows bias.
Recommendations
- Provide Linux/macOS examples alongside Windows examples, such as using '/var/svcfab' for dataPath.
- Add guidance or links for SSH access to Linux nodes, not just RDP/PowerShell for Windows.
- Clarify which tasks are Windows-only and offer Linux alternatives where possible.
- Include sample ARM template snippets for both 'ServiceFabricNode' (Windows) and 'ServiceFabricLinuxNode' (Linux) with relevant property values.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias toward Windows in some sections: Windows container runtimes are listed in greater detail, Windows scenarios (such as IIS lift-and-shift) are described first, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned. Linux is covered, but Windows examples and tools are sometimes presented before Linux equivalents.
Recommendations
- Present Linux and Windows examples/tools in parallel or alternate order to avoid 'Windows first' bias.
- Expand Linux-specific scenarios (e.g., Apache, NGINX, Python apps) alongside Windows/IIS examples.
- Mention Linux container runtimes (e.g., containerd, Podman) if relevant, not just Docker.
- Ensure that quickstart/tutorial links for Linux and Windows are equally prominent and described.
- Clarify when features or scenarios are Windows-only to avoid confusion.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page mentions Windows base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in container image cleanup, but does not mention Linux base images or provide examples relevant to Linux containers. The examples and explanations focus on Windows images first, and there is no explicit guidance for Linux container scenarios.
Recommendations
- Add examples and explanations for Linux base images (e.g., 'mcr.microsoft.com/linux', 'docker.io/library/ubuntu') in the 'ContainerImagesToSkip' setting.
- Clarify whether the cleanup process applies equally to Linux containers and Windows containers, and provide Linux-specific guidance if needed.
- Include sample configurations or notes for clusters running Linux containers, ensuring parity in documentation.
- Explicitly mention that the feature is cross-platform (if applicable), or clarify any platform limitations.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page for Service Fabric Reliable Services app manifest examples exhibits mild Windows bias. Windows concepts (such as 'NetworkService', 'Administrators', '.bat' files, and EXE executables) are referenced throughout, and Windows terminology is used for user accounts and groups. The only script example is a Windows batch file (Setup.bat), and EXE executables are assumed. There is a mention of using the ServiceFabric PowerShell module to create service instances, with no Linux CLI equivalent. However, the manifest XML itself is cross-platform, and no critical steps are Windows-only.
Recommendations
- Add examples or notes for Linux deployments, such as using shell scripts (.sh) instead of batch files (.bat) in SetupEntryPoint.
- Mention Linux user/group equivalents or clarify how Service Fabric handles principals on Linux nodes.
- Provide CLI examples for Linux (e.g., Azure CLI or Service Fabric CLI) alongside PowerShell references.
- Clarify that EXE/NetworkService/Administrators are Windows-specific and provide Linux alternatives where applicable.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally platform-neutral, but there are subtle signs of Windows bias. Windows-specific terminology (such as referencing 'auto-start Windows service, FabricHost.exe') is used in the definition of nodes, and Windows executables (EXE/DLL) are mentioned as typical code packages. Windows containers are mentioned before Linux containers in some sections. However, Linux support is acknowledged, and most concepts are described in a generic way.
Recommendations
- Clarify that 'FabricHost.exe' and related Windows services have Linux equivalents, or explicitly state how node management differs on Linux clusters.
- When mentioning code packages, note that Linux executables (such as ELF binaries or scripts) are equally supported.
- In sections discussing containers, mention Linux containers first or equally, and clarify that Docker containers are supported on Linux and Windows.
- Where Windows-specific terminology is used, add a note or parenthetical to explain the Linux equivalent or behavior.
- Consider adding explicit Linux examples or references where Windows tools or patterns are mentioned.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page for Azure Service Fabric container image management shows minor Windows bias. Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) are mentioned as default exclusions in cleanup settings, and Windows examples are given first in the 'ContainerImagesToSkip' section. However, Linux images (e.g., docker.io/library/alpine:latest) are also referenced, and the documentation does not restrict the guidance to Windows-only scenarios.
Recommendations
- Provide explicit examples for Linux container base images (such as Ubuntu, Alpine, or other common Linux distributions) in the 'ContainerImagesToSkip' section.
- Clarify that the cleanup settings and image management apply equally to both Windows and Linux containers, unless there are platform-specific limitations.
- Consider mentioning Linux container image patterns alongside Windows examples, or list Linux examples first to balance presentation.
- Add a note about any differences in image cleanup behavior between Windows and Linux containers, if applicable.
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page provides examples and links for Azure PowerShell before mentioning Azure CLI or sfctl, and the 'Best practices' section highlights PowerShell-based workflows. While Azure CLI and ARM/Bicep tools are listed, PowerShell is emphasized, and no explicit Linux/macOS usage examples are given. This creates mild friction for Linux/macOS users, though all recommended tools (except Service Fabric PowerShell) are cross-platform.
Recommendations
- Add explicit Azure CLI examples for key operations (e.g., deleting NodeTypes, restarting/reimaging scale sets) alongside PowerShell examples.
- Clarify that Azure PowerShell and Azure CLI are both cross-platform and provide links to installation/use guides for Linux/macOS.
- Consider showing Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Mention sfctl usage for relevant tasks, or clarify its limitations compared to ARM-backed tools.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and cross-platform CLI (sfctl) examples for deploying Docker Compose files to Azure Service Fabric. However, PowerShell examples are presented first and in more detail, which may signal a Windows-first bias. The CLI examples (sfctl) are included and are cross-platform, but are listed after PowerShell and with slightly less introductory context.
Recommendations
- Present CLI (sfctl) examples before PowerShell, or clarify that sfctl is cross-platform and recommended for Linux/macOS users.
- Explicitly state that sfctl works on all platforms and is the preferred method for non-Windows environments.
- Ensure that all PowerShell examples have equivalent sfctl commands and vice versa.
- Consider adding a short section or callout for Linux/macOS users to highlight the cross-platform workflow.
Service Fabric
Change Azure Service Fabric cluster settings
...rvice-fabric/service-fabric-cluster-fabric-settings.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page provides a comprehensive reference for Service Fabric cluster settings, but exhibits mild Windows bias. Windows-specific terminology, defaults, and tools (such as certificate store names like 'MY', store locations like 'LocalMachine', and references to Windows Defender Firewall) are used throughout. Windows is often mentioned first in settings (e.g., 'ContainerNetworkSetup' defaults to TRUE for Windows, FALSE for Linux), and some parameters (like log file settings for containers) are marked 'Windows only' without Linux equivalents or guidance. There are references to Windows-specific APIs (e.g., CertGetCertificateChain) and settings (e.g., NTLM authentication, Windows Fabric Replicator endpoints), but Linux settings are sometimes present (e.g., 'LinuxExternalExecutablePath', 'X509Folder'). However, Linux-specific guidance and parity are often missing or less detailed.
Recommendations
- Provide explicit Linux/macOS examples or guidance for settings where Windows defaults or terminology are used (e.g., certificate store names, log file locations, firewall configuration).
- Where parameters are 'Windows only', clarify Linux equivalents or explicitly state if no equivalent exists.
- Ensure Linux-specific settings (such as 'LinuxExternalExecutablePath', 'X509Folder') are documented as thoroughly as Windows settings.
- Add notes or tables summarizing differences in behavior, defaults, or required actions between Windows and Linux clusters.
- Where Windows APIs or tools are referenced (e.g., CertGetCertificateChain), provide Linux alternatives or clarify applicability.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric's container support for both Linux and Windows, but there is a slight bias toward Windows. Windows container runtimes and tools are discussed in more detail, and Windows scenarios (such as IIS lift-and-shift) are mentioned first in the 'Scenarios for using containers' section. Windows tutorials and references are often listed before Linux equivalents, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are highlighted.
Recommendations
- Ensure Linux scenarios are presented with equal prominence to Windows scenarios, such as mentioning NGINX or Apache lift-and-shift alongside IIS.
- List Linux and Windows tutorials/examples in parallel or alternate their order to avoid Windows-first bias.
- Provide more detail about Linux container runtimes and tools, such as mentioning containerd or Podman if relevant.
- Expand Linux-specific use cases and highlight Linux container orchestration patterns where applicable.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page for Service Fabric application and service manifest examples shows a mild Windows bias. Batch scripts (.bat), EXE files, and references to Windows user accounts (Administrators, NetworkService) are used in examples, and Windows-specific terminology appears throughout. The only mention of command-line tooling is a reference to the ServiceFabric PowerShell module, with no Linux CLI equivalent. However, the page focuses on XML manifest structure and does not explicitly exclude Linux, nor does it use Windows-only features.
Recommendations
- Provide Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) instead of only .bat files.
- Mention cross-platform deployment tools (e.g., Azure CLI, sfctl) in addition to PowerShell.
- Clarify which user account concepts apply to Linux (e.g., mapping NetworkService to Linux equivalents, or noting limitations).
- Add notes or examples for running services on Linux Service Fabric clusters, including any differences in manifest usage.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no equivalent Linux/macOS tooling or examples provided. The main content does not reference Windows-specific patterns or tools, but the ordering and selection of upgrade tutorials could create minor friction for non-Windows users.
Recommendations
- Add links or references to Linux/macOS-compatible upgrade workflows, such as using Azure CLI or REST APIs.
- Clarify whether PowerShell examples are cross-platform (PowerShell Core) or Windows-only.
- Consider mentioning cross-platform development environments (e.g., VS Code, CLI) alongside Visual Studio.
- Explicitly state if certain tools are Windows-only, and provide alternatives for Linux/macOS users.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page contains several instances of Windows-centric terminology and examples, such as referencing Windows services (FabricHost.exe), EXE/DLL files, and Windows-specific containers. Windows tools and patterns are mentioned first or exclusively in some sections, with Linux equivalents referenced later or less prominently. However, Linux support is acknowledged, and most concepts are described in a cross-platform manner.
Recommendations
- Clarify when features or terminology are Windows-specific versus cross-platform.
- Provide Linux-specific examples and terminology alongside Windows examples (e.g., mention Linux service management, file types, and container support equally).
- Avoid referencing Windows executables (EXE/DLL) exclusively; mention Linux binaries or scripts where relevant.
- Ensure that descriptions of cluster nodes and services do not imply Windows-only operation unless the feature is truly Windows-specific.
- Add explicit Linux/macOS parity notes for development clusters and guest executables.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows, but there are minor signs of Windows bias. Windows container runtimes and IIS scenarios are mentioned before Linux equivalents in some sections, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are listed in detail. However, Linux support is clearly described, and Linux tutorials are linked alongside Windows ones.
Recommendations
- Ensure Linux examples and tools are presented with equal prominence and detail as Windows equivalents.
- When listing container runtimes, provide more information about Linux alternatives (e.g., mention containerd or other runtimes if supported).
- In scenario sections, balance Windows-specific use cases (like IIS lift and shift) with Linux-centric examples (such as Apache or NGINX migration).
- Where possible, alternate the order of Linux and Windows examples to avoid 'windows_first' bias.
Service Fabric
Azure Service Fabric image store connection string
...fabric/service-fabric-image-store-connection-string.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references PowerShell as the primary example for retrieving the cluster manifest and links to a PowerShell-based deployment guide as the next step. While .NET and REST are mentioned, PowerShell is consistently listed first, and there are no explicit Linux/CLI/bash examples or guidance. This creates a subtle Windows-first bias, though the core content is platform-neutral.
Recommendations
- Add explicit examples or references for retrieving the cluster manifest using Azure CLI or bash scripts, especially for Linux/macOS users.
- When listing programmatic options, alternate the order or clarify that all methods are equally supported across platforms.
- Provide a 'Next steps' link to a cross-platform deployment guide (e.g., using Azure CLI or REST) in addition to the PowerShell-focused guide.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. The schema definition for manifest files is referenced with a Windows file path, and the application package structure example uses a Windows-style executable (.exe). There is no explicit Linux example or mention of Linux tooling, and Visual Studio (a Windows-centric IDE) is referenced as a packaging option before command-line utilities. However, the content does not prevent Linux/macOS users from understanding or completing the task, as Service Fabric supports guest executables of any type (Node.js, Java, C++), and the packaging model is platform-agnostic.
Recommendations
- Add Linux/macOS file path examples for schema definitions, or clarify if the schema is available on non-Windows platforms.
- Include examples of packaging non-Windows executables (e.g., .sh, Node.js, Java) in the directory structure.
- Mention cross-platform command-line tools and editors (e.g., VS Code, CLI utilities) alongside Visual Studio.
- Explicitly state that the packaging process is platform-agnostic and provide links or guidance for Linux/macOS users.
Service Fabric
Manage apps for multiple environments
...e-fabric-manage-multiple-environment-app-configuration.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for managing application parameters in Azure Service Fabric, mentioning PowerShell and Visual Studio (both Windows-centric tools) first, with Linux-compatible tools (sfctl, install.sh) mentioned second. There is a slight bias toward Windows tools and workflows, but Linux options are present.
Recommendations
- Present Linux-compatible tools (sfctl, install.sh) before or alongside Windows tools to avoid Windows-first bias.
- Include explicit Linux/macOS example commands and workflows, such as using sfctl from Bash or shell scripts.
- Clarify which tools are cross-platform and which are Windows-only, to help users choose appropriate options.
- Add a section or note for Linux/macOS users outlining recommended workflows and tools.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows development and tools (Visual Studio, PowerShell) before Linux equivalents (Eclipse, Yeoman), and links to the Windows quickstart as the primary next step. However, Linux support and tools are referenced, and the page is not Windows-specific.
Recommendations
- Present Windows and Linux development options in parallel, rather than listing Windows first.
- Include links to both Windows and Linux quickstart guides in the 'Next steps' section.
- Ensure examples and tool references are balanced between Windows and Linux throughout the documentation.