Operator Service Manager

48
Total Pages
35
Linux-Friendly Pages
13
Pages with Bias
27.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

48 issues found
Showing 1-25 of 48 flagged pages
Operator Service Manager About the Azure Operator Service Manager CLI extension ...r/concepts-about-azure-operator-service-manager-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax for CLI commands and output examples, implicitly prioritizing Windows users. There are no Bash or Linux shell examples, nor any mention of Linux-specific considerations, despite the Azure CLI being cross-platform. This may make Linux/macOS users feel less supported or unsure if the instructions apply to their environments.
Recommendations
  • Provide equivalent Bash/Linux shell command examples alongside PowerShell examples.
  • Clarify that the Azure CLI commands work identically on Linux/macOS terminals.
  • Show example outputs in a generic format or note any differences in output formatting between platforms.
  • Explicitly mention cross-platform compatibility in the installation and usage instructions.
GitHub Create Pull Request
Operator Service Manager Interrupt a Service Deployment with Azure Operator Service Manager ...r-service-manager/how-to-cancel-service-deployments.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively providing Azure CLI examples in PowerShell syntax, which is native to Windows. No Bash or Linux shell equivalents are shown, and the examples use PowerShell formatting (curly braces for variables, command style). There is no mention of Linux-specific usage patterns, nor are Linux/Bash examples provided alongside or before the Windows/PowerShell ones.
Recommendations
  • Provide equivalent Azure CLI examples using Bash syntax (e.g., az tag update --resource-id $resourceGroup ...), with variable usage and quoting appropriate for Linux shells.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and show examples for both environments.
  • Avoid using only PowerShell syntax for CLI commands; include Bash examples or use generic syntax where possible.
  • If referencing command-line usage, clarify any platform-specific differences (such as variable substitution or quoting).
GitHub Create Pull Request
Operator Service Manager Prerequisites for Operator and Containerized Network Function (CNF) ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Set environment variables' section, where Windows PowerShell is mentioned first and given as the only explicit example for setting environment variables, while Linux/bash examples are provided only for subsequent variables and not for the initial example. There is no explicit Linux or macOS equivalent for referencing environment variables, and the initial guidance is tailored to Windows users. The rest of the page uses Azure CLI and bash syntax, which is cross-platform, but the initial orientation and examples favor Windows.
Recommendations
  • Provide Linux/macOS equivalents alongside Windows PowerShell examples when discussing environment variable setting and referencing.
  • Present both Windows and Linux/macOS examples in parallel, or use a tabbed interface to allow users to select their platform.
  • Avoid presenting Windows examples first or exclusively; ensure parity by alternating or combining examples for all major platforms.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and clarify any platform-specific nuances.
  • Include notes or tips for macOS users where applicable, especially for environment variable syntax and shell differences.
GitHub Create Pull Request
Operator Service Manager Publisher artifact store resiliency with Azure Operator Service Manager ...service-manager/publisher-artifact-store-resiliency.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively providing PowerShell and Azure CLI examples, with no mention of Linux shell equivalents (e.g., bash), nor any cross-platform command alternatives. All code snippets and operational instructions use Windows-centric tooling and syntax, and there is no guidance for Linux or macOS users. The FAQ and operational steps assume use of PowerShell or Azure CLI without clarifying platform compatibility or offering Linux-specific instructions.
Recommendations
  • Provide equivalent bash or shell examples for Linux users alongside PowerShell/CLI commands.
  • Clarify that Azure CLI commands are cross-platform, and show examples in both Windows (PowerShell) and Linux (bash) syntax.
  • Explicitly mention platform compatibility for all commands and tools referenced.
  • Include notes or sections for Linux/macOS users, especially for steps involving scripting, endpoints, or DNS updates.
  • Avoid using only PowerShell syntax in code blocks; use generic CLI or REST API examples where possible.
