Partner Solutions

106
Total Pages
93
Linux-Friendly Pages
13
Pages with Bias
12.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

28 issues found
Showing 1-25 of 28 flagged pages
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/new-relic/manage.md ...ob/main/articles/partner-solutions/new-relic/manage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias, particularly in the section about monitoring App Services with the New Relic agent. It explicitly states that App Service extensions are only supported for Windows, and App Services running on Linux are not displayed or supported. There are no Linux-specific instructions, examples, or parity in tooling or guidance for Linux-based environments. The documentation also omits any mention of Linux command-line tools or patterns, and the only supported scenario for App Services is Windows.
Recommendations
  • Provide clear guidance and examples for monitoring Linux-based App Services, or explicitly state the roadmap or alternatives for Linux users.
  • If Linux support is not available, add a prominent note at the top of the relevant sections to inform users early.
  • Include parity in documentation for Linux environments wherever possible, such as instructions for installing the New Relic agent on Linux VMs or App Services.
  • Mention and link to any CLI or scripting options (e.g., Azure CLI, Bash) for Linux users, not just portal-based workflows.
  • If certain features are Windows-only, offer alternative monitoring approaches for Linux users or direct them to relevant resources.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/sso.md ...s/blob/main/articles/partner-solutions/includes/sso.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Microsoft Entra ID and the Azure portal, both of which are Microsoft-centric tools. There are no examples or instructions for Linux users or for using cross-platform or open-source tools. The workflow assumes use of the Azure portal UI, which is typically accessed via a web browser but is closely associated with Windows environments. No alternative methods (such as CLI or Linux-native tools) are mentioned.
Recommendations
  • Include instructions for using the Azure CLI or Microsoft Graph API, which are cross-platform and can be used from Linux systems.
  • Provide examples or notes for Linux users, such as how to access the Azure portal from non-Windows environments.
  • Mention open-source or cross-platform identity providers or tools, if applicable, to broaden the scope beyond Microsoft-specific solutions.
  • Clearly state that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows exclusivity.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/new-relic/manage.md ...ob/main/articles/partner-solutions/new-relic/manage.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias, particularly in the App Services monitoring section, where only Windows-based App Services are supported and documented. App Services running on Linux are explicitly excluded, and there are no instructions or examples for Linux-based environments. The documentation also references App Service extensions, which are a Windows-specific pattern, and does not provide parity for Linux users.
Recommendations
  • Add support and documentation for monitoring App Services running on Linux, or clearly indicate roadmap/timeline if not yet available.
  • Provide equivalent instructions and examples for Linux-based virtual machines and App Services where possible.
  • If certain features are Windows-only, offer alternative monitoring approaches for Linux users (e.g., manual agent installation, custom scripts) and document these alternatives.
  • Ensure that all sections referencing Windows tools or patterns (such as App Service extensions) also mention Linux equivalents or workarounds.
  • Include explicit examples and screenshots for both Windows and Linux environments to ensure parity and inclusivity.
GitHub Create Pull Request
Partner Solutions Link to an Existing Azure Native Dynatrace Service Resource ...tner-solutions/dynatrace/link-to-existing-resources.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 describes using the Azure portal (web UI) for linking Dynatrace resources, with all screenshots and instructions referencing the portal interface. There are no examples or guidance for performing these tasks via command-line tools such as Azure CLI, PowerShell, or ARM templates, nor is there mention of Linux/macOS-specific workflows. The absence of CLI or automation examples means Linux users (who may prefer or require non-GUI methods) are underserved.
Recommendations
  • Add equivalent instructions for linking Dynatrace resources using Azure CLI and/or ARM templates.
  • Include example commands for Linux/macOS environments, ensuring parity with portal-based steps.
  • If PowerShell is relevant, provide both PowerShell and Bash (Azure CLI) examples, and present them side-by-side.
  • Explicitly mention cross-platform options for performing the task, clarifying that the process is not limited to the Azure portal.
