Cost Management Billing

298
Total Pages
220
Linux-Friendly Pages
78
Pages with Bias
26.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 301-325 of 365 flagged pages
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/understand-usage.md ...cost-management-billing/understand/understand-usage.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by mentioning Microsoft Excel as the primary tool for opening the usage and charges CSV file, without referencing Linux-native spreadsheet applications or command-line tools. There are no examples or instructions for Linux users, such as using LibreOffice Calc or CSV utilities. No PowerShell commands are present, but the lack of Linux parity in tooling and examples is notable.
Recommendations
  • Explicitly mention Linux-compatible spreadsheet applications (e.g., LibreOffice Calc, GNOME Spreadsheet) alongside Microsoft Excel.
  • Suggest command-line tools for viewing CSV files on Linux, such as 'cat', 'less', or 'csvkit'.
  • Include examples or instructions for downloading and opening the CSV file on Linux systems.
  • Ensure future documentation provides parity in tool recommendations and examples for both Windows and Linux users.
GitHub Create Pull Request
Cost Management Billing 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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists PowerShell’s Invoke-RestMethod as a popular way to query the API before mentioning curl, which is the standard tool on Linux/macOS. PowerShell is a Windows-centric tool, and its placement before curl suggests a Windows-first bias. There are no explicit Linux command-line examples, and no mention of bash or shell scripting, which are common on Linux. The examples and instructions do not provide parity for Linux users.
Recommendations
  • List curl before PowerShell in the 'popular ways to query the API' section to reflect its cross-platform usage.
  • Provide explicit curl command examples for API requests, including headers and body formatting.
  • Mention bash or shell scripting as alternatives for automation alongside PowerShell.
  • Ensure that all code examples are cross-platform or provide both PowerShell and curl/bash equivalents.
  • Clarify that PowerShell is available on Linux, but curl is more commonly used in Linux environments.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/enable-tag-inheritance.md ...ost-management-billing/costs/enable-tag-inheritance.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes enabling tag inheritance using the Azure portal GUI, which is primarily accessed via web browsers on Windows. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor any mention of Linux-specific tools or workflows. The absence of Linux or cross-platform command-line instructions may disadvantage users who prefer or require automation or non-Windows environments.
Recommendations
  • Add Azure CLI examples for enabling tag inheritance, as the CLI is cross-platform and widely used on Linux.
  • Include Bash script snippets for common operations, demonstrating parity with PowerShell examples if provided.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide alternative instructions for users who prefer command-line or automation workflows.
  • If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are present and presented with equal prominence.
GitHub Create Pull Request
Cost Management Billing 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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on the Power BI App and Power BI Desktop, both of which are primarily Windows-based tools. There are no references to Linux-compatible alternatives or instructions for Linux users. All installation and usage steps assume access to the Power BI ecosystem, which has limited or no support on Linux. No command-line or cross-platform examples are provided, and troubleshooting assumes use of the Power BI GUI. The only mention of operating systems is in the context of Windows Server AHB usage, with no mention of Linux VMs or their cost management.
Recommendations
  • Explicitly state the platform requirements and limitations for Power BI App and Desktop, including lack of Linux support.
  • Provide alternative instructions or recommendations for Linux users, such as using Power BI web service (if applicable) or exporting data for analysis in cross-platform tools (e.g., Jupyter, Tableau, or open-source BI tools).
  • If possible, include examples or guidance for accessing Azure cost data via APIs or CLI tools that are cross-platform, with sample scripts for Linux environments.
  • When discussing VM cost management, include examples or notes relevant to Linux VMs, not just Windows Server AHB.
  • Add a section addressing common questions or workarounds for users on non-Windows platforms.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/create-subscription-request.md ...nagement-billing/manage/create-subscription-request.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes subscription creation and acceptance using the Azure portal, with screenshots and instructions that reflect the Windows-centric Azure portal UI. There are no examples or references to Linux-specific tools, command-line interfaces, or cross-platform alternatives (such as Azure CLI or REST API usage). The only mention of programmatic creation is a link to another page, with no direct examples or parity for Linux users. The documentation implicitly assumes a Windows environment and user experience.