GitHub Create Pull Request
Operator Service Manager Publisher resource clean-up management with Azure Operator Service Manager ...perator-service-manager/resource-cleanup-management.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily through the exclusive use of PowerShell for Azure Resource Graph (ARG) query examples, without providing equivalent Bash or Linux shell examples. Additionally, the use of PowerShell syntax (e.g., | %{ ... }) in Azure CLI command pipelines is a Windows-centric pattern, and Linux-native alternatives (such as using xargs or while-read loops) are not mentioned. The scheduling example references crontab, but the actual command pipeline remains Windows-oriented. No Linux/Bash examples are given for ARG queries or Azure CLI command chaining.
Recommendations
  • Provide equivalent Bash/Linux shell examples for all PowerShell-based ARG queries and Azure CLI command pipelines.
  • When showing Azure CLI command chaining, use cross-platform syntax (e.g., xargs, while-read) alongside PowerShell examples.
  • Explicitly mention that both Windows and Linux environments are supported, and clarify any platform-specific behaviors.
  • Order examples so that Linux/Bash and Windows/PowerShell are presented with equal prominence, or alternate which comes first.
  • Add notes or code tabs to allow users to select their preferred shell (PowerShell, Bash, etc.) for all command examples.
GitHub Create Pull Request
Operator Service Manager About the Azure Operator Service Manager CLI extension ...r/concepts-about-azure-operator-service-manager-cli.md
High 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 all CLI command examples in PowerShell syntax, which is primarily used on Windows. There are no Bash or Linux shell examples, nor is there any mention of Linux-specific considerations. This may lead Linux users to feel unsupported or confused, especially since the Azure CLI is cross-platform.
Recommendations
  • Provide command examples in both PowerShell and Bash syntax, or use a neutral format that works on both platforms.
  • Explicitly mention that the Azure CLI and the AOSM extension are supported on Linux and macOS, not just Windows.
  • Include notes or sections addressing Linux/macOS installation and usage, such as differences in shell syntax or environment setup.
  • Avoid using PowerShell-specific formatting (e.g., code blocks labeled 'powershell') for generic CLI commands.
GitHub Create Pull Request
Operator Service Manager Interrupt a Service Deployment with Azure Operator Service Manager ...r-service-manager/how-to-cancel-service-deployments.md
High 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 consistently uses PowerShell syntax for Azure CLI commands, which is most common on Windows. All command-line examples are given in PowerShell format, with no Bash or Linux shell equivalents. There is no mention of Linux-specific patterns, and the use of PowerShell may confuse Linux users, who typically use Bash for Azure CLI. The documentation does not clarify cross-platform usage or provide parity for Linux environments.
Recommendations
  • Provide Azure CLI examples in Bash syntax alongside PowerShell, or use generic CLI syntax that works on both platforms.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and clarify any platform-specific considerations.
  • Avoid using PowerShell-specific syntax (such as curly braces for parameters) in CLI examples unless also providing Bash equivalents.
  • Include notes or sections for Linux users, ensuring that instructions are clear for both Windows and Linux environments.
  • If referencing tools or workflows, mention both Windows and Linux alternatives where applicable.
GitHub Create Pull Request
Operator Service Manager Publisher artifact store resiliency with Azure Operator Service Manager ...service-manager/publisher-artifact-store-resiliency.md
High 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 Windows bias by providing only PowerShell and Azure CLI examples, with no Linux shell (bash) or cross-platform command alternatives. All code snippets and operational instructions use PowerShell syntax, and there is no mention of Linux-specific tools or workflows. The FAQ and operational guidance also assume use of Windows-centric tooling, omitting Linux-native approaches.
Recommendations
  • Provide equivalent bash or shell examples for all PowerShell and Azure CLI commands, ensuring Linux users can follow along.
  • Explicitly mention cross-platform compatibility for Azure CLI commands, clarifying usage on Linux, macOS, and Windows.
  • Include references to Linux-native tools (e.g., curl, jq) where API calls are shown, and demonstrate their usage.
  • Add a section or note highlighting any platform-specific considerations, such as authentication or environment setup differences between Windows and Linux.
  • Ensure that documentation screenshots, file paths, and environment variables use platform-neutral or dual examples.
