13
Pages Scanned
3
Pages Flagged
13
Changed Pages
23.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-01-23 00:00:08
Finished At: 2026-01-23 18:07:07
Status: failed
Target Repo: Azure Management
Current Phase: discovery
Files Queued: 13
Files Completed: 13
Problematic Pages
3 issues found
Azure Arc
Enable VM Extensions Using Azure Resource Manager Template
...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, ensuring parity in template content. However, all deployment command examples use Azure PowerShell exclusively, with no Azure CLI or Bash equivalents shown. Additionally, PowerShell deployment commands are presented first and solely, which may create friction for Linux/macOS users who prefer CLI or Bash. The template file examples are well-balanced between Linux and Windows, but the operational/deployment instructions are Windows/PowerShell-centric.
Recommendations
- Add equivalent Azure CLI deployment commands (e.g., az deployment group create) alongside PowerShell examples.
- Include Bash script examples for template deployment where appropriate.
- Explicitly mention that both PowerShell and CLI can be used on Linux/macOS, and link to cross-platform instructions.
- Consider presenting CLI examples before or alongside PowerShell to avoid Windows-first perception.
Create Pull Request
Azure Arc
Next steps for cloud-native server management with Azure Arc-enabled servers
.../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation references Windows-centric management tools (Group Policy Objects, WSUS) as examples of existing solutions to be used alongside Azure services. These Windows tools are mentioned exclusively and before any Linux equivalents, with no mention of Linux-native management tools or practices. No Linux-specific examples or references are provided for patching, configuration, or compliance, which may create friction for Linux users transitioning to Azure Arc.
Recommendations
- Include examples of Linux-native management tools (e.g., Ansible, Chef, Puppet, cron jobs, or native package managers like apt/yum) when discussing existing solutions to be used alongside Azure services.
- Provide Linux-specific scenarios for phased adoption, such as using Azure Update Manager in parallel with apt/yum/dnf/zypper for patching, or comparing Azure Policy with Linux configuration management tools.
- Add references to Linux onboarding scripts or automation patterns, and clarify that Azure Arc supports both Windows and Linux servers.
- Ensure that training and operational procedure examples mention Linux command-line tools and workflows (e.g., Bash, SSH, systemd).
Azure Portal
Use Azure Copilot with the Azure mobile app
...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key capability, listing PowerShell (Windows-centric) alongside CLI without clarifying Linux/macOS parity or providing Bash examples. PowerShell is mentioned before any Linux shell, which may subtly signal a Windows-first approach.
Recommendations
- Explicitly state that Azure Copilot can generate both PowerShell and Bash (or Azure CLI) scripts, and clarify support for Linux/macOS users.
- Provide example prompts or screenshots showing both PowerShell and Bash/CLI script generation.
- Avoid listing PowerShell before CLI unless there is a functional reason; consider using 'CLI and PowerShell' or 'CLI (Bash) and PowerShell' for clarity.