Automanage

25
Total Pages
10
Linux-Friendly Pages
15
Pages with Bias
60.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (26)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-smb-over-quic.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-go-sdk.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing a Linux equivalent. There are no Linux-specific instructions or examples, and the documentation implicitly assumes a Windows VM context.
Recommendations:
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Clarify that the instructions apply to both Windows and Linux VMs, or specify any differences if applicable.
  • Provide examples or notes relevant to Linux virtual machines, especially if there are any platform-specific considerations.
  • Use neutral language when referring to virtual machines, avoiding implicit assumptions that the user is working with Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-arc.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/arm-deploy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page provides generic ARM template instructions without explicit OS-specific steps, but it implicitly prioritizes Windows by omitting Linux-specific deployment examples or considerations. The only direct mention of Linux is relegated to the 'Next steps' section, while no Linux-specific guidance or examples are present in the main onboarding workflow.
Recommendations:
  • Add explicit Linux onboarding examples or notes within the main deployment instructions, not just as a link in 'Next steps'.
  • Include any Linux-specific considerations, such as supported distributions, required extensions, or troubleshooting tips, alongside Windows information.
  • Present both Linux and Windows guidance in parallel where relevant, ensuring parity in detail and visibility.
  • If there are differences in ARM template parameters or deployment steps for Linux VMs, document these clearly with examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/how-to-disable-automanage.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides instructions only for disabling Azure Automanage via the Azure portal and does not include any command-line examples or scripts. There is no mention of PowerShell, Windows tools, or Windows-specific patterns, but there is also no coverage of Linux CLI tools or cross-platform automation methods. The absence of CLI or automation examples (such as Azure CLI, which is cross-platform) may disadvantage Linux users who often prefer or require non-GUI workflows.
Recommendations:
  • Add step-by-step instructions for disabling Automanage using the Azure CLI, which works on both Windows and Linux.
  • If PowerShell examples are added in the future, ensure equivalent Azure CLI or Bash examples are provided.
  • Explicitly mention that the portal method is platform-agnostic, but highlight automation options for users who may not use the GUI.
  • Include links to relevant Azure CLI documentation for managing Automanage profiles and VM onboarding/offboarding.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-custom-profile.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-python-sdk.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page exhibits a Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent guidance for Linux virtual machines. There are no Linux-specific instructions or examples, which may lead Linux users to feel unsupported or unclear about the process.
Recommendations:
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Clarify that the instructions apply to both Windows and Linux VMs, or specify any differences if they exist.
  • Add a note or example demonstrating the process with a Linux VM, if there are any distinctions.
  • Ensure parity in documentation references and examples for both major operating systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-configuration-profiles.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page references both Linux and Windows in a single section, but does not provide any concrete examples or details for either platform within the main content. However, the link to 'Automanage for Linux' is listed after 'Automanage for Windows Server', suggesting a subtle 'windows_first' ordering. There are no command-line examples, but the absence of any Linux-specific examples or tools in the main text constitutes a 'missing_linux_example' bias.
Recommendations:
  • Provide explicit examples for both Windows and Linux platforms within the main documentation, such as how to enable or customize Automanage profiles using platform-specific tools (e.g., PowerShell for Windows, Bash/CLI for Linux).
  • When listing platform-specific documentation or links, alternate the order or list Linux first in some cases to avoid implicit prioritization.
  • Include a table or section summarizing differences and supported features for both Windows and Linux, ensuring parity and clarity.
  • Reference Linux tools and patterns (such as cloud-init, shell scripts, or Linux security solutions) alongside Windows tools where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-javascript-sdk.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent guidance for Linux virtual machines. There are no Linux-specific instructions or examples, and the only VM creation link is for Windows.
Recommendations:
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Explicitly state that the instructions apply to both Windows and Linux VMs, if applicable.
  • Provide examples or notes for any steps that may differ between Windows and Linux environments.
  • Ensure parity in documentation references and examples for both operating systems to avoid user confusion and improve inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-best-practices.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias primarily by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents or clarifying Linux support. There are no explicit Linux examples or references to Linux-specific best practices, tools, or configuration profiles. The only detailed configuration example (Guest configuration) is Windows-centric, and the documentation does not clarify how or if these best practices apply to Linux VMs.
Recommendations:
  • Explicitly state which services and best practices apply to Linux VMs and provide links to Linux-specific documentation where available.
  • For each service (e.g., Guest configuration, Antimalware), mention both Windows and Linux support, including any differences in onboarding, configuration, or available features.
  • Include examples or references for configuring and managing Linux VMs, such as using Linux security baselines or supported Linux antimalware solutions.
  • Where Windows-specific links are provided (e.g., Windows security baselines), provide parallel Linux resources (e.g., CIS benchmarks for Linux).
  • Clarify in tables and descriptions whether each feature or profile is available for Linux, Windows, or both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/repair-automanage-account.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-best-practices.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page exhibits a Windows-first bias, particularly in the 'Guest configuration' section, which only references the installation of Windows security baselines and does not mention Linux equivalents. There are no explicit Linux examples or references to Linux-specific best practices, tools, or configuration baselines, despite Azure Automanage supporting both Windows and Linux VMs.