GitHub Create Pull Request
Operator Service Manager Publisher resource clean-up management with Azure Operator Service Manager ...perator-service-manager/resource-cleanup-management.md
High 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 Windows bias by providing only PowerShell examples for Azure Resource Graph queries, omitting equivalent Linux-friendly shell (bash/az CLI) examples. The use of PowerShell syntax (e.g., | %{ ... }) in Azure CLI command snippets further reinforces a Windows-centric approach, potentially confusing Linux users. While crontab is mentioned for scheduling, all code samples and query instructions are tailored to Windows/PowerShell environments, with no direct Linux or bash alternatives.
Recommendations
  • Provide bash/Azure CLI examples for all PowerShell queries, especially for ARG queries.
  • Replace PowerShell-specific pipeline syntax (e.g., | %{ ... }) with bash equivalents (e.g., xargs or while read loops) in Azure CLI command samples.
  • Explicitly mention cross-platform usage and clarify which commands are suitable for Linux/macOS environments.
  • Add notes or sections for Linux users, including how to run queries and schedule tasks using native Linux tools.
  • Ensure that examples are presented in both PowerShell and bash, or use platform-neutral Azure CLI syntax where possible.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/concepts-about-azure-operator-service-manager-cli.md ...r/concepts-about-azure-operator-service-manager-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax for all CLI examples and command blocks, and does not provide any Linux or macOS shell equivalents (e.g., Bash). There is no mention of Linux-specific considerations or alternative command patterns, which may make the documentation less accessible to users on non-Windows platforms.
Recommendations
  • Provide Bash (Linux/macOS) equivalents for all CLI command examples, either alongside or in place of PowerShell blocks.
  • Use generic shell code blocks (e.g., ```sh or ```bash) for Azure CLI commands, since the CLI is cross-platform and the commands are typically the same across OSes.
  • Avoid using PowerShell-specific code block annotations unless demonstrating PowerShell-specific features.
  • Explicitly mention that the Azure CLI and the AOSM extension are supported on Windows, Linux, and macOS, and provide links or notes for platform-specific installation instructions if relevant.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-cancel-service-deployments.md ...r-service-manager/how-to-cancel-service-deployments.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell-formatted Azure CLI examples, which are more familiar to Windows users. There are no Bash or Linux shell examples, nor is there mention of Linux-specific usage patterns. The use of PowerShell syntax for Azure CLI commands may confuse Linux users, and the documentation does not clarify cross-platform compatibility or provide parity in example formats.
Recommendations
  • Provide Azure CLI examples in both PowerShell and Bash syntax, or use neutral formatting that works on all platforms.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Add notes or sections highlighting any platform-specific differences, if they exist.
  • Include screenshots or instructions for using the Azure CLI on Linux terminals.
  • Avoid using PowerShell-specific formatting for CLI commands unless necessary, and clarify when commands are platform-agnostic.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/publisher-artifact-store-resiliency.md ...service-manager/publisher-artifact-store-resiliency.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell and Azure CLI examples, with no mention of Linux shell equivalents or cross-platform command syntax. All code snippets and operational instructions use PowerShell or Azure CLI, which are more commonly associated with Windows environments. There is no guidance for Linux users, such as bash commands, nor any mention of Linux-specific considerations or alternative tooling.
Recommendations
  • Provide equivalent bash or shell script examples for Linux users alongside PowerShell/Azure CLI commands.
  • Explicitly state that Azure CLI is cross-platform and show usage in both Windows (PowerShell) and Linux (bash) environments.
  • Include notes or sections addressing Linux-specific considerations, such as authentication, environment setup, and file path differences.
  • Avoid assuming PowerShell as the default shell; present examples in both PowerShell and bash where relevant.
  • Mention that Azure CLI can be installed and used on Linux, and provide installation instructions or links for Linux users.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the 'Set environment variables' section, where Windows PowerShell is mentioned first and given as the primary example for setting environment variables. There is no explicit Linux or macOS example for referencing environment variables, and the PowerShell syntax is presented before the Bash syntax. Other sections use cross-platform Azure CLI commands, but the initial environment variable setup may confuse Linux/macOS users due to lack of parity.