Recommendations
  • Add step-by-step instructions for creating and accepting subscriptions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples of using REST API calls for subscription management, with sample curl commands.
  • Clarify that the Azure portal is accessible from any OS, but provide screenshots or notes that reflect usage from Linux/macOS browsers.
  • Ensure that any programmatic or automation steps are demonstrated with tools available on Linux (e.g., bash scripts, Azure CLI, PowerShell Core).
  • Explicitly mention cross-platform compatibility and provide links to documentation for Linux users.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/discover-cloud-footprint.md ...-management-billing/manage/discover-cloud-footprint.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on Microsoft cloud management through web portals (Azure portal, Microsoft 365 admin center) and Microsoft-specific tools (Azure CLI, REST API). There is no mention of Linux-specific tools, shell commands, or cross-platform CLI usage outside of Azure CLI, which is available on Linux but not highlighted as such. No PowerShell examples are present, but the lack of Linux shell (bash) or open-source tool examples means the page assumes users are operating in a Microsoft-centric environment.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide bash-specific examples or notes where relevant.
  • Include examples using curl or other standard Linux tools to interact with REST APIs, alongside Azure CLI.
  • Reference cross-platform management options (e.g., using browser-based portals from any OS, or using open-source tools where applicable).
  • Add a section or note for Linux administrators, clarifying how to perform key tasks from Linux environments and mentioning any OS-specific considerations.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/add-change-subscription-administrator.md ...illing/manage/add-change-subscription-administrator.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references the Azure portal for administrative tasks, without mentioning or providing examples for command-line tools such as Azure CLI or PowerShell. While no explicit Windows tools are named, the lack of CLI instructions and the portal-centric approach implicitly favors Windows users, as the Azure portal experience is often associated with Windows environments. There are no Linux-specific examples or parity for users who prefer or require command-line operations.
Recommendations
  • Add step-by-step instructions for assigning subscription administrators using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples if relevant, but ensure Azure CLI instructions are presented first or alongside them.
  • Explicitly mention that all tasks can be performed from Linux, macOS, or Windows using CLI tools.
  • Provide links to documentation for Azure CLI and PowerShell role assignment commands.
  • Clarify that the Azure portal is web-based and accessible from any OS, but highlight CLI alternatives for automation and scripting.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-billing-access.md ...ost-management-billing/manage/manage-billing-access.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references the Azure portal for managing billing access and role assignments, with no mention of command-line or automation options such as Azure CLI, PowerShell, or REST API. Where programmatic access is referenced (Cost Management APIs), no usage examples are provided. The only linked instructions for role assignment are for the Azure portal, which is a web interface and does not differentiate between Windows and Linux, but in practice, Windows users are more likely to use GUI tools. There are no examples or guidance for Linux users who may prefer CLI or automation workflows.
Recommendations
  • Add examples for assigning roles using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for parity, but ensure Azure CLI is presented first or alongside PowerShell.
  • Provide REST API examples for programmatic access to billing information.
  • Explicitly mention that all steps can be performed from any OS using CLI or API, not just via the portal.
  • Link to documentation for Azure CLI and REST API role assignment and billing access management.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-enterprise-agreement.md ...grammatically-create-subscription-enterprise-agreement.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for REST, Azure PowerShell, and Azure CLI, but consistently lists PowerShell before CLI in code tabs and walkthroughs. PowerShell is a Windows-centric tool, and its precedence may signal a Windows-first bias. There are no explicit Linux-only examples or references to Linux-specific tools or shell environments. However, Azure CLI is cross-platform and is included in all major example sections, which helps mitigate bias. No examples are missing for Linux users, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or list CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide sample shell commands for Bash/zsh where relevant.
  • Add a note clarifying that PowerShell Core is available cross-platform, but that Azure CLI may be more familiar to Linux users.
  • Consider including screenshots or walkthroughs using Linux terminals or macOS, not just Windows/PowerShell environments.
  • Review and balance the frequency of PowerShell and CLI examples to ensure equal visibility for Linux users.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/understand-vm-reservation-charges.md ...nt-billing/manage/understand-vm-reservation-charges.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific concepts (such as Azure Hybrid Benefit and Windows software charges) are described in greater detail and referenced with dedicated links, while Linux equivalents (such as Red Hat licensing) are mentioned only briefly and without links. The table of VM types lists Windows scenarios after Linux, but Windows licensing and features (like Azure Hybrid Benefit) are given more attention and documentation support. There are no command-line examples, so no Powershell bias is present, but Windows tools and patterns (e.g., Azure Hybrid Benefit) are highlighted without Linux alternatives.
