Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1001-1025 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/connectors-native-http-swagger.md
.../articles/connectors/connectors-native-http-swagger.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by providing a PowerShell script as the only example for automating CORS configuration, and by referencing Azure Storage Explorer (a GUI tool primarily distributed for Windows, though available cross-platform) without mentioning Linux-native alternatives or CLI approaches. There are no Linux shell (bash/CLI/az CLI) examples for tasks such as enabling CORS or uploading Swagger files, and no explicit mention of Linux workflows or tools.
Recommendations
- Provide equivalent bash or Azure CLI examples for configuring CORS and uploading Swagger files to Azure Storage, alongside the PowerShell script.
- Mention and link to cross-platform or Linux-native tools (such as az CLI) for managing Azure Storage and blob containers.
- Clarify that Azure Storage Explorer is available for Linux and macOS, or suggest alternative methods for users on those platforms.
- Ensure that automation examples are balanced between PowerShell and shell/CLI scripts to support both Windows and Linux users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/enable-stateful-affinity-built-in-connectors.md
...ectors/enable-stateful-affinity-built-in-connectors.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides detailed instructions and examples for using Azure PowerShell to update website configuration, but does not mention or provide equivalent examples for Linux-native tools (such as Azure CLI, Bash scripting, or REST calls using curl). The only command-line automation method shown is PowerShell, which is primarily associated with Windows environments, and there is no guidance for users on Linux or macOS platforms. Additionally, troubleshooting steps and error handling are only shown in PowerShell.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including configuration updates and troubleshooting steps.
- Provide REST API usage examples using curl or HTTPie, which are cross-platform and commonly used on Linux/macOS.
- Explicitly mention that PowerShell Core is cross-platform if PowerShell is to be retained, and provide installation guidance for non-Windows users.
- Ensure troubleshooting and error handling sections include CLI and REST API approaches, not just PowerShell.
- Review all steps to ensure that Linux and macOS users have clear, tested paths for accomplishing the same tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/code-to-cloud-options.md
...main//articles/container-apps/code-to-cloud-options.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools (Visual Studio, Visual Studio Code) and workflows, referencing PowerShell before Bash, and omitting explicit Linux or cross-platform examples. There are no Linux-specific editors or CLI usage examples, and the documentation assumes familiarity with Windows tooling and patterns.
Recommendations
- Include explicit Linux examples and workflows, such as using VS Code on Linux or deploying from Linux terminals.
- When mentioning shell automation, list Bash before or alongside PowerShell, and provide sample commands for both.
- Reference cross-platform editors (e.g., VS Code) with Linux/Mac installation and usage notes, not just Visual Studio (which is Windows-centric).
- Add links or sections for deploying from Linux environments, including common Linux tools and patterns.
- Ensure that all CLI instructions and screenshots are shown in both Windows (PowerShell/CMD) and Linux (Bash) contexts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/connectors/integrate-cics-apps-ibm-mainframe.md
...ticles/connectors/integrate-cics-apps-ibm-mainframe.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft Host Integration Server (HIS) Designer, which is a Windows-only tool, as the required method to generate the HIDX metadata file. There are no mentions of Linux-compatible alternatives or instructions for non-Windows environments. The only prerequisite for the HIS Designer is the Microsoft .NET Framework 4.8, which is also Windows-centric. No Linux or cross-platform tooling is suggested, and all setup and workflow steps assume use of Windows tools and environments.
Recommendations
- Explicitly state whether the HIS Designer tool is available for Linux or provide guidance for Linux users (e.g., using Wine, containers, or remote Windows VMs).
- If no Linux-native tool exists, suggest alternative approaches for Linux users, such as using a Windows VM or Azure-hosted environment to generate the HIDX file.
- Document any command-line or cross-platform options (if available) for generating HIDX files.
- Consider providing sample workflows or instructions that can be followed from Linux environments, or clarify the limitations for non-Windows users.
- Add a section addressing Linux/macOS developer scenarios, even if only to acknowledge the current limitations and suggest workarounds.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/manage-secrets.md
...s/blob/main//articles/container-apps/manage-secrets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides extensive PowerShell examples and references, with no explicit Linux shell or Bash examples. PowerShell is presented as a primary scripting interface alongside Azure CLI and ARM templates, but there are no Linux-specific command-line or scripting examples. The use of PowerShell and its cmdlets, as well as the lack of Bash or Linux-native scripting, demonstrates a Windows-centric bias. Additionally, PowerShell examples are sometimes provided even when the equivalent functionality (e.g., Key Vault secret references, secret volume mounts) is not supported, but there is no alternative Linux guidance.
Recommendations
- Add Linux/Bash shell examples for all Azure CLI commands, including environment variable usage and secret handling.
- Explicitly mention cross-platform compatibility for Azure CLI commands, and provide sample Bash scripts for Linux users.
- Where PowerShell is not supported (e.g., Key Vault secret references, secret volume mounts), provide alternative Linux-native approaches or clarify how Linux users can achieve similar outcomes.
- Balance the order of examples so that Azure CLI (cross-platform) or Bash examples are presented before or alongside PowerShell, rather than after.
- Avoid assuming PowerShell as the default scripting environment; instead, offer parity between Windows and Linux command-line tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/deploy-visual-studio.md
.../main//articles/container-apps/deploy-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows users by exclusively using Visual Studio (a primarily Windows IDE) for all instructions and workflows. There are no examples or instructions for deploying from Linux or using Linux-native tools (such as VS Code, CLI, or Docker commands). The workflow assumes a GUI and Windows-centric development environment, with no parity for Linux users who may use different editors or command-line tools.
Recommendations
- Add parallel instructions for deploying to Azure Container Apps using cross-platform tools such as the Azure CLI, Docker CLI, and VS Code.
- Include Linux-specific setup and deployment steps, such as using the terminal to build and push Docker images, and deploying via az containerapp commands.
- Mention and provide links to Linux-compatible IDEs (e.g., VS Code) and show how to perform equivalent tasks outside of Visual Studio.
- Reorder or supplement the documentation so that Windows and Linux workflows are presented with equal prominence, or clarify that this guide is specific to Visual Studio/Windows and link to Linux-focused guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/java-component-logs.md
...b/main//articles/container-apps/java-component-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for querying logs, but the Bash examples use the non-standard 'SET' command for variable assignment, which is a Windows CMD syntax, not valid in Bash or Linux shells. This can confuse Linux users. Additionally, PowerShell examples are always present, and the variable assignment is shown first with 'SET' (Windows) before PowerShell, indicating a Windows-first approach. There are no explicit Linux-native (e.g., export, or POSIX-compliant) examples, and no mention of Linux-specific tools or patterns.
Recommendations
- Replace 'SET $WORKSPACE_ID=<WORKSPACE_ID>' in Bash examples with 'export WORKSPACE_ID=<WORKSPACE_ID>' to use standard Linux shell syntax.
- Ensure Bash/Linux examples are correct and tested in a Linux environment.
- Consider listing Bash/Linux examples before PowerShell/Windows examples to avoid a Windows-first impression.
- Explicitly mention compatibility with Linux and provide troubleshooting tips for common Linux shell issues.
- If possible, add examples using other common Linux tools (e.g., curl, jq) where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/metrics.md
...ure-docs/blob/main//articles/container-apps/metrics.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned alongside CLI in a way that may suggest parity, despite PowerShell being Windows-centric. No Linux-specific tools, shell examples, or screenshots are provided. There are no explicit Linux command-line examples or references to Linux-native workflows, and the documentation does not clarify cross-platform support for the CLI or PowerShell commands.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell/CMD) and Linux/macOS (Bash).
- When referencing command-line tools, list Azure CLI (which is cross-platform) before PowerShell, and clarify that PowerShell is primarily for Windows users.
- Include sample Bash commands for common metric retrieval tasks.
- Add screenshots or terminal snippets from Linux environments where appropriate.
- Mention any differences or considerations for Linux users, such as installation steps or environment variables.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/energy-data-services/overview-microsoft-energy-data-services.md
...ta-services/overview-microsoft-energy-data-services.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Microsoft and Windows-centric tools and patterns. It exclusively references Microsoft products (SharePoint, Synapse, Power BI, Entra ID) for extensibility and integration, without mentioning Linux-native or cross-platform alternatives. There are no examples or references to Linux tools, command-line interfaces, or workflows, and the documentation assumes the use of Microsoft’s ecosystem as the default.
Recommendations
- Include references to cross-platform or Linux-native tools for data ingestion, transformation, and visualization (e.g., Apache NiFi, Jupyter, Grafana).
- Provide examples or documentation links for using the platform from Linux environments, such as via Azure CLI, REST APIs, or open-source SDKs.
- Mention authentication and authorization options compatible with non-Microsoft identity providers, if supported.
- Highlight interoperability with open-source or non-Microsoft applications where possible.
- Balance the mention of Microsoft tools by also listing popular Linux or open-source equivalents in the extensibility section.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/managed-identity-image-pull.md
...articles/container-apps/managed-identity-image-pull.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but there is a notable emphasis on PowerShell, especially in the prerequisites and setup steps. PowerShell commands are given equal or greater prominence than Bash, and Windows-specific tools (Azure PowerShell) are mentioned alongside or even before their Linux equivalents. There are no Linux-specific tools or patterns discussed, and the documentation assumes parity between Bash and PowerShell without addressing platform-specific nuances. No Linux-only examples or troubleshooting are provided, and some steps (e.g., Bicep installation) are more detailed for PowerShell/Windows users.
Recommendations
- Ensure that Bash/Azure CLI examples are always presented first, as Bash is more universally available across platforms.
- Add explicit notes about platform differences, such as file path conventions, environment variable syntax, and installation steps for Linux/macOS users.
- Include troubleshooting tips or common issues for Linux environments (e.g., permissions, dependency installation).
- Provide links to Linux/macOS-specific installation guides where appropriate.
- Where PowerShell is mentioned, clarify that it is available cross-platform, but also highlight any differences in behavior or prerequisites on Linux/macOS.
- Consider adding a section or appendix specifically for Linux/macOS users to address any unique considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/troubleshooting.md
.../blob/main//articles/container-apps/troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Portal-based instructions and terminology are platform-neutral, but the only explicit OS-specific references and examples are for Windows. The Docker example mentions running in an 'elevated command prompt' and refers to 'Docker on Windows' with a link, but does not mention Linux or macOS equivalents. In the CLI extension installation section, both Bash (Azure CLI) and PowerShell examples are given, but the PowerShell section is more detailed (including update instructions), and there is no mention of Linux-specific shell environments or troubleshooting. There are no explicit Linux/macOS instructions or links, and no screenshots or notes for non-Windows users.
Recommendations
- For Docker instructions, explicitly mention that the 'docker run' command works on Linux and macOS as well, and provide links to Docker installation guides for those platforms.
- When referencing an 'elevated command prompt', add a note for Linux/macOS users to use 'sudo' if necessary.
- In the CLI extension section, provide parity between Bash and PowerShell instructions (e.g., show how to update the Azure CLI extension in Bash, not just PowerShell module updates).
- Wherever a Windows-specific tool or pattern is mentioned (such as 'command prompt'), add the Linux/macOS equivalent (such as 'terminal').
- Consider including a short section or callout for Linux/macOS users, especially in sections where OS-specific behavior or troubleshooting may differ.
- Add links to Linux/macOS troubleshooting or installation documentation where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/automate/cost-management-api-permissions.md
...nt-billing/automate/cost-management-api-permissions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing explicit instructions and links for assigning roles using Azure PowerShell, a Windows-centric tool, while omitting equivalent CLI or scripting examples for Linux/macOS users. The portal-based instructions are platform-neutral, but the only automation example references PowerShell, and there are no Azure CLI or REST API command examples for Linux environments.
Recommendations
- Add equivalent Azure CLI examples for assigning roles to service principals, as Azure CLI is cross-platform and widely used on Linux/macOS.
- When referencing automation, provide both PowerShell and CLI (az) command examples side-by-side.
- Mention REST API options for permissions assignment, including example requests, to ensure platform neutrality.
- Avoid referencing PowerShell before CLI or REST API unless there is a clear reason; consider presenting cross-platform tools first.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI or REST API, and provide links or code snippets accordingly.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/tutorial-code-to-cloud.md
...ain//articles/container-apps/tutorial-code-to-cloud.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash and PowerShell examples for most commands, but the PowerShell sections are significantly more detailed, often using Az PowerShell modules rather than cross-platform Azure CLI. In some cases, PowerShell-specific tools (like Connect-AzContainerRegistry, New-AzUserAssignedIdentity, New-AzContainerApp) are used, which are primarily Windows-centric. The PowerShell examples are often more verbose and sometimes appear before or in more detail than their Bash equivalents. There is little to no mention of Linux-specific patterns, shells, or troubleshooting, and the documentation assumes familiarity with PowerShell and its object-oriented scripting, which is less common on Linux/macOS.
Recommendations
- Prioritize Azure CLI (az) examples, which are cross-platform, and only provide PowerShell-specific examples as secondary or in advanced sections.
- Ensure that Bash examples are as detailed as PowerShell ones, including variable setup, error handling, and output parsing.
- Avoid using PowerShell-specific Az module commands (e.g., New-AzContainerApp) as primary examples; instead, use Azure CLI equivalents where possible.
- Explicitly mention that Bash examples work on Linux/macOS/WSL and provide troubleshooting tips for common Linux environments.
- Where PowerShell is used, clarify that it is available cross-platform (PowerShell Core), but avoid assuming Windows as the default environment.
- Include Linux/macOS-specific notes or callouts where behaviors or prerequisites differ (e.g., Docker Desktop installation, file permissions, environment variable syntax).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/automate/tutorial-seed-historical-cost-dataset-exports-api.md
...e/tutorial-seed-historical-cost-dataset-exports-api.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the list of popular ways to query the API, Windows-centric tools (Visual Studio and PowerShell’s Invoke-RestMethod) are mentioned before cross-platform or Linux-native tools (Insomnia, Bruno, Curl). PowerShell is specifically highlighted, and there are no explicit Linux shell or command-line examples (e.g., bash with curl), nor are Linux-specific tools or workflows discussed. The ordering and tool selection may subtly prioritize Windows users.
Recommendations
- Provide explicit Linux/macOS shell examples using curl or httpie, including sample commands.
- List cross-platform and Linux-native tools (e.g., curl, httpie, Insomnia) before Windows-specific tools in the 'popular ways to query the API' section.
- Include bash/zsh shell snippets alongside or instead of PowerShell examples.
- Mention Linux package managers or installation instructions for relevant tools (e.g., how to install curl or httpie on Linux).
- Ensure parity in troubleshooting or tips for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/vnet-custom.md
...docs/blob/main//articles/container-apps/vnet-custom.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but PowerShell is given equal or sometimes slightly more detailed coverage, and is always present as a first-class citizen. PowerShell is a Windows-centric tool, and its prominence (including advanced scripting and parameterization) may signal a Windows bias. There are no Linux-specific tools or patterns (e.g., native Linux shell scripting, use of Linux package managers, or references to Linux-only environments). The documentation does not mention or provide examples for Linux-native tools beyond Bash, and PowerShell is always presented alongside Bash, not as a secondary or optional alternative.
Recommendations
- Clearly indicate that PowerShell examples are primarily for Windows users, and Bash/CLI for Linux/macOS users.
- Consider providing Linux-native shell scripting examples (e.g., using only Bash, avoiding PowerShell-specific constructs) where possible.
- Add notes or callouts for Linux/macOS users, especially where environment variable syntax or command-line behavior may differ.
- If PowerShell is included, clarify its cross-platform availability, but avoid implying it is the default for all users.
- Where advanced scripting is shown in PowerShell, provide equivalent Bash scripting for Linux users.
- Consider mentioning Linux package managers or environment setup steps if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/analyze-cost-data-azure-cost-management-power-bi-template-app.md
...-cost-data-azure-cost-management-power-bi-template-app.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on the Power BI App and Power BI Desktop, both of which are primarily Windows-centric tools. There are no references to Linux-compatible alternatives or instructions for Linux users. The workflow assumes the use of Microsoft authentication and Azure portal interfaces, which are optimized for Windows environments. Additionally, the 'Windows Server AHB Usage' report section specifically highlights Windows VMs, with no mention of Linux VMs or their cost management features.
Recommendations
- Include explicit statements about Power BI Desktop and App availability on non-Windows platforms, and provide links to any Linux or web-based alternatives if available.
- Add instructions or guidance for Linux users, such as using Power BI web service or third-party BI tools that can connect to Azure Cost Management data.
- When discussing VM cost management, include information about Linux VMs and their cost optimization features, not just Windows Server AHB.
- Where screenshots or UI steps are shown, clarify if the experience is the same on all platforms or note any differences.
- If certain features are Windows-only, clearly state this and suggest alternative workflows for Linux/Mac users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/manage-automation.md
...les/cost-management-billing/costs/manage-automation.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively mentioning and recommending Windows-centric tools such as Power BI and Excel for cost data analysis, without referencing Linux-friendly alternatives or command-line workflows. There are no examples or guidance for Linux users (e.g., using CLI tools, scripting in Bash, or open-source data analysis tools), and the documentation assumes the use of GUI tools more common on Windows. This may hinder Linux users or those working in cross-platform or headless environments.
Recommendations
- Include examples for Linux users, such as using curl or wget to interact with the Cost Details API, and parsing CSV data with command-line tools like awk, sed, or Python scripts.
- Mention open-source or cross-platform data analysis tools (e.g., Jupyter Notebooks, pandas, Apache Arrow, or LibreOffice Calc) alongside Power BI and Excel.
- Provide sample automation scripts in Bash or Python, not just API request payloads, to demonstrate end-to-end workflows on Linux.
- Clarify that the APIs and exports can be consumed and processed on any platform, not just with Windows tools.
- If referencing Power BI, note its availability (or lack thereof) on non-Windows platforms and suggest alternatives for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/tutorial-acm-create-budgets.md
...anagement-billing/costs/tutorial-acm-create-budgets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell examples, referencing PowerShell before CLI or cross-platform tools, and omitting explicit Linux shell (bash) or macOS-specific instructions. The CLI example is present but follows the PowerShell example, and there are no explicit Linux/macOS setup or troubleshooting notes. The use of PowerShell as the primary programmatic example and the lack of Linux-specific context or parity in screenshots and instructions further reinforce the bias.
Recommendations
- Present CLI (az) examples before or alongside PowerShell examples, emphasizing its cross-platform nature.
- Include explicit bash/Linux shell examples and troubleshooting notes for Linux/macOS users (e.g., environment variable setup, file path differences).
- Add a section or callout noting that Azure CLI and Terraform are fully supported on Linux and macOS, and provide links to relevant installation guides.
- Ensure screenshots and navigation instructions are OS-agnostic or include Linux/macOS UI where relevant.
- Review language to avoid implying PowerShell is the default or preferred automation tool; clarify that both CLI and PowerShell are supported.
- Where PowerShell is mentioned, add equivalent bash/CLI commands for common tasks (e.g., authentication, selecting subscriptions).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/costs/quick-create-budget-template.md
...nagement-billing/costs/quick-create-budget-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While it does mention cross-platform tools like Azure CLI and REST API, the structure and references prioritize Windows-centric tools and workflows. The Azure portal (which is web-based but often associated with Windows workflows) is always presented first for deployment and validation, and PowerShell is given equal or greater prominence than CLI. References to deployment documentation link to PowerShell-specific pages, and there are no explicit Linux shell or scripting examples, nor is there mention of Linux-native tools or workflows.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
- When referencing deployment documentation, link to both PowerShell and Azure CLI guides, or to a neutral landing page that covers both.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands (e.g., bash) for Linux users.
- Where possible, add Linux-specific notes or screenshots (e.g., terminal windows) to illustrate parity.
- Avoid using language or structure that implies the Azure portal or PowerShell are the default or preferred methods, and instead present all supported methods equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/assign-roles-azure-service-principals.md
...illing/manage/assign-roles-azure-service-principals.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell for automation, referencing Windows-centric tools (such as Visual Studio and PowerShell cmdlets), and omitting Linux- or cross-platform command-line examples. The only explicit code example for generating a GUID uses PowerShell's New-Guid, with no mention of Linux or macOS alternatives. REST API usage is discussed, but the tooling and workflow examples are Windows-first, and there are no Bash, shell, or Linux-native tool examples provided.
Recommendations
- Provide equivalent Linux/macOS command-line examples for all PowerShell commands (e.g., show how to generate a GUID with uuidgen or openssl).
- Include Bash/cURL command-line examples for REST API calls, not just references to PowerShell's Invoke-RestMethod.
- Mention cross-platform editors and tools (such as VS Code, Postman, or httpie) alongside or before Windows-specific tools like Visual Studio.
- Ensure that all screenshots and walkthroughs are not exclusively from Windows environments, or provide Linux/macOS equivalents where relevant.
- Explicitly state that all steps can be performed from Linux/macOS, and provide links to relevant authentication and setup guides for those platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/cost-management-budget-scenario.md
...ment-billing/manage/cost-management-budget-scenario.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows tools and workflows. Examples and instructions frequently reference Windows-centric tools such as Visual Studio, PowerShell’s Invoke-RestMethod, and ARMClient (which requires Visual Studio to build). There are no Linux-specific examples or explicit cross-platform alternatives provided for key steps, such as building ARMClient, running command-line operations, or interacting with APIs. Linux users are left to infer or adapt instructions, and Linux-native tools (e.g., Bash, wget, native package managers) are not mentioned.
Recommendations
- Provide explicit Linux/macOS alternatives for all command-line steps, such as using dotnet CLI to build ARMClient or providing pre-built binaries.
- Include API interaction examples using curl or httpie with sample commands for Linux/macOS users, not just PowerShell.
- Mention cross-platform editors (e.g., VS Code) alongside Visual Studio.
- Clarify that ARMClient can be built and run on Linux/macOS using .NET Core, and provide instructions.
- Ensure that all tool recommendations (e.g., API clients) include Linux-compatible options and installation instructions.
- Add a section or callouts for Linux/macOS users where workflows or commands differ.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/manage-billing-across-tenants.md
...gement-billing/manage/manage-billing-across-tenants.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented around the Azure portal and Microsoft 365 admin center, both of which are web-based tools but are most commonly associated with Windows-centric workflows and environments. There are no command-line examples (such as PowerShell, CLI, or Bash), but all instructions and screenshots are based on the Azure portal UI, which is designed and documented primarily for Windows users. There is no mention of Linux or cross-platform command-line alternatives, nor are there any references to Linux-specific tools or workflows. The documentation implicitly assumes a Windows/Microsoft ecosystem, omitting parity for Linux users.
Recommendations
- Provide equivalent instructions using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
- Include examples for managing billing tenants using REST APIs or scripting, with sample commands in Bash or Python.
- Explicitly state that the Azure portal and Microsoft 365 admin center are web-based and accessible from any OS, and provide browser compatibility notes.
- If PowerShell is referenced elsewhere, ensure Azure CLI or REST API alternatives are always presented alongside.
- Add a section or callout for Linux users, highlighting any differences or additional steps required for common Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/auth0-log-stream-blob-storage.md
...//articles/event-grid/auth0-log-stream-blob-storage.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation assumes use of the Azure Portal and Visual Studio Code, both of which are cross-platform but are often associated with Windows workflows. There are no explicit examples or instructions for Linux users, such as using the Azure CLI, Bash, or other Linux-native tools. All steps involving copying connection strings, configuring settings, and deploying functions are described via GUI interactions, which are more familiar to Windows users. There are no command-line examples (e.g., Bash, Azure CLI) or references to Linux-specific workflows.
Recommendations
- Add parallel instructions for using the Azure CLI and Bash for all steps, including creating resources, configuring settings, and deploying functions.
- Include examples of copying connection strings and managing configuration via command line (e.g., az storage account show-connection-string).
- Provide explicit notes or links for Linux/macOS users on how to perform each step outside the Azure Portal or Visual Studio Code GUI.
- Where screenshots are used, consider including CLI output or terminal screenshots as alternatives.
- Clarify that all tools and steps are cross-platform, and provide troubleshooting tips for Linux environments if needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/link-partner-id.md
...cles/cost-management-billing/manage/link-partner-id.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently presenting command-line examples with Windows-specific syntax (e.g., 'C:\>' prompt), listing PowerShell instructions before Azure CLI, and referencing Windows tools and conventions. There are no explicit Linux or macOS shell examples, and installation or usage instructions assume a Windows environment.
Recommendations
- Provide Linux/macOS shell examples alongside or before Windows examples, using appropriate prompts (e.g., '$' for Bash).
- Include installation instructions for PowerShell and Azure CLI on Linux/macOS, not just Windows.
- Avoid using Windows-specific file paths or prompts in generic command examples; use platform-neutral syntax where possible.
- Explicitly state cross-platform compatibility of tools and commands, and link to relevant platform-specific documentation.
- Balance the order of examples (sometimes showing Azure CLI or Bash first) to avoid reinforcing a Windows-first perspective.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cost-management-billing/manage/mca-role-migration.md
...s/cost-management-billing/manage/mca-role-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All scripting examples are provided only in PowerShell (.ps1), and users are explicitly instructed to select PowerShell in Azure Cloud Shell, with no mention of Bash or cross-platform alternatives. There are no Linux shell or CLI examples, and the workflow assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
- Update instructions to mention both Bash and PowerShell options in Azure Cloud Shell, and clarify that either can be used where possible.
- Include notes about running scripts on Linux/macOS, including any prerequisites or differences in authentication or file handling.
- Where PowerShell-specific cmdlets are used, suggest cross-platform alternatives or clarify if the script is compatible with PowerShell Core on Linux/macOS.
- Avoid language that assumes Windows as the default environment (e.g., 'save the file locally as PS1 file') and instead use neutral, cross-platform phrasing.