Recommendations
  • Provide both Windows (PowerShell) and Linux/macOS (Bash) examples side-by-side when setting environment variables and referencing them.
  • Explicitly mention that Bash syntax applies to Linux/macOS and PowerShell syntax applies to Windows, to avoid confusion.
  • Where referencing environment variables is shown, add the Bash/Linux/macOS equivalent (e.g., $resourceGroup or ${resourceGroup}) alongside the PowerShell example.
  • Review other sections for similar patterns and ensure examples are platform-neutral or include both Windows and Linux/macOS variants where appropriate.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/resource-cleanup-management.md ...perator-service-manager/resource-cleanup-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for Azure Resource Graph queries, omitting equivalent Linux-friendly shell (bash/az CLI) examples. The use of PowerShell syntax (e.g., | %{}) in Azure CLI command snippets further reinforces this bias, as it is not portable to Linux environments. While crontab is mentioned for scheduling, actual command examples and automation patterns are Windows-centric.
Recommendations
  • Provide bash and az CLI examples for all resource queries, especially for ARG queries currently shown only in PowerShell.
  • Replace or supplement PowerShell pipeline syntax (| %{ ... }) with bash equivalents (e.g., xargs) in Azure CLI command snippets.
  • Explicitly mention and demonstrate Linux automation patterns (e.g., using cron, shell scripts) alongside Windows/PowerShell approaches.
  • Ensure all command-line examples are cross-platform, or clearly label them as Windows/PowerShell-specific and provide Linux alternatives.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/concepts-about-azure-operator-service-manager-cli.md ...r/concepts-about-azure-operator-service-manager-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-formatted command examples and output, which are typically associated with Windows environments. There are no explicit Linux or macOS shell (bash/zsh) examples, nor is there mention of platform-specific considerations or parity. This may give the impression that the CLI extension is primarily intended for Windows users, potentially alienating Linux or cross-platform users.
Recommendations
  • Provide command examples in both PowerShell (Windows) and bash/zsh (Linux/macOS) formats, or use a neutral format where possible.
  • Clarify that the Azure CLI and its extensions are cross-platform, and note any platform-specific differences if they exist.
  • Include example outputs from Linux/macOS terminals, or use generic output formatting.
  • Explicitly state that the instructions apply to all supported platforms, and provide troubleshooting tips for common issues on Linux/macOS.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias in the 'Set environment variables' section by presenting the Windows PowerShell method first and exclusively, while the Bash/Linux method is given afterward. The PowerShell example is explicitly called out, but there is no mention of Linux shells or their usage context. Additionally, there are no examples for macOS or Linux-specific nuances elsewhere, and portal instructions do not clarify cross-platform differences.
Recommendations
  • Present environment variable examples for Bash/Linux/macOS before or alongside PowerShell, with clear headings for each platform.
  • Explicitly mention that Bash examples work on Linux and macOS, and PowerShell examples are for Windows.
  • Add a note clarifying which shell/environment each example is intended for.
  • Where Azure Portal steps are given, clarify that the portal is cross-platform and does not depend on OS.
  • Consider including CLI commands for role assignments, not just portal instructions, to improve parity for Linux users.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-cancel-service-deployments.md ...r-service-manager/how-to-cancel-service-deployments.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by exclusively providing Azure CLI examples in PowerShell syntax, without Bash or Linux shell equivalents. All command-line examples use PowerShell formatting (e.g., curly braces for parameters) and do not mention or show Linux/Bash usage. There is no explicit reference to Linux tools, nor are Linux-specific instructions or examples provided.
Recommendations
  • Provide Azure CLI examples in both PowerShell (Windows) and Bash (Linux/macOS) syntax, clearly labeling each.
  • Use generic parameter notation (e.g., <resourceGroup>) or provide both curly brace and angle bracket formats to avoid Windows-centric conventions.
  • Explicitly mention that Azure CLI is cross-platform and can be used from Bash, PowerShell, or other shells.
  • Include a note or section for Linux/macOS users, highlighting any differences in command usage or environment setup.
  • Avoid using only PowerShell code blocks; use 'bash' and 'powershell' code blocks where appropriate.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/publisher-artifact-store-resiliency.md ...service-manager/publisher-artifact-store-resiliency.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing PowerShell and Azure CLI examples, with no Linux shell (bash) equivalents. All code snippets and command-line instructions use PowerShell syntax, and there is no mention of Linux-specific tools, patterns, or considerations. The FAQ and configuration sections assume a Windows-centric workflow, potentially excluding Linux users or those using bash/zsh shells.