GitHub Create Pull Request
Partner Solutions Create a Confluent Connector for Azure Blob Storage (Preview) ...ache-kafka-confluent-cloud/add-confluent-connectors.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively describes connector creation via the Azure portal UI, which is primarily a Windows-centric tool. There are no CLI, shell, or cross-platform instructions provided, nor any mention of Linux/macOS workflows or tools. All screenshots and step-by-step instructions assume use of the Azure portal, which is most commonly accessed from Windows environments.
Recommendations
  • Add instructions for creating connectors using Azure CLI, PowerShell, and Bash, with explicit Linux/macOS compatibility notes.
  • Provide examples for connector creation via REST API or Confluent CLI, which are platform-agnostic.
  • Include screenshots or terminal output from Linux/macOS environments to demonstrate parity.
  • Mention any prerequisites or differences for Linux/macOS users (e.g., browser compatibility, CLI installation steps).
GitHub Create Pull Request
Partner Solutions Create a Confluent Connector for Azure Blob Storage (Preview) ...ache-kafka-confluent-cloud/add-confluent-connectors.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all instructions and screenshots, which is most commonly accessed from Windows environments. There is no mention of Linux-specific CLI tools, shell commands, or alternative workflows (such as using Azure CLI, REST API, or Confluent CLI from Linux/macOS). No examples are provided for Linux users, and all steps assume a graphical interface typical of Windows usage.
Recommendations
  • Add equivalent instructions for creating and managing connectors using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include examples of using Confluent CLI or REST API to create connectors, with sample shell commands for Linux/macOS environments.
  • Explicitly mention that the Azure portal can be accessed from any OS and provide screenshots or notes relevant to Linux desktop environments.
  • Where possible, provide parity between GUI and command-line workflows, so Linux users are not required to use the Windows-centric portal UI.
GitHub Create Pull Request
Partner Solutions Troubleshoot Apache Kafka & Apache Flink on Confluent Cloud ...solutions/apache-kafka-confluent-cloud/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references Azure portal workflows and Microsoft Entra ID, which are primarily associated with Windows environments. There are no examples or troubleshooting steps for Linux users, nor are Linux command-line tools or patterns mentioned. All instructions assume usage of the Azure portal, with no mention of CLI alternatives (such as Azure CLI or Bash), which are commonly used on Linux.
Recommendations
  • Include troubleshooting steps using Azure CLI and Bash commands, which are platform-agnostic and widely used on Linux.
  • Add examples for managing Confluent Cloud resources from Linux environments, such as using curl, az CLI, or other cross-platform tools.
  • Explicitly mention that the Azure portal is accessible from any OS, and provide parity for Linux users where possible.
  • Reference documentation for Linux users on how to find tenant IDs, manage permissions, and perform resource operations outside of the portal.
  • Avoid assuming the user is on Windows by providing instructions for both GUI (portal) and CLI workflows.
GitHub Create Pull Request
Partner Solutions Link to an Existing Azure Native Dynatrace Service Resource ...tner-solutions/dynatrace/link-to-existing-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to link Dynatrace resources using the Azure portal GUI, with screenshots and instructions that reflect the Windows-centric Azure portal experience. There are no CLI, PowerShell, or Azure Cloud Shell examples, nor any mention of Linux tools or workflows. This approach assumes users are working in a graphical environment, typically on Windows, and omits guidance for Linux users or those preferring command-line automation.
Recommendations
  • Add equivalent instructions for linking Dynatrace resources using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include examples for using Azure PowerShell and Azure Cloud Shell, noting their availability on Linux and macOS.
  • Provide screenshots or terminal output for CLI workflows, not just GUI steps.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows using CLI tools.
  • Add a section comparing portal and CLI methods, helping users choose the best fit for their environment.
GitHub Create Pull Request
Partner Solutions Create a Confluent Connector for Azure Blob Storage (Preview) ...ache-kafka-confluent-cloud/add-confluent-connectors.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes connector creation via the Azure portal UI, which is primarily accessed through web browsers on Windows. There are no CLI, shell, or cross-platform examples (such as Azure CLI, Bash, or Linux-native tools), nor any mention of Linux-specific workflows. All screenshots and instructions assume use of the Azure portal, which is often associated with Windows environments, and there is no guidance for users who may prefer or require Linux-based automation or command-line approaches.
Recommendations
  • Add equivalent instructions for creating connectors using Azure CLI, which is cross-platform and widely used on Linux.
  • Provide examples for connector creation using REST APIs or automation scripts (e.g., Bash, Python), suitable for Linux environments.
  • Include notes or links to Linux-specific tools and workflows for managing Confluent connectors in Azure.
  • Ensure that screenshots and UI references are supplemented with command-line alternatives.
  • Explicitly state that all steps can be performed from any OS with a supported browser, and clarify any platform-specific requirements.
