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 76-100 of 102 flagged pages
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-go-sdk.md
...ure-docs/blob/main/articles/automanage/quick-go-sdk.md
Medium Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/arm-deploy.md
...azure-docs/blob/main/articles/automanage/arm-deploy.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-python-sdk.md
...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 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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-configuration-profiles.md
...articles/automanage/overview-configuration-profiles.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-javascript-sdk.md
.../blob/main/articles/automanage/quick-javascript-sdk.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-best-practices.md
...articles/automanage/virtual-machines-best-practices.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/virtual-machines-best-practices.md
...articles/automanage/virtual-machines-best-practices.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/arm-deploy.md
...azure-docs/blob/main/articles/automanage/arm-deploy.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-go-sdk.md
...ure-docs/blob/main/articles/automanage/quick-go-sdk.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-java-sdk.md
...e-docs/blob/main/articles/automanage/quick-java-sdk.md
Medium Priority
View Details →
Detected Bias Types
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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-javascript-sdk.md
.../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 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.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/quick-python-sdk.md
...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 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.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by linking only to the Windows VM creation guide in the prerequisites and not mentioning Linux VM equivalents. There are no OS-specific code examples, but the prerequisite section may cause confusion or friction for Linux users.
Recommendations
- Add a link to the Linux VM creation guide alongside the Windows guide in the prerequisites.
- Clarify that Automanage supports both Windows and Linux VMs.
- Ensure examples and instructions are OS-neutral or provide notes for both platforms where relevant.
Automanage
Azure Quickstart SDK for Python
...docs/blob/main/articles/automanage/quick-python-sdk.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. The prerequisite section links only to the Windows VM creation guide, with no mention or link to Linux VM equivalents. There are no explicit Linux-specific instructions or examples, and the documentation does not clarify whether the steps apply equally to Linux VMs. However, the core Python SDK usage is platform-agnostic, and no Windows-only tools or PowerShell commands are referenced.
Recommendations
- Add links to both Windows and Linux VM creation guides in the prerequisites section.
- Explicitly state that the Python SDK instructions apply to both Windows and Linux VMs, or clarify any platform-specific considerations.
- Include a note or example showing usage with a Linux VM, if any differences exist.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a minor Windows bias by linking only to the Windows VM quick-create guide in the prerequisites, without mentioning or linking to the equivalent Linux VM documentation. No PowerShell or Windows-specific tools are referenced, and the Go SDK usage is platform-neutral.
Recommendations
- Add a link to the Linux VM quick-create documentation alongside the Windows VM link in the prerequisites.
- Clarify that the Go SDK instructions apply equally to both Windows and Linux VMs.
- Include a note or example referencing Linux VM scenarios, if relevant.
Automanage
Repair a broken Azure Automanage Account
.../main/articles/automanage/repair-automanage-account.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for ARM template deployment, but PowerShell is mentioned second and only in passing. There is no explicit Linux/macOS example or mention of platform-specific considerations. The Azure CLI is cross-platform, but the inclusion of PowerShell (a traditionally Windows-centric tool) without clarifying its cross-platform availability may create a subtle Windows bias. No Linux-specific tools (like bash scripts) or explicit Linux/macOS instructions are provided.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- If mentioning PowerShell, note that PowerShell Core is available cross-platform.
- Provide explicit Linux/macOS instructions or examples (e.g., bash script snippets for ARM template deployment).
- Avoid implying that PowerShell is the default or preferred method unless justified.
- Consider listing Azure CLI examples first, as it is more universally available.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by linking only to the Windows VM creation guide in the prerequisites and omitting references or examples for Linux VM creation. No Linux-specific instructions or parity are provided, which may cause confusion for Linux users.
Recommendations
- Include links to both Windows and Linux VM creation guides in the prerequisites section.
- Clarify that the Java SDK and Automanage features work with both Windows and Linux VMs.
- Add a note or example demonstrating usage with a Linux VM, if any differences exist.
- Ensure terminology and instructions are platform-neutral where possible.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a minor Windows bias by linking only to the Windows VM quick-create portal in the prerequisites section, without mentioning or providing a link to the equivalent Linux VM documentation. All code examples are platform-agnostic (Go SDK), but the initial VM creation guidance is Windows-centric.
Recommendations
- Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
- Clarify that the Go SDK examples work for both Windows and Linux VMs.
- Add a note or example referencing Linux VM scenarios where relevant.
Automanage
About Azure Automanage Machine Best Practices
...e-docs/blob/main/articles/automanage/overview-about.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally maintains parity between Windows and Linux, mentioning both platforms in prerequisites and linking to dedicated pages for each. However, there is a subtle 'windows_first' bias: Windows Server is mentioned before Linux in several lists (e.g., prerequisites, participating services), and the primary examples and links tend to reference Windows before Linux. There are no explicit PowerShell-heavy examples, Windows-only tools, or missing Linux examples on this overview page.
Recommendations
- Alternate the order of Windows and Linux mentions to avoid implicit prioritization.
- Ensure that examples, diagrams, and links are presented for both platforms in parallel, rather than listing Windows first.
- Explicitly state that all features and services apply equally to Linux and Windows where relevant.
- Add direct links to Linux onboarding guides and examples in the 'Next steps' section, not just Windows.
- Review subpages (linked for Windows and Linux) to ensure example parity and avoid deeper bias.
Automanage
Automanage Configuration profiles
...articles/automanage/overview-configuration-profiles.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally maintains neutrality but subtly exhibits a 'windows_first' bias by listing the Windows Server documentation link after the Linux link, but not providing any in-page examples or details for either OS. There are no explicit examples or tools mentioned that are Windows-specific, nor are there missing Linux examples, but the lack of OS-specific examples altogether means parity is not demonstrated.
Recommendations
- Include explicit configuration examples for both Windows and Linux virtual machines within the main documentation page.
- When referencing further documentation, provide equal prominence and detail for both Windows and Linux, possibly by summarizing key differences or considerations inline.
- Avoid assuming familiarity with Windows-specific tools or patterns; if mentioned, always provide the Linux equivalent.
- Consider a comparative table or section that highlights supported features and behaviors for both Windows and Linux environments.
Automanage
Disable Azure Automanage for virtual machines
.../main/articles/automanage/how-to-disable-automanage.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page only describes how to disable Azure Automanage using the Azure portal, without providing any command-line examples or automation options. There is no mention of platform-specific tools, but the absence of CLI or scripting examples (such as Azure CLI, PowerShell, or Bash) means Linux users are not given parity with Windows users, who are more likely to use PowerShell or GUI workflows.
Recommendations
- Add instructions for disabling Automanage using Azure CLI, which is cross-platform and works on both Windows and Linux.
- If PowerShell examples are provided in other documentation, ensure Bash or Azure CLI equivalents are also included.
- Explicitly mention that the Azure portal method works regardless of the VM's operating system, but provide automation options for users who prefer scripting or need to manage many VMs.
- Include links to relevant automation documentation for both Windows and Linux users.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-about.md
...e-docs/blob/main/articles/automanage/overview-about.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally maintains parity between Windows and Linux, mentioning both platforms in prerequisites and linking to dedicated pages for each. However, there is a subtle 'windows_first' bias: Windows Server is listed before Linux distros in the prerequisites, and the link to 'Automanage for Windows Server' precedes 'Automanage for Linux' in the participating services section. No examples, tools, or commands specific to either platform are provided, so there is no evidence of Powershell-heavy bias, missing Linux examples, or exclusive mention of Windows tools.
Recommendations
- List Windows and Linux platforms in alphabetical order or alternate their order to avoid implicit prioritization.
- Ensure that examples, if added in future revisions, include both Windows (e.g., PowerShell) and Linux (e.g., Bash) usage.
- Where platform-specific documentation is linked, present both links together or in a neutral order.
- Explicitly state that Automanage supports both Windows and Linux equally in introductory sections.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/automanage-upgrade.md
...cs/blob/main/articles/automanage/automanage-upgrade.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, commands, or guidance, but all screenshots and instructions are generic and portal-based. There is no explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, there is a lack of Linux-specific examples or considerations, which may leave Linux users uncertain about any OS-specific steps or differences.
Recommendations
- Add explicit notes clarifying that the upgrade process applies equally to both Windows and Linux VMs, or highlight any differences if they exist.
- Include examples or screenshots showing both Windows and Linux VMs in the portal, to demonstrate parity.
- If there are CLI or automation steps, provide both PowerShell (for Windows) and Bash/Azure CLI (for Linux) examples.
- Mention any OS-specific prerequisites or caveats, such as agent compatibility or required permissions, for Linux systems.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/how-to-disable-automanage.md
.../main/articles/automanage/how-to-disable-automanage.md
Low Priority
View Details →
Detected Bias Types
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 automation options. There is no mention of PowerShell, Windows tools, or Windows-specific patterns, but the lack of CLI examples means there is no parity for Linux users who may prefer or require az CLI or bash scripting methods.
Recommendations
- Add instructions for disabling Automanage using the Azure CLI (az), which is cross-platform and commonly used on Linux.
- Include examples for disabling Automanage via REST API or ARM templates to support automation and Linux environments.
- Explicitly mention that the portal method works for both Windows and Linux VMs, if applicable.
- If PowerShell examples are added in the future, ensure equivalent az CLI/bash examples are provided for Linux parity.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/how-to-disable-automanage.md
.../main/articles/automanage/how-to-disable-automanage.md
Low Priority
View Details →
Detected Bias Types
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.