Cost Management Billing
591
Total Pages
510
Linux-Friendly Pages
81
Pages with Bias
13.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
177 issues found
Showing 26-50 of 177 flagged pages
Cost Management Billing
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
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples first and in greater detail, referencing Windows-specific tools (PowerShell) and patterns, and mentioning Windows-centric approaches before their Linux equivalents. The CLI example is present but follows PowerShell, and there is no mention of Linux-specific shell usage or cross-platform scripting nuances. The tutorial also references the Azure portal and mobile app, which are platform-neutral, but the programmatic sections favor Windows tools and workflows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide shell-specific notes (e.g., bash, zsh) where relevant.
- Include Linux/macOS-specific instructions for installing and using Azure CLI and Terraform, such as package manager commands (apt, yum, brew).
- Add notes or examples for scripting budget creation using bash or other common Linux shells.
- Clarify that PowerShell Core is available on Linux/macOS, and provide installation instructions for those platforms.
- Ensure that REST API usage is highlighted as platform-agnostic and provide curl or httpie examples for Linux users.
- Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., avoid referencing Windows-only UI elements or terminology).
Create Pull Request
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/link-partner-id-power-apps-accounts.md
...-billing/manage/link-partner-id-power-apps-accounts.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-centric tools and workflows. PowerShell is featured prominently and described before Azure CLI, with no mention of Bash or Linux-native scripting. The Azure portal (a GUI tool most commonly used on Windows) is the primary method described for PAL association, and all command-line examples use PowerShell or Azure CLI, with no Linux-specific instructions or examples. There is no discussion of Linux environments, nor are there examples using Bash, shell scripts, or Linux package managers. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux parity.
Recommendations
- Add explicit Bash and shell script examples for PAL association and resource attribution.
- Include instructions for installing and using Azure CLI and PowerShell on Linux, including any platform-specific caveats.
- Mention cross-platform compatibility of Azure CLI and PowerShell, and clarify any differences in usage or output on Linux.
- Provide screenshots or walkthroughs using Linux desktop environments (e.g., GNOME, KDE) where GUI steps are shown.
- Reference Linux package managers (e.g., apt, yum) for installing Azure CLI and PowerShell.
- Add a section discussing best practices for Linux users, including automation and scripting approaches common in Linux environments.
Cost Management Billing
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 presenting all command-line examples with Windows-style prompts (e.g., 'C:\>'), listing PowerShell instructions before Azure CLI, and not providing any explicit Linux/macOS-specific guidance or examples. The installation and usage instructions for both PowerShell and Azure CLI assume a Windows environment, with no mention of Bash, Linux/macOS terminal conventions, or cross-platform differences.
Recommendations
- Provide Linux/macOS-specific examples alongside or immediately after Windows examples, using appropriate shell prompts (e.g., '$' for Bash).
- Clarify that both PowerShell and Azure CLI are cross-platform, and provide installation and usage instructions for Linux/macOS environments.
- Avoid using Windows-style paths and prompts exclusively; instead, show both 'C:\>' and '$' where relevant.
- Explicitly mention any platform-specific prerequisites or differences in behavior.
- Consider including screenshots or instructions from the Azure portal as it appears on non-Windows platforms, if applicable.
Cost Management Billing
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 demonstrates a strong Windows bias by exclusively providing a PowerShell script for automating billing role migration, instructing users to select PowerShell in Azure Cloud Shell, and omitting any Bash or cross-platform scripting alternatives. The instructions and screenshots prioritize PowerShell usage, and there is no mention of how to accomplish the task using Linux-native tools or shell environments.
Recommendations
- Provide equivalent Bash (or Azure CLI) script examples for Linux and macOS users.
- Update instructions to include both PowerShell and Bash options in Azure Cloud Shell, with guidance for each.
- Clarify that the process can be completed on any platform, and specify any platform-specific prerequisites or differences.
- Include screenshots and step-by-step instructions for both PowerShell and Bash workflows.
- Reference cross-platform tools (e.g., Azure CLI, REST API via curl/jq) where possible, not just Windows-centric tools.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for obtaining the service principal ID, but lists the Azure CLI (cross-platform) example first. However, there is a notable presence of PowerShell-specific instructions, and no explicit mention of Linux or bash scripting environments outside of the Azure CLI. There are no Linux-specific shell examples or guidance for users who may not have access to PowerShell, and the documentation does not clarify cross-platform compatibility for all steps. The rest of the process uses REST API calls, which are platform-agnostic, but the lack of explicit Linux/bash examples or notes may hinder Linux users.
Recommendations
- Ensure that for every PowerShell example, an equivalent bash or shell script example is provided, especially for common Linux environments.
- Explicitly state that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Where REST API calls are shown, provide example invocations using curl or similar Linux-native tools.
- Add a note at the beginning of the 'Programmatically create a subscription' section clarifying that all steps can be performed from Linux, macOS, or Windows, and link to Azure CLI installation instructions for Linux.
- Consider including a table summarizing which tools/commands are available on which platforms (e.g., Azure CLI, Azure PowerShell, curl, etc.).
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-microsoft-partner-agreement.md
...ically-create-subscription-microsoft-partner-agreement.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation shows a moderate Windows/PowerShell bias. PowerShell is consistently presented as a first-class automation method alongside REST and Azure CLI, even though the Azure CLI is fully cross-platform and REST is OS-agnostic. In several steps, PowerShell tabs are present but simply instruct users to use Azure CLI or REST, indicating lack of parity or support. The documentation also references PowerShell module installation and usage patterns typical of Windows environments, and PowerShell examples are given equal or greater prominence than CLI. There is no mention of Linux-specific considerations, shells, or scripting environments.
Recommendations
- Ensure all PowerShell examples have equivalent, tested Azure CLI examples, and vice versa.
- Clearly state that Azure CLI is fully supported and cross-platform, and recommend it for Linux/macOS users.
- Avoid presenting PowerShell as the default or first automation method unless it is the only supported option.
- When PowerShell is not supported, consider omitting the tab or providing a clear message about cross-platform alternatives.
- Add notes or sections for Linux/macOS users, including shell-specific tips (e.g., Bash scripting, environment variables).
- Review and balance the order of example tabs so that REST and Azure CLI are not consistently placed after PowerShell.
- Where PowerShell module installation is discussed, provide parallel instructions for Azure CLI extension installation.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Microsoft-centric tools and platforms (Azure portal, Microsoft 365 Admin Center, Microsoft Entra ID), with no mention of Linux-specific workflows, CLI examples, or cross-platform alternatives. References to deletion and transfer actions are tied to Microsoft portals and admin centers, which are typically accessed via Windows environments. The only command-line reference in related content is to Azure PowerShell, with no Bash or Azure CLI examples provided, indicating a Windows-first and Windows-tools bias.
Recommendations
- Include Azure CLI and Bash examples alongside Azure PowerShell for resource deletion and subscription management.
- Explicitly mention cross-platform access methods (e.g., using Azure CLI on Linux/macOS) for all actions.
- Provide links or references to Linux/macOS documentation where applicable.
- Clarify that actions can be performed from any OS, not just Windows, and highlight any differences or prerequisites for non-Windows users.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/prepare-buy-reservation.md
...gement-billing/reservations/prepare-buy-reservation.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page displays a mild Windows bias. While it mentions multiple automation options (Azure portal, APIs, PowerShell, CLI), PowerShell is listed before CLI, and the only automation example link that is not generic is for PowerShell. There are no explicit Linux or Bash examples, and the CLI is only mentioned after PowerShell. No Linux-specific tools or workflows are referenced.
Recommendations
- Ensure CLI (az CLI) examples and documentation links are presented alongside or before PowerShell, especially since az CLI is cross-platform and popular among Linux users.
- Add explicit Bash/Linux shell examples where automation or scripting is discussed.
- Include references to Linux-native tools or workflows where relevant, such as using Bash scripts with az CLI for automation.
- Balance the order of tool mentions (e.g., 'PowerShell or CLI' vs. 'CLI or PowerShell') to avoid implying a Windows-first approach.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing PowerShell and Power BI as primary tools for interacting with reservation utilization data, without providing equivalent examples or explicit instructions for Linux users. There are no CLI (e.g., Azure CLI) or API usage examples, and no mention of Linux-native tools or workflows.
Recommendations
- Add explicit Azure CLI examples for viewing reservation utilization, including command-line instructions suitable for Linux/macOS users.
- Include REST API usage examples with curl or similar cross-platform tools.
- Clarify that Power BI is available on Windows only, and suggest alternative reporting tools or methods for Linux users (such as exporting data to CSV and using open-source BI tools).
- Ensure that any PowerShell instructions are accompanied by Azure CLI equivalents.
- Review all tool references to ensure Linux parity and avoid implying that only Windows tools are supported.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/view-purchase-refunds.md
...nagement-billing/reservations/view-purchase-refunds.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by focusing on the Azure portal (a web GUI), Power BI (a Windows-centric tool), and REST APIs, with no mention of Linux-native tools, CLI commands, or cross-platform scripting examples. Power BI is highlighted as the primary reporting tool, which is not natively available on Linux. There are no examples using Azure CLI, Bash, or other Linux-friendly methods, and Windows-oriented tools are mentioned before any platform-neutral alternatives.
Recommendations
- Add Azure CLI and Bash examples for viewing reservation transactions, including sample commands and expected outputs.
- Mention and provide examples for using cross-platform tools (e.g., Azure CLI, Python scripts) to access reservation data.
- Clarify that Power BI is not natively available on Linux and suggest alternatives, such as exporting data via API and analyzing it with open-source tools (e.g., Jupyter Notebook, pandas).
- Ensure that REST API usage is demonstrated with both Windows (e.g., PowerShell, curl for Windows) and Linux (e.g., curl, wget, jq) command-line examples.
- Reorder sections or provide parallel instructions so that Linux-friendly methods are presented alongside or before Windows-specific tools.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/understand-reserved-instance-usage.md
...ing/reservations/understand-reserved-instance-usage.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page consistently uses Windows-based virtual machines (VMs) as the default example and discusses Windows software costs in detail, without providing equivalent Linux-based examples or mentioning Linux-specific considerations. There are no Linux VM scenarios, nor are there references to Linux software costs or Azure Hybrid Benefit for Linux. This creates a Windows-centric perspective and omits guidance for Linux users.
Recommendations
- Add parallel examples using Linux VMs (e.g., Standard_DS1_v2 running Ubuntu or Red Hat) alongside Windows examples.
- Discuss Linux-specific considerations, such as the absence of additional software charges for most Linux distributions.
- Mention Azure Hybrid Benefit as it applies to Linux (if relevant), or clarify that it is Windows-only.
- Ensure that tables and screenshots include both Windows and Linux VM reservation scenarios.
- Include a note or section addressing differences in reservation usage and billing for Linux VMs.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/view-reservations.md
...t-management-billing/reservations/view-reservations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides detailed instructions for managing Azure reservations primarily through the Azure portal and Azure PowerShell. There are explicit references to PowerShell for access management, but there are no equivalent examples or guidance for Linux users (e.g., using Azure CLI or Bash). The only command-line tool mentioned is PowerShell, which is more closely associated with Windows environments, and there are no cross-platform command-line examples or alternatives.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell instructions, especially for granting and viewing RBAC access to reservations.
- Explicitly mention that Azure CLI is cross-platform and supported on Linux, macOS, and Windows.
- Where PowerShell is referenced, provide Bash/Azure CLI alternatives side-by-side or in tabs.
- Clarify that all portal-based instructions are OS-agnostic, and highlight any differences if they exist.
- Review related content and ensure that Linux users are not required to use PowerShell for any task that can be accomplished with Azure CLI.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/permission-view-manage.md
...agement-billing/savings-plan/permission-view-manage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell script examples for managing savings plan permissions, with no mention of equivalent Azure CLI (cross-platform) or Bash examples. This creates a bias toward Windows/PowerShell users and may hinder Linux or macOS users who prefer or require CLI/Bash tools. The exclusive use of PowerShell and the absence of Azure CLI or REST API (curl) examples indicate a lack of Linux parity.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts, using 'az role assignment' commands.
- Include Bash/curl examples for REST API operations where applicable.
- Explicitly state that the operations can be performed from any platform (Windows, Linux, macOS) and provide guidance for non-Windows users.
- Consider reordering sections or providing tabs to present PowerShell, Azure CLI, and REST API examples side-by-side.
- Mention that Azure PowerShell is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/tutorial-azure-hybrid-benefits-sql.md
...ling/scope-level/tutorial-azure-hybrid-benefits-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-based SQL Server VM registration guides, omitting Linux equivalents. The only script/tool mentioned for usage analysis is a PowerShell script, with no mention of Bash, CLI, or Linux-native alternatives. All example links and instructions for registering SQL Server VMs point to Windows-specific documentation, and there is no guidance for Linux SQL Server VM scenarios.
Recommendations
- Include links and instructions for registering SQL Server VMs running on Linux, such as documentation for the SQL IaaS Agent Extension on Linux.
- Provide Linux/Bash/CLI examples for gathering license usage and availability details, alongside PowerShell examples.
- Mention Linux-compatible tools or scripts for analyzing Azure Hybrid Benefit usage, or clarify cross-platform compatibility of existing tools.
- Ensure that examples and walkthroughs explicitly address both Windows and Linux SQL Server VM scenarios, or note any limitations.
- Add a section or note clarifying Azure Hybrid Benefit support for SQL Server on Linux VMs, including any differences in management or registration.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/sql-iaas-extension-registration.md
...billing/scope-level/sql-iaas-extension-registration.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only Windows-centric examples and instructions. All command-line automation references use PowerShell scripts, and the main registration walkthrough links to a Windows-specific documentation page. There are no Linux-specific instructions, examples, or mentions of Linux tools (such as Bash, Azure CLI, or Linux VM management patterns). The documentation assumes users are operating in a Windows environment and does not address Linux VM scenarios or provide parity for Linux administrators.
Recommendations
- Add Linux-specific instructions for SQL IaaS Agent extension registration, including examples using Azure CLI and Bash.
- Include references and links to Linux documentation pages, such as managing SQL Server on Linux VMs.
- Provide sample scripts for Linux environments, and clarify any differences in the registration process for Linux VMs.
- Mention Linux VM management tools and patterns alongside Windows/PowerShell options, ensuring both are covered equally.
- Ensure that all steps and automation options are available for both Windows and Linux users, and highlight any platform-specific considerations.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/transition-existing.md
...-management-billing/scope-level/transition-existing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell scripts for usage analysis and not providing equivalent examples for Linux users. All scripting and automation guidance is centered on PowerShell, with no mention of Bash, Azure CLI, or cross-platform tools. There are no Linux-specific instructions or examples, and the only automation tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux and macOS users, especially for tasks like analyzing SQL license usage.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for non-Windows systems.
- Include sample commands and scripts for Linux environments, ensuring parity in automation and scripting guidance.
- Reference cross-platform tools and patterns (such as Azure CLI) alongside or before Windows-specific tools.
- Add notes or sections clarifying that all features and management experiences are available regardless of the user's operating system.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/troubleshoot-billing/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables.md
...tomer-agreement-billing-issues-usage-file-pivot-tables.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Microsoft Excel for all examples and screenshots, implicitly prioritizing a Windows-centric workflow. There are no examples or instructions for Linux users or for using open-source spreadsheet tools like LibreOffice Calc. Keyboard shortcuts and menu paths are specific to Excel, and no alternatives are provided for Linux environments.
Recommendations
- Add parallel examples and screenshots using LibreOffice Calc or another cross-platform spreadsheet tool.
- Include instructions for opening and manipulating CSV files on Linux, such as using Calc or command-line tools (e.g., csvkit, pandas).
- Mention that all steps can be performed on Linux or macOS with equivalent tools, and provide relevant shortcuts/menu paths.
- Consider providing a downloadable template or macro that works in both Excel and LibreOffice.
- Explicitly state that Excel is not required and list supported alternatives at the beginning of the article.
Cost Management Billing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/review-enterprise-agreement-bill.md
...billing/understand/review-enterprise-agreement-bill.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias primarily through exclusive references to Microsoft Excel for handling CSV report formatting issues, with no mention of Linux or cross-platform alternatives. All step-by-step instructions for viewing and manipulating billing data are based on the Azure portal, which is web-based and cross-platform, but the only tooling guidance for CSV manipulation assumes use of Excel on Windows. There are no examples or instructions for Linux users (e.g., using LibreOffice, OpenOffice, or command-line tools like awk/csvkit), nor is there guidance for handling CSV files outside of the Microsoft ecosystem.
Recommendations
- Add instructions for opening and formatting CSV files using Linux-compatible tools such as LibreOffice Calc, OpenOffice Calc, or command-line utilities (awk, csvkit, pandas).
- Include examples of how to inspect and manipulate CSV files on Linux/macOS, such as using 'cat', 'head', 'awk', or 'csvtool'.
- Mention that the Azure portal is accessible from any modern browser on Windows, Linux, or macOS to reinforce cross-platform compatibility.
- Provide troubleshooting steps for CSV import issues in non-Windows environments, including how to set delimiters and data formats in LibreOffice or OpenOffice.
- Consider adding a note or section on cross-platform best practices for handling Azure billing data and reports.
Cost Management Billing
Manage Azure Reservations
...nt-billing/reservations/manage-reserved-vm-instance.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides PowerShell-only examples for splitting reservations, with no equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. The documentation also refers to PowerShell cmdlets as the primary automation method, rather than presenting CLI or API options first or alongside.
Recommendations
- Add Azure CLI examples for splitting reservations, updating scope, and other management tasks.
- Include REST API sample requests for reservation management operations.
- Present CLI and API options alongside PowerShell, or list CLI first for cross-platform parity.
- Explicitly mention that PowerShell examples are for Windows users and provide links to CLI/API docs for Linux/macOS users.
Cost Management Billing
View Azure Reservation purchase and refund transactions
...nagement-billing/reservations/view-purchase-refunds.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references Power BI as a method to view reservation transactions, which is primarily a Windows tool and does not mention cross-platform alternatives or clarify Power BI's availability on Linux/macOS. No command-line or scripting examples (e.g., Azure CLI, Bash, PowerShell) are provided for Linux/macOS users, and the REST API section lacks concrete usage examples. The page does not provide Linux/macOS-specific guidance or parity for viewing reservation transactions outside the Azure portal.
Recommendations
- Clarify Power BI's platform support and mention any web-based or cross-platform alternatives for Linux/macOS users.
- Add examples using Azure CLI or Bash scripts to retrieve reservation transactions via the REST API, ensuring Linux/macOS users have actionable guidance.
- Provide sample REST API requests (e.g., using curl) for reservation transactions to help users on all platforms.
- Explicitly state if certain tools (like Power BI) are Windows-only and suggest alternatives where possible.
Cost Management Billing
Permissions to View and Manage Azure Reservations
...t-management-billing/reservations/view-reservations.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed instructions for managing Azure reservations primarily through the Azure portal and Azure PowerShell. PowerShell is featured as the only command-line automation example, with no mention of Azure CLI or Bash/Linux-native tools. The 'Grant access by using PowerShell' section is the only automation example provided, and PowerShell is referenced before any Linux-friendly alternatives. This creates friction for Linux/macOS users who may prefer or require Azure CLI or other cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell instructions, especially in the 'Grant access by using PowerShell' section.
- Explicitly mention that Azure CLI can be used for RBAC and reservation management, and link to relevant Azure CLI documentation.
- Where possible, provide Bash or shell script examples alongside PowerShell to improve accessibility for Linux/macOS users.
- Clarify that PowerShell Core is cross-platform, but also highlight Azure CLI as a first-class alternative.
Cost Management Billing
SQL IaaS extension registration options for Cost Management administrators
...billing/scope-level/sql-iaas-extension-registration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples and scripts exclusively for PowerShell, with no mention of Linux or macOS equivalents (such as Azure CLI or Bash). The registration process is described primarily through the Azure portal and PowerShell, both of which are Windows-centric. There are no instructions or examples for users on Linux or macOS platforms, creating friction for those users.
Recommendations
- Provide Azure CLI and/or Bash script examples for checking and registering SQL IaaS Agent extension, alongside PowerShell.
- Explicitly mention that the Azure portal is cross-platform and can be used from any OS, but clarify any limitations.
- If any steps are Windows-specific, clearly label them and offer alternative instructions for Linux/macOS users where possible.
- Link to cross-platform tooling documentation (e.g., Azure CLI docs) for managing SQL IaaS Agent extension.
Cost Management Billing
Transition to centrally managed Azure Hybrid Benefit
...-management-billing/scope-level/transition-existing.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell script as the only example for analyzing SQL Server license usage across Azure subscriptions. There are no equivalent examples or guidance for users on Linux or macOS platforms, nor are cross-platform alternatives (such as Azure CLI, Bash, or REST API) mentioned. This creates friction for non-Windows users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent examples using Azure CLI, Bash, or REST API for analyzing SQL Server license usage.
- Clearly indicate whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS), and provide installation instructions if so.
- If the script is Windows-only, explicitly state this and offer alternative methods for Linux/macOS users.
- Wherever possible, present cross-platform solutions first or alongside PowerShell examples to ensure parity.
Cost Management Billing
Calculate Enterprise Agreement (EA) savings plan cost savings
...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 uses Microsoft Excel for data preparation and calculation steps, with all screenshots and instructions tailored to Excel's Windows interface. There are no examples or guidance for Linux/macOS users or alternative spreadsheet tools (e.g., LibreOffice Calc, Google Sheets), despite a brief mention that other applications can be used.
Recommendations
- Provide explicit instructions and screenshots for at least one cross-platform spreadsheet tool (e.g., LibreOffice Calc, Google Sheets).
- Include notes or links to resources for opening and manipulating CSV files on Linux/macOS.
- Clarify any differences in formula syntax or filtering steps for non-Excel applications.
- Consider listing alternative command-line methods (e.g., using pandas in Python, csvkit) for users who prefer not to use GUI spreadsheet tools.
Cost Management Billing
Link a partner ID to your Power Platform and Dynamics Customer Insights accounts with your Azure credentials
...-billing/manage/link-partner-id-power-apps-accounts.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced frequently and in detail, with explicit cmdlet examples and guidance. The Azure portal (a GUI tool most commonly used on Windows) is presented as the primary method for PAL association, with CLI and PowerShell alternatives mentioned later. The PowerShell examples are more extensive than Azure CLI, and some product-specific instructions (e.g., changing owners) reference PowerShell cmdlets without equivalent Linux/macOS-friendly alternatives. There is no mention of Bash or shell scripting, and the overall flow assumes familiarity with Windows-centric tools.
Recommendations
- Provide Linux/macOS-specific instructions or notes, especially for Azure CLI usage and authentication.
- Ensure Azure CLI examples are as detailed as PowerShell examples, and consider showing CLI before PowerShell to reduce Windows-first bias.
- Mention cross-platform compatibility explicitly for all tools, including PowerShell Core and Azure CLI.
- Add troubleshooting or setup guidance for Linux/macOS environments (e.g., installing PowerShell Core, using Azure CLI on non-Windows OS).
- Where PowerShell is referenced for product-specific actions, provide equivalent Azure CLI or REST API instructions if available.