Private 5G Core

85
Total Pages
76
Linux-Friendly Pages
9
Pages with Bias
10.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (13)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/region-move-private-mobile-network-resources.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by providing a PowerShell (az CLI) example for deploying the ARM template but omitting equivalent Linux/macOS shell (bash) examples. The only command-line deployment example is shown using PowerShell syntax, and there is no mention of Linux or cross-platform CLI usage, nor are there instructions for using bash or other common Linux tools. The Azure portal is referenced, which is cross-platform, but the CLI example is Windows-centric.
Recommendations:
  • Provide both PowerShell and bash (Linux/macOS) examples for CLI commands, especially for az deployment group create.
  • Explicitly mention that the Azure CLI can be used on Windows, Linux, and macOS, and show syntax for both environments where it differs.
  • Consider using neutral CLI syntax (e.g., $HOME or ~ for home directory, forward slashes in paths) or clarify any OS-specific differences.
  • Add a note or section for Linux/macOS users, ensuring parity in instructions and examples.
  • Where possible, use 'az' CLI commands in a way that is copy-paste friendly for all platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/enable-azure-active-directory.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a Windows-first and PowerShell-heavy bias, particularly in the 'Apply Kubernetes Secret Objects' section, where users are instructed to use Azure Cloud Shell and specifically select PowerShell. No equivalent instructions or examples are provided for Linux users or those preferring Bash, despite earlier mentioning Bash for base64 encoding. This may cause confusion or additional effort for Linux users.
Recommendations:
  • Provide parallel instructions for both PowerShell and Bash environments when using Azure Cloud Shell, including how to select Bash and run the same kubectl commands.
  • Avoid assuming PowerShell as the default shell; explicitly state that users can use either Bash or PowerShell, and provide command examples for both where differences exist.
  • Where possible, use shell-agnostic commands (e.g., kubectl) and clarify any differences in syntax or environment setup between Windows/PowerShell and Linux/Bash.
  • Ensure that all steps, especially those involving command-line operations, are demonstrated for both Windows and Linux users to improve parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/whats-new.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a bias toward Windows environments by referencing PowerShell for site creation and management, and by mentioning tools and workflows (such as Power BI) that are primarily associated with Windows. There are no Linux or cross-platform CLI examples, and Linux-native tools or workflows are not discussed. This may make it harder for Linux users to follow or replicate the instructions.
Recommendations:
  • Provide equivalent CLI examples using Azure CLI (az), Bash, or other cross-platform tools alongside PowerShell examples.
  • Explicitly mention Linux support and provide instructions or scripts that work on Linux systems.
  • Reference cross-platform tools (e.g., Azure CLI, REST API, or open-source analytics tools) in addition to or instead of Windows-centric tools like PowerShell and Power BI.
  • Ensure that all automation and scripting guidance is available in both PowerShell and Bash (or at least Azure CLI) formats.
  • Add a section or note clarifying platform compatibility for all tools and scripts mentioned.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/complete-private-mobile-network-prerequisites.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation exhibits a Windows bias by specifying a Windows PC and Windows Administrator account as prerequisites, listing PowerShell as a required tool, and referencing Windows-specific technologies (e.g., WinRM, Windows Server Failover Clustering). There are no Linux equivalents or alternatives mentioned for these requirements, and no Linux-specific instructions or examples are provided. The documentation assumes a Windows environment throughout, even though Azure CLI and kubectl are cross-platform tools.
Recommendations:
  • Update the prerequisites to include support for Linux and macOS platforms, clarifying that Azure CLI and kubectl are cross-platform.
  • Provide Linux (and optionally macOS) equivalents for all steps, including installation instructions for required tools (Azure CLI, kubectl, PowerShell) on those platforms.
  • Where PowerShell is required, clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide usage examples.
  • For steps referencing Windows-specific technologies (e.g., WinRM, Windows Server Failover Clustering), explain if/how these steps can be performed from Linux/macOS, or provide alternative approaches.
  • Avoid language that assumes the user is on Windows (e.g., 'A Windows PC with internet access'), and instead use inclusive phrasing such as 'A computer with internet access (Windows, Linux, or macOS)'.
  • Add explicit notes or callouts wherever a step is only supported or tested on Windows, and provide a roadmap or workaround for users on other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/set-up-kubectl-access.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation is heavily biased toward Windows environments, requiring the use of PowerShell, WinRM, and Windows-specific tools for accessing the minishell and managing kubeconfig files. There are no instructions or examples for performing these tasks from Linux or macOS systems, and Windows is assumed as the default and only supported platform for these procedures.
