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 326-350 of 365 flagged pages
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/automate/automation-ingest-usage-details-overview.md
...g/automate/automation-ingest-usage-details-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows subtle Windows bias by mentioning Microsoft Excel as the example spreadsheet application for opening CSV files, without naming any Linux alternatives. There are no command-line examples or automation scripts, but when tools are mentioned, they are Windows-centric or Microsoft-branded. No Linux-specific tools, workflows, or examples are provided, and the documentation does not address cross-platform considerations for data ingestion or analysis.
Recommendations
- When mentioning spreadsheet applications, include cross-platform options such as LibreOffice Calc or Google Sheets alongside Microsoft Excel.
- If providing examples for downloading or processing CSV files, include both Windows (PowerShell, Excel) and Linux (bash, awk, LibreOffice) workflows.
- Explicitly state that the APIs and exported CSV files can be used on any platform, and provide sample scripts or command-line instructions for both Windows and Linux environments.
- Reference open-source or platform-agnostic tools where possible, and avoid implying that Microsoft tools are required.
- Add a section or note about cross-platform compatibility for cost data analysis and ingestion.
Create Pull Request
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/billing-tags.md
...articles/cost-management-billing/costs/billing-tags.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively describes how to apply billing tags using the Azure portal, which is a web-based interface accessible from any OS. However, there are no examples or references to command-line or automation methods (such as Azure CLI, PowerShell, or REST API), which are often used in cross-platform or Linux environments. If automation were discussed, there is a risk that only Windows/PowerShell examples would be provided first or exclusively, but in this case, the omission itself is a form of bias as it does not address Linux users' needs for automation or scripting.
Recommendations
- Add examples for applying billing tags using Azure CLI, which is cross-platform and widely used on Linux.
- If PowerShell examples are added, ensure Azure CLI or REST API examples are also provided and presented first or alongside PowerShell.
- Explicitly mention that all operations can be performed from any OS via the portal, but also provide automation options for Linux users.
- Include links to relevant Azure CLI and REST API documentation for managing billing tags.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/protect-tenants-subscriptions.md
...gement-billing/manage/protect-tenants-subscriptions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references deletion of resource groups and resources with a link that includes an 'azure-powershell' tab, suggesting a preference for Windows tooling. There are no explicit Linux or cross-platform CLI examples or references, and the documentation does not mention or provide parity for Linux users or tools such as Azure CLI or Bash scripts.
Recommendations
- Include examples and references for cross-platform tools such as Azure CLI and Bash scripts alongside or instead of PowerShell.
- Ensure that linked articles and code samples provide both PowerShell and Azure CLI (or REST API) instructions, and make this explicit in the main documentation.
- Avoid defaulting to Windows-centric tooling in links or examples; if PowerShell is mentioned, provide equivalent Linux-friendly alternatives.
- Add a section or note clarifying that all actions can be performed from any OS using cross-platform tools, and provide links to relevant documentation.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/understand-ea-roles.md
.../cost-management-billing/manage/understand-ea-roles.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on the Azure portal (a web interface) and does not provide any command-line examples or automation guidance. There is no mention of PowerShell, Windows-specific tools, or scripts, but there is also a complete absence of Linux CLI tools (such as Azure CLI) or cross-platform automation methods. All instructions and examples assume use of the Azure portal, which is accessible from any OS, but the lack of parity in mentioning or demonstrating CLI-based management (which is common for Linux users) creates a subtle bias by omission.
Recommendations
- Add examples for managing EA roles using Azure CLI commands, which are cross-platform and widely used by Linux users.
- Include references to REST API usage with curl or other Linux-native tools for automation.
- Where possible, provide both portal-based and CLI/API-based instructions for all administrative tasks.
- Explicitly mention that all tasks can be performed from any OS via the portal, but highlight automation options for Linux users.
- Ensure that links to further documentation include both PowerShell and Azure CLI where applicable.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining the service principal ID, but the PowerShell example is presented second. However, the presence of PowerShell (a Windows-centric tool) as a primary scripting example, and the absence of any explicit Linux shell or Bash-specific guidance (beyond the Azure CLI, which is cross-platform), indicates a slight Windows bias. There are no Linux- or Bash-specific examples, and PowerShell is highlighted as an alternative, which may not be as familiar or readily available to Linux users.
Recommendations
- Ensure that all command-line examples are provided in both Azure CLI (which is cross-platform) and Bash shell script formats where appropriate.
- If PowerShell examples are included, clarify that Azure CLI commands work natively on Linux/macOS and Windows, and consider providing Bash script equivalents for automation scenarios.
- Avoid assuming the use of PowerShell as the default scripting environment; instead, present Azure CLI or REST API examples first, as these are more universally accessible.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide troubleshooting notes for non-Windows environments if needed.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/reservation-utilization.md
...gement-billing/reservations/reservation-utilization.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page primarily references Windows-centric tools such as PowerShell and Power BI, without providing equivalent examples or explicit guidance for Linux users. There are no command-line examples for Linux shells, and the focus on Power BI and PowerShell may implicitly favor Windows environments.
Recommendations
- Include Azure CLI examples for retrieving reservation utilization, with sample commands that work cross-platform (Linux, macOS, Windows).
- Mention and provide examples for using Bash or other Linux shells where appropriate.
- Clarify that Power BI Desktop is only available on Windows, and suggest alternative reporting tools or methods for Linux users (such as using the API with Python or other cross-platform tools).
- Ensure that references to PowerShell are accompanied by Azure CLI or REST API examples, to provide parity for Linux users.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/calculate-ea-reservations-savings.md
...ling/reservations/calculate-ea-reservations-savings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Excel for data preparation and calculation steps, with no mention of Linux-compatible spreadsheet tools (such as LibreOffice Calc or Google Sheets) or command-line alternatives. All screenshots and instructions are tailored to Excel, which is primarily a Windows (and Mac) application, and there are no examples or guidance for users on Linux or those preferring open-source tools.
Recommendations
- Explicitly mention and provide parallel instructions for Linux-compatible spreadsheet applications such as LibreOffice Calc and Google Sheets.
- Include screenshots and step-by-step examples using LibreOffice Calc or Google Sheets alongside Excel.
- Offer a brief section or appendix on how to perform the calculations using command-line tools (e.g., csvkit, awk, pandas in Python) for advanced or Linux-native users.
- Use more generic terminology (e.g., 'spreadsheet application' instead of 'Excel') throughout the documentation, except where Excel-specific features are referenced.
- Where possible, provide downloadable example files in open formats and ensure formulas are compatible with non-Excel spreadsheet software.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/nutanix-bare-metal.md
...-management-billing/reservations/nutanix-bare-metal.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively references the Azure portal (a web interface) for all reservation management tasks and does not provide any command-line examples, such as using Azure CLI, PowerShell, or REST APIs. While this avoids explicit Windows/Powershell bias, it implicitly favors GUI-based workflows, which are more familiar to Windows users. There are no examples or guidance for Linux users who may prefer or require command-line or automation-friendly approaches (e.g., Azure CLI on Linux).
Recommendations
- Add step-by-step examples for purchasing and managing reservations using the Azure CLI, which is cross-platform and widely used on Linux.
- Include REST API references or examples for advanced automation scenarios, which are platform-agnostic.
- If PowerShell examples are added, ensure equivalent Azure CLI examples are provided and presented first or side-by-side.
- Explicitly mention that all tasks can be performed from Linux, macOS, or Windows using the Azure CLI or REST API, not just the Azure portal.
- Provide links to Azure CLI and REST API documentation for reservation management.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively references Excel for data preparation and calculation, with all instructions and screenshots based on the Excel interface. There are no examples or guidance for Linux users or those using non-Microsoft spreadsheet tools (such as LibreOffice Calc, Google Sheets, or command-line tools like awk/csvkit). The workflow assumes a Windows-centric environment, implicitly prioritizing Windows tools and patterns.
Recommendations
- Include parallel instructions and screenshots for at least one popular Linux-compatible spreadsheet application, such as LibreOffice Calc or Google Sheets.
- Mention and provide examples for command-line CSV processing tools (e.g., csvkit, awk, pandas) for users who may not use GUI spreadsheet software.
- Rephrase references to 'Excel' as 'spreadsheet application' throughout, and clarify that the process is applicable to any tool capable of handling CSV files.
- Where possible, provide downloadable sample data and formulas in formats compatible with both Excel and LibreOffice Calc.
- Add a note or section specifically addressing Linux/macOS users, outlining alternative tools and any differences in steps or formulas.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/manage-savings-plan.md
...management-billing/savings-plan/manage-savings-plan.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes management of Azure savings plans using the Azure Portal GUI, with no mention of command-line tools or automation options. There are no examples using Azure CLI, Bash, or Linux-native workflows, nor are there any references to PowerShell or Windows-specific tools. However, the lack of Linux/CLI examples and the focus on GUI navigation (which is more common in Windows-centric documentation) results in a subtle Windows-first and missing Linux example bias.
Recommendations
- Add equivalent instructions for managing savings plans using the Azure CLI, with example commands for common tasks (e.g., changing scope, viewing details, modifying auto-renewal).
- Include Bash shell examples for Linux users, especially for automation or scripting scenarios.
- Explicitly mention cross-platform tools (Azure CLI, REST API) and provide links to their documentation.
- Clarify that all management actions can be performed from any OS using the Azure Portal, but highlight automation options for both Windows and Linux users.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides browser troubleshooting steps that reference Edge and Chrome in detail, with Edge (a Microsoft product) consistently listed first and described in greater detail. There are no Linux-specific instructions or references to Linux browsers or environments. The guidance assumes the use of browsers and settings most common on Windows or macOS, omitting mention of Linux distributions, Firefox (a popular Linux browser), or command-line alternatives for clearing cache/cookies.
Recommendations
- Include instructions for Firefox, which is widely used on Linux systems, for private browsing and clearing cache/cookies.
- Add a note or section addressing Linux users, specifying where browser settings may differ or how to access them on common Linux desktop environments.
- Consider providing command-line alternatives for clearing browser data on Linux (e.g., using rm to delete browser cache directories).
- Avoid always listing Edge first; rotate browser order or group instructions by operating system.
- Explicitly mention that the steps apply to all platforms, and highlight any platform-specific differences where relevant.
Cost Management Billing
Troubleshoot Azure payment issues
...t-billing/billing-troubleshoot-azure-payment-issues.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows minor Windows bias by referencing Microsoft Edge and Internet Explorer for troubleshooting browser issues, specifically linking to an Edge support article and mentioning InPrivate browsing in those browsers. No Linux/macOS browser equivalents (e.g., Firefox Private Window, Chrome Incognito) are mentioned, nor are there examples or troubleshooting steps tailored for non-Windows platforms. However, most troubleshooting steps are platform-agnostic and do not require Windows-specific tools or commands.
Recommendations
- Include instructions for private/incognito browsing in popular Linux/macOS browsers such as Firefox and Chrome.
- Reference browser-agnostic terminology (e.g., 'open a private/incognito window in your browser') rather than naming only Windows browsers.
- Add links to support articles for private browsing in Firefox and Chrome.
- Explicitly state that the Azure portal is accessible from any modern browser on any OS.
Cost Management Billing
Optimize your cloud investment with Cost Management
...st-management-billing/costs/cost-mgt-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits minor Windows bias by referencing Windows-specific licensing programs (Azure Hybrid Benefit for Windows Server and SQL Server) and mentioning Windows tools (Power BI) for reporting and integration. These references are presented without Linux/macOS equivalents or alternatives. However, the majority of the content is platform-agnostic, focusing on Azure APIs, services, and general cost management practices.
Recommendations
- Include examples or references to Linux/macOS-compatible analytics and reporting tools (e.g., Grafana, Kibana, or open-source BI solutions) alongside Power BI.
- Clarify that Azure Hybrid Benefit is specific to Windows Server/SQL Server and mention that Linux VMs have different licensing and cost optimization strategies (e.g., reserved instances, spot VMs).
- Add explicit statements or examples showing how Linux workloads can be optimized for cost in Azure, such as using reserved instances or spot pricing for Linux VMs.
- Ensure that any automation or scripting examples (if added in future revisions) include cross-platform options (e.g., Bash, Python, CLI) and not just PowerShell.
Cost Management Billing
Quickstart - Create a budget with an Azure Resource Manager template
...nagement-billing/costs/quick-create-budget-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias by consistently mentioning Azure PowerShell before Azure CLI and REST API when listing deployment options. The main deployment flow relies on the Azure portal, which is cross-platform, but references to PowerShell and links to PowerShell-specific documentation appear before Linux/macOS-friendly alternatives. CLI examples are present, but PowerShell is given equal or greater prominence throughout.
Recommendations
- List Azure CLI before Azure PowerShell when presenting deployment alternatives, as CLI is more universally available across platforms.
- Provide direct links to both CLI and PowerShell deployment documentation, not just PowerShell.
- Explicitly state that all command-line examples work on Linux/macOS and Windows, and clarify any platform-specific differences.
- Ensure that screenshots and walkthroughs do not imply a Windows-only experience (e.g., avoid showing only Windows-style UI elements).
- Where possible, add bash script examples alongside PowerShell for resource cleanup and other tasks.
Cost Management Billing
Grant access to create Azure Enterprise subscriptions
...-billing/manage/grant-access-to-create-subscription.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for REST, PowerShell, and Azure CLI, with PowerShell (a Windows-centric tool) featured prominently and described in detail, including instructions for using Azure Cloud Shell. PowerShell examples are presented before Azure CLI, which is more cross-platform. There is also mention of ARMClient, a tool that is primarily used on Windows, with no mention of Linux-native alternatives. No Linux/macOS-specific issues or workarounds are discussed, and the portal instructions are generic but do not address platform-specific differences.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI and REST examples work on Linux/macOS, and provide any necessary platform-specific notes.
- Include instructions or links for installing and using Azure CLI on Linux/macOS.
- Suggest Linux-native tools (e.g., curl, httpie) for REST API calls instead of or alongside ARMClient.
- Clarify that Azure Cloud Shell is available in-browser and not tied to Windows.
- Add troubleshooting notes for Linux/macOS users if any step is known to differ.
Cost Management Billing
Programmatically create MCA subscriptions across tenants
...bscription-microsoft-customer-agreement-across-tenants.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining the service principal ID, but the PowerShell example is given immediately after the CLI example, and both are presented as equivalent options. There are no Linux- or macOS-specific tools or shell commands (such as Bash scripts or REST calls via curl) shown for any step, and the only command-line tools referenced are Azure CLI and Azure PowerShell. However, Azure CLI is cross-platform, and the REST API examples are also platform-agnostic. There is a slight ordering bias in listing Azure CLI before PowerShell, but no critical steps are Windows-only.
Recommendations
- Add explicit Bash/curl examples for REST API calls to demonstrate Linux/macOS parity.
- Clarify that Azure CLI commands work identically on Windows, Linux, and macOS.
- If PowerShell is mentioned, note that PowerShell Core is cross-platform, or provide Bash alternatives.
- Consider including a table or section summarizing equivalent commands for Windows (PowerShell), Linux/macOS (Bash/curl), and Azure CLI.
Cost Management Billing
Programmatically create Azure subscriptions for a Microsoft Partner Agreement with the latest APIs
...ically-create-subscription-microsoft-partner-agreement.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for REST, Azure CLI, and Azure PowerShell for all major steps. However, PowerShell is referenced in every section, even when it is not supported for certain operations (with explicit notes to use CLI or REST instead). PowerShell is given equal or greater prominence than Azure CLI, and installation instructions for PowerShell modules are included, which may be less relevant for Linux/macOS users. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of platform-specific considerations for CLI usage. The documentation does not reference Windows-only tools directly, but the repeated PowerShell focus and lack of Linux/macOS context creates a mild Windows bias.
Recommendations
- Remove PowerShell tabs/examples for steps where PowerShell is not supported, rather than including a placeholder.
- Add explicit Bash or shell script examples for Azure CLI usage to demonstrate Linux/macOS parity.
- Clarify that Azure CLI works cross-platform and provide any platform-specific installation or usage notes.
- Reorder examples so that Azure CLI is shown before PowerShell, or alternate the order to avoid Windows-first perception.
- Include notes or links for Linux/macOS users regarding installation of Azure CLI and any differences in command usage.
Cost Management Billing
Programmatically create Azure subscriptions with legacy APIs
...manage/programmatically-create-subscription-preview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for REST, Azure PowerShell, and Azure CLI for EA subscriptions, but consistently presents PowerShell examples before Azure CLI. PowerShell is a Windows-centric tool, and the instructions explicitly mention opening Azure Cloud Shell and selecting PowerShell, which may be confusing or less relevant for Linux/macOS users. There are no Bash or shell script examples, and no mention of platform-specific considerations for Linux/macOS users. For MCA and MPA subscriptions, only REST API examples are provided, which are platform-neutral.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide guidance for installation/use on those platforms.
- Add Bash or shell script examples where appropriate, especially for automation scenarios.
- Clarify that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
- Avoid language that assumes use of Windows tools (e.g., PowerShell) as the default.
Cost Management Billing
Protect tenants and subscriptions from abuse and fraud attacks
...gement-billing/manage/protect-tenants-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Microsoft-specific tools and portals (Azure portal, Microsoft 365 Admin Center, Microsoft Entra ID) throughout, with no mention of Linux/macOS command-line alternatives or cross-platform tooling. The related content also links to resources that often default to Azure PowerShell tabs, and there is no explicit parity for Linux users or CLI-based workflows.
Recommendations
- Include examples and guidance for using Azure CLI and REST APIs, which are cross-platform and work on Linux/macOS.
- When linking to articles with platform-specific instructions (e.g., deleting resource groups), ensure Linux/bash examples are present and referenced equally.
- Explicitly mention that actions can be performed via CLI or portal, and provide links to both sets of instructions.
- Add a section or note clarifying cross-platform support and pointing to Linux/macOS documentation where relevant.
Cost Management Billing
Buy an Azure reservation
...gement-billing/reservations/prepare-buy-reservation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell before Azure CLI in the 'Next steps' section and lists PowerShell as a primary automation method alongside REST APIs and CLI. No explicit Linux/macOS examples or tools are prioritized, and PowerShell (traditionally Windows-centric) is highlighted before CLI, which is more cross-platform. However, the page does mention Azure CLI and REST APIs, which are platform-neutral, and does not provide any example commands or instructions that are Windows-only.
Recommendations
- List Azure CLI before PowerShell in automation sections to reflect its cross-platform nature.
- Explicitly state that both PowerShell and CLI are available on Windows, Linux, and macOS.
- Provide example commands for both PowerShell and CLI in relevant sections.
- Add a note or section highlighting Linux/macOS parity for reservation management tasks.
Cost Management Billing
What is Azure savings plans for compute?
...-billing/savings-plan/savings-plan-compute-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows virtual machines and Windows-specific metering before Linux, and discusses Windows software costs and Azure Hybrid Benefit (which is Windows-centric) in multiple places. While Linux is referenced, Windows examples and considerations are presented first and in more detail, and there are no Linux-specific examples or guidance.
Recommendations
- Present Linux and Windows examples side-by-side when discussing VM metering and costs.
- Explicitly clarify that the compute meter applies equally to Linux and Windows, and detail any differences in licensing or cost structure for Linux VMs.
- Add a section or examples for Linux-specific scenarios, such as how savings plans apply to Linux VMs and any relevant cost considerations.
- Mention open-source licensing or cost implications for Linux VMs, if any, to balance the focus on Windows licensing.
- Avoid presenting Windows considerations before Linux unless there is a technical reason.
Cost Management Billing
View and download Azure usage and charges
...ement-billing/understand/download-azure-daily-usage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes how to view and download Azure usage and charges using the Azure portal, which is a web-based interface accessible across platforms. However, there is a subtle Windows bias: all screenshots and step-by-step instructions reference the Azure portal UI, which is visually and functionally identical across platforms, but there are no explicit Linux/macOS CLI or automation examples except for a brief mention of Azure CLI. The Azure CLI section does not provide OS-specific instructions or highlight Linux/macOS usage patterns, and there are no PowerShell examples, which avoids a stronger Windows bias. The page does not mention Linux-specific tools, nor does it provide parity for Linux users in terms of alternative workflows or troubleshooting.
Recommendations
- Add explicit instructions or notes confirming that the Azure portal and Azure CLI are fully supported on Linux and macOS, and provide links to installation guides for these platforms.
- Include example commands for downloading usage data using Bash or other Linux-native tools (e.g., curl, wget) for automation.
- If screenshots are shown, clarify that the UI is identical across platforms, or provide screenshots from Linux/macOS browsers.
- Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, CLI authentication).
Cost Management Billing
Plan to manage Azure costs
...ost-management-billing/understand/plan-manage-costs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Example
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias, most notably in the example for estimating VM costs, which specifically references a Windows VM and provides a screenshot labeled 'A1 Windows VM.' There are no equivalent Linux VM examples or screenshots, and Windows is mentioned first when discussing VM sizing and cost estimation. While the page does link to both Linux and Windows VM pricing FAQs, practical examples and visuals are Windows-centric. No PowerShell or Windows-only tools are referenced, and most instructions are platform-neutral, focusing on the Azure portal and APIs.
Recommendations
- Include Linux VM examples and screenshots alongside Windows VM examples when demonstrating cost estimation.
- When discussing VM sizing and cost estimation, mention both Windows and Linux VMs equally, or use generic VM examples.
- Ensure that any platform-specific features (such as auto-shutdown) clarify parity and differences for both Windows and Linux VMs.
- Review all examples and visuals to ensure balanced representation of operating systems.
Cost Management Billing
Troubleshoot Azure payment issues
...t-billing/billing-troubleshoot-azure-payment-issues.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows minor Windows bias by referencing Microsoft Edge and Internet Explorer for troubleshooting browser issues, and linking to a Microsoft support article about InPrivate browsing. No Linux/macOS browser equivalents (such as Chrome Incognito or Firefox Private Browsing) are mentioned, and no examples or troubleshooting steps are tailored for non-Windows platforms. However, most of the content is platform-neutral and focuses on Azure portal usage.
Recommendations
- Include instructions for private browsing in Chrome and Firefox, which are commonly used on Linux and macOS.
- Mention that the Azure portal is accessible from any modern browser, including those on Linux/macOS.
- Add troubleshooting steps or links relevant to Linux/macOS users, such as clearing cookies in Chrome/Firefox or using their private browsing modes.
- Avoid referencing Windows-specific browsers exclusively; provide cross-platform alternatives.
Cost Management Billing
Tutorial - Seed a historical cost dataset with the Exports API
...e/tutorial-seed-historical-cost-dataset-exports-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists PowerShell's Invoke-RestMethod as a primary way to query the API, and it is the only command-line example tool called out by name (besides curl, which is listed last). The ordering of tools puts Visual Studio (Windows-centric), Insomnia, Bruno, PowerShell, and then curl, which subtly prioritizes Windows tools and workflows. No Linux/macOS-specific shell examples (e.g., bash scripts, wget) are provided, nor are there explicit Linux/macOS command-line walkthroughs.
Recommendations
- Provide explicit Linux/macOS shell examples using curl or wget, including sample commands.
- Reorder the list of tools to avoid Windows-first bias (e.g., list curl before PowerShell).
- Include a sample bash script for automating the API calls.
- Mention cross-platform tools like httpie.
- Clarify that all API calls can be made from any OS, and provide parity in example walkthroughs.