Operator Service Manager

45
Total Pages
37
Linux-Friendly Pages
8
Pages with Bias
17.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (11)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation demonstrates a 'windows_first' bias in the section on setting environment variables, where Windows PowerShell syntax is presented before the Bash/Linux equivalent. However, the remainder of the documentation uses cross-platform Azure CLI and Bash commands, and does not otherwise prioritize or exclusively reference Windows tools or patterns.
Recommendations:
  • Present Linux/Bash environment variable examples before or alongside Windows PowerShell examples, as Linux is the primary platform for containerized workloads.
  • Explicitly state that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows (with WSL or native Bash).
  • Wherever platform-specific instructions are needed, provide both Windows and Linux/macOS variants in parallel, or link to platform-specific setup guides.
  • Consider removing the PowerShell example unless there is a clear user need, or move it to an appendix or a 'Windows users' note.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-prerequisites.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation subtly prioritizes Windows and macOS users by mentioning them explicitly in the note about running Azure CLI in Docker, while Linux users are not directly addressed. There are no Linux-specific instructions or examples, and the guidance assumes familiarity with Windows/macOS environments. No Linux command-line or package manager examples are provided for installing tools like Docker or Helm.
Recommendations:
  • Explicitly mention Linux as a supported platform alongside Windows and macOS in all relevant sections.
  • Provide Linux-specific installation instructions or command examples for Docker and Helm (e.g., using apt, yum, or snap).
  • Include a note or section on running Azure CLI in Docker on Linux, not just for Windows/macOS.
  • Ensure parity in troubleshooting tips or environment setup for Linux users.
  • Add example commands for common Linux distributions where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-publish-containerized-network-function-definition.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Note Missing Linux Example
Summary:
The documentation is generally cross-platform, using Azure CLI commands and referencing Docker and Helm, which are available on both Windows and Linux. However, there is a Windows-specific note stating that Docker Desktop must be running during the publish step if you are using Windows, but there is no equivalent note or guidance for Linux users (e.g., Docker daemon requirements or troubleshooting). No explicit Linux or macOS examples, troubleshooting, or environment-specific notes are provided, which could leave Linux users uncertain about platform-specific requirements.
Recommendations:
  • Add a note for Linux users clarifying any requirements for Docker (e.g., Docker daemon must be running, or how to check Docker status).
  • Include troubleshooting tips or common issues for both Windows and Linux environments.
  • Explicitly state that all commands are cross-platform and provide any necessary platform-specific instructions (such as file path conventions or Docker setup differences).
  • If mentioning Docker Desktop for Windows, mention the equivalent (e.g., Docker Engine) for Linux.
  • Consider adding a short section or callout confirming that the workflow has been tested on both Windows and Linux, and highlight any differences if they exist.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-containerized-network-function-cli.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-azure-resource-manager-resources-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation generally avoids explicit Windows bias in command examples, as all CLI commands are cross-platform and there are no PowerShell or Windows-specific tools shown. However, there is subtle bias in the order and completeness of platform guidance: Windows and macOS are mentioned first when discussing Dockerized Azure CLI usage, and there is a lack of explicit Linux-specific instructions or examples throughout. File path guidance does mention using Linux-style slashes even on Windows, but no Linux terminal or environment is ever directly referenced or shown.
Recommendations:
  • Explicitly mention Linux as a supported platform in all relevant sections, especially where Windows and macOS are called out.
  • Provide Linux-specific examples or notes, such as using native package managers (apt, yum, snap) for installing Azure CLI, Helm, and Docker.
  • When discussing running Azure CLI in Docker, include Linux as a primary example, not just Windows/macOS.
  • Add example commands or screenshots from a Linux terminal where appropriate.
  • Ensure parity in troubleshooting and environment setup instructions for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-containerized-network-function-cli.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-delete-operator-resources.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively describes resource deletion using the Azure portal UI, which is platform-agnostic but implicitly assumes a GUI workflow common to Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux or cross-platform automation tools. This can disadvantage Linux users or those preferring CLI-based workflows, as well as those automating tasks in non-Windows environments.
Recommendations:
  • Add equivalent instructions for deleting resources using the Azure CLI, which is cross-platform and widely used on Linux and macOS as well as Windows.
  • Include sample scripts or commands for resource deletion using Bash and/or PowerShell, highlighting both where appropriate.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide parity for users who prefer or require command-line or automated approaches.
  • Where screenshots are used, consider including text-based alternatives or references to CLI documentation for accessibility and platform neutrality.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-create-user-assigned-managed-identity.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows-first bias by exclusively providing instructions and screenshots for the Azure Portal (a web GUI) and omitting any command-line examples for Linux or cross-platform CLI tools such as Azure CLI or Azure PowerShell. There are no Linux shell or cross-platform automation examples for creating or assigning managed identities, nor are there references to Linux-specific workflows. The only automation example provided is in Bicep, which is cross-platform, but there are no CLI-based instructions for users who prefer or require command-line interfaces, especially on Linux.
Recommendations:
  • Add Azure CLI examples for all major operations (creating UAMI, assigning roles, etc.), as Azure CLI is cross-platform and widely used on Linux.
  • Include PowerShell examples only if parity with Azure CLI is maintained, and clearly indicate which examples are cross-platform.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using the Azure CLI.
  • Provide at least one end-to-end workflow using only CLI commands, suitable for Linux users.
  • If screenshots are included, consider also providing terminal output or command snippets to ensure accessibility for users not using the Azure Portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-publish-virtualized-network-function-definition.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-publish-containerized-network-function-definition.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page is largely cross-platform in its use of Azure CLI and Docker, but it contains a Windows-first bias in its notes and lacks explicit Linux/macOS instructions or examples. Specifically, it mentions 'Docker Desktop' only for Windows users and does not clarify equivalent requirements or steps for Linux/macOS users. There are no PowerShell-specific commands, but the absence of Linux/macOS-specific notes or troubleshooting tips may leave non-Windows users underserved.
Recommendations:
  • Add explicit notes for Linux/macOS users regarding Docker requirements (e.g., 'Ensure Docker Engine is running' or 'Ensure you have Docker installed and running on your system').
  • Where the documentation says 'If you are using Windows, you must have Docker Desktop running during the publish step,' add a parallel note for Linux/macOS users (e.g., 'If you are using Linux or macOS, ensure the Docker daemon is running').
  • Include example commands or troubleshooting tips that are relevant to Linux/macOS users, such as verifying Docker installation or permissions.
  • Mention file path conventions for both Windows and Linux/macOS, especially when discussing Helm chart paths, to avoid confusion.
  • Consider including a table or section summarizing platform-specific prerequisites or steps to ensure parity and clarity for all users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-operator.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation demonstrates a mild 'windows_first' bias in the section on setting environment variables. The PowerShell (Windows) example for setting environment variables is presented before the Bash (Linux/macOS) example, and is specifically called out in the text. However, the rest of the documentation uses Bash syntax and Azure CLI commands, which are cross-platform and suitable for both Linux and Windows (with WSL or Azure CLI installed). There are no exclusive Windows tools or missing Linux examples elsewhere.
Recommendations:
  • Present Linux/Bash and Windows/PowerShell environment variable examples side by side, or explicitly note that both platforms are supported.
  • Avoid language that implies Windows is the default or primary platform (e.g., 'in Windows PowerShell, you would...'), and instead provide parallel instructions for both environments.
  • Consider adding a short section or table at the start that shows how to set environment variables in both Bash and PowerShell, making it clear that either can be used throughout.
  • Ensure that any future examples or troubleshooting steps include both Linux and Windows variants if platform-specific commands are required.