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 126-150 of 365 flagged pages
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Power BI (both Windows-centric tools) as primary methods for accessing reservation utilization data. There are no examples or instructions for Linux users (e.g., using Azure CLI or REST API from bash), and Windows tools are mentioned before any cross-platform alternatives. The lack of Linux-specific guidance or parity in examples makes it harder for non-Windows users to follow the documentation.
Recommendations
  • Add Azure CLI examples for viewing reservation utilization, with explicit instructions for Linux/macOS terminals.
  • Include REST API usage examples with curl or other cross-platform tools.
  • Mention Power BI alternatives or clarify Power BI Desktop's availability on non-Windows platforms.
  • Ensure that cross-platform methods (CLI, API) are described before or alongside Windows-specific tools like PowerShell.
  • Add a section or notes for Linux/macOS users to improve parity and accessibility.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive mention of Azure PowerShell for command-line management of reservations, without providing equivalent examples for Linux users (such as Azure CLI or Bash). The only non-portal automation example is PowerShell, which is typically associated with Windows environments. There is no mention of Linux-native tools, nor are cross-platform alternatives presented alongside PowerShell. Additionally, the PowerShell method is introduced before any discussion of cross-platform command-line options, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for managing reservation permissions, including role assignments and viewing reservations, to ensure parity for Linux and macOS users.
  • Explicitly mention that Azure CLI and REST API can be used for these tasks, and provide links or code snippets.
  • Where PowerShell is referenced, include a note or section about equivalent commands in Azure CLI.
  • Review and update automation sections to ensure cross-platform coverage, not just Windows/PowerShell.
  • Clarify that PowerShell Core is available cross-platform, but also provide CLI/Bash alternatives for users who prefer native Linux tools.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/save-compute-costs-reservations.md ...illing/reservations/save-compute-costs-reservations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools and terminology (e.g., PowerShell) are mentioned as purchase and management options, but Linux equivalents (such as Bash or Azure CLI on Linux) are not explicitly referenced. Windows-specific topics (e.g., Windows software costs, Azure Hybrid Benefit) are highlighted in the 'Next steps' section before Linux equivalents. There is limited mention of Linux-specific reservation scenarios, and examples or guidance for Linux users are sparse or missing.
Recommendations
  • Explicitly mention and provide examples for Linux users, such as using Azure CLI on Linux or Bash scripts, alongside PowerShell.
  • Ensure parity in 'Next steps' and reference sections by including Linux-focused articles and guidance at equal prominence to Windows topics.
  • Add examples or scenarios for purchasing and managing reservations from Linux environments, including screenshots or command-line instructions.
  • Clarify that reservation management is platform-agnostic and provide links to cross-platform tools and documentation.
  • When listing software plans, ensure Linux options (SUSE, Red Hat) are described with the same detail and placement as Windows options.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell script examples for managing savings plan permissions. There are no equivalent examples using cross-platform tools such as Azure CLI, nor is there mention of Bash or Linux shell usage. The reliance on PowerShell and the absence of Linux-oriented instructions or examples may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, if relevant, but still provide CLI alternatives.
  • Include Bash shell script examples where appropriate, especially for automation scenarios.
  • Review and update documentation to ensure parity between Windows and Linux/macOS instructions, tools, and examples.
  • Consider adding a section comparing PowerShell and Azure CLI usage for savings plan management, helping users choose the best tool for their platform.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/savings-plan/savings-plan-compute-overview.md ...-billing/savings-plan/savings-plan-compute-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific concepts (such as Windows VMs, Windows IP meter, and Windows software costs) are mentioned explicitly and before their Linux equivalents. There is a lack of Linux-specific examples or discussion of Linux licensing or software costs, and no parity in examples or guidance for Linux users. The documentation refers to Windows tools and patterns (e.g., Azure Hybrid Benefit for Windows licensing) without mentioning Linux alternatives or considerations.
Recommendations
  • Include explicit Linux VM examples and clarify how savings plans apply to Linux workloads, including any differences in metering or cost structure.
  • Discuss Linux licensing and software costs, if applicable, to provide parity with the Windows software cost discussion.
  • When mentioning Windows-specific meters or benefits, provide equivalent information for Linux (e.g., clarify that Linux VMs do not incur OS licensing costs, or mention any relevant Linux-specific benefits).
  • Ensure examples and guidance are balanced between Windows and Linux scenarios, especially in sections discussing how savings plans apply to different VM types.