Recommendations:
  • Provide equivalent instructions for Linux and macOS users, including how to access the minishell or perform similar operations using SSH or other cross-platform tools.
  • Offer shell (bash) command examples alongside PowerShell, and clarify any platform-specific prerequisites.
  • Document any platform limitations explicitly, and if Windows is truly required, state this clearly at the beginning of the guide.
  • Where possible, use platform-agnostic methods for downloading and managing kubeconfig files, or provide alternative workflows for non-Windows users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/complete-private-mobile-network-prerequisites.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation exhibits a clear Windows bias. It explicitly requires a Windows PC and a Windows Administrator account, lists PowerShell as a required tool, and references Windows-specific technologies (e.g., WinRM, Windows Server Failover Clustering). There are no Linux or cross-platform alternatives provided for key steps, and Linux equivalents for tools and commands are not mentioned. The documentation assumes a Windows environment throughout, which may exclude or inconvenience users on Linux or macOS.
Recommendations:
  • Remove the explicit requirement for a Windows PC and Windows Administrator account unless absolutely necessary. If Windows is required for specific steps, clearly explain why and provide alternatives where possible.
  • For each tool (Azure CLI, PowerShell, kubectl), provide installation and usage instructions for Linux and macOS, not just Windows.
  • Where PowerShell or WinRM is referenced, include equivalent instructions for Bash/SSH on Linux/macOS, or clarify if these steps can be completed using cross-platform tools.
  • When referencing Windows-specific technologies (e.g., Windows Server Failover Clustering, cloud witness), indicate whether Linux-based alternatives are supported or provide guidance for non-Windows environments.
  • Ensure all command-line examples are provided for both Windows (PowerShell/CMD) and Linux/macOS (Bash), or use cross-platform syntax where possible.
  • Review all prerequisite and setup steps to ensure Linux users can follow the documentation without needing to switch to a Windows machine.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/create-site-arm-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page demonstrates a bias toward the Azure Portal GUI and does not provide any command-line examples for deploying the ARM template. There are no Windows-specific tools or PowerShell examples, but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash, or PowerShell) instructions are provided. The only deployment method shown is via the Azure Portal, which is platform-agnostic but omits command-line automation options commonly used on Linux.
Recommendations:
  • Add Azure CLI examples for deploying the ARM template, including full command syntax and sample parameters.
  • If relevant, include PowerShell examples as well, but ensure Azure CLI (cross-platform) is presented first or alongside.
  • Explicitly mention that the ARM template can be deployed using both Azure CLI and PowerShell, and link to official documentation for both.
  • Provide sample Bash scripts for Linux users to automate deployment.
  • Ensure that any references to tools or workflows are not Windows-centric and clarify cross-platform compatibility where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/create-slice-arm-template.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 assumes and describes only the Azure Portal (web UI) workflow for deploying ARM templates, without mentioning or providing examples for command-line deployment methods such as Azure CLI or PowerShell. While this avoids explicit Windows-only tools, it implicitly prioritizes the GUI approach, which is more commonly associated with Windows users, and omits cross-platform (Linux-friendly) automation options. There are no Linux-specific instructions or examples, nor is there mention of using the Azure CLI, which is available on all platforms.
Recommendations:
  • Add a section showing how to deploy the ARM template using the Azure CLI (az deployment group create ...), which works on Windows, Linux, and macOS.
  • If relevant, provide PowerShell examples, but always include Azure CLI examples first or alongside them to ensure cross-platform parity.
  • Explicitly mention that the Azure CLI can be used on Linux, macOS, and Windows, and provide installation links.
  • Consider including a table or callout comparing deployment methods (Portal, CLI, PowerShell) and their platform compatibility.
  • Ensure that any screenshots or instructions referencing the Azure Portal are supplemented with equivalent command-line instructions for automation and scripting use cases.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/modify-local-access-configuration.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by instructing users to use Azure Cloud Shell with PowerShell for command-line operations, without mentioning Bash or Linux alternatives. All command-line examples are presented in a generic or PowerShell context, and there is no explicit guidance for Linux users or those preferring Bash, despite the cross-platform nature of kubectl and Azure CLI.
