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 151-175 of 365 flagged pages
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/scope-level/overview-azure-hybrid-benefit-scope.md ...ing/scope-level/overview-azure-hybrid-benefit-scope.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by exclusively referencing Windows Server and SQL Server on Windows, with no mention of Linux-based SQL Server deployments or examples. All references to SQL Server VMs and IaaS extensions point to Windows-specific documentation. There are no examples or guidance for users running SQL Server on Linux VMs in Azure, nor are Linux tools or management patterns discussed.
Recommendations
  • Include explicit references to SQL Server on Linux, clarifying whether Azure Hybrid Benefit applies equally to Linux-based SQL Server VMs.
  • Provide parallel documentation links and examples for registering SQL Server on Linux VMs with the SQL IaaS Agent extension.
  • Mention any differences (or confirm parity) in license assignment, management, and monitoring for SQL Server on Linux versus Windows.
  • If certain features or extensions are Windows-only, clearly state this and provide alternative guidance for Linux users.
  • Ensure that all screenshots, walkthroughs, and step-by-step instructions are inclusive of both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows-based VM examples (Standard_DS1_v2 Windows virtual machine) and referencing Windows software costs. There are no examples or mentions of Linux VMs or Linux-specific considerations, and the only software cost discussion is for Windows. This may give the impression that reservations are primarily or only relevant for Windows workloads, and omits guidance for Linux users.
Recommendations
  • Include parallel examples using a popular Linux VM SKU (e.g., Standard_DS1_v2 running Ubuntu or another Linux distribution) alongside the Windows example.
  • Discuss how reservation usage and software costs apply to Linux VMs, including any differences (such as the absence of extra OS licensing charges for most Linux distributions).
  • Reference Linux-specific documentation or considerations where relevant, such as Azure Hybrid Benefit for Linux or BYOL (Bring Your Own License) scenarios.
  • Ensure that screenshots and CSV file examples include both Windows and Linux VM reservations to illustrate parity.
  • Add a section or note explicitly stating that the reservation process and CSV analysis apply equally to Linux VMs, and highlight any differences.