GitHub Create Pull Request
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently referencing Windows Server and SQL Server in a Windows context, mentioning Windows tools and patterns (such as Windows Server VMs and SQL IaaS Agent extension) without providing Linux equivalents or examples. All instructions and references are tailored to Windows environments, with no mention of Linux-based SQL Server deployments or management patterns. The documentation also links to Windows-specific guides and omits any discussion of Linux licensing, deployment, or management within Azure Hybrid Benefit.
Recommendations
  • Include examples and instructions for managing Azure Hybrid Benefit with SQL Server on Linux VMs.
  • Mention and link to documentation for deploying and managing SQL Server on Linux in Azure.
  • Clarify whether Azure Hybrid Benefit applies to SQL Server on Linux and, if so, provide parity in guidance for license assignment and management.
  • Add notes or sections comparing Windows and Linux deployment scenarios, including any differences or similarities in benefit application.
  • Ensure that screenshots, code samples, and walkthroughs are not exclusively Windows-focused, and provide Linux alternatives where applicable.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing PowerShell scripts for usage analysis and omitting any mention of Linux or cross-platform alternatives. All scripting and tooling examples are Windows-centric, with no Bash, CLI, or Linux-native instructions provided. The documentation assumes users are operating in a Windows environment and does not address how Linux users can perform equivalent tasks.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for analyzing SQL license usage, ensuring Linux users can follow along without relying on PowerShell.
  • Explicitly mention cross-platform tools or scripts, and clarify which instructions are platform-specific.
  • Include references to Linux-compatible methods for managing Azure Hybrid Benefit settings, such as using the Azure CLI or REST API from a Linux shell.
  • Add a note or section for Linux users, outlining any differences in workflow or available tooling.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/understand/mosp-new-customer-experience.md ...ent-billing/understand/mosp-new-customer-experience.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its repeated mention of PowerShell as the automation and scripting tool for API and subscription operations, without referencing Linux-native equivalents (such as Bash, Azure CLI, or REST calls via curl). There are no Linux-specific examples or instructions, and the only tooling mentioned for automation is PowerShell, which is traditionally associated with Windows environments. This may create the impression that Windows is the preferred or only supported platform for scripting and automation, despite Azure's cross-platform capabilities.
Recommendations
  • Include examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS, alongside PowerShell examples.
  • Explicitly mention that all API operations can be performed via REST calls (e.g., using curl or httpie) and provide sample commands.
  • Add notes or sections clarifying that all features and operations are available on Linux, macOS, and Windows, and provide parity in instructions.
  • Where PowerShell is referenced, also provide equivalent Bash or shell script examples for Linux users.
  • Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., file paths, UI elements, or terminology).
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
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 handling CSV report formatting issues, with no mention of Linux or cross-platform alternatives. All step-by-step instructions for downloading and viewing reports assume usage of the Azure portal and Excel, both of which are most commonly used on Windows. There are no examples or guidance for Linux users, such as using LibreOffice, OpenOffice, or command-line tools (e.g., awk, csvkit) to process CSV files. The documentation also presents Windows-centric tools and workflows first and exclusively, omitting Linux equivalents.
Recommendations
  • Include instructions for opening and processing CSV files using Linux tools such as LibreOffice Calc, OpenOffice, or command-line utilities like awk, sed, or csvkit.
  • Add examples for importing and formatting CSV files on Linux and macOS platforms.
  • Mention cross-platform alternatives to Microsoft Excel for users who do not use Windows.
  • Clarify that the Azure portal is accessible from any modern browser and is not limited to Windows.
  • Where possible, provide CLI-based workflows (e.g., using Azure CLI or PowerShell Core, which is cross-platform) for downloading and processing billing reports.
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-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for command-line management of reservations, without mentioning or providing examples for cross-platform tools such as Azure CLI or REST API. The 'Grant access with PowerShell' section and related links only discuss PowerShell, which is traditionally associated with Windows environments, and there are no Linux- or macOS-specific instructions or examples. This may hinder Linux users or those preferring cross-platform tooling.
Recommendations
  • Add equivalent Azure CLI examples and instructions alongside PowerShell for all command-line operations, especially in the 'Grant access' and management sections.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, but also offer CLI and REST API alternatives.
  • Include a table or section comparing PowerShell, Azure CLI, and REST API approaches for managing reservation permissions.
  • Ensure that all code snippets and walkthroughs are available for both PowerShell and Azure CLI to support users on Linux, macOS, and Windows equally.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/microsoft-customer-agreement/onboard-microsoft-customer-agreement.md ...omer-agreement/onboard-microsoft-customer-agreement.md