Recommendations:
  • Provide equivalent instructions and examples for Bash in Azure Cloud Shell, not just PowerShell.
  • Explicitly mention that users can use either Bash or PowerShell in Azure Cloud Shell, and show how to select each.
  • Where command-line examples are given, clarify that they work on both Windows and Linux, or provide OS-specific notes if there are differences.
  • Add a note or section for Linux/macOS users, confirming that all kubectl and Azure CLI commands are cross-platform.
  • If any commands or steps are Windows-specific, provide Linux/macOS equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/set-up-kubectl-access.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation is heavily biased towards Windows environments, requiring the use of PowerShell, WinRM, and Windows-specific tools and workflows. All command-line examples are given exclusively in PowerShell, and there is no mention of how to perform these steps from Linux or macOS. The requirement to use a Windows machine is stated explicitly, and no alternatives or parity for Linux users are provided.
Recommendations:
  • Provide equivalent instructions and command examples for Linux (and optionally macOS) environments, using SSH or other cross-platform tools instead of WinRM and PowerShell.
  • If certain steps are only possible from Windows, clearly state this limitation and, if possible, provide workarounds or alternative approaches for non-Windows users.
  • Include Linux shell (bash) command examples alongside PowerShell, especially for obtaining and using kubeconfig files.
  • Mention and document any platform-specific prerequisites (such as required packages or permissions) for Linux users.
  • Consider using cross-platform tools (e.g., OpenSSH) for remote sessions where possible, or provide guidance on how Linux users can access the required functionality.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/region-move-private-mobile-network-resources.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing a PowerShell (az CLI) deployment example without mentioning or providing equivalent Linux/macOS shell commands. The only CLI example is shown using PowerShell syntax, and there is no explicit mention of Linux or cross-platform command-line usage. Additionally, the Azure portal is referenced as an alternative, but no Linux-specific tools, shell commands, or considerations are discussed.
Recommendations:
  • Provide both Windows (PowerShell) and Linux/macOS (bash) command-line examples for az CLI commands, making it clear that the Azure CLI is cross-platform.
  • Explicitly mention that the az CLI commands work on all major platforms and show the command in a generic shell format (e.g., az deployment group create ...) without PowerShell-specific syntax.
  • If any file paths or environment variables are referenced, show both Windows and Linux/macOS formats.
  • Add a note or section clarifying that all steps can be performed from Linux, macOS, or Windows, and link to Azure CLI installation instructions for all platforms.
  • Avoid implying that PowerShell is the default or only supported shell for these operations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/ue-usage-event-hub.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any explicit Windows bias, such as Windows/Powershell-specific commands, tools, or patterns. However, it does reference only .NET SDKs as an example for consuming Event Hubs data, without mentioning or providing examples for Linux-friendly SDKs or tools (such as Python, Java, or CLI usage). There are no explicit Linux or cross-platform examples, which may implicitly bias the documentation toward Windows-centric development environments.
Recommendations:
  • Include examples using cross-platform SDKs such as Python, Java, or Node.js for consuming Event Hubs data.
  • Mention and provide sample code for using the Azure CLI or Azure Event Hubs CLI tools, which are available on Linux.
  • Add a note clarifying that Event Hubs SDKs are available for multiple languages and platforms, with links to relevant documentation.
  • If possible, provide a Linux shell (bash) example for interacting with Event Hubs or processing the data.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/private-5g-core/whats-new.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias towards Windows environments by referencing PowerShell for site creation and management, and by mentioning Windows-centric tools (such as Power BI and Azure Stream Analytics) for data consumption. There are no Linux or cross-platform command-line examples, and no mention of Linux-native tools or workflows for equivalent tasks. The documentation assumes the use of Azure portal and ARM templates, which are cross-platform, but the only explicit scripting example is PowerShell, with no Bash, CLI, or Linux shell alternatives provided.
Recommendations:
  • Provide equivalent Linux/Bash/Azure CLI examples alongside PowerShell for all scripted or command-line tasks.
  • Mention and demonstrate cross-platform or Linux-native tools (e.g., jq, curl, Linux text processing utilities) where relevant.
  • When referencing data consumption tools like Power BI, also mention open-source or Linux-compatible alternatives (e.g., Grafana, Kibana).
  • Ensure that any automation or scripting guidance is presented in a platform-neutral way, or with clear parity between Windows and Linux workflows.
  • Explicitly state platform requirements or compatibility for any tools or scripts mentioned.