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 26-50 of 365 flagged pages
Cost Management Billing
View Azure Reservation purchase and refund transactions
...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 exclusively referencing Windows-centric tools (Azure portal, Power BI) and omitting Linux-native equivalents or CLI-based workflows. There are no examples using cross-platform tools like Azure CLI, Bash, or Linux desktop reporting tools. The order of presentation also places Windows GUI tools before mentioning REST APIs, which are platform-agnostic.
Recommendations
- Add examples using Azure CLI commands to retrieve reservation transactions, suitable for Linux and macOS users.
- Include instructions for accessing reservation data via Bash scripts or other Linux-native tools.
- Mention and provide examples for open-source or cross-platform reporting tools that can be used as alternatives to Power BI.
- Reorder sections to present platform-agnostic methods (APIs, CLI) before Windows-specific GUI tools.
- Explicitly state that the REST API and Azure CLI are available and supported on Linux, macOS, and Windows.
Create Pull Request
Cost Management Billing
Permissions to View and Manage Azure Reservations
...t-management-billing/reservations/view-reservations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page provides detailed instructions for managing Azure reservations primarily through the Azure portal and PowerShell, with explicit references to PowerShell commands and workflows. There are no examples or mentions of Linux-native tools (such as Azure CLI), nor are cross-platform command-line options presented. The only command-line automation method described is PowerShell, which is most commonly associated with Windows environments, and there is no guidance for Linux or macOS users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell instructions, ensuring Linux and macOS users have clear, supported workflows.
- Explicitly mention that Azure CLI can be used from any OS and provide links to relevant CLI documentation.
- Where PowerShell is referenced, clarify its cross-platform availability, but also offer CLI alternatives for parity.
- Review all command-line sections to ensure both Windows and Linux/macOS users are addressed equally, including troubleshooting tips for non-Windows environments.
Cost Management Billing
What is Azure savings plans for compute?
...-billing/savings-plan/savings-plan-compute-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific details (such as Windows VM metering and Windows software costs) are mentioned before Linux equivalents, and there is a focus on Windows licensing and Azure Hybrid Benefit for Windows and SQL workloads. There are no explicit Linux or open-source tooling examples, nor is there parity in discussing Linux-specific scenarios or licensing. The documentation does not provide examples or guidance for Linux users, nor does it mention Linux-specific considerations in savings plans beyond a brief reference to Linux meters.
Recommendations
- Include explicit examples or scenarios for Linux VMs, such as how savings plans apply to popular Linux distributions and workloads.
- Discuss Linux licensing and cost considerations, even if only to clarify that there are no additional software costs for Linux VMs.
- Balance the order of presentation: mention Linux and Windows meters together, or provide a comparative table.
- Reference open-source or Linux-native management tools (e.g., Azure CLI, Bash scripting) alongside or before Windows tools.
- Add guidance for Linux users on how to optimize savings plan usage, including any unique considerations for Linux workloads.
Cost Management Billing
Permissions to view and manage Azure savings plans
...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 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, Bash, or REST API calls, which are commonly used on Linux and macOS systems. The repeated use of PowerShell and references to PowerShell modules and commands reinforce a Windows-centric approach, potentially excluding users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API call examples (e.g., using curl or httpie) for key operations, allowing users to interact with Azure from any OS.
- Add notes clarifying that PowerShell Core is available on Linux and macOS, but still offer CLI and REST alternatives for parity.
- Ensure that documentation sections referencing command-line management do not assume a Windows environment by default.
- Consider adding Bash script snippets for common tasks to further support Linux users.
Cost Management Billing
Transition to centrally managed Azure Hybrid Benefit
...-management-billing/scope-level/transition-existing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive use of PowerShell for scripting examples and guidance, without mention of Linux alternatives such as Bash or CLI. Windows tools and patterns (PowerShell scripts) are referenced as the default method for analyzing SQL license usage, and no Linux-specific instructions or parity examples are provided. The documentation assumes familiarity with Windows-centric tooling and does not address how Linux users can perform equivalent tasks.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux users, especially for tasks like analyzing SQL license usage.
- Explicitly mention cross-platform compatibility for scripts and tools, or provide links to Linux-compatible resources.
- Reorder sections or examples so that platform-neutral or Linux options are presented alongside or before Windows/PowerShell options.
- Include notes or guidance for Linux administrators on how to perform Azure Hybrid Benefit management tasks without relying on Windows-specific tools.
Cost Management Billing
Tutorial - Optimize centrally managed Azure Hybrid Benefit for SQL Server
...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 demonstrates Windows bias by exclusively referencing Windows-based SQL Server VM registration guides and PowerShell scripts for license usage analysis. There are no Linux-specific instructions, examples, or tool references for managing SQL Server on Linux VMs in Azure, nor is there mention of Linux-compatible alternatives to the PowerShell script.
Recommendations
- Include equivalent instructions and links for registering SQL Server VMs running on Linux in Azure, such as using the SQL IaaS Agent Extension for Linux.
- Provide Linux shell (bash/CLI) examples for gathering license usage and availability details, alongside PowerShell examples.
- Reference or develop Linux-compatible scripts or tools for analyzing Azure Hybrid Benefit usage, and link to them in the documentation.
- Ensure that all steps and walkthroughs mention both Windows and Linux scenarios where applicable, to support cross-platform administrators.
Cost Management Billing
SQL IaaS extension registration options for Cost Management administrators
...billing/scope-level/sql-iaas-extension-registration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools and workflows, such as the Azure portal, PowerShell scripts, and linking to Windows-specific documentation. There are no examples or guidance for Linux-based environments, nor are Linux command-line tools or patterns mentioned. The PowerShell script is the only automation example provided, and the registration process references Windows-centric resources and terminology throughout.
Recommendations
- Include equivalent Linux CLI (az CLI, Bash) examples for registration and verification steps.
- Reference Linux-specific documentation and workflows where applicable, such as managing SQL Server on Linux VMs.
- Provide parity in automation scripts, offering Bash or Python alternatives alongside PowerShell.
- Clarify that the SQL IaaS Agent extension and registration process is applicable to both Windows and Linux SQL Server VMs, and highlight any differences.
- Add screenshots or walkthroughs for Linux VM scenarios in the Azure portal, if relevant.
Cost Management Billing
Troubleshoot Azure payment issues
...t-billing/billing-troubleshoot-azure-payment-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Microsoft Edge and Internet Explorer as the primary browsers for troubleshooting payment method issues, specifically linking to an Edge support article for private browsing. No mention is made of Linux browsers (such as Firefox or Chrome) or their private/incognito modes. There are no examples or troubleshooting steps tailored for Linux users, nor are cross-platform considerations addressed.
Recommendations
- Include instructions for private/incognito browsing in popular Linux browsers (e.g., Firefox, Chrome) alongside Microsoft Edge/Internet Explorer.
- Provide troubleshooting steps that are applicable to Linux users, such as clearing cache/cookies in Linux browsers.
- Avoid referencing only Windows-specific tools or browsers; mention alternatives and ensure parity in guidance for Linux and macOS users.
- Add a note clarifying that the Azure portal is accessible from any modern browser and provide links to relevant help articles for non-Windows platforms.
Cost Management Billing
Get started with your updated Azure billing account
...ent-billing/understand/mosp-new-customer-experience.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references PowerShell as a primary automation and scripting tool for billing and subscription operations, without mentioning Linux-native alternatives (such as Bash, Azure CLI, or shell scripting). There are no examples or instructions for Linux users, and the only tooling mentioned for automation is PowerShell, which is traditionally associated with Windows environments. This creates a bias toward Windows users and may leave Linux users without clear guidance.
Recommendations
- Include examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Explicitly mention that APIs and SDKs can be accessed from Linux environments, and provide sample Bash or shell scripts for common operations.
- When referencing PowerShell, also provide equivalent commands for Azure CLI or Bash to ensure Linux parity.
- Add troubleshooting and setup instructions relevant to Linux users (e.g., installing Azure CLI, authenticating from Linux).
- Review screenshots and UI instructions to ensure they are not Windows-specific, and clarify any OS-neutral steps.
Cost Management Billing
Review your Azure Enterprise Agreement bill
...billing/understand/review-enterprise-agreement-bill.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Excel Heavy
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Microsoft Excel for CSV report handling and troubleshooting. All instructions for importing and correcting CSV formatting issues are tailored to Excel, with no mention of Linux-native tools (such as LibreOffice Calc, csvkit, or command-line utilities). There are no examples or guidance for users on Linux or macOS platforms, nor are alternative tools or workflows suggested. The documentation assumes users are operating in a Windows-centric environment.
Recommendations
- Add instructions for opening and importing CSV files using LibreOffice Calc, which is available on Linux and macOS.
- Provide examples of using command-line tools (e.g., awk, sed, csvkit) to process and correct CSV formatting issues on Linux.
- Mention alternative spreadsheet applications (such as Google Sheets or OpenOffice) and how to handle regional formatting in those tools.
- Include a note clarifying that the CSV files can be opened and processed on non-Windows platforms, and offer troubleshooting steps for common issues in those environments.
- Ensure parity by presenting Linux/macOS options alongside Windows/Excel instructions, rather than only referencing Microsoft tools.
Cost Management Billing
View Azure reservation utilization
...gement-billing/reservations/reservation-utilization.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by referencing Windows-centric tools such as Power BI Desktop and the Azure portal, without mentioning Linux alternatives or providing CLI-based examples. There are no examples or instructions for Linux users, and the documentation prioritizes Windows tools and interfaces.
Recommendations
- Include Azure CLI examples for viewing reservation utilization, as the CLI is cross-platform and widely used on Linux.
- Mention and provide instructions for accessing reservation utilization data via REST APIs, including sample curl commands.
- Clarify that Power BI Desktop is Windows-only and suggest alternative reporting tools or methods for Linux users, such as using Python with pandas or connecting to the API directly.
- Add explicit guidance for Linux/macOS users on how to perform equivalent tasks without relying on Windows-specific tools.
Cost Management Billing
Get started with your updated Azure billing account
...ent-billing/understand/mosp-new-customer-experience.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell as a primary automation and scripting tool for billing and subscription operations, without mentioning Linux-native alternatives such as Bash, Azure CLI, or cross-platform SDK usage. There are no Linux-specific examples or guidance, and the only tool explicitly called out for automation is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- Mention Bash scripting and provide sample commands for common billing/account management tasks.
- Clarify that PowerShell Core is available cross-platform, or provide equivalent instructions for Linux users.
- Add explicit guidance or links for Linux users on how to perform billing and subscription operations using their preferred tools.
- Ensure screenshots and step-by-step instructions do not assume a Windows environment (e.g., referencing Windows-specific UI elements or terminology).
Cost Management Billing
SQL IaaS extension registration options for Cost Management administrators
...billing/scope-level/sql-iaas-extension-registration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools and workflows, such as the Azure portal, PowerShell scripts, and Windows-specific documentation links. There are no examples or guidance for Linux-based SQL Server VMs, nor are cross-platform command-line alternatives (e.g., Azure CLI, Bash) mentioned. The documentation also links to a Windows-focused registration guide and omits Linux-specific considerations or instructions.
Recommendations
- Include explicit instructions and examples for registering SQL IaaS Agent extension on Linux-based SQL Server VMs.
- Provide Azure CLI and Bash script alternatives alongside PowerShell examples for cross-platform parity.
- Add links to Linux-specific documentation, such as registering SQL IaaS Agent extension for Linux VMs.
- Clarify any differences or prerequisites for Linux environments in the registration process.
- Ensure that video and walkthrough resources cover both Windows and Linux scenarios.
Cost Management Billing
Assign permissions to Cost Management APIs
...nt-billing/automate/cost-management-api-permissions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell as the primary command-line tool for assigning service principal permissions, without mentioning cross-platform alternatives such as Azure CLI. The instructions and links focus on portal and PowerShell methods, which are most familiar to Windows users, and do not provide Linux-specific or platform-neutral examples for automating permission assignment.
Recommendations
- Include Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used for role assignments, and provide links to relevant CLI documentation.
- Add examples or instructions for automating permissions assignment using REST API calls, which are platform-agnostic.
- Review linked articles to ensure Linux parity in examples and tool recommendations.
- Clarify that the Azure portal is accessible from any OS, but provide command-line alternatives for users who prefer automation or non-GUI workflows.
Cost Management Billing
Introduction to cost allocation
...nagement-billing/costs/cost-allocation-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (Azure portal, PowerShell) before cross-platform options (CLI, REST API) when describing how to manage subscriptions and resource groups. There are no explicit Linux or Bash examples, and PowerShell is mentioned as a primary management tool, with no parity for Linux users. The absence of Linux-specific instructions or examples (such as Bash/CLI commands) may disadvantage users on non-Windows platforms.
Recommendations
- Present Azure CLI and REST API options before or alongside PowerShell and Azure portal to ensure cross-platform parity.
- Include explicit Bash/CLI examples for common management tasks (e.g., viewing and managing subscriptions/resource groups).
- Add notes or sections highlighting Linux compatibility and usage patterns.
- Avoid implying PowerShell is the default or preferred tool; clarify that CLI and REST API are fully supported and cross-platform.
- Where possible, provide side-by-side examples for PowerShell and Bash/CLI.
Cost Management Billing
Quickstart - Create a budget with Bicep
...-management-billing/costs/quick-create-budget-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment and management tasks. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some cases, Windows-specific patterns (such as PowerShell array syntax) are shown. There is implicit Windows bias in the use of PowerShell and the lack of explicit Linux shell examples (e.g., Bash array syntax), and Windows tools (PowerShell) are mentioned as primary options alongside CLI, rather than CLI being the default cross-platform choice. There are no Bash or Linux-native command examples, and variable assignment patterns are PowerShell-specific in the PowerShell tabs.
Recommendations
- Add explicit Bash shell examples for variable assignment and command usage, especially for Linux/macOS users.
- Clarify that Azure CLI is cross-platform and recommend it as the default for non-Windows environments.
- Instruct users on how to assign arrays/variables in Bash for CLI commands (e.g., using bash arrays or strings).
- Consider reordering examples so that Azure CLI (cross-platform) appears before PowerShell (Windows-centric) in each section.
- Add notes or callouts for Linux/macOS users regarding shell differences and how to adapt examples.
- Avoid assuming PowerShell is available on all platforms; mention installation steps if needed.
Cost Management Billing
Tutorial - Create and manage budgets
...anagement-billing/costs/tutorial-acm-create-budgets.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the first and most detailed programmatic example for creating and managing budgets, with CLI and Terraform examples following. The use of PowerShell and references to installing the Az PowerShell module are Windows-centric. There is no mention of Linux-specific tools, nor are there Bash or shell script examples. The CLI example is provided, but PowerShell is prioritized and described in more detail, reinforcing a Windows-first approach.
Recommendations
- Provide Bash or shell script examples for Linux users alongside PowerShell examples.
- Explicitly mention cross-platform compatibility for Azure CLI and PowerShell, including installation instructions for Linux and macOS.
- Reorder example tabs so that CLI or platform-neutral options appear before PowerShell.
- Include notes or links for Linux users on how to install and use Azure CLI and PowerShell on their systems.
- Add examples using native Linux tools or scripting patterns where relevant.
- Ensure that all screenshots and instructions are platform-agnostic or provide alternatives for Linux/macOS environments.
Cost Management Billing
Assign Enterprise Agreement roles to service principals
...illing/manage/assign-roles-azure-service-principals.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell for automation examples, referencing Windows-centric tools (PowerShell, Visual Studio), and providing explicit PowerShell commands (e.g., New-Guid) without equivalent Linux or cross-platform alternatives. Linux-native tools and workflows (such as Bash, shell commands, or Linux-based GUID generation) are not mentioned or exemplified, and Windows tools are listed before cross-platform or Linux tools.
Recommendations
- Provide Linux and macOS equivalents for all PowerShell commands, such as showing how to generate a GUID using 'uuidgen' in Bash.
- Include CLI examples using Azure CLI (az), which is cross-platform, alongside or instead of PowerShell.
- List cross-platform tools (curl, Insomnia, Bruno) before Windows-specific tools (PowerShell, Visual Studio) when suggesting API query methods.
- Add explicit Linux/macOS shell examples for REST API calls and authentication steps.
- Clarify that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
- Where screenshots show Windows UI, consider adding notes or screenshots for Linux/macOS environments if relevant.
Cost Management Billing
Quickstart - Create a budget with an Azure Resource Manager template
...nagement-billing/costs/quick-create-budget-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently mentioning Azure PowerShell and linking to PowerShell deployment documentation before or alongside Azure CLI and REST API. The primary deployment method is via the Azure portal, which is more familiar to Windows users. References to deployment alternatives point to PowerShell documentation, and PowerShell examples are given equal prominence to CLI, despite CLI being more cross-platform. There is no explicit mention of Linux-specific patterns, nor are Linux shell scripting examples provided.
Recommendations
- Provide explicit Linux shell (bash) examples for deployment and cleanup, in addition to Azure CLI.
- Link to Azure CLI deployment documentation before or alongside PowerShell, emphasizing CLI as the cross-platform choice.
- Clarify that Azure CLI works natively on Linux/macOS and Windows, and highlight installation instructions for non-Windows platforms.
- Add notes or sections for deploying ARM templates using Linux-native tools (e.g., curl, jq, az CLI in bash scripts).
- Balance the prominence of PowerShell and CLI examples, ensuring CLI is not secondary to PowerShell.
- Avoid referring to the Azure portal as the default method; instead, present CLI and REST API as equally valid, especially for automation and Linux users.
Cost Management Billing
Azure billing and cost management budget scenario
...ment-billing/manage/cost-management-budget-scenario.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily referencing Windows-centric tools (Visual Studio, PowerShell, ARMClient), providing examples and instructions that assume a Windows environment (e.g., building ARMClient in Visual Studio, using Windows command prompt), and listing Windows tools before cross-platform or Linux alternatives. There are no explicit Linux or macOS instructions or examples, and Linux-native tools are not mentioned or prioritized.
Recommendations
- Include Linux/macOS equivalents for all tool references (e.g., mention VS Code, JetBrains Rider, or CLI-based workflows for ARMClient).
- Provide step-by-step instructions for using ARMClient on Linux/macOS, including installation and usage from a Bash shell.
- List cross-platform tools (e.g., Curl, Insomnia, Bruno) before Windows-specific tools like Visual Studio and PowerShell.
- Offer PowerShell and Bash (or Azure CLI) examples side-by-side for API calls and automation tasks.
- Clarify that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
- Reference Linux-native editors and shells (e.g., nano, vim, Bash) where appropriate.
- Ensure screenshots and walkthroughs do not assume a Windows-only environment.
Cost Management Billing
Discover your Microsoft cloud footprint FAQ
...-management-billing/manage/discover-cloud-footprint.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal and Microsoft 365 admin center (both web GUIs typically accessed from Windows), and by providing only Azure CLI examples without mentioning Linux-specific tools or shell patterns. There are no PowerShell examples, but the absence of Linux shell (bash) or cross-platform command-line alternatives, and the lack of references to Linux-native admin tools or patterns, indicate a Windows-first perspective. The documentation does not address how Linux administrators might access or automate these tasks, nor does it mention Linux-specific considerations for managing Microsoft cloud resources.
Recommendations
- Include Linux shell (bash) examples alongside Azure CLI commands, demonstrating usage in Linux environments.
- Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux.
- Mention Linux-native tools or patterns (such as curl, jq, or bash scripting) for interacting with Microsoft cloud APIs.
- Add guidance for accessing the Azure portal and Microsoft 365 admin center from Linux browsers, and note any platform-specific limitations.
- Provide parity in troubleshooting and automation instructions for both Windows and Linux administrators.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is featured prominently and described before Azure CLI, with detailed PowerShell command examples and references to installing PowerShell modules. The Azure portal (a GUI tool most commonly used on Windows) is presented as the primary method for PAL association, with alternate approaches (including CLI) described later. There is no mention of Linux-specific considerations, nor are there examples or troubleshooting steps tailored for Linux environments. The documentation assumes familiarity with Windows tools and does not address cross-platform differences or limitations.
Recommendations
- Provide explicit Linux and macOS compatibility notes for all command-line instructions, including installation steps for Azure CLI and PowerShell on non-Windows platforms.
- Include Linux/macOS-specific examples, such as shell commands (bash/zsh), and clarify any differences in authentication or environment setup.
- Balance the order of presentation: introduce Azure CLI and PowerShell together, or lead with the more cross-platform Azure CLI.
- Mention any limitations or differences when using the Azure portal or PowerShell on Linux/macOS, and offer troubleshooting guidance.
- Reference alternative tools or workflows that are native to Linux/macOS where possible.
- Add a section on cross-platform best practices for partners who do not use Windows as their primary OS.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Command-line examples for both PowerShell and Azure CLI are consistently shown with Windows-style prompts (e.g., 'C:\>'), and installation instructions reference Windows conventions. PowerShell is presented as a primary automation tool, with no mention of Bash or Linux shell equivalents. There are no explicit Linux-specific instructions, nor are there examples showing Linux/MacOS terminal usage or file paths. The ordering and presentation of examples and tools implicitly prioritize Windows environments.
Recommendations
- Provide Linux/MacOS-specific command-line examples, using appropriate shell prompts (e.g., '$' or '~$') and file paths.
- Include Bash or shell script equivalents for PowerShell commands where possible.
- Clarify that Azure CLI and PowerShell are cross-platform, and show usage on both Windows and Linux/MacOS.
- Avoid using Windows-style prompts ('C:\>') in CLI examples; use generic or platform-appropriate prompts.
- Add notes or sections addressing installation and usage on Linux/MacOS, including package managers and environment setup.
- Ensure that tool recommendations and instructions are platform-neutral or offer parity for all major operating systems.
Cost Management Billing
Copy billing roles from one MCA to another MCA across tenants with a script
...s/cost-management-billing/manage/mca-role-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides instructions and scripting examples using PowerShell (.ps1), with explicit guidance to select PowerShell in Azure Cloud Shell. There are no Bash or Linux-native script examples, nor any mention of how to accomplish the task using Linux tools or workflows. The prerequisites and steps assume a Windows/PowerShell environment, and the script is not cross-platform.
Recommendations
- Provide equivalent Bash or Python script examples for Linux/macOS users.
- Clarify whether the PowerShell script can be run using PowerShell Core on Linux/macOS, and provide installation/setup guidance if so.
- Include instructions for using Bash in Azure Cloud Shell, or note any limitations.
- Mention cross-platform tools (e.g., Az CLI) where possible, and provide alternative workflows.
- Explicitly state platform requirements and offer parity for Linux users in all steps and prerequisites.
Cost Management Billing
Set up billing for Microsoft Customer Agreement - Azure
...es/cost-management-billing/manage/mca-setup-account.md
High Priority
View Details →
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 most commonly accessed from Windows environments), omitting any Linux-specific CLI or automation examples. All instructions and screenshots are based on the Azure portal, with no mention of cross-platform tools like Azure CLI, Bash scripts, or Linux-native automation. PowerShell is referenced only in passing (for export jobs), and Windows-centric terminology (e.g., 'portal', 'browser') is used throughout. There are no Linux or macOS-specific instructions, nor are there examples for managing billing via command-line tools or REST APIs from non-Windows platforms.
Recommendations
- Provide equivalent instructions using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
- Include examples for managing billing accounts and roles using REST APIs, with sample requests using curl or other Linux-native tools.
- Reference automation options for Linux environments, such as Bash scripts, in addition to PowerShell.
- Clarify that all portal-based steps can be performed from any OS/browser, and explicitly mention Linux/macOS compatibility.
- Add links to documentation for Azure CLI and REST API billing management.
- Where PowerShell is mentioned, offer Bash or Azure CLI alternatives.