Recommendations:
  • Include information about Linux guest configuration, such as supported Linux security baselines or compliance policies, alongside the Windows example.
  • Explicitly state which services and features are available for both Windows and Linux VMs, and highlight any differences or limitations.
  • Provide links to Linux-specific documentation where appropriate (e.g., for configuring security baselines or monitoring on Linux VMs).
  • Ensure that examples and descriptions are balanced between Windows and Linux, or clearly indicate when a feature is Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/tutorial-create-assignment-python.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-custom-profile.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/arm-deploy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides generic ARM template instructions without explicit OS bias in the main content, but it lacks Linux-specific examples or guidance. The only mention of Linux is in the 'Next steps' section, which links to a Linux-specific page after the main instructions, suggesting a secondary status for Linux. No Linux-specific deployment nuances or examples are provided, and the documentation does not clarify if the instructions are equally applicable to Linux and Windows VMs.
Recommendations:
  • Add explicit statements clarifying that the ARM template and deployment steps apply to both Windows and Linux VMs, or call out any differences.
  • Include a Linux-specific example or scenario, such as onboarding a Linux VM, and note any parameters or considerations unique to Linux.
  • Present links to both Linux and Windows guidance equally and earlier in the document, not just in 'Next steps'.
  • If there are OS-specific prerequisites or limitations, highlight them in the prerequisites section.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-go-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by linking only to the Windows virtual machine quick-create guide in the prerequisites and not mentioning or providing links/examples for Linux virtual machines. There are no Linux-specific instructions or parity in the examples or references.
Recommendations:
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Clarify that the instructions apply to both Windows and Linux VMs, or provide separate examples if there are differences.
  • Add a note or section addressing any Linux-specific considerations for using Automanage with Go SDK.
  • Ensure that all references to virtual machines are inclusive of both operating systems, not just Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-smb-over-quic.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-configuration-profile.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-arc.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/how-to-disable-automanage.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation provides instructions only for disabling Azure Automanage via the Azure Portal, with no mention of command-line methods (such as PowerShell, Azure CLI, or Bash). However, there is no explicit Windows bias in the form of PowerShell-heavy examples, Windows-first ordering, or exclusive mention of Windows tools. The main bias is the lack of parity for users who prefer or require CLI-based workflows, which are especially common on Linux.
Recommendations:
  • Add instructions for disabling Automanage using the Azure CLI, which is cross-platform and widely used on Linux.
  • If PowerShell examples are added, ensure equivalent Bash/Azure CLI examples are provided.
  • Explicitly mention that the portal method works for both Windows and Linux VMs, or clarify any differences if they exist.
  • Include links to relevant CLI documentation for both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-about.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation lists Windows Server before Linux in the prerequisites and in the links to further documentation, suggesting a subtle 'windows_first' bias. However, there are no explicit examples, commands, or tools shown that are Windows-specific, and Linux is mentioned as supported throughout. No PowerShell-heavy content or exclusive Windows tooling is present.
Recommendations:
  • Alternate the order of Windows and Linux mentions or list them alphabetically to avoid implicit prioritization.
  • Ensure that Linux and Windows documentation links are presented with equal prominence.
  • Consider including a brief example or mention of both Windows and Linux onboarding flows, even if only at a high level, to reinforce parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-java-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites and not mentioning or providing examples for Linux virtual machines. There are no Linux-specific instructions, links, or considerations, which may lead Linux users to feel unsupported or unclear about the process.
Recommendations:
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Explicitly state that the Java SDK and Automanage can be used with both Windows and Linux VMs, if applicable.
  • Provide at least one example or note for Linux VM users, such as any differences in configuration profile assignment or prerequisites.
  • Ensure that terminology and instructions are platform-neutral unless a step is truly platform-specific, in which case both platforms should be covered.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-javascript-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page exhibits a Windows-first bias by linking exclusively to the Windows virtual machine quick-create guide in the prerequisites, without mentioning or providing equivalent guidance for Linux virtual machines. There are no Linux-specific examples or references, which may lead Linux users to feel unsupported or unsure if the instructions are applicable to their environment.
Recommendations:
  • Include links to both Windows and Linux virtual machine quick-create guides in the prerequisites section.
  • Explicitly state that the JavaScript SDK and Automanage features are supported for both Windows and Linux VMs, if applicable.
  • Provide examples or notes relevant to Linux virtual machines where appropriate.
  • Ensure parity in documentation references and guidance for both operating systems to avoid alienating Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-python-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates Windows bias by linking only to the Windows virtual machine creation guide in the prerequisites section and not mentioning or providing equivalent Linux VM instructions or examples. There are no Linux-specific references or parity in the examples or links.
Recommendations:
  • Add a link to the Linux virtual machine creation quickstart alongside the Windows link in the prerequisites section.
  • Clarify that the instructions apply to both Windows and Linux virtual machines, or specify any differences if they exist.
  • Include examples or notes relevant to Linux VMs where appropriate, especially if there are any platform-specific considerations.
  • Review all links and references to ensure both Windows and Linux users are equally supported.