Recommendations
  • Provide equal detail and documentation links for Linux VM scenarios, such as Red Hat or SUSE licensing and benefits.
  • Include references to Linux-specific cost management features or licensing programs, if available.
  • Ensure that any special Windows features (like Azure Hybrid Benefit) are matched with Linux equivalents or explicitly state if none exist.
  • Add examples or links for managing reservations on Linux VMs, similar to those provided for Windows VMs.
  • Review related content to ensure Linux VM reservation management is covered as thoroughly as Windows.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/microsoft-foundry.md ...t-management-billing/reservations/microsoft-foundry.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively references the Azure portal for all reservation management tasks and examples, without mentioning or providing parity for Linux command-line tools, CLI, or automation options. There are no PowerShell examples, but the overall workflow assumes GUI usage, which is more common on Windows. There is no mention of Azure CLI, Bash, or Linux-native automation, and no examples for Linux users. The documentation implicitly favors Windows-centric patterns by omitting Linux/CLI alternatives.
Recommendations
  • Add Azure CLI examples for reservation management tasks (purchase, cancel, exchange, refund) alongside portal instructions.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI or REST APIs.
  • Provide sample Bash scripts or command-line workflows for common scenarios.
  • Include links to Azure CLI documentation for reservations.
  • Clarify that the Azure portal is cross-platform (browser-based), but highlight automation options for non-Windows environments.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/software-costs-not-included.md ...nt-billing/savings-plan/software-costs-not-included.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Windows software meters and licensing costs, with no mention of Linux equivalents or how savings plans affect Linux VM usage. All examples and tables are Windows-centric, and there is no discussion of Linux VM software costs or licensing, which may lead users to assume that only Windows VMs incur extra software charges.
Recommendations
  • Add a section clarifying how savings plans apply to Linux VMs, including whether there are any software meters or licensing costs for Linux.
  • Explicitly state that Linux VMs do not incur similar software charges, if that is the case, to help users understand the differences.
  • Provide parity by listing any Linux-specific meters or confirming their absence.
  • Consider a comparative table showing both Windows and Linux VM cost components under savings plans.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/calculate-ea-savings-plan-savings.md ...ling/savings-plan/calculate-ea-savings-plan-savings.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Excel for data preparation and calculation steps, with all instructions and screenshots tailored to Excel on Windows. There are no examples or guidance for performing these tasks using Linux tools (such as LibreOffice Calc, csvkit, pandas, awk, etc.), nor is there mention of command-line or open-source alternatives. The workflow assumes a GUI spreadsheet application, which is most commonly associated with Windows environments.
Recommendations
  • Add explicit instructions and examples for performing the calculations using open-source spreadsheet applications (e.g., LibreOffice Calc) available on Linux.
  • Provide command-line alternatives for data filtering and calculation, such as using csvkit, pandas (Python), or awk, which are popular on Linux.
  • Include screenshots or terminal output examples from Linux environments to illustrate parity.
  • Mention that the CSV file can be processed on any operating system and highlight cross-platform tools.
  • Rephrase steps to be application-agnostic where possible, or provide parallel instructions for both Excel and Linux-friendly tools.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/plan-manage-costs.md ...ost-management-billing/understand/plan-manage-costs.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias, particularly in the section discussing estimated costs for virtual machines. The example specifically references a Windows VM, with a screenshot and description focused on Windows, without providing a parallel example for Linux VMs. While Linux is mentioned later in the context of pricing FAQs, the primary example and imagery are Windows-centric. There are no PowerShell-heavy examples or exclusive references to Windows tools, but the ordering and example selection favor Windows over Linux.
Recommendations
  • Provide parallel examples and screenshots for both Windows and Linux VMs when discussing cost estimation in the Azure portal.
  • Ensure that references to VM types and pricing include both Windows and Linux equally, or use neutral language and imagery.
  • When discussing features like auto-shutdown, clarify any differences or parity between Windows and Linux VM management.
  • Review other examples and screenshots throughout the documentation to ensure Linux scenarios are represented alongside Windows.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/renew-savings-plan.md ...-management-billing/savings-plan/renew-savings-plan.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes using the Azure portal UI for managing savings plan renewals, without mentioning command-line or automation options. There are no examples using Azure CLI, Bash, or Linux-native tools, nor is PowerShell mentioned. However, the instructions implicitly assume a graphical interface, which is more commonly associated with Windows environments, and do not provide parity for Linux users who may prefer CLI or automation.
Recommendations
  • Add instructions and examples for managing savings plan renewals using Azure CLI, including sample commands for Linux/macOS users.
  • Explicitly mention cross-platform tools (Azure CLI, REST API) and provide links to their documentation.
  • Ensure that automation options are described for both Windows (PowerShell) and Linux (Bash, CLI), if available.
  • Clarify that the Azure portal is accessible from any OS/browser, but highlight alternative methods for users who prefer command-line or automated workflows.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-billing/billing-troubleshoot-azure-payment-issues.md ...t-billing/billing-troubleshoot-azure-payment-issues.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Microsoft Edge and Internet Explorer for troubleshooting browser issues, without mentioning Linux browsers or providing Linux-specific guidance. There are no examples or instructions tailored for Linux users, and the troubleshooting steps assume a Windows environment.
Recommendations
  • Include troubleshooting steps for popular Linux browsers such as Firefox and Chrome, with instructions for opening private/incognito sessions.
  • Add notes clarifying that the Azure portal is accessible from any modern browser and operating system.
  • Provide parity in examples and guidance for users on Linux and macOS platforms, not just Windows.
  • Avoid referencing only Windows-specific tools or browsers; mention cross-platform alternatives where relevant.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-subscription/troubleshoot-sign-in-issue.md ...roubleshoot-subscription/troubleshoot-sign-in-issue.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents browser troubleshooting steps with a Windows-first approach, listing Edge and Chrome before Safari, and omits Linux-specific browser instructions or examples. There are no references to Linux browsers (such as Firefox) or Linux-specific troubleshooting steps, nor any mention of command-line alternatives that Linux users might use.
Recommendations
  • Include Linux-specific browser instructions, such as steps for Firefox and Chromium on Linux.
  • Add troubleshooting examples for clearing cache and cookies on Linux browsers.
  • Present browser options in a neutral order (e.g., alphabetical or by market share) rather than prioritizing Windows browsers.
  • Mention command-line alternatives for clearing browser data on Linux (e.g., using terminal commands to clear cache for Firefox or Chromium).
  • Explicitly state that the steps apply to all platforms, and provide platform-specific notes where necessary.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/download-azure-daily-usage.md ...ement-billing/understand/download-azure-daily-usage.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and Azure CLI without providing platform-specific guidance or examples for Linux or macOS users. There are no mentions of Linux-specific tools, shell commands, or alternative workflows (e.g., Bash, curl, scripting patterns). All screenshots and navigation instructions assume a GUI workflow typical of Windows users. The CLI section does not clarify cross-platform compatibility or provide examples for Linux environments.
Recommendations
  • Add explicit notes confirming that Azure CLI commands work on Linux, macOS, and Windows, and link to installation instructions for each platform.
  • Include Linux/macOS-specific examples, such as using Bash scripts, curl, or jq to process downloaded usage files.
  • Provide guidance for automating downloads and processing usage data on Linux systems, including sample shell scripts.
  • Add screenshots or terminal output examples from Linux environments to illustrate parity.
  • Mention cross-platform considerations (e.g., file paths, environment variables) when discussing CLI usage.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-microsoft-customer-agreement-across-tenants.md ...bscription-microsoft-customer-agreement-across-tenants.md
Medium Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving the service principal ID, but the PowerShell example is given after the CLI example. There are no explicit Linux-specific instructions or examples, but the use of Azure CLI (which is cross-platform) mitigates this. However, the presence of Azure PowerShell (traditionally associated with Windows) and the lack of explicit mention of Linux or bash scripting may suggest a mild Windows-first and PowerShell-heavy bias.
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
  • Add bash shell examples where relevant, especially for REST API calls (e.g., using curl or httpie) to demonstrate Linux parity.
  • Clarify that Azure PowerShell is available cross-platform, but also provide equivalent bash or shell scripting examples for Linux users.
  • Consider including a table or section summarizing command options for Windows (PowerShell), Linux (bash), and macOS users.
  • Where portal instructions are given, note any OS-agnostic aspects to further reduce perceived bias.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/billing-subscription-transfer.md ...gement-billing/manage/billing-subscription-transfer.md
Medium Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes the transfer process using the Azure Portal web interface, with all screenshots and instructions tailored to a graphical user interface. There are no command-line examples provided, such as Azure CLI or PowerShell, which are cross-platform (with Azure CLI being especially Linux-friendly). There is no mention of Linux-specific tools, nor are there any references to performing these actions from non-Windows environments. The documentation implicitly assumes users will interact via a browser, which is platform-agnostic, but omits parity for users who prefer or require automation or command-line workflows, which are common in Linux environments.
Recommendations
  • Add equivalent instructions for performing subscription transfer using Azure CLI commands, which are cross-platform and widely used on Linux.
  • If possible, provide PowerShell examples as well, but ensure Azure CLI is presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that all steps can be performed from any OS via the Azure Portal, but highlight command-line alternatives for automation and Linux users.
  • Include links to Azure CLI documentation for managing subscriptions and billing, and provide example commands for common transfer scenarios.
  • Review screenshots and language to ensure they do not assume a Windows environment (e.g., avoid showing Windows-specific browser UI or terminology).
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/billing-subscription-transfer.md ...gement-billing/manage/billing-subscription-transfer.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes the transfer process using the Azure portal web interface, with screenshots and instructions that implicitly assume a Windows-centric experience. There are no examples or mentions of Linux-specific tools, command-line interfaces (such as Azure CLI), or cross-platform automation options. All instructions and troubleshooting steps focus on GUI navigation, which is most commonly associated with Windows environments, and there is no guidance for users who may prefer or require Linux-native workflows.
Recommendations
  • Add equivalent instructions for performing subscription transfers using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples or references for automating the transfer process via PowerShell and Bash, highlighting parity between Windows and Linux scripting environments.
  • Mention that the Azure portal is accessible from any modern browser on Linux, and clarify that the process is not limited to Windows users.
  • Provide troubleshooting steps and next actions that include CLI commands, not just portal navigation.
  • Ensure that screenshots and instructions do not implicitly assume a Windows environment (e.g., avoid Windows-specific UI elements or terminology).
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/manage-azure-discount.md ...ost-management-billing/manage/manage-azure-discount.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation exclusively uses the Azure portal (a web GUI) for all management tasks and does not provide any command-line examples, such as Azure CLI or PowerShell. While this avoids explicit Windows/Powershell bias, it implicitly favors Windows users by omitting Linux-friendly CLI instructions. There is no mention of Linux tools, shell commands, or cross-platform automation patterns, and the only tool referenced is the Azure portal, which is most commonly used by Windows users. There are no examples for Azure CLI, which is widely used on Linux and macOS.
Recommendations
  • Add Azure CLI examples for all major operations (moving, viewing, deleting, tagging discount resources), as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that all operations can be performed via Azure CLI and provide links to relevant CLI documentation.
  • If PowerShell is referenced in related documentation, ensure Azure CLI equivalents are provided and shown before or alongside PowerShell examples.
  • Include notes or sections for automation and scripting approaches suitable for Linux environments.
  • Clarify that the Azure portal is accessible from any OS, but provide parity for users who prefer command-line or automated workflows.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-subscription/troubleshoot-sign-in-issue.md ...roubleshoot-subscription/troubleshoot-sign-in-issue.md
Medium Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides browser troubleshooting steps that reference Edge and Chrome (and Safari), but omits Linux-specific browsers (such as Firefox) and does not mention Linux-specific instructions for clearing cache or cookies. The order of browser instructions consistently lists Edge (a Microsoft product) first, which may reinforce a Windows-centric perspective. There are no command-line or OS-specific instructions, but the lack of Linux browser examples and the prioritization of Edge indicate a subtle Windows bias.
Recommendations
  • Include instructions for Firefox, which is widely used on Linux, for clearing cache/cookies and private browsing.
  • Add a note or section for Linux users, clarifying that steps for Chrome/Firefox apply to Linux as well, and specify any differences if present.
  • Rotate the order of browser instructions or use alphabetical order to avoid consistently prioritizing Edge.
  • Explicitly mention that the instructions are applicable across operating systems where possible, or provide OS-specific notes as needed.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/microsoft-customer-agreement/onboard-microsoft-customer-agreement.md ...omer-agreement/onboard-microsoft-customer-agreement.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented around Microsoft-specific tools and portals (Azure portal, Microsoft Admin Center, Power BI, Microsoft 365 admin center) and does not provide any platform-specific command-line examples or automation instructions. There are no references to Windows-only scripting (e.g., PowerShell), but the documentation assumes use of web-based Microsoft portals and tools, which are most commonly associated with Windows environments. There are no Linux-specific instructions, CLI examples, or cross-platform automation guidance, and all video and tutorial links focus on the GUI experience.
Recommendations
  • Add examples and guidance for using the Azure CLI and Azure REST APIs for onboarding and managing MCA, including sample commands that work on Linux, macOS, and Windows.
  • Include automation examples using cross-platform tools such as Azure CLI, Bash scripts, or Python, not just references to the Azure portal or Microsoft Admin Center.
  • Explicitly mention that the Azure portal and Admin Center are accessible from any modern browser on any OS, to clarify cross-platform compatibility.
  • Provide links to documentation or tutorials that cover command-line and programmatic approaches to MCA management, not just GUI/video resources.
  • If possible, include sample workflows for onboarding and billing management that can be performed from Linux or macOS environments.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/software-costs-not-included.md ...nt-billing/savings-plan/software-costs-not-included.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Windows VM software costs and related meters, without mentioning Linux or other operating systems. There are no examples or explanations for Linux VM scenarios, nor is there any discussion of software costs or meters that might apply to non-Windows environments. This creates a Windows-first perspective and omits information relevant to Linux users.
Recommendations
  • Add a section explicitly addressing software costs for Linux VMs, even if to state that there are no additional software meters for standard Linux distributions.
  • Include a comparative table or statement clarifying how savings plans apply to both Windows and Linux VMs.
  • If there are software costs for Linux (e.g., for premium distributions or third-party software), list those meters as well.
  • Use inclusive language throughout, such as 'Windows and Linux VMs', rather than only referencing Windows.
  • Provide links to documentation about licensing and costs for Linux and other non-Windows OSes in Azure.
GitHub Create Pull Request
← Previous Page 13 of 15 Next →