GitHub Create Pull Request
Partner Solutions Troubleshoot Apache Kafka & Apache Flink on Confluent Cloud ...solutions/apache-kafka-confluent-cloud/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure portal workflows and troubleshooting steps, which are primarily accessed via web UI and Microsoft-centric tools. There are no examples or instructions for Linux users, such as command-line alternatives, nor is there mention of Linux-specific tools or patterns. All references to troubleshooting, permissions, and resource management are given in the context of the Azure portal, which is most commonly used on Windows environments.
Recommendations
  • Add CLI-based troubleshooting steps using Azure CLI or REST API, which can be run on Linux, macOS, and Windows.
  • Include examples for managing resources and permissions via command-line tools (e.g., az commands) alongside portal instructions.
  • Mention Linux compatibility and provide links to documentation for Linux users where relevant.
  • Clarify that the Azure portal is accessible from any OS, and provide parity for users who prefer non-GUI workflows.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/add-confluent-connectors.md ...ache-kafka-confluent-cloud/add-confluent-connectors.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes connector creation via the Azure portal UI, which is primarily accessed through a web browser on Windows systems and is strongly associated with Windows workflows. There are no CLI, shell, or Linux-native instructions or examples (such as using Azure CLI, REST API, or direct connector configuration via files or scripts), nor is there any mention of Linux-specific tools or patterns. The documentation implicitly assumes a Windows-centric environment and omits Linux parity in terms of operational guidance.
Recommendations
  • Add instructions for creating connectors using Azure CLI, including example commands for Linux/macOS terminals.
  • Include REST API examples for connector creation and management, with curl commands suitable for Linux environments.
  • Explicitly mention that the Azure portal is accessible from any OS and provide screenshots or notes that reflect cross-platform usage.
  • Provide guidance for managing connectors via configuration files or scripts, with examples using bash or other Linux-native tools.
  • Ensure troubleshooting and related content include Linux-specific scenarios and tools.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/troubleshoot.md ...solutions/apache-kafka-confluent-cloud/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively references Azure portal workflows and Microsoft Entra ID, which are primarily Windows-centric tools and patterns. There are no examples or troubleshooting steps involving Linux tools, command-line interfaces, or cross-platform alternatives. All instructions assume use of the Azure portal (web UI), with no mention of CLI, Bash, or Linux-native troubleshooting approaches.
Recommendations
  • Add troubleshooting steps using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include examples of how to check resource status, permissions, and perform actions using Bash or shell scripts.
  • Reference Linux-compatible tools for interacting with Confluent Cloud and Azure resources, such as curl, jq, or az CLI.
  • Explicitly state that the instructions apply to all platforms, or provide platform-specific guidance where workflows differ.
  • Mention that the Azure portal is accessible from any OS, but offer parity for users who prefer command-line or automation approaches.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/troubleshoot.md ...solutions/apache-kafka-confluent-cloud/troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure portal (a web interface, but often associated with Windows environments) and Microsoft-specific tools and terminology (e.g., Microsoft Entra, Azure roles, Azure Marketplace). There are no examples or troubleshooting steps for Linux environments, command-line tools, or cross-platform alternatives. All instructions assume use of the Azure portal and do not mention Linux CLI, shell commands, or non-Windows workflows.
Recommendations
  • Add troubleshooting steps and examples for Linux users, such as using Azure CLI on Linux, shell commands, or relevant Linux tools.
  • Include parity for role and permission management using CLI (az command) and PowerShell, with examples for both Windows and Linux.
  • Mention cross-platform access methods and clarify that the Azure portal is web-based and accessible from any OS.
  • Provide troubleshooting guidance for common Linux-specific issues (e.g., authentication, connectivity, resource management) when using Confluent Cloud.
  • Ensure that all instructions and examples are OS-agnostic or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/add-confluent-connectors.md ...ache-kafka-confluent-cloud/add-confluent-connectors.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes connector creation via the Azure portal UI, which is primarily accessed through a web browser on Windows systems. There are no CLI, shell, or Linux-native instructions or examples. All screenshots and workflow descriptions assume use of the Azure portal, with no mention of Linux tools, terminal commands, or cross-platform alternatives. This creates a subtle Windows bias by omitting Linux-centric workflows and examples.