High Priority View Details →
Scanned: 2025-08-25 00:01
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 by exclusively referencing Microsoft-centric tools and portals (such as Azure portal, Microsoft Admin Center, Microsoft 365 admin center, Power BI, and Microsoft Entra) without mentioning or providing parity for Linux or cross-platform alternatives. There are no command-line examples (Windows or Linux), but where automation or scripting is referenced (e.g., 'PowerShell scripts', 'Azure Commerce Toolbox'), only Windows-native tooling is mentioned. All video and walkthrough examples are based on the Azure portal or Microsoft admin interfaces, which are web-based but often assume a Windows-centric workflow. There is no mention of Linux CLI, Azure CLI, or cross-platform automation approaches, and no Linux-specific guidance or examples are provided.
Recommendations
  • Include references to Azure CLI (which is cross-platform) alongside or instead of PowerShell and Windows-specific tools when discussing automation, scripting, or API usage.
  • Provide explicit examples or links for managing billing, subscriptions, and automation tasks using Linux/macOS environments, such as bash scripts or Azure CLI commands.
  • When mentioning tools like Power BI or Microsoft Admin Center, clarify their platform compatibility and suggest alternatives or access methods for Linux users if available.
  • Ensure that any references to scripting or automation (such as recreating export jobs) include both PowerShell and bash/Azure CLI examples.
  • Review all video and tutorial links to ensure at least some demonstrate cross-platform or Linux-compatible workflows, or add notes about how Linux users can accomplish the same tasks.
  • Where possible, avoid assuming the user is operating from a Windows environment; use neutral, cross-platform language and tool recommendations.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/mca-setup-account.md ...es/cost-management-billing/manage/mca-setup-account.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web GUI) and does not provide any command-line examples, such as Azure CLI or scripting, which are commonly used in Linux or cross-platform environments. All instructions and validation steps are centered around the Azure portal, with no mention of alternative tools or methods (e.g., Azure CLI, Bash, or REST API) that are platform-agnostic. There are also references to PowerShell scripts and tools (such as in the export jobs section), but no equivalent Bash or Linux-native tooling is mentioned. This approach assumes users are comfortable with or prefer GUI and Windows-centric workflows, potentially excluding Linux-first or automation-focused users.
Recommendations
  • Provide equivalent Azure CLI and/or REST API instructions for all major actions (e.g., starting migration, validating billing account setup, managing roles), alongside portal-based steps.
  • Include Bash and cross-platform scripting examples where PowerShell or Windows tools are referenced, especially for automation tasks like export jobs.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.
  • Where screenshots or instructions are GUI-only, add notes or links to command-line alternatives for users who prefer or require automation.
  • Review references to PowerShell or Windows-specific tools and ensure Linux-native or cross-platform alternatives are documented and equally discoverable.
GitHub Create Pull Request
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 →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell environments. All scripting examples are provided exclusively in PowerShell (.ps1), and users are instructed to use PowerShell in Azure Cloud Shell, with no mention of Bash or cross-platform alternatives. The instructions and screenshots prioritize PowerShell selection, and there are no Linux shell (Bash) script examples or guidance for non-Windows users. The use of .ps1 files and PowerShell-specific cmdlets further reinforces this bias.
Recommendations
  • Provide equivalent Bash (or cross-platform) script examples for Linux/macOS users.
  • Include instructions for running the migration script in Bash within Azure Cloud Shell, or clarify if it is not possible.
  • Mention and demonstrate how to use Azure CLI (az) commands where possible, as these are cross-platform.
  • Add notes or sections specifically addressing Linux/macOS users, including any prerequisites or differences in workflow.
  • If PowerShell is required, clarify that PowerShell Core is available on Linux/macOS and provide installation instructions or references.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/programmatically-create-subscription-microsoft-customer-agreement-across-tenants.md ...bscription-microsoft-customer-agreement-across-tenants.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving the service principal ID, but lists Azure CLI first. However, there is a notable emphasis on Azure PowerShell, and no explicit mention of Linux or bash-specific patterns, nor any examples using bash scripting or Linux-native tools. The rest of the documentation is platform-neutral, focusing on REST API calls, but the lack of Linux-specific guidance or examples may disadvantage Linux users.
Recommendations
  • Add explicit bash/shell script examples for key steps, such as retrieving service principal IDs and making REST API calls.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
  • Include troubleshooting notes or tips relevant to Linux environments (e.g., authentication, environment variables).
  • Where PowerShell is mentioned, also provide equivalent bash/CLI commands side-by-side.
  • Ensure that any tool references (e.g., Azure CLI, PowerShell) specify their availability and installation instructions for Linux.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/mca-setup-account.md ...es/cost-management-billing/manage/mca-setup-account.md
High Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a web GUI that is most commonly used on Windows), and by mentioning tools and patterns that are typically associated with Windows environments (such as Power BI, Azure Commerce Toolbox, and PowerShell scripts) without providing equivalent Linux or cross-platform CLI examples. There are no instructions or examples using Azure CLI, Bash, or Linux-native tools, nor are there references to Linux-specific workflows. The documentation assumes use of the Azure portal and PowerShell for administrative tasks, and does not mention or prioritize Linux-compatible methods for billing account setup and migration.
Recommendations
  • Add equivalent examples using Azure CLI (az billing, az account, etc.) for all major steps, including billing account setup, role assignment, and migration validation.
  • Include Bash script snippets for common administrative tasks, such as exporting billing data or managing roles, to demonstrate Linux compatibility.
  • Reference cross-platform tools (such as Azure CLI and REST API calls) before or alongside Windows-specific tools like PowerShell.
  • Explicitly state that all steps can be performed on Linux, macOS, and Windows, and provide links to platform-agnostic documentation.
  • Where screenshots of the Azure portal are shown, consider including CLI output examples for parity.
  • Mention and link to documentation for Linux users on installing and using Azure CLI and other relevant tools.
GitHub Create Pull Request
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 →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias by referencing Microsoft-specific tools and admin centers (such as Microsoft 365 Admin Center and Azure portal) without mentioning cross-platform or Linux-native alternatives. There are no command-line examples (PowerShell or otherwise), but where command-line is referenced (in related links), it defaults to Azure PowerShell tabs. No Linux CLI or Azure CLI examples or guidance are provided, and the workflow assumes use of Microsoft portals and tools, which are more familiar to Windows users.
Recommendations
  • Include Azure CLI examples alongside or instead of Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • When referencing admin centers or portals, mention that these are web-based and accessible from any OS, or provide equivalent command-line instructions.
  • In related links, ensure that documentation pages default to or include Linux/CLI tabs, not just Azure PowerShell.
  • Explicitly state that actions can be performed from any OS, and provide parity in instructions for Linux/macOS users.
  • Where possible, avoid assuming familiarity with Microsoft-specific tools and provide context or alternatives for users from non-Windows backgrounds.
GitHub Create Pull Request
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 →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting all command-line examples (both PowerShell and Azure CLI) with Windows-style prompts (C:\>), referencing PowerShell modules and workflows first, and omitting explicit Linux/macOS instructions or examples. There is no mention of Linux-specific shell usage, installation, or file paths, and the CLI examples use Windows conventions exclusively.
Recommendations
  • Provide both Windows and Linux/macOS command-line examples, using appropriate prompts (e.g., $ for bash, C:\> for Windows).
  • Include installation instructions for PowerShell and Azure CLI on Linux/macOS, or link to relevant cross-platform guides.
  • Avoid using Windows-specific file paths or prompts in CLI examples unless specifically targeting Windows users.
  • Clarify that both PowerShell and Azure CLI are cross-platform, and provide usage notes for different operating systems.
  • If screenshots are included, consider showing both Windows and Linux/macOS interfaces where relevant.
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-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric tool) in both instructions and tooling tables, frequently referencing PowerShell cmdlets before or instead of cross-platform alternatives. The Azure portal (GUI) and PowerShell are emphasized for key operations, with the Azure CLI (which is more cross-platform) only mentioned later and with less detail. There are no explicit Linux/macOS-specific instructions or examples, and no mention of platform-specific considerations for non-Windows users.
Recommendations
  • Ensure all PowerShell examples are paired with equivalent Azure CLI examples, and present both side-by-side or in parallel sections.
  • Explicitly state that Azure CLI is cross-platform and provide installation and usage notes for Linux/macOS users.
  • Where GUI instructions are given, clarify that the Azure portal is accessible from any OS with a modern browser.
  • Review all tooling tables to include and highlight cross-platform tools (e.g., Azure CLI, PP CLI) equally with PowerShell.
  • Add a section or notes addressing any platform-specific differences or limitations for Linux/macOS users.
  • Avoid assuming PowerShell is the default scripting environment; clarify when a step is Windows-specific or provide alternatives.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/reservations/manage-reserved-vm-instance.md ...nt-billing/reservations/manage-reserved-vm-instance.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 Windows bias by providing only PowerShell examples for splitting reservations, with no equivalent Azure CLI (cross-platform) or Bash examples. The exclusive use of PowerShell commands assumes a Windows environment and omits guidance for Linux or macOS users. There is also a lack of mention or prioritization of cross-platform tools where applicable.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI example, which is cross-platform and works on Windows, Linux, and macOS.
  • Explicitly mention that the Azure CLI can be used for these operations and provide sample CLI commands.
  • Where possible, include Bash script examples or note that the CLI commands can be run in Bash or other shells.
  • Add a section or note clarifying tool availability and platform compatibility (e.g., 'The following examples use PowerShell, but you can also use Azure CLI on any platform').
  • Review for other sections where Windows-specific tools or patterns are referenced and ensure Linux/macOS parity.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/analyze-cost-data-azure-cost-management-power-bi-template-app.md ...-cost-data-azure-cost-management-power-bi-template-app.md
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 is heavily focused on the Power BI app and Power BI Desktop, which are primarily Windows-based tools. There are no examples or instructions for Linux users, nor are alternative cross-platform tools or methods mentioned. The only operating system-specific reference is to Windows Server AHB usage, with no mention of Linux VM equivalents. The documentation assumes the reader is using Windows and does not provide parity for Linux environments.
Recommendations
  • Explicitly state the platform requirements for Power BI App and Power BI Desktop, including any limitations for Linux or Mac users.
  • If possible, provide alternative instructions or tools for Linux users, such as using Power BI on the web or exporting data for analysis in cross-platform BI tools (e.g., Tableau, Apache Superset, or Jupyter Notebooks).
  • Include a section addressing Linux users, clarifying what is and isn't supported, and suggest workarounds or equivalent workflows.
  • When referencing VM usage (e.g., Windows Server AHB Usage), also mention Linux VM cost management features or reports, if available, to provide parity.
  • Ensure troubleshooting and authentication steps note any OS-specific differences, especially for authentication dialogs or file downloads.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/costs/ingest-azure-usage-at-scale.md ...anagement-billing/costs/ingest-azure-usage-at-scale.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by describing performance tests and sample applications exclusively on Windows 10, using .NET and the Azure Data Movement Library (DML), which are Windows-centric technologies. There are no examples or mentions of Linux or cross-platform alternatives for copying blobs or automating exports. The test environment, tooling, and code samples are all Windows-focused, and Linux users are not provided with equivalent guidance or tooling references.
Recommendations
  • Include equivalent Linux-based examples for copying large Azure storage blobs, such as using AzCopy, Azure CLI, or Python SDK scripts.
  • Mention and provide sample commands for cross-platform tools (e.g., AzCopy, Azure CLI) before or alongside Windows/.NET examples.
  • Describe performance testing or usage on Linux environments, including any differences or considerations.
  • Reference and link to documentation or guides for Linux users on automating exports and handling large blob transfers.
  • Avoid assuming the reader is using Windows by default; clarify that the .NET/DML approach is one of several options.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/assign-roles-azure-service-principals.md ...illing/manage/assign-roles-azure-service-principals.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell for automation and GUID generation, referencing Windows-centric tools (Visual Studio, PowerShell), and omitting Linux-specific or cross-platform command-line examples for key tasks. While curl is mentioned, the primary automation flow and examples assume a Windows/PowerShell environment, with no Linux shell or CLI parity.
Recommendations
  • Provide equivalent Linux/bash command-line examples for all PowerShell commands (e.g., show how to generate a GUID with uuidgen or openssl).
  • List cross-platform tools (curl, httpie, Postman, etc.) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Include Linux/macOS authentication and scripting guidance (e.g., Azure CLI usage, bash scripts) alongside PowerShell.
  • Clarify that all REST API examples are platform-agnostic and provide sample requests using curl or httpie.
  • Avoid assuming the user is on Windows; use neutral language and tool ordering.
  • Where screenshots or instructions reference Windows UI, note any differences for Linux/macOS users or provide alternative instructions if needed.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by consistently presenting command-line examples with Windows-style prompts (C:\>), listing PowerShell instructions before Azure CLI, and referencing PowerShell modules and workflows. There is no mention of Linux or macOS environments, and all CLI examples use Windows paths and conventions, which may confuse or alienate Linux/macOS users.
Recommendations
  • Provide command-line examples using both Windows (PowerShell/CMD) and Linux/macOS (bash) syntax, including appropriate prompts (e.g., $ for bash).
  • Avoid using Windows-specific paths (C:\>) in Azure CLI examples; use generic or cross-platform prompts (e.g., $ or az ...).
  • Explicitly mention that the Azure CLI and PowerShell modules are cross-platform, and provide installation or usage notes for Linux/macOS where relevant.
  • Ensure that instructions for installing tools (like Azure CLI extensions) include Linux/macOS commands and package managers.
  • Consider reordering sections so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell.
  • Add a note or section addressing any platform-specific differences or requirements.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides a PowerShell script and instructs users to use PowerShell in Azure Cloud Shell, with no mention of Bash, Linux shell scripting, or cross-platform alternatives. The instructions and screenshots prioritize PowerShell, and there are no examples or guidance for users on Linux or macOS who may prefer Bash or other scripting environments.
Recommendations
  • Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and clarify if the process can be performed in Bash.
  • Include notes or links to cross-platform tools or scripts where possible.
  • If PowerShell is required due to specific module support, explain why and provide installation instructions for PowerShell Core on Linux/macOS.
  • Add a section addressing Linux/macOS users, outlining any differences or additional steps needed.
GitHub Create Pull Request
Cost Management Billing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/mca-setup-account.md ...es/cost-management-billing/manage/mca-setup-account.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 is heavily oriented around the Azure portal web interface, with all instructions and screenshots assuming use of a graphical browser. There are no command-line examples or automation options provided (e.g., Azure CLI, PowerShell, or REST API), and no mention of Linux or cross-platform tooling. The only tool mentioned for automation is Terraform, but even that is referenced as a link rather than an integrated example. This approach implicitly favors Windows users, who are more likely to use the Azure portal and PowerShell, and does not address the needs of Linux users or those who prefer command-line or automated workflows.
Recommendations
  • Add equivalent instructions and examples for managing billing accounts using the Azure CLI (az), which is cross-platform and widely used on Linux.
  • Where possible, provide REST API examples (with curl or similar tools) for key operations, to support automation and scripting on any OS.
  • If PowerShell is referenced, ensure Azure CLI or bash alternatives are given equal prominence and appear before or alongside PowerShell examples.
  • Explicitly mention that all portal-based steps can be performed from any OS with a supported browser, but highlight CLI/API options for users who prefer or require non-GUI workflows.
  • Include links to Azure CLI and REST API documentation for billing/account management tasks.
  • Consider adding a section or callout for Linux/macOS users, summarizing available tools and approaches for managing billing outside the Azure portal.
GitHub Create Pull Request
← Previous Page 6 of 15 Next →