Automanage
50
Total Pages
35
Linux-Friendly Pages
15
Pages with Bias
30.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
44 issues found
Showing 26-44 of 44 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only the Windows VM quick-create documentation in the prerequisites and omitting any mention or example of Linux virtual machines. There are no Linux-specific instructions, links, or examples, which may lead users to assume the SDK is primarily or exclusively for Windows VMs.
Recommendations
- Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
- Explicitly state that the SDK supports both Windows and Linux VMs, if applicable.
- Provide example usage or notes for Linux VMs, highlighting any differences in configuration or prerequisites.
- Ensure that terminology and instructions are platform-neutral unless a step is genuinely platform-specific.
Create Pull Request
Automanage
Automanage Configuration profiles
...articles/automanage/overview-configuration-profiles.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page discusses Azure Automanage configuration profiles in a general way but shows subtle Windows bias. It references Microsoft Antimalware (a Windows-centric solution) as the default example for customizing profiles, and does not provide any Linux-specific examples or mention Linux tools. The links to further documentation list 'Automanage for Linux' after 'Automanage for Windows Server', and the only concrete example (antimalware) is Windows-specific. No Linux command-line or configuration examples are present.
Recommendations
- Include Linux-specific examples when discussing customization, such as referencing Linux security tools (e.g., ClamAV) alongside Microsoft Antimalware.
- Alternate the order of links or mention Linux and Windows equivalently when listing further reading or supported platforms.
- Provide examples or notes on how configuration profiles differ for Linux machines, including any unique services or settings.
- Explicitly state parity or differences between Windows and Linux support in Automanage profiles to help users understand platform-specific considerations.
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 demonstrates Windows bias by linking exclusively to the Windows VM quick-create portal in the prerequisites, without mentioning or providing equivalent instructions or links for Linux virtual machines. There are no Linux-specific examples or references, and the documentation implicitly assumes the user is working with Windows VMs.
Recommendations
- Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
- Clarify that Automanage supports both Windows and Linux VMs, if applicable.
- Provide examples or notes for enabling Automanage on Linux VMs, including any differences in configuration or supported features.
- Ensure terminology and instructions are platform-neutral unless a feature is Windows-specific, in which case explicitly state so.
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 demonstrates Windows bias by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents, and by omitting Linux-specific examples or guidance throughout. The guest configuration section only discusses Windows baselines, and there is no mention of Linux security baselines or configuration management. No Linux-specific tools, patterns, or examples are provided, and the documentation implicitly assumes a Windows-centric environment.
Recommendations
- Include information about Linux security baselines and how guest configuration applies to Linux VMs.
- Provide examples or guidance for both Windows and Linux environments, especially in sections discussing configuration, monitoring, and compliance.
- Mention Linux-specific tools or patterns where relevant (e.g., OS update management, security hardening).
- Clarify which services and features are supported for Linux VMs and highlight any differences in implementation or configuration.
- Add links to Linux documentation or best practices where appropriate.
Automanage
About Azure Automanage Machine Best Practices
...e-docs/blob/main/articles/automanage/overview-about.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally maintains platform neutrality in its descriptions, but there is a subtle Windows bias: Windows Server is mentioned before Linux in lists and links, and there are no concrete examples or walkthroughs for Linux users (e.g., onboarding steps, configuration, or screenshots). The page references both platforms but does not provide Linux-specific examples or parity in guidance.
Recommendations
- Alternate the order of Windows and Linux mentions to avoid implicit prioritization (e.g., list Linux before Windows in some sections).
- Provide concrete onboarding/configuration examples for both Windows and Linux, including screenshots or command-line instructions relevant to each platform.
- Ensure that any referenced tools or services (such as Azure Update Management) include notes or links about Linux compatibility and usage.
- Add a section or callout specifically addressing Linux users, highlighting any differences or considerations unique to Linux environments.
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 VM quick-create guide in the prerequisites, without mentioning or providing a Linux VM equivalent. There are no Linux-specific instructions or examples, and the documentation implicitly assumes Windows as the default platform for virtual machines.
Recommendations
- Include links to both Windows and Linux VM quick-create guides in the prerequisites section.
- Clarify that Automanage can be used with both Windows and Linux VMs, if applicable.
- Provide examples or notes for Linux VM scenarios where relevant.
- Ensure terminology and instructions are platform-neutral unless a feature is Windows-only.
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 Windows bias by referencing only Windows virtual machines in the prerequisites and linking exclusively to Windows VM creation guides. There are no examples or guidance for Linux VMs, nor are Linux-specific considerations mentioned, despite Azure Automanage supporting both Windows and Linux VMs.
Recommendations
- Include links to both Windows and Linux VM creation guides in the prerequisites section.
- Explicitly state that the steps apply to both Windows and Linux VMs, or note any differences if applicable.
- Provide examples or notes for Linux VM users, such as OS-specific configuration profile options or troubleshooting tips.
- Ensure parity in documentation references and examples for both platforms to avoid implicit bias.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/overview-about.md
...e-docs/blob/main/articles/automanage/overview-about.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page mentions both Windows and Linux support but consistently lists Windows before Linux (e.g., 'Supported Windows Server versions and Linux distros'), and does not provide any concrete examples, walkthroughs, or tool references for either platform. However, the structure and phrasing (such as 'Automanage for Windows Server' and 'Automanage for Linux') suggest a Windows-first approach, and there are no Linux-specific examples or tools mentioned, which may leave Linux users with less clarity.
Recommendations
- Provide explicit Linux examples and walkthroughs alongside Windows ones, ensuring parity in detail and clarity.
- When listing supported platforms, alternate the order or use neutral phrasing (e.g., 'Supported operating systems: Windows Server and Linux distributions').
- Include references to Linux-specific tools, commands, or configuration steps where relevant.
- Ensure that any linked pages (such as 'Automanage for Linux') are equally comprehensive as their Windows counterparts.
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 bias towards Windows by linking only to the Windows VM quick-create portal in the prerequisites, without mentioning or providing equivalent instructions for Linux VMs. There are no Linux-specific examples or references, and the documentation implicitly assumes the user is working with Windows virtual machines.
Recommendations
- Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
- Explicitly state that Automanage supports both Windows and Linux VMs, if applicable.
- Provide example resource IDs or configuration profile assignments for Linux VMs, if they differ.
- Add notes or examples relevant to Linux VM onboarding and management where appropriate.
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 referencing only Windows virtual machines in the prerequisites section and linking exclusively to the Windows VM quick-create guide. There are no Linux VM examples, nor is there mention of Linux-specific considerations or links to Linux VM documentation. All instructions and code samples are generic, but the context and references favor Windows.
Recommendations
- Include links to both Windows and Linux VM quick-create guides in the prerequisites.
- Explicitly state that the instructions apply to both Windows and Linux VMs, or provide notes on any OS-specific differences.
- Add examples or notes for onboarding Linux VMs, if there are any differences in the process.
- Ensure parity in documentation references and resources for both Windows and Linux users.
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 VM quick-create guide in the prerequisites, without mentioning or providing equivalent instructions for Linux virtual machines. There are no Linux-specific examples, notes, or links, and the documentation implicitly assumes the user is working with Windows VMs.
Recommendations
- Add links to both Windows and Linux VM quick-create guides in the prerequisites section.
- Clarify that Automanage supports both Windows and Linux VMs, if applicable.
- Include examples or notes for Linux VM scenarios, such as differences in configuration profile application or prerequisites.
- Ensure terminology and instructions are platform-neutral unless a feature is Windows-only, in which case explicitly state the limitation.
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 by referencing Windows-specific features (such as Windows security baselines) without mentioning Linux equivalents. There are no explicit examples or guidance for Linux VMs, and the guest configuration section only refers to Windows security baselines, omitting information about Linux compliance or configuration options.
Recommendations
- Include information about Linux security baselines or compliance options in the guest configuration section.
- Provide examples or references for both Windows and Linux VM onboarding and configuration.
- Clarify which services and features apply to Linux VMs and highlight any differences in implementation.
- Add links to documentation about configuring best practices for Linux VMs, such as CIS benchmarks or other relevant standards.
- Ensure that any mention of Windows-specific tools or settings is paired with Linux equivalents where available.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a minor Windows bias by linking to the Windows virtual machine quick-create guide as the example for prerequisites, without mentioning or linking to the equivalent Linux VM documentation. All code examples are platform-agnostic (Go SDK), but the VM example is Windows-centric.
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, unless there are platform-specific limitations.
- Add a note clarifying any differences in Automanage support or behavior between Windows and Linux VMs, if applicable.
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
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell as a deployment option alongside Azure CLI, but does not provide equivalent Linux/macOS shell examples (e.g., Bash, shell scripting) for ARM template deployment. PowerShell is mentioned before Linux-native tools, and no explicit Linux/macOS instructions are given for tasks like ARM template deployment. However, Azure CLI is referenced and used for most command-line examples, which are cross-platform.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
- Provide Bash or shell script examples for ARM template deployment (e.g., using Azure CLI in Bash).
- Clarify that PowerShell is available cross-platform, or offer links to install/use PowerShell on Linux/macOS.
- Avoid listing PowerShell before Azure CLI unless there is a technical reason.
- Add a note or section for Linux/macOS users with any platform-specific considerations.
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. All code examples are platform-agnostic Go SDK usage, but the initial setup guidance assumes a Windows VM context.
Recommendations
- Include links to both Windows and Linux VM quick-create documentation in the prerequisites.
- Explicitly state that the instructions apply to both Windows and Linux VMs, if true.
- Add a note or section clarifying any platform-specific considerations for Linux users (if any).
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by linking only to the Windows VM creation guide in the prerequisites and omitting references or examples for Linux VM scenarios. No PowerShell or Windows-specific tooling is mentioned, but the lack of Linux parity in examples and links may cause friction for non-Windows users.
Recommendations
- Include links to both Windows and Linux VM creation guides in the prerequisites.
- Clarify that the Java SDK and Automanage features apply to both Windows and Linux VMs, if applicable.
- Provide example resource IDs or configuration profile assignments for Linux VMs, if they differ.
- Add notes or sections highlighting any platform-specific considerations for Linux/macOS users.
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 provides both Azure CLI and PowerShell examples for ARM template deployment, but PowerShell is mentioned second and only as an alternative. There is a slight Windows-first bias, as PowerShell is a Windows-centric tool and is referenced directly, but Linux/macOS users are not excluded since Azure CLI instructions are present and shown first. No exclusive Windows tools or missing Linux examples are detected.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
- Clarify that PowerShell Core is cross-platform if referencing PowerShell, or link to instructions for using PowerShell on Linux/macOS.
- Consider providing Bash script examples for ARM template deployment for Linux users.
- Add a note that all steps can be performed on Linux/macOS using Azure CLI.
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 instructions. However, it implicitly assumes a generic VM management workflow without mentioning or demonstrating Linux-specific tools, commands, or considerations. There are no references to Windows-specific tools either, but the lack of Linux parity (e.g., shell commands, Linux onboarding nuances) may leave Linux users underserved.
Recommendations
- Add explicit instructions or examples for both Windows and Linux VMs, including any differences in the upgrade process.
- Include sample commands for Linux environments (e.g., Bash/CLI) where relevant, especially for automation or scripting.
- Clarify if there are OS-specific prerequisites, limitations, or behaviors during the upgrade process.
- Mention any Linux-specific tools or patterns (such as cloud-init, systemd, or relevant Azure Linux VM extensions) if applicable.
- Ensure screenshots and UI references are representative of both Windows and Linux VM management experiences.
Automanage
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/automanage/move-automanaged-vms.md
.../blob/main/articles/automanage/move-automanaged-vms.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or instructions, but it references UI actions (e.g., 'Automanage blade') without mentioning CLI or automation options. There are no examples for Linux users, such as using Azure CLI, Bash, or Linux tooling, nor is there mention of Powershell or Windows-specific tools. However, the lack of Linux/CLI examples may disadvantage users who prefer or require non-Windows workflows.
Recommendations
- Add instructions for performing the same actions using Azure CLI, which is cross-platform and commonly used on Linux.
- Include examples or references for automating the process via scripts (Bash, Powershell), making it clear that both Windows and Linux users are supported.
- Explicitly mention that the process can be performed on any platform, and provide parity in documentation for both GUI and CLI workflows.
- If Powershell or Windows tools are referenced in related articles, ensure Linux equivalents are also mentioned or linked.