GitHub 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows environments by prioritizing PowerShell-based instructions and tools, referencing Windows-centric patterns, and not providing explicit Linux/macOS guidance or examples. PowerShell is mentioned and exemplified before Azure CLI, and there is no discussion of cross-platform shell usage or Linux-specific considerations. The documentation assumes familiarity with Windows tools and does not address potential differences or requirements for Linux users.
Recommendations
  • Provide explicit Linux/macOS instructions and examples, especially for authentication and environment setup (e.g., clarify that Azure CLI and PowerShell Core are cross-platform, and show usage in bash/zsh).
  • When listing tooling (e.g., PowerShell, Azure CLI), present Azure CLI examples first or in parallel, as it is natively cross-platform.
  • Include notes or sections on any OS-specific prerequisites, such as package managers for installing Azure CLI or PowerShell on Linux/macOS.
  • Where PowerShell cmdlets are referenced, clarify if they require Windows PowerShell or if they work with PowerShell Core on Linux/macOS.
  • Add screenshots or terminal output examples from Linux/macOS environments where applicable.
  • Explicitly state that all command-line steps can be performed on Linux/macOS, and provide troubleshooting tips for non-Windows users.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page demonstrates a strong bias toward Windows by exclusively providing Azure PowerShell scripts and instructions for managing Azure reservations. There are no examples or guidance for using cross-platform tools such as Azure CLI, nor are there any references to Linux or macOS environments. The use of PowerShell, which is traditionally associated with Windows (despite now being cross-platform), and the absence of Azure CLI or REST API examples, limits accessibility for Linux and macOS users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts and management tasks, as Azure CLI is widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is cross-platform, and provide installation instructions for Linux/macOS if PowerShell usage is retained.
  • Include REST API examples or references for advanced users who may prefer scripting without PowerShell.
  • Ensure that all instructions and screenshots (if any) are applicable to users on Linux, macOS, and Windows.
  • Review and update the documentation to use neutral, cross-platform language (e.g., 'command line' instead of 'PowerShell prompt').
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/prepay-hana-large-instances-reserved-capacity.md ...tions/prepay-hana-large-instances-reserved-capacity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides examples using armclient with PowerShell syntax and Azure PowerShell code blocks. There are no examples or instructions for Linux or cross-platform CLI tools (such as Azure CLI or curl), nor is there mention of how to perform these tasks on non-Windows systems. The use of PowerShell and armclient (which is most commonly used on Windows) is presented as the default and only method, indicating a Windows-first and PowerShell-heavy bias.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
  • Include REST API call examples using curl or httpie, which are standard tools on Linux.
  • Use generic code blocks (e.g., ```bash or ```sh) for REST API examples, not just ```azurepowershell-interactive.
  • Explicitly mention that the operations can be performed from any OS, and clarify any tool prerequisites for Linux/macOS users.
  • If armclient is required, provide installation and usage instructions for Linux/macOS, or suggest alternatives.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing PowerShell scripts for license usage analysis, without providing equivalent examples or guidance for Linux users. No mention is made of Bash, Azure CLI, or cross-platform tooling, and the only script linked is a PowerShell script. There are no Linux-specific instructions or examples, and the documentation assumes the use of Windows-centric tools.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts for analyzing SQL license usage, ensuring Linux and macOS users can follow along.
  • Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, or provide guidance for cross-platform compatibility.
  • Include references to cross-platform tools (such as Azure CLI) wherever PowerShell is mentioned, and offer side-by-side examples.
  • Review all instructions and ensure that Linux users are not required to use Windows-specific tools or interfaces.
  • Add a note clarifying platform compatibility for any scripts or tools referenced.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation exclusively uses Microsoft Excel for all examples and instructions, implicitly assuming a Windows environment. There are no examples or guidance for users on Linux or macOS, such as using LibreOffice Calc or command-line tools (e.g., csvkit, pandas). Keyboard shortcuts and UI references are specific to Excel, and no alternatives are mentioned. This creates a Windows-centric experience and may alienate users on other platforms.
Recommendations
  • Include parallel instructions and screenshots for at least one cross-platform or Linux-native spreadsheet application, such as LibreOffice Calc or Google Sheets.
  • Mention and provide basic examples for command-line tools (e.g., csvkit, pandas) to manipulate and analyze CSV usage files, especially for large files.
  • Use neutral language when referring to spreadsheet applications (e.g., 'spreadsheet application such as Excel or LibreOffice Calc') and avoid assuming Excel is available.
  • Provide keyboard shortcuts and menu navigation for both Windows and Linux/macOS environments where relevant.
  • Add a section or callout for Linux/macOS users outlining alternative workflows for analyzing large CSV files.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
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 CSV report handling and troubleshooting. All instructions for importing and formatting CSV files are tailored to Excel, with no mention of Linux-compatible tools (such as LibreOffice Calc or command-line utilities). There are no examples or guidance for users on Linux or macOS platforms, and the documentation assumes the use of Windows-centric workflows and tools throughout.
Recommendations
  • Include instructions for opening and formatting CSV reports using cross-platform tools such as LibreOffice Calc, Google Sheets, or command-line utilities (e.g., csvkit, awk, pandas).
  • Provide examples or notes for Linux and macOS users, especially in sections related to CSV handling and report downloads.
  • Avoid assuming that users will use Microsoft Excel by default; offer alternative workflows for non-Windows environments.
  • Where screenshots or step-by-step guides are provided, consider adding parallel instructions for at least one major Linux-compatible tool.
  • Explicitly state that the Azure portal is accessible from any modern browser on any OS, and clarify that report downloads are not limited to Windows users.
GitHub Create Pull Request
Cost Management Billing Tutorial - Optimize centrally managed Azure Hybrid Benefit for SQL Server ...ling/scope-level/tutorial-azure-hybrid-benefits-sql.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell scripts as the primary method for analyzing Azure SQL license usage and links only to Windows-specific instructions for registering SQL Server VMs with the SQL IaaS Agent Extension. No Linux or cross-platform alternatives are mentioned, and Windows tools/patterns are presented first and exclusively.
Recommendations
  • Include equivalent CLI or Bash examples for gathering SQL license usage, or clarify if PowerShell scripts work on Linux/macOS via PowerShell Core.
  • Add links to documentation for registering SQL Server VMs running on Linux, if supported, or explicitly state if the registration process is Windows-only.
  • Where PowerShell is referenced, note platform compatibility and provide guidance for Linux/macOS users.
  • If certain steps are Windows-only, clarify this in the documentation to set expectations for Linux users.
GitHub Create Pull Request
Cost Management Billing Save on SAP HANA Large Instances with an Azure reservation ...-docs/prepay-hana-large-instances-reserved-capacity.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation provides all command-line examples using armclient with PowerShell syntax and Azure PowerShell code blocks. There is no mention of Linux/macOS equivalents, nor are cross-platform tools or shell examples (such as Bash/cURL) provided. This creates friction for Linux/macOS users who may not use PowerShell or armclient in the same way.
Recommendations
  • Include equivalent examples using Bash and cURL or HTTPie for REST API calls.
  • Clarify whether armclient is cross-platform and provide installation/use instructions for Linux/macOS if applicable.
  • Use generic REST API examples (e.g., with cURL) alongside PowerShell to ensure parity.
  • Explicitly state that the process is platform-agnostic if true, and highlight any platform-specific requirements.
GitHub Create Pull Request
Cost Management Billing Manage Azure Reservations ...nt-billing/reservations/manage-reserved-vm-instance.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation provides command-line examples exclusively using PowerShell cmdlets for reservation management tasks (e.g., splitting a reservation), without offering Azure CLI equivalents or REST API sample calls. This creates friction for Linux/macOS users, who typically use Azure CLI or direct API calls rather than PowerShell. The page also refers to PowerShell as the primary automation tool, implicitly favoring Windows environments.
Recommendations
  • Add Azure CLI examples for all reservation management tasks currently demonstrated with PowerShell, especially for splitting reservations and updating scope.
  • Include REST API sample requests (with curl or HTTP examples) for relevant operations to ensure cross-platform accessibility.
  • Clearly indicate that PowerShell is one of several supported tools, and link to Azure CLI and REST API documentation for parity.
  • Where screenshots or instructions reference PowerShell, provide equivalent steps for CLI and API usage.
GitHub Create Pull Request
Cost Management Billing Calculate EA reservations cost savings ...ling/reservations/calculate-ea-reservations-savings.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily demonstrates the reservation savings calculation process using Microsoft Excel, a Windows-centric application, and all step-by-step instructions and screenshots are based on Excel. While it briefly mentions that other spreadsheet applications can be used, no examples or guidance are provided for Linux/macOS alternatives (e.g., LibreOffice Calc, Google Sheets). There are no command-line or open-source tool examples, and the workflow assumes a GUI-heavy, Windows-first approach.
Recommendations
  • Provide explicit instructions or examples for performing the same calculations in LibreOffice Calc, Google Sheets, or other cross-platform spreadsheet tools.
  • Include screenshots or step-by-step guidance for at least one non-Windows spreadsheet application.
  • Mention command-line alternatives (e.g., using Python/pandas or csvkit) for users who prefer scripting or do not use GUI spreadsheet tools.
  • Clarify any differences in CSV handling or formula syntax between Excel and other spreadsheet applications.
GitHub Create Pull Request
Cost Management Billing SQL IaaS extension registration options for Cost Management administrators ...billing/scope-level/sql-iaas-extension-registration.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides PowerShell script examples and references for checking and completing SQL IaaS Agent extension registration, but does not mention or provide equivalent CLI, Bash, or Linux/macOS-specific instructions. The registration process is described primarily through Azure portal steps and PowerShell automation, with no discussion of cross-platform alternatives. This creates friction for Linux/macOS users who may prefer or require non-PowerShell tooling.
Recommendations
  • Add Azure CLI examples for checking registration status and enabling SQL IaaS Agent extension registration, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state whether PowerShell Core (pwsh) is supported for the provided scripts, and clarify any Windows-only requirements.
  • Provide Bash script or REST API examples for automation, or link to relevant cross-platform documentation.
  • Include a note on platform compatibility for the PowerShell scripts, and suggest alternatives for non-Windows environments.
GitHub Create Pull Request
Cost Management Billing Permissions to View and Manage Azure Reservations ...t-management-billing/reservations/view-reservations.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a section on managing reservation access using PowerShell but does not mention or provide examples for cross-platform alternatives such as Azure CLI, which is widely used on Linux and macOS. The only command-line tool referenced is Azure PowerShell, and the only command shown is a PowerShell cmdlet. There are no CLI or REST API examples, and the documentation does not clarify whether the described PowerShell steps are available or equivalent on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for managing reservation RBAC roles, including commands for viewing and assigning roles.
  • Clarify whether the PowerShell steps can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Explicitly state that Azure PowerShell is cross-platform if that is the case, or provide installation/use guidance for Linux/macOS users.
  • Wherever possible, present both PowerShell and CLI examples side by side, or at least mention both approaches.
GitHub Create Pull Request
Cost Management Billing Transition to centrally managed Azure Hybrid Benefit ...-management-billing/scope-level/transition-existing.md
Medium Priority View Details →
Scanned: 2026-01-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a PowerShell script as the primary method for analyzing SQL Server license usage across Azure subscriptions, without mentioning or providing equivalent Linux/macOS-friendly alternatives (such as Azure CLI, Bash, or REST API examples). PowerShell is natively available only on Windows, and while cross-platform versions exist, many Linux/macOS users expect CLI or Bash examples. The documentation also refers to PowerShell before mentioning APIs or other methods, indicating a Windows-first approach.
Recommendations
  • Provide equivalent examples using Azure CLI or Bash scripts for analyzing SQL Server license usage.
  • Explicitly mention REST API options for license usage analysis and link to relevant API documentation.
  • Clarify that PowerShell Core is available cross-platform, but also offer instructions for Linux/macOS users who may prefer CLI or Bash.
  • Where PowerShell scripts are referenced, add notes or links to cross-platform installation guides.
GitHub Create Pull Request
Cost Management Billing Tutorial - Create and manage budgets ...anagement-billing/costs/tutorial-acm-create-budgets.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of PowerShell as the first and most detailed programmatic example for creating and managing budgets. Windows-centric tools (PowerShell) are presented before cross-platform alternatives (CLI, Terraform, ARM templates), and PowerShell is described as the recommended method for EA customers, even though REST API and CLI are more platform-neutral. The CLI and Terraform examples are present, but PowerShell is given prominence and more context, which may create friction for Linux/macOS users.
Recommendations
  • Present CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Add explicit notes clarifying platform compatibility for each tool (e.g., PowerShell, CLI, Terraform).
  • Ensure REST API and ARM template methods are equally emphasized as programmatic options.
  • Provide links to installation and usage guides for CLI and Terraform, similar to PowerShell.
  • Avoid language that recommends PowerShell as the default for EA customers; instead, recommend REST API or CLI for broader compatibility.
GitHub Create Pull Request
Cost Management Billing Manage Azure Reservations ...nt-billing/reservations/manage-reserved-vm-instance.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, especially in the 'Split a single reservation into two reservations' section, where only PowerShell commands are provided for splitting and updating reservations. There are no CLI (az) or REST API examples shown, and PowerShell is presented as the primary method, which is most commonly used on Windows. The rest of the documentation relies heavily on Azure Portal instructions, which are cross-platform, but command-line automation is Windows-centric in this context.
Recommendations
  • Add equivalent Azure CLI (az) examples for splitting and updating reservations, as the CLI is cross-platform and preferred by Linux/macOS users.
  • Include REST API request examples for reservation management tasks to support automation on any platform.
  • When presenting command-line instructions, show both PowerShell and CLI examples side-by-side, or indicate platform applicability.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, but prioritize CLI for parity.
GitHub Create Pull Request
Cost Management Billing Troubleshoot Azure subscription sign-in issues ...roubleshoot-subscription/troubleshoot-sign-in-issue.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently lists Microsoft Edge (a Windows-centric browser) first when describing troubleshooting steps, and omits explicit instructions for clearing cache/cookies in Safari (the default browser on macOS) and Firefox (popular on Linux/macOS). No Linux-specific browser guidance or parity for browser settings is provided.
Recommendations
  • Include explicit instructions for clearing cache/cookies in Safari and Firefox, as these are commonly used on macOS and Linux.
  • Alternate the order of browser examples so that Windows-centric browsers are not always listed first.
  • Add a note or section acknowledging Linux/macOS users and providing parity in troubleshooting steps for their environments.
  • Consider including command-line alternatives (e.g., clearing browser data via terminal) for advanced Linux/macOS users.
GitHub Create Pull Request
Cost Management Billing Assign permissions to Cost Management APIs ...nt-billing/automate/cost-management-api-permissions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the primary CLI tool for assigning roles, without mentioning or providing examples for cross-platform alternatives such as Azure CLI or REST API calls. The instructions and linked resources focus on PowerShell, which is traditionally associated with Windows, and do not offer Linux/macOS-specific guidance or examples. No Linux/macOS command-line patterns or tools are discussed, and PowerShell is mentioned before any other automation method.
Recommendations
  • Add Azure CLI examples for assigning roles to service principals, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example requests for role assignment to demonstrate platform-agnostic automation.
  • Explicitly mention that Azure PowerShell is available cross-platform, but also provide parity with CLI and API methods.
  • Reorder examples so that platform-neutral methods (CLI, API) are presented before or alongside PowerShell.
  • Add a note clarifying that all steps can be performed on Linux/macOS, and link to relevant documentation for those platforms.
GitHub Create Pull Request
Cost Management Billing Tutorial - Seed a historical cost dataset with the Exports API ...e/tutorial-seed-historical-cost-dataset-exports-api.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation lists PowerShell's Invoke-RestMethod as a primary example for querying the API, and PowerShell is mentioned before curl (the standard Linux/macOS tool). Windows-centric tools (Visual Studio, PowerShell) are listed before cross-platform or Linux-native tools. No Linux/macOS shell examples (e.g., bash/curl command lines) are provided, and the only scripting example referenced is PowerShell.
Recommendations
  • Provide explicit curl command-line examples for Linux/macOS users alongside PowerShell examples.
  • List cross-platform tools (curl, Insomnia, Bruno) before Windows-specific tools in the 'popular ways to query the API' section.
  • Include bash or shell scripting examples for API calls.
  • Clarify that all examples are platform-agnostic or provide platform-specific guidance where necessary.
GitHub Create Pull Request
Cost Management Billing Quickstart - Create a budget with Bicep ...-management-billing/costs/quick-create-budget-bicep.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and management tasks, but PowerShell examples are always shown immediately after CLI and use Windows-centric variable syntax (e.g., arrays with @()). There is no explicit mention of Linux/macOS shell equivalents for variable assignment, nor any guidance for Bash users on how to adapt PowerShell examples. The CLI examples are cross-platform, but the variable assignment syntax shown (single-quoted, parenthesized lists) is not standard Bash and may confuse Linux/macOS users.
Recommendations
  • Add explicit Bash/Linux/macOS variable assignment examples for all CLI commands, using standard Bash array or string syntax.
  • Clarify that Azure CLI commands work on all platforms and provide platform-specific notes where variable syntax differs.
  • Reorder examples to show CLI (cross-platform) first, and PowerShell (Windows-centric) second, with clear headings.
  • Add a note or section explaining differences in variable assignment between PowerShell and Bash, with examples.
  • Review and update sample variable assignments to use syntax that works natively in Bash/zsh (e.g., myContactEmails='user1@contoso.com user2@contoso.com' or as an array).
GitHub Create Pull Request
Cost Management Billing Assign Enterprise Agreement roles to service principals ...illing/manage/assign-roles-azure-service-principals.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced as the primary automation tool, with explicit links to PowerShell documentation and commands (e.g., New-Guid). Windows-specific tools (Visual Studio, PowerShell) are listed before cross-platform alternatives (Curl, Insomnia, Bruno). There are no Linux/macOS-specific command-line examples, and the only mention of generating GUIDs is via PowerShell or a web tool, omitting standard Linux/macOS methods. The examples and screenshots are all Azure portal-based, which is platform-neutral, but the automation focus leans toward Windows.
Recommendations
  • Provide Linux/macOS command-line examples for tasks such as GUID generation (e.g., 'uuidgen' command).
  • Include Azure CLI examples alongside PowerShell, as Azure CLI is cross-platform.
  • List cross-platform tools (Curl, Insomnia, Bruno) before Windows-specific ones (PowerShell, Visual Studio) when suggesting API query methods.
  • Explicitly mention that all steps can be performed on Linux/macOS, and highlight any platform-specific caveats.
  • Add troubleshooting tips for Linux/macOS users if any step differs from Windows.
GitHub Create Pull Request
Cost Management Billing Add or change Azure subscription administrators ...illing/manage/add-change-subscription-administrator.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 all administrative tasks and does not mention or provide examples for command-line tools such as Azure CLI or PowerShell. While this avoids explicit Windows/Powershell bias, it implicitly favors GUI-based workflows, which are more commonly associated with Windows environments. There are no Linux/macOS-specific instructions or examples, nor is there mention of cross-platform command-line alternatives.
Recommendations
  • Add instructions for performing administrator role assignments using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include PowerShell examples for completeness, but ensure Azure CLI examples are presented first or alongside them.
  • Explicitly state that all steps can be performed from any OS using the Azure portal, and highlight cross-platform command-line options.
  • Provide links to Azure CLI and PowerShell documentation for role assignment tasks.
GitHub Create Pull Request
Cost Management Billing Azure billing and cost management budget scenario ...ment-billing/manage/cost-management-budget-scenario.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (Visual Studio, PowerShell’s Invoke-RestMethod, ARMClient) are mentioned first or exclusively in several places, especially for API testing and authentication. PowerShell is highlighted as a primary method for interacting with REST APIs, and ARMClient (which is Windows-centric) is used for authentication, with instructions referencing Visual Studio and Windows file paths. While curl and cross-platform API clients (Insomnia, Bruno) are mentioned, Windows tools are consistently listed first and in more detail. There are no explicit Linux/macOS examples for ARMClient usage or alternative authentication/token generation methods.
Recommendations
  • Provide Linux/macOS equivalents for ARMClient authentication, such as using Azure CLI (az login, az account get-access-token) and document those steps.
  • List cross-platform tools (curl, Insomnia, Bruno) before or alongside Windows-specific tools like Visual Studio and PowerShell.
  • Include example commands for curl and Azure CLI for API calls and authentication.
  • Clarify that ARMClient is Windows-only and suggest alternatives for non-Windows users.
  • Add notes or sections for Linux/macOS users where file paths, tools, or procedures differ.
GitHub Create Pull Request
Cost Management Billing Link a partner ID to your account that’s used to manage customers ...cles/cost-management-billing/manage/link-partner-id.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation displays a moderate Windows bias. Command-line examples for both PowerShell and Azure CLI are provided, but all sample commands use Windows-style paths (C:\>) and PowerShell is presented before Azure CLI. There is no mention of Linux/macOS-specific considerations, such as shell differences, installation steps, or example outputs for non-Windows platforms. The use of 'C:\>' as the prompt in CLI examples may confuse Linux/macOS users. No Linux/macOS-specific troubleshooting or guidance is offered.
Recommendations
  • Provide Linux/macOS-specific command-line examples, using appropriate shell prompts (e.g., $ or %).
  • Clarify that both PowerShell and Azure CLI are cross-platform, and provide installation instructions for Linux/macOS.
  • Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side.
  • Add notes or sections addressing platform-specific differences, such as authentication flows or environment setup.
  • Avoid using Windows-style prompts (C:\>) in CLI examples; use neutral or platform-appropriate prompts.
GitHub Create Pull Request
← Previous Page 7 of 15 Next →