Recommendations
  • Add instructions for creating connectors using Azure CLI, PowerShell, and Bash, with explicit Linux shell examples.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
  • Mention cross-platform access to the Azure portal and clarify that all steps can be performed from Linux, macOS, or Windows.
  • Provide links to documentation for Linux users on installing required tools (e.g., Azure CLI) and accessing the portal.
  • If possible, offer REST API examples for connector creation, with sample curl commands usable on Linux.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/dynatrace/link-to-existing-resources.md ...tner-solutions/dynatrace/link-to-existing-resources.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web interface) and does not provide any command-line examples, such as Azure CLI or PowerShell. While this avoids explicit Windows tool bias, it implicitly favors Windows users by referencing the Azure portal and its screenshots, which are most commonly accessed from Windows environments. There are no Linux-specific instructions, nor is there mention of using the Azure CLI or other cross-platform tools, which are popular among Linux users. The absence of Linux command-line examples or parity in instructions constitutes a subtle Windows-first and missing Linux example bias.
Recommendations
  • Add equivalent instructions for linking Dynatrace resources using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples or notes for performing these steps via command line, with sample scripts for both PowerShell (Windows) and Bash (Linux).
  • Explicitly mention that the Azure portal is accessible from any OS and provide guidance for Linux users where relevant.
  • Provide links to documentation for Azure CLI and PowerShell usage for resource management, so users can choose their preferred platform.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/sso.md ...s/blob/main/articles/partner-solutions/includes/sso.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references the Azure portal, a Microsoft-centric (and thus Windows-associated) tool, without mentioning or providing alternatives for Linux users or command-line options. There are no examples or instructions for Linux environments or cross-platform command-line tools.
Recommendations
  • Include instructions for using cross-platform tools such as Azure CLI or PowerShell Core (which runs on Linux) to accomplish the same task.
  • Provide examples or references for Linux users, such as how to perform the operation from a Linux environment.
  • Clarify whether the Azure portal steps are platform-agnostic (i.e., accessible from any web browser), and if so, explicitly state this to reassure non-Windows users.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/get-support.md ...-solutions/apache-kafka-confluent-cloud/get-support.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily focused on the Azure portal and does not mention or provide examples for Linux or cross-platform command-line tools. All instructions assume use of the Azure web interface, which is most commonly accessed from Windows environments, and there is no mention of Linux-specific workflows, CLI tools, or parity for non-Windows users.
Recommendations
  • Include instructions for submitting support requests using the Azure CLI, which is cross-platform and commonly used on Linux.
  • Mention and provide examples for accessing Confluent Cloud support from Linux environments or via terminal-based workflows.
  • Clarify that the Azure portal can be accessed from any OS, and provide links or notes for Linux users where appropriate.
  • If relevant, add troubleshooting or support contact steps that can be performed from Linux command line or scripts.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/apache-kafka-confluent-cloud/manage-access.md ...olutions/apache-kafka-confluent-cloud/manage-access.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is heavily oriented around the Azure portal GUI, which is primarily accessed via web browsers on any OS, but the context and all screenshots are from the Azure portal, a Microsoft product. There are no references to command-line tools, scripts, or automation methods (such as Azure CLI, Bash, or PowerShell), nor are there any Linux-specific instructions or examples. The documentation implicitly assumes use of the Azure portal, which is most closely associated with Windows environments, and does not mention or provide parity for Linux-native workflows or tools.
Recommendations
  • Add instructions for managing Confluent Access Management using Azure CLI, including Bash and PowerShell examples where applicable.
  • Provide explicit guidance for Linux users, such as how to perform these tasks from a Linux environment or using cross-platform tools.
  • Include screenshots or terminal output from Linux environments to demonstrate parity.
  • Mention any differences or prerequisites for Linux users (e.g., required packages, browser compatibility, etc.).
  • If possible, provide API or automation options for managing users and permissions, with examples for both Windows and Linux command-line environments.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/manage.md ...lob/main/articles/partner-solutions/includes/manage.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation assumes use of the Azure portal web interface, which is platform-neutral, but the workflow and terminology (e.g., 'search bar', 'All resources') are reminiscent of Windows-centric UI patterns. There are no examples or instructions for performing the same tasks using Linux-friendly tools such as the Azure CLI or Bash scripts, nor is there mention of command-line alternatives.
Recommendations
  • Add equivalent instructions for accessing and managing resources using the Azure CLI, with example commands.
  • Include Bash shell examples for Linux users.
  • Explicitly mention that the Azure portal is accessible from any operating system and provide links to cross-platform tools.
  • Consider rephrasing UI instructions to be less reminiscent of Windows-specific patterns.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/dynatrace/link-to-existing-resources.md ...tner-solutions/dynatrace/link-to-existing-resources.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to link to an Azure Native Dynatrace Service resource using the Azure portal, with all instructions and screenshots based on the Azure web UI. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), and no mention of Linux or cross-platform automation methods. The focus on the Azure portal implicitly favors Windows users, as it is the default experience for many Windows-centric organizations, and omits guidance for users who prefer or require command-line or Linux-based workflows.
Recommendations
  • Add equivalent instructions for performing the linking process using the Azure CLI (az), which is cross-platform and widely used on Linux and macOS.
  • If PowerShell examples are added in the future, ensure that Azure CLI or Bash examples are provided alongside them.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide links or references to command-line alternatives for users who prefer automation or non-GUI workflows.
  • Include a section or appendix with sample scripts for Linux users to automate the resource linking process.
  • Review all screenshots and instructions to ensure they do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or terminology).
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/delete-resource.md ...articles/partner-solutions/includes/delete-resource.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only GUI-based instructions, which are typically associated with Windows environments, and does not mention or provide examples for command-line deletion methods common on Linux (such as using Azure CLI or Bash). There is no mention of Linux tools or workflows.
Recommendations
  • Include equivalent command-line instructions using Azure CLI or Bash that can be run on Linux and macOS.
  • Explicitly mention that the GUI instructions apply to all platforms if that is the case, or clarify platform-specific differences.
  • Provide screenshots or step-by-step guides for both Windows and Linux environments if the process differs.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/reconfigure-sso.md ...articles/partner-solutions/includes/reconfigure-sso.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Microsoft Entra ID, a Microsoft-specific tool, and does not provide any Linux-specific instructions or cross-platform alternatives. There are no examples or guidance for users on Linux or non-Windows platforms.
Recommendations
  • Include instructions or notes for enabling single sign-on using non-Microsoft identity providers or tools commonly used on Linux.
  • Provide command-line or configuration examples relevant to Linux environments, such as using SSSD, PAM, or other open-source authentication mechanisms.
  • Clarify whether the process is platform-agnostic or provide equivalent steps for Linux-based systems if applicable.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/tags.md .../blob/main/articles/partner-solutions/includes/tags.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it also does not mention or illustrate Linux tools, commands, or workflows. This omission may lead to a lack of clarity for Linux users if platform-specific steps are required.
Recommendations
  • If there are platform-specific steps, provide examples for both Windows (e.g., PowerShell, Command Prompt) and Linux (e.g., Bash).
  • Explicitly state if the instructions are platform-agnostic.
  • Include screenshots or command-line snippets for both Windows and Linux environments if applicable.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/agent.md ...blob/main/articles/partner-solutions/includes/agent.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides generic installation and uninstallation steps without specifying any platform, but it uses terms like 'Install Extension' and 'Uninstall Extension' that are more commonly associated with Windows GUIs. There are no command-line examples or references to Linux-specific tools or procedures, and no mention of Linux package managers or shell commands.
Recommendations
  • Add explicit Linux installation and uninstallation instructions, including command-line examples (e.g., using apt, yum, or shell scripts).
  • Clarify whether the steps apply to both Windows and Linux, or provide separate sections for each platform.
  • Include screenshots or command snippets for Linux environments to ensure parity.
  • Avoid using GUI-centric terminology unless it applies equally to Linux desktop environments.
GitHub Create Pull Request
Partner Solutions https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/partner-solutions/includes/delete-resource.md ...articles/partner-solutions/includes/delete-resource.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only GUI-based instructions without mentioning command-line alternatives. There is no reference to platform-specific tools, but the lack of CLI examples (such as Bash or PowerShell) may disadvantage Linux users who often prefer or require command-line instructions.
Recommendations
  • Add command-line instructions for deleting the resource using both PowerShell (for Windows users) and Bash/CLI (for Linux/macOS users).
  • Explicitly mention cross-platform tools such as Azure CLI and provide examples for each supported OS.
  • Clarify whether the GUI instructions apply equally to all platforms or if there are platform-specific differences.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →