Automanage
25
Total Pages
9
Linux-Friendly Pages
16
Pages with Bias
64.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
102 issues found
Showing 26-50 of 102 flagged pages
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md
.../main/articles/automanage/repair-automanage-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary method for ARM template deployment before mentioning Linux-friendly alternatives, and by providing explicit PowerShell module references. There are no Linux shell (bash) or cross-platform scripting examples, and PowerShell is referenced without clarifying its cross-platform availability. The Azure CLI is mentioned, but not prioritized, and no Linux-specific guidance is given.
Recommendations
- Provide explicit bash or shell script examples for ARM template deployment, especially for Linux users.
- Clarify that PowerShell is available cross-platform, or avoid assuming Windows-only usage.
- List Azure CLI examples before PowerShell, as CLI is natively cross-platform.
- Include notes or links for Linux users on installing and using Azure CLI and PowerShell Core.
- Ensure screenshots and portal instructions do not assume a Windows environment.
Create Pull Request
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md
...ticles/automanage/tutorial-create-assignment-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating Windows virtual machines, omitting Linux VM creation steps. Both Azure CLI and PowerShell instructions are given, but PowerShell (a Windows-centric tool) is featured equally, and no Linux shell or bash-specific guidance is present. The tutorial does not mention or show how to use Linux images or create Linux VMs, nor does it reference Linux-specific patterns or tools.
Recommendations
- Add parallel examples for creating Linux virtual machines using both Azure CLI and PowerShell, specifying a popular Linux image (e.g., UbuntuLTS).
- Include notes or tabs for bash shell usage, especially for Azure CLI commands, to clarify cross-platform compatibility.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide links to installation instructions for all platforms.
- Show how to assign Automanage profiles to Linux VMs, if supported, and clarify any differences in supported features or configuration.
- Balance the use of PowerShell and CLI by prioritizing CLI (which is cross-platform) or by providing bash script examples.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-custom-profile.md
...articles/automanage/virtual-machines-custom-profile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by referencing Windows-specific features (such as Microsoft Antimalware and Windows Admin Center) and providing customization options only for Windows machines (e.g., audit modes for Azure security baselines in Guest Configuration). There are no Linux-specific examples, features, or equivalent configuration options mentioned, and Linux support/parity is not addressed.
Recommendations
- Explicitly state which features are supported for Linux VMs and provide equivalent Linux configuration options where possible.
- Include Linux-specific examples or notes, especially for features that differ between Windows and Linux (e.g., antimalware, security baselines, monitoring agents).
- If certain features are Windows-only, clearly indicate this and suggest alternative approaches or tools for Linux users.
- Add examples or documentation links for configuring Automanage profiles for Linux VMs, including supported services and settings.
- Review and update ARM template examples to include Linux-relevant configuration options or clarify which settings apply to Linux.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-smb-over-quic.md
...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes SMB over QUIC in the context of Windows Server 2022 Datacenter: Azure Edition, with no mention of Linux support, Linux VM images, or cross-platform configuration. All examples and steps assume a Windows environment, and the only referenced documentation is for Windows Server. There are no Linux equivalents, tools, or instructions provided.
Recommendations
- Explicitly state whether SMB over QUIC and Automanage best practices are supported on Linux VMs. If not supported, clarify this early in the documentation.
- If Linux support exists or is planned, provide parallel instructions for enabling and managing SMB over QUIC on Linux-based Azure VMs.
- Include references to Linux SMB/QUIC documentation or community resources, if available.
- When mentioning prerequisites or supported images, list both Windows and Linux options (if applicable), or explain the Windows-only limitation.
- Consider adding a comparison table or section outlining feature parity and differences between Windows and Linux environments for SMB over QUIC and Automanage.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-arc.md
...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page lists both Windows and Linux as supported operating systems, but there is a clear Windows bias. Windows Server versions are listed first, and the only anti-malware solution mentioned is Microsoft Antimalware, which is explicitly stated as Windows-only. There are no Linux-specific examples, tools, or guidance, and no mention of Linux equivalents for anti-malware or other management tools. The documentation does not provide Linux-specific considerations or best practices, despite being tagged as part of a Linux collection.
Recommendations
- List Linux operating systems before or alongside Windows to avoid the impression of Windows primacy.
- For each Windows-specific tool or feature (e.g., Microsoft Antimalware), mention Linux equivalents (such as ClamAV, ESET, or other supported anti-malware solutions for Linux) or explicitly state if there is no Linux support.
- Provide Linux-specific configuration examples, troubleshooting steps, or best practices where relevant.
- Include notes on any differences in feature support or behavior between Windows and Linux, especially for services like Change Tracking, Update Management, and Machine Configuration.
- Ensure that documentation sections and examples are balanced between Windows and Linux, especially in articles marked as relevant to Linux.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-custom-profile.md
...articles/automanage/virtual-machines-custom-profile.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific features (such as Windows Admin Center and Microsoft Antimalware), mentioning Windows-only customization options, and omitting Linux-specific guidance or examples. There are no Linux-specific instructions or parity notes for Linux VMs, and Windows tools are referenced without Linux equivalents.
Recommendations
- Explicitly state which features are Windows-only and which are available for Linux VMs.
- Add examples or notes for configuring Automanage custom profiles for Linux VMs, including supported services and any Linux-specific settings.
- If certain services (e.g., Antimalware, Windows Admin Center) are not available for Linux, provide equivalent Linux security or management recommendations, or clarify their absence.
- Include Linux command-line examples (such as Bash/CLI) where relevant, especially in deployment steps.
- Consider a table or section comparing feature support between Windows and Linux VMs in Automanage.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md
.../main/articles/automanage/repair-automanage-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is mentioned explicitly and equally alongside the cross-platform Azure CLI. There are no Linux- or bash-specific examples or mentions, and PowerShell is referenced without clarifying its cross-platform availability. The ordering of instructions often lists PowerShell before or alongside CLI, but never bash or Linux-native tooling. No Linux-specific guidance or screenshots are provided.
Recommendations
- Emphasize Azure CLI as the primary example, as it is cross-platform and works natively on Linux, macOS, and Windows.
- Clarify that PowerShell Core is available cross-platform, or otherwise avoid implying it is Windows-only.
- Add explicit bash shell examples for ARM template deployment, e.g., using curl and az CLI together.
- Where screenshots or UI instructions are given, ensure they are not Windows-specific or clarify that the Azure portal is OS-agnostic.
- If mentioning PowerShell, always mention Azure CLI first to avoid the perception of Windows-first bias.
- Consider including a section or note for Linux users, highlighting any differences or confirming parity.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md
...ticles/automanage/tutorial-create-assignment-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by only providing examples for creating a Windows virtual machine (no Linux VM example), and by referencing Windows-specific tools and patterns (e.g., Azure PowerShell, Windows image names). There is no mention or example of creating a Linux VM, nor are Linux-specific considerations or commands provided.
Recommendations
- Add parallel examples for creating a Linux virtual machine using both Azure CLI and Azure PowerShell, including appropriate image references (e.g., Ubuntu, CentOS).
- Explicitly mention that the tutorial applies to both Windows and Linux VMs, and highlight any differences in configuration or prerequisites.
- Include Linux-specific notes or troubleshooting tips where relevant (e.g., SSH key authentication, Linux admin username requirements).
- Ensure that all tool references (Azure CLI, PowerShell) are presented with equal prominence and that Linux users are not implicitly directed to Windows-centric tools or workflows.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md
.../main/articles/automanage/repair-automanage-account.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI, and in some cases, before Linux-native alternatives. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the PowerShell module is referenced directly. The documentation assumes familiarity with Windows tools and does not provide parity for Linux users beyond the Azure CLI.
Recommendations
- Ensure that Azure CLI (which is cross-platform) examples are always listed first, before PowerShell.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash shell usage examples where appropriate.
- Avoid referencing PowerShell-specific modules (like New-AzDeployment) without also providing equivalent bash or shell script examples.
- Add a note or section for Linux/macOS users, clarifying that all steps can be performed using Azure CLI in their native shell environments.
- Where screenshots or UI instructions are given, ensure they are not Windows-specific, or clarify that the Azure portal is OS-agnostic.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md
...ticles/automanage/tutorial-create-assignment-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating a Windows virtual machine, omitting any Linux VM creation examples. Additionally, the PowerShell example is presented alongside Azure CLI, but there is no mention of Linux-specific tools or shell environments. The Azure CLI installation link defaults to the Windows tab, and the VM creation command uses a Windows image without showing how to use a Linux image.
Recommendations
- Add a Linux virtual machine creation example using both Azure CLI and PowerShell, specifying a common Linux image (e.g., Ubuntu).
- Ensure the Azure CLI installation link is platform-neutral or includes Linux installation instructions prominently.
- Where PowerShell is mentioned, also reference Bash or other common Linux shells for parity.
- Explicitly state that the tutorial works for both Windows and Linux VMs, and provide guidance or examples for both.
- Include screenshots or portal instructions that show both Windows and Linux VM Automanage blades if there are differences.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-custom-profile.md
...articles/automanage/virtual-machines-custom-profile.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific features (such as modifying audit modes for security baselines in Guest Configuration for Windows machines only) and enabling WindowsAdminCenter in the ARM template, without mentioning Linux equivalents or providing Linux-specific guidance. There are no Linux-specific examples or clarifications about Linux support, and Windows-related options are mentioned explicitly while Linux is omitted.
Recommendations
- Explicitly state which features are supported for Linux VMs and which are Windows-only, especially in sections referencing features like Guest Configuration or WindowsAdminCenter.
- Provide Linux-specific examples or clarify how to configure Automanage profiles for Linux VMs, including any differences in supported services or settings.
- If certain services (e.g., Microsoft Antimalware, WindowsAdminCenter) are not available for Linux, mention equivalent Linux tools or note their absence.
- Include ARM template snippets or configuration examples tailored for Linux VMs, highlighting any required changes or limitations.
- Review the documentation for opportunities to mention Linux support alongside Windows, rather than only referencing Windows features.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-smb-over-quic.md
...b/main/articles/automanage/automanage-smb-over-quic.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references Windows Server 2022 Datacenter: Azure Edition and only describes enabling SMB over QUIC and Automanage best practices for Windows VMs. There are no examples, instructions, or mentions of Linux support, tools, or equivalents. All links and references point to Windows Server documentation, and the workflow assumes a Windows-centric environment.
Recommendations
- Clearly state whether SMB over QUIC and Automanage best practices are supported or unsupported on Linux VMs.
- If Linux support exists, provide equivalent instructions and examples for Linux-based VMs, including any required packages, configuration steps, and management tools.
- If Linux is not supported, explicitly mention this limitation early in the documentation to set user expectations.
- Include references or links to Linux SMB (Samba) documentation and clarify differences in feature support between Windows and Linux.
- Consider providing a comparison table of supported features and management workflows for both Windows and Linux environments.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-configuration-profile.md
...s/automanage/move-automanaged-configuration-profile.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no equivalent examples for Linux users (e.g., using Bash, curl, or az CLI), and the workflow assumes familiarity with Windows scripting and tools. This creates a significant bias toward Windows environments and leaves Linux users without clear guidance.
Recommendations
- Provide equivalent examples using Bash and curl for REST API calls.
- Include az CLI commands for all operations where possible, as az CLI is cross-platform.
- Explicitly mention that the steps can be performed from any OS, and clarify tool requirements.
- Structure the documentation to present both Windows/PowerShell and Linux/Bash examples side by side.
- Avoid assuming PowerShell as the default scripting environment; offer alternatives for Linux/macOS users.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-arc.md
...e-docs/blob/main/articles/automanage/automanage-arc.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation lists Windows Server versions first in the supported OS section and includes a Windows-only service (Microsoft Antimalware) in the participating services table. There are no Linux-specific examples, tools, or guidance, and the only security/antimalware solution mentioned is exclusive to Windows. No Linux security or monitoring tools are referenced, and no Linux-specific configuration or troubleshooting examples are provided.
Recommendations
- List Linux distributions before or alongside Windows Server in the supported operating systems section to avoid the impression of Windows primacy.
- Include Linux-specific security/antimalware solutions (such as Microsoft Defender for Endpoint on Linux or third-party supported solutions) in the participating services table, or clarify the Linux equivalents.
- Add Linux-specific configuration, troubleshooting, or onboarding examples, especially for common tasks like monitoring, update management, and compliance.
- Reference Linux-native tools and patterns (e.g., systemd, auditd, Linux package managers) where relevant, or provide links to Linux documentation for these services.
- Clearly indicate which services or features are Windows-only and provide Linux alternatives or workarounds where possible.
Automanage
Move an Azure Automanage configuration profile across regions
...s/automanage/move-automanaged-configuration-profile.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no Linux/macOS equivalents (e.g., Bash, curl, az CLI), nor is there mention of how to perform these steps on non-Windows platforms. This creates friction for Linux/macOS users, who must translate the instructions themselves.
Recommendations
- Add equivalent examples using Bash and curl for REST API calls.
- Include instructions using the Azure CLI (az) where possible, which is cross-platform.
- Explicitly state that the process can be performed on Linux/macOS and provide sample commands.
- Reorder examples so that cross-platform tools (az CLI, REST API via curl) are shown first or alongside PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively providing examples for creating a Windows virtual machine and omitting Linux VM creation steps. While Azure CLI and PowerShell commands are shown, only Windows images are referenced, and there are no instructions or examples for Linux VM creation or Linux-specific considerations.
Recommendations
- Include parallel examples for creating a Linux virtual machine (e.g., using --image UbuntuLTS in Azure CLI).
- Add notes or tabs for Linux/macOS users, especially in sections where PowerShell is referenced.
- Clarify that Azure CLI works cross-platform and provide Linux/macOS installation links.
- Mention any differences in Automanage profile assignment for Linux VMs if applicable.
Automanage
Azure Automanage Machine Best Practices
...articles/automanage/virtual-machines-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Automanage Machine Best Practices demonstrates a Windows bias by referencing Windows-specific features (such as Windows security baselines) and omitting explicit mention of Linux equivalents or examples. The 'Guest configuration' section specifically states that Windows security baselines are installed, with no mention of Linux security baselines or configuration options. Throughout the page, there are no examples or clarifications for Linux VM onboarding, configuration, or best practices, despite Azure Automanage supporting both Windows and Linux VMs.
Recommendations
- Explicitly mention Linux support and provide examples or references for Linux VM onboarding and configuration.
- Clarify whether features like Guest configuration and security baselines have Linux equivalents, and link to relevant documentation.
- Add a table column or section indicating OS applicability (Windows, Linux, or both) for each participating service.
- Provide links to Linux-specific best practices or configuration guides where appropriate.
Automanage
Azure Quickstart SDK for JavaScript
.../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a 'windows_first' bias by linking only to the Windows VM quick-create guide in the prerequisites, without mentioning or linking to the equivalent Linux VM documentation. There are no Linux-specific instructions or examples, and the prerequisites implicitly assume a Windows VM context, which may create confusion or friction for Linux users.
Recommendations
- Add a link to the Linux VM quick-create documentation alongside the Windows link in the prerequisites.
- Clarify that the JavaScript SDK works with both Windows and Linux VMs, and provide examples or notes relevant to Linux users where appropriate.
- Ensure that any referenced Azure VM documentation or examples are platform-neutral or include both Windows and Linux variants.
Automanage
Create a custom profile in Azure Automanage for VMs
...articles/automanage/virtual-machines-custom-profile.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows Only Feature
Summary
The documentation page presents Azure Automanage features and configuration steps in a platform-neutral way for most of the content, focusing on the Azure portal and ARM templates. However, there is a notable Windows bias in the mention of 'WindowsAdminCenter/Enable' and the statement that only Windows machines can modify audit modes for Azure security baselines in Guest Configuration. No Linux/macOS-specific features, examples, or parity notes are provided, and some features appear to be Windows-only.
Recommendations
- Explicitly state which features are Windows-only and which are available for Linux/macOS.
- Add examples or notes for Linux VM configuration, especially regarding security baselines and management agent support.
- If Linux equivalents exist (e.g., for monitoring, backup, security), mention them and provide configuration guidance.
- Clarify any limitations for non-Windows VMs in the ARM template section.
- Consider including a table summarizing feature parity between Windows and Linux VMs.
Automanage
Move an Azure Automanage configuration profile across regions
...s/automanage/move-automanaged-configuration-profile.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell syntax) for all examples and instructions. There are no equivalent examples for Linux/macOS users (e.g., using curl, bash, or Azure CLI), nor is there any mention of how to perform these steps outside of PowerShell. This creates friction for users on non-Windows platforms and may prevent them from completing the task without additional research.
Recommendations
- Add equivalent examples using curl and/or wget for Linux/macOS users to perform REST API calls.
- Provide Azure CLI examples for all major steps (GET, PUT, property modification) as Azure CLI is cross-platform.
- Explicitly mention that the process can be performed on any OS using REST API calls, and link to REST API documentation.
- Consider reordering examples so that cross-platform tools (Azure CLI, REST API) are shown before or alongside PowerShell.
Automanage
Azure Quickstart SDK for JavaScript
.../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by linking only to the Windows virtual machine quick-create guide in the prerequisites section and omitting any mention of Linux VM equivalents. No Linux-specific instructions, examples, or links are provided, which may lead Linux users to feel unsupported or uncertain about compatibility.
Recommendations
- Add a link to the Linux VM quick-create documentation alongside the Windows link in the prerequisites.
- Explicitly state that the JavaScript SDK and Automanage features are compatible with both Windows and Linux VMs, if applicable.
- Provide examples or notes for any Linux-specific considerations, such as configuration differences or supported features.
- Ensure parity in documentation by mentioning both operating systems where relevant.
Automanage
Repair a broken Azure Automanage Account
.../main/articles/automanage/repair-automanage-account.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for ARM template deployment, but PowerShell is mentioned before Azure CLI, and only the PowerShell module name is explicitly referenced. There are no Linux/macOS-specific instructions or examples, and no mention of shell environments other than PowerShell. The Azure CLI examples are present, but the documentation implicitly prioritizes Windows/PowerShell tools and patterns.
Recommendations
- List Azure CLI instructions before PowerShell to reflect cross-platform parity.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS.
- Provide bash/zsh shell command examples where relevant, especially for ARM template deployment.
- Clarify that PowerShell examples are for Windows users, and offer alternatives for Linux/macOS.
- Add a note about platform compatibility for each tool mentioned.
Automanage
Azure Automanage Machine Best Practices
...articles/automanage/virtual-machines-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page for Azure Automanage Machine Best Practices demonstrates a Windows bias primarily through its explicit mention of installing Windows security baselines via guest configuration, without reference to Linux equivalents. There are no examples or guidance specific to Linux VMs, and the documentation does not clarify how Automanage best practices apply to Linux environments, despite Azure supporting both Windows and Linux virtual machines.
Recommendations
- Add explicit references to Linux support in each service description, clarifying which features are available for Linux VMs.
- Include examples or documentation links for configuring Automanage on Linux VMs, such as Linux security baselines or compliance policies.
- When mentioning guest configuration, specify whether Linux equivalents (e.g., CIS benchmarks, OS-specific policies) are supported and how they are applied.
- Ensure parity in documentation by listing both Windows and Linux scenarios, tools, and outcomes where applicable.
Automanage
Azure Quickstart SDK for Python
...docs/blob/main/articles/automanage/quick-python-sdk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows virtual machines in the prerequisites and linking exclusively to Windows VM creation guides. There are no Linux-specific instructions, examples, or links, and Linux VM scenarios are not mentioned or supported explicitly.
Recommendations
- Include links to both Windows and Linux VM creation guides in the prerequisites.
- Clarify that the Python SDK works with both Windows and Linux VMs, if applicable.
- Add examples or notes for Linux VM users, such as differences in configuration profiles or requirements.
- Ensure terminology and instructions are platform-neutral unless a feature is Windows-only.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by only providing examples for creating a Windows virtual machine and omitting Linux VM creation steps. Additionally, while both Azure CLI and PowerShell are shown, the resource creation examples (especially VM creation) use Windows-specific images and parameters, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
- Add parallel examples for creating a Linux virtual machine (e.g., using --image UbuntuLTS in Azure CLI and PowerShell).
- Explicitly mention that the Azure CLI works on Linux/macOS and provide installation links for those platforms.
- Include notes or tabs for Linux/macOS users where command syntax or behavior differs.
- Clarify that the Python SDK steps are cross-platform, and highlight any OS-specific considerations if relevant.