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 26-48 of 48 flagged pages
Operator Service Manager
How to create, assign, and use a User Assigned Managed Identity in Azure Operator Service Manager
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for the Azure Portal (GUI), which is most commonly accessed from Windows environments. There are no CLI examples (such as Azure CLI, Bash, or PowerShell) for creating, assigning, or managing User Assigned Managed Identities, nor are there any Linux/macOS-specific instructions or screenshots. The only automation example provided is via Bicep, which is platform-neutral but assumes prior knowledge and setup. The absence of Azure CLI or cross-platform scripting examples creates friction for Linux/macOS users who may prefer or require command-line workflows.
Recommendations
- Add Azure CLI examples for all major operations (creating UAMI, assigning roles, updating templates), as Azure CLI is cross-platform.
- Include PowerShell examples only if Azure CLI is also present, and clearly indicate platform compatibility.
- Provide guidance for performing these tasks via command line on Linux/macOS, including installation prerequisites if needed.
- Where screenshots are used, clarify that the Azure Portal is web-based and accessible from any OS, or balance with CLI/script examples.
- Explicitly mention that Bicep and ARM templates can be used from any platform, and provide links to setup guides for Linux/macOS.
Create Pull Request
Operator Service Manager
Publisher resource clean-up management with Azure Operator Service Manager
...perator-service-manager/resource-cleanup-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. All query examples for Azure Resource Graph (ARG) are provided only in PowerShell syntax, with no equivalent Bash or cross-platform Azure CLI examples. The use of PowerShell pipelines (| %{ ... }) in Azure CLI command snippets further reinforces a Windows-centric approach, as this syntax is not natively supported in Bash or Linux shells. There is mention of scheduling with crontab, but no Linux/macOS-specific command examples are given for ARG queries or artifact deletion.
Recommendations
- Provide ARG query examples using Azure CLI and Bash syntax alongside PowerShell.
- Replace PowerShell pipeline constructs in Azure CLI examples with Bash-compatible alternatives (e.g., xargs).
- Explicitly mention Linux/macOS usage patterns for all command-line operations.
- Add notes or sections clarifying cross-platform compatibility and differences.
Operator Service Manager
About the Azure Operator Service Manager CLI extension
...r/concepts-about-azure-operator-service-manager-cli.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses PowerShell syntax for all CLI command examples, implicitly favoring Windows users. There are no bash or Linux/macOS shell examples, nor any mention of platform-specific considerations for Linux or macOS users. This creates friction for non-Windows users, who may be unsure if commands or output formatting differ on their platforms.
Recommendations
- Provide command examples using bash syntax alongside PowerShell, e.g., use $ for bash prompts.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and note any platform-specific differences if they exist.
- Show sample output using a generic shell prompt or clarify that output formatting may differ by platform.
- Add a section on prerequisites for Linux/macOS users, such as installation steps for Azure CLI on those platforms.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through the exclusive use of PowerShell syntax for Azure CLI commands. All command-line examples are shown in PowerShell format, with no Bash or Linux shell equivalents provided. This may create friction for Linux/macOS users who are more familiar with Bash or other shells, especially since Azure CLI is cross-platform and commonly used in Bash environments.
Recommendations
- Provide Azure CLI examples in Bash syntax alongside PowerShell, using standard Bash variable notation (e.g., $RESOURCE_GROUP instead of {resourceGroup}).
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and clarify any platform-specific differences if present.
- Avoid using PowerShell-specific syntax unless the command is truly Windows-only; prefer generic CLI syntax for cross-platform parity.
- Include screenshots or instructions for using the Azure portal on non-Windows platforms if relevant.
Operator Service Manager
Publisher artifact store resiliency with Azure Operator Service Manager
...service-manager/publisher-artifact-store-resiliency.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples and resource configuration snippets exclusively using Powershell syntax and Azure CLI commands, without offering equivalent Linux/macOS shell examples or clarifying cross-platform compatibility. Powershell-style code blocks are shown by default, and there is no mention of Linux-specific tools, shell commands, or alternative workflows for non-Windows users.
Recommendations
- Include equivalent Bash shell examples for all command-line operations, especially for Azure CLI commands (e.g., az acr replication list).
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals, not just Powershell.
- Avoid labeling code blocks as Powershell unless the syntax is truly Powershell-specific; use 'azurecli' or 'bash' where appropriate.
- Explicitly mention Linux/macOS compatibility in relevant sections.
- Provide guidance or links for installing and using Azure CLI on Linux/macOS.
Operator Service Manager
Publisher resource clean-up management with Azure Operator Service Manager
...perator-service-manager/resource-cleanup-management.md
Medium Priority
View Details →
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 and using PowerShell-specific syntax in command snippets. There are no equivalent examples for Linux/macOS users (e.g., Bash or Azure CLI with shell pipes), and PowerShell is presented as the default interface for resource queries. While Azure CLI is mentioned for artifact purging, the example uses a Windows-centric pipeline operator (%{ ... }) without a Bash alternative.
Recommendations
- Provide equivalent Azure Resource Graph query examples using Bash/Azure CLI for Linux/macOS users.
- When showing command pipelines, include both PowerShell and Bash versions side-by-side.
- Clarify that PowerShell examples are for Windows and provide explicit instructions for Linux/macOS environments.
- Avoid using Windows-specific pipeline operators (e.g., %{ ... }) without showing the Bash equivalent (e.g., xargs or while read loops).
Operator Service Manager
How to create, assign, and use a User Assigned Managed Identity in Azure Operator Service Manager
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for assigning roles and managed identities using the Azure Portal, which is a GUI-centric workflow most familiar to Windows users. There are no CLI examples (such as Azure CLI or PowerShell), nor are Linux-specific workflows or screenshots provided. The portal instructions are presented first and in detail, while the only automation example is via Bicep (which is cross-platform but less commonly used than CLI tools). There are no examples using Azure CLI, which is the most common tool for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI examples for all portal-based steps, including creating UAMI, assigning roles, and permissions.
- Explicitly mention that all steps can be performed using Azure CLI or PowerShell, and provide links or code blocks for those workflows.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid references to Windows-only tools or UI elements).
- Consider providing Bash script snippets for automation, especially for Linux/macOS users.
- Clarify that Bicep is cross-platform and can be used on Linux/macOS, and provide installation instructions for those platforms if needed.
Operator Service Manager
Prerequisites for Operator and Virtualized Network Function (VNF)
...er/quickstart-virtualized-network-function-operator.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation relies heavily on Azure Portal GUI instructions, which are platform-agnostic but implicitly favor Windows due to the prevalence of Windows users and screenshots. There are no explicit Linux/macOS command-line alternatives for tasks like retrieving resource IDs or assigning roles, which could be completed using Azure CLI or PowerShell. All command-line examples use Azure CLI, which is cross-platform, but GUI steps and screenshots may create friction for Linux/macOS users who prefer or require CLI-only workflows.
Recommendations
- Provide Azure CLI commands for locating resource IDs (e.g., using 'az identity show' and 'az network vnet show') as alternatives to Azure Portal navigation.
- Include CLI-based instructions for role assignments (e.g., 'az role assignment create') alongside GUI steps.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-specific browser or OS elements).
- Add explicit notes that all CLI commands work on Linux/macOS, and encourage CLI usage for automation and parity.
Operator Service Manager
How to create, assign, and use a User Assigned Managed Identity in Azure Operator Service Manager
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for using the Azure Portal (a GUI tool most commonly accessed from Windows environments) and omitting any CLI-based examples (such as Azure CLI or PowerShell). There are no Linux-specific instructions or examples, nor is there mention of using cross-platform tools for role assignment or managed identity operations. The only automation example provided is via Bicep, which is cross-platform, but the interactive steps are portal-centric and lack parity for Linux users.
Recommendations
- Add equivalent instructions for assigning roles and managed identities using Azure CLI and/or PowerShell, with explicit examples for both Windows and Linux environments.
- Include screenshots or terminal output for CLI-based workflows to complement portal-based instructions.
- Clearly indicate that all operations can be performed from Linux, macOS, or Windows using CLI tools, and provide guidance for installing and using these tools.
- Where possible, mention automation options (e.g., ARM templates, Terraform) that are platform-agnostic.
- Ensure that portal instructions are not presented as the only or primary method, but as one of several options.
Operator Service Manager
How to create, assign, and use a User Assigned Managed Identity in Azure Operator Service Manager
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and screenshots for the Azure Portal (a GUI tool most commonly used on Windows) and omitting any CLI-based examples (such as Azure CLI, Bash, or PowerShell). There are no Linux-specific instructions or parity for command-line workflows, and the only automation example is via Bicep (which is cross-platform but not a direct Linux shell or CLI example). The documentation does not mention or demonstrate how to perform these tasks using Linux tools or workflows.
Recommendations
- Add equivalent Azure CLI examples for all portal-based steps, showing how to create, assign, and use a User Assigned Managed Identity via command line.
- Include Bash shell scripts or instructions for Linux users to perform identity and role assignments.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and provide parity in examples.
- Where screenshots are used, supplement with CLI output or code blocks to ensure accessibility for non-Windows users.
- Consider adding PowerShell examples only if Azure CLI and Bash examples are also present, and order examples so that CLI/Bash comes before or alongside portal/PowerShell instructions.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates Windows bias in the 'Set environment variables' section, where Windows PowerShell syntax is presented first and in detail, while Bash/Linux syntax is presented afterwards. The only explicit mention of an OS-specific tool is PowerShell; there is no mention of Linux-specific shells or tools. No Linux-specific instructions or parity notes are provided for other platform-specific steps, such as Azure Portal navigation or CLI usage.
Recommendations
- Present Linux/Bash examples before or alongside Windows/PowerShell examples to avoid ordering bias.
- Explicitly mention that both Bash (Linux/macOS) and PowerShell (Windows) are supported for CLI commands, and clarify any differences in syntax or environment variable usage.
- Add a note or section for Linux/macOS users, including common shell usage patterns and troubleshooting tips.
- Where possible, provide parity for any OS-specific instructions, such as referencing Linux terminal or macOS Terminal for environment variable setting.
- Review all screenshots and portal navigation instructions to ensure they are not Windows-centric, or add clarifying notes for Linux/macOS users.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-create-user-assigned-managed-identity.md
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure Portal (GUI) instructions for role assignment and managed identity operations, which are most commonly accessed from Windows environments. There are no CLI-based examples (such as Azure CLI, Bash, or PowerShell) for these tasks, and no Linux-specific guidance is provided. The only automation example is via Bicep, which is cross-platform, but the step-by-step instructions for manual operations are portal-centric and lack parity for Linux users who may prefer command-line tools.
Recommendations
- Add Azure CLI examples for creating, assigning, and managing User Assigned Managed Identities and roles, ensuring commands are compatible with Bash and PowerShell.
- Include PowerShell examples for users who prefer scripting on Windows.
- Provide explicit instructions for performing all key operations (role assignment, managed identity creation, etc.) via CLI, not just via the portal.
- Clarify that all operations can be performed from Linux, macOS, or Windows environments using Azure CLI or Bicep.
- Add a section comparing portal and CLI approaches, highlighting cross-platform options.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-create-user-assigned-managed-identity.md
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure Portal (GUI) instructions for role assignment and managed identity operations, which are most commonly accessed from Windows environments. There are no CLI-based examples (such as Azure CLI, Bash, or PowerShell), nor any Linux-specific guidance. The only automation example is via Bicep, which is platform-neutral, but the step-by-step instructions assume use of the Azure Portal, a pattern more familiar to Windows users. No Linux terminal or cross-platform command-line alternatives are presented.
Recommendations
- Add Azure CLI examples for all major operations (creating UAMI, assigning roles, etc.), with explicit Bash syntax.
- Include PowerShell examples if desired, but always present CLI/Bash examples first or alongside.
- Clarify that all operations can be performed from Linux, macOS, or Windows using the Azure CLI.
- Reference cross-platform tools and workflows, such as VS Code with Azure extensions, or GitHub Actions for automation.
- Explicitly mention platform neutrality where possible, and avoid implying that the Azure Portal is the only or preferred method.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-containerized-network-function-prerequisites.md
...uickstart-containerized-network-function-prerequisites.md
Medium Priority
View Details →
Detected Bias Types
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.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-publish-containerized-network-function-definition.md
...tart-publish-containerized-network-function-definition.md
Medium Priority
View Details →
Detected Bias Types
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.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-azure-resource-manager-resources-cli.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-onboard-azure-resource-manager-resources-cli.md
Medium Priority
View Details →
Detected Bias Types
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.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-delete-operator-resources.md
...or-service-manager/how-to-delete-operator-resources.md
Medium Priority
View Details →
Detected Bias Types
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.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/how-to-create-user-assigned-managed-identity.md
...anager/how-to-create-user-assigned-managed-identity.md
Medium Priority
View Details →
Detected Bias Types
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.
Operator Service Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/operator-service-manager/quickstart-publish-containerized-network-function-definition.md
...tart-publish-containerized-network-function-definition.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows a mild Windows bias in the section on setting environment variables: it presents the Windows PowerShell example first and does not provide a Linux/macOS equivalent for referencing environment variables (e.g., $resourceGroup vs $env:ARC_RG). The rest of the guide uses Azure CLI and Bash-style syntax, which is cross-platform, but the initial environment variable reference may confuse Linux/macOS users.
Recommendations
- Provide both Windows PowerShell and Linux/macOS Bash examples for setting and referencing environment variables, and present them side-by-side or clearly labeled.
- When referencing environment variables, show both $env:VAR (PowerShell) and $VAR (Bash) usages.
- Consider presenting Bash/Linux examples first or equally with Windows to avoid implicit prioritization.
- Add a note clarifying that Azure CLI commands and Bash syntax work on Windows (with WSL or Git Bash), macOS, and Linux.
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
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation shows a mild Windows bias in the 'Set environment variables' section, where the PowerShell (Windows) method is presented first and explicitly, while the Linux/macOS (bash) method is shown second and without introductory explanation. The PowerShell example is also more prominent, and there is no mention of macOS. The rest of the documentation uses Azure CLI and bash syntax, which is cross-platform, but the initial environment variable setup may cause confusion or friction for Linux/macOS users.
Recommendations
- Present environment variable examples for Windows (PowerShell), Linux (bash), and macOS (zsh/bash) side by side or in parallel sections.
- Explicitly state that the bash examples work on both Linux and macOS.
- Avoid presenting Windows/PowerShell examples first by default; consider alternating or using tabs for OS-specific instructions.
- Add a short note clarifying how to set environment variables on each supported OS.
- Where possible, provide parity in screenshots or GUI steps for Linux/macOS users if relevant (e.g., Azure Portal steps are OS-agnostic, but CLI/terminal screenshots could reflect both environments).
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
Low Priority
View Details →
Detected Bias Types
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.
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
Low Priority
View Details →
Detected Bias Types
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.