Recommendations
  • Provide equivalent bash (Linux shell) examples for all PowerShell and Azure CLI commands.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands in bash syntax.
  • Include notes or sections addressing Linux-specific considerations, such as authentication, environment setup, and file path differences.
  • Avoid using PowerShell-specific syntax (e.g., comments with //) in JSON examples; use standard JSON comments or provide context in documentation text.
  • Ensure that documentation is platform-neutral by alternating or combining Windows and Linux examples, rather than defaulting to Windows-first presentation.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/resource-cleanup-management.md ...perator-service-manager/resource-cleanup-management.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through the exclusive use of PowerShell for Azure Resource Graph (ARG) query examples, without providing equivalent Bash or Linux shell examples. Additionally, the use of PowerShell syntax (e.g., | %{ ... }) in Azure CLI command pipelines suggests a Windows-first approach, which may not work as written on Linux or macOS shells. There is no mention of Linux-specific tools or patterns, and scheduling examples reference crontab but do not show Linux-native command-line usage.
Recommendations
  • Provide Bash/sh examples alongside PowerShell for ARG queries, using az graph query or equivalent.
  • Replace PowerShell pipeline syntax (| %{ ... }) with Bash-compatible syntax (e.g., xargs or while read loops) for Azure CLI commands.
  • Explicitly mention cross-platform compatibility for all CLI commands and queries.
  • Include notes or examples for Linux/macOS users, especially for command scheduling and scripting.
  • Where possible, use generic Azure CLI syntax that works on all platforms, or provide both Windows and Linux variants.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-containerized-network-function-cli.md ...r/how-to-onboard-containerized-network-function-cli.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. While the main workflow is cross-platform (using Azure CLI, Docker, and Helm), there are several instances where Windows is mentioned first or exclusively, and some guidance is tailored to Windows users. For example, the note 'If you are using Windows, you must have Docker Desktop running during the publish step' singles out Windows, but does not mention the equivalent for Linux (e.g., Docker Engine). File path examples use Linux-style slashes but explicitly instruct Windows users to use them, rather than showing both formats. There are no explicit Linux command-line examples or troubleshooting notes for Linux users, and the only OS-specific tool mentioned is Docker Desktop (Windows/macOS), with no mention of Linux Docker installation nuances.
Recommendations
  • Provide explicit Linux examples or notes where Windows-specific instructions are given (e.g., mention that on Linux, Docker Engine must be running, and provide troubleshooting tips for common Linux Docker issues).
  • When referencing file paths, show both Windows and Linux formats, or clarify that the CLI expects Linux-style slashes on all platforms.
  • Avoid mentioning Windows or macOS first; instead, use neutral phrasing or list Linux first to balance representation.
  • Include a section or note on installing and running Docker on Linux, similar to the note about Docker Desktop for Windows.
  • Where OS-specific behavior is relevant (e.g., authentication, permissions), provide parity in documentation for both Windows and Linux users.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-containerized-network-function-cli.md ...r/how-to-onboard-containerized-network-function-cli.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation displays some Windows bias, most notably by mentioning Windows-specific tools (Docker Desktop) and conditions ("If you are using Windows, you must have Docker Desktop running") without providing equivalent Linux guidance. In addition, when discussing file paths, it instructs users to use Linux-style slashes even on Windows, but does not provide explicit Linux path examples or clarify Linux-specific behaviors. The only explicit OS-specific note is for Windows (Docker Desktop), and there is no mention of Linux-specific requirements or troubleshooting. The order of OS mentions in the note about running Azure CLI in Docker also lists Windows before macOS and Linux.
Recommendations
  • Add explicit Linux (and macOS) instructions for Docker installation and requirements, e.g., mention that on Linux, Docker Engine or Podman should be running, and provide troubleshooting tips for common Linux issues.
  • When referencing Docker Desktop for Windows, also mention the equivalent for Linux (Docker Engine, Podman, etc.), and clarify that Docker Desktop is not required on Linux.
  • Provide Linux-specific file path examples and clarify any differences in file system handling or permissions that may affect Linux users.
  • Ensure that when listing OS options, Linux is mentioned first or at least equally, and provide parity in examples and troubleshooting steps.
  • Add a section or notes for Linux users regarding prerequisites, permissions (e.g., needing to use sudo for Docker), and any common pitfalls.
GitHub Create Pull Request
Operator Service Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-publish-virtualized-network-function-definition.md ...kstart-publish-virtualized-network-function-definition.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows Reference Linux Slash Guidance Windows Path Escape Note
Summary
The documentation is generally cross-platform and uses Azure CLI commands, which are available on both Windows and Linux. However, there are minor references to Windows-specific behaviors, such as instructing users to use Linux-style slashes (/) for file paths even on Windows, and noting that on Windows, backslashes must be escaped in file paths. No PowerShell or Windows-only tools are used, and Linux is not omitted from any examples, but the guidance assumes users may be on Windows and need extra instructions.
Recommendations
  • Provide explicit Linux and Windows examples for file paths, showing both formats where relevant.
  • Clarify that Azure CLI commands work identically on both Windows and Linux, and provide any OS-specific caveats if they exist.
  • Where path separators or escaping are discussed, include a short table or note showing both Windows and Linux conventions.
  • Consider adding a brief section in prerequisites about supported OS environments for the Azure CLI extension, with links to installation instructions for both Windows and Linux.
GitHub Create Pull Request
Operator Service Manager Publisher artifact store resiliency with Azure Operator Service Manager ...service-manager/publisher-artifact-store-resiliency.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides all command-line examples using Powershell syntax and references Azure CLI commands without specifying platform parity. There are no Linux/macOS-specific shell examples (e.g., Bash), and Powershell-style code blocks are used exclusively. This may create friction for Linux/macOS users unfamiliar with Powershell or Windows-centric command patterns.
Recommendations
  • Add equivalent Bash/Linux shell examples for all Powershell commands, especially for Azure CLI usage.
  • Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or CMD, and provide sample invocations for each.
  • Avoid using Powershell-specific code block annotations unless the command is truly Powershell-only.
  • Explicitly mention platform compatibility where relevant, and provide guidance for Linux/macOS users.
GitHub Create Pull Request
Operator Service Manager About the Azure Operator Service Manager CLI extension ...r/concepts-about-azure-operator-service-manager-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax for all CLI examples, implicitly prioritizing Windows users. There are no bash or Linux/macOS shell examples, nor any mention of platform-specific considerations. This may create friction for Linux and macOS users unfamiliar with PowerShell conventions.
Recommendations
  • Provide bash/zsh equivalents for all CLI commands alongside PowerShell examples.
  • Clarify that the Azure CLI commands work cross-platform and specify any OS-specific differences if relevant.
  • Use generic CLI blocks (without PowerShell or bash annotation) when the command is identical across platforms.
  • Include a note about shell compatibility for the Azure CLI and extension.
GitHub Create Pull Request
Operator Service Manager Interrupt a Service Deployment with Azure Operator Service Manager ...r-service-manager/how-to-cancel-service-deployments.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides command-line examples exclusively in PowerShell syntax, which is primarily used on Windows. There are no Bash or Linux/macOS shell examples, and the PowerShell-based Azure CLI commands are shown without clarification that they work cross-platform. This may cause confusion or friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI examples in Bash syntax alongside PowerShell, clarifying cross-platform compatibility.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and that the examples are not Windows-specific.
  • Avoid using PowerShell-specific formatting for CLI commands; use generic shell syntax where possible.
  • Add notes or examples for using the Azure portal or REST API from non-Windows environments.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →