Cloud Services Extended Support

45
Total Pages
14
Linux-Friendly Pages
31
Pages with Bias
68.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

234 issues found
Showing 101-125 of 234 flagged pages
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-wad.md ...articles/cloud-services-extended-support/enable-wad.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based examples and instructions for applying the Azure diagnostics extension. All command-line guidance is given in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. Windows-centric tools and patterns (such as Visual Studio and PowerShell) are referenced before or instead of Linux equivalents, and there are no examples or instructions for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for Linux/macOS users.
  • Include Bash shell script examples for downloading and manipulating configuration files.
  • Mention cross-platform tools and workflows (e.g., VS Code, Azure CLI) alongside Windows-specific ones.
  • Clarify which steps are platform-agnostic and which require Windows, and provide alternatives where possible.
  • Ensure that deployment instructions reference Linux and macOS environments, not just Windows/PowerShell/Visual Studio.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/available-sizes.md ...les/cloud-services-extended-support/available-sizes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for listing available VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio) before or instead of Linux alternatives, and omitting CLI/bash examples. The deployment instructions and next steps also prioritize Windows tools and workflows, with no mention of Linux-native commands or tooling.
Recommendations
  • Add equivalent Azure CLI or Bash examples for listing VM sizes to provide Linux parity.
  • Mention Linux-friendly deployment options (e.g., Azure CLI, ARM templates via Bash) alongside PowerShell and Visual Studio.
  • Ensure that examples and instructions are presented in a cross-platform manner, or explicitly note platform-specific steps.
  • Include links to Linux documentation or guides where relevant, especially for common tasks like deployment and management.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-2-3-4-retirement.md ...port/cloud-services-guestos-family-2-3-4-retirement.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, exclusively referencing Windows Server versions, Windows-specific configuration files, and providing only Azure PowerShell scripts for discovery. There are no examples or guidance for Linux-based cloud services, nor any mention of Linux OS families or migration paths.
Recommendations
  • Include information about Linux-based guest OS families if supported, or clarify if only Windows is relevant.
  • Provide equivalent discovery and migration instructions for Linux-based services, such as using Azure CLI, Bash scripts, or REST API examples.
  • Mention Linux-compatible development tools and frameworks where applicable.
  • Clearly state the scope of supported OS families (Windows vs. Linux) at the beginning of the document to avoid confusion.
  • If Linux is not supported in this context, explicitly note this to help users understand the limitations.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-microsoft-security-response-center-releases.md ...es-guestos-microsoft-security-response-center-releases.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively covers Windows-based Azure Guest OS updates, referencing only Windows versions, Windows-specific KB articles, and Microsoft technologies such as .NET Framework, Internet Explorer, and Windows Defender. There is no mention of Linux distributions, Linux kernel updates, or any Linux-specific security advisories or tools. No examples, tables, or references are provided for Linux-based guest OSes, and the entire structure assumes a Windows-only environment.
Recommendations
  • Add equivalent update tracking tables for supported Linux distributions (e.g., Ubuntu, CentOS, Red Hat, SUSE) running as Azure Guest OS.
  • Include references to Linux security advisories (e.g., USN, RHSA, DSA) and kernel update tracking.
  • Provide links to Linux vendor documentation for update and patch management.
  • Clearly indicate in the introduction that this page is Windows-only, and link to a parallel Linux Guest OS update documentation page.
  • If Linux is not supported in this context, explicitly state so to avoid confusion for cross-platform users.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/certificates-and-key-vault.md ...ervices-extended-support/certificates-and-key-vault.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as a primary method for creating Key Vaults, requiring certificates in .PFX format (commonly used in Windows environments), and mentioning Visual Studio as a deployment tool. There are no examples or instructions for Linux users (e.g., using Azure CLI or OpenSSL), and Windows-centric tools and formats are prioritized or mentioned exclusively.
Recommendations
  • Add instructions and examples for creating Key Vaults and uploading certificates using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include guidance for preparing certificates in PEM format and converting between PEM and PFX using OpenSSL, with Linux command examples.
  • Mention Linux-compatible deployment tools and workflows (e.g., Azure CLI, Bicep, or Terraform) alongside PowerShell and Visual Studio.
  • Ensure that all code snippets and configuration steps are platform-agnostic or provide both Windows and Linux alternatives.
  • Explicitly state that the process can be completed on Linux and macOS, not just Windows, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-1-retirement.md ...-support/cloud-services-guestos-family-1-retirement.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All examples and recommendations are centered around Windows Server OS families, with no mention of Linux-based guest OS options. The only script provided is in Azure PowerShell, and there are no equivalent Bash, CLI, or Linux-native examples. The migration paths exclusively reference Windows Server versions and .NET frameworks, omitting any guidance for users running Linux workloads or seeking Linux parity.
Recommendations
  • Include examples for identifying affected services using Azure CLI and Bash scripts, which are cross-platform and commonly used on Linux.
  • Mention Linux-based guest OS options available in Azure Cloud Services, if supported, and provide migration guidance for those workloads.
  • Present OS family migration recommendations for both Windows and Linux, or clarify if only Windows is supported.
  • Add notes or links for Linux users on how to check and migrate their services, ensuring parity in instructions and tooling.
  • Avoid assuming all users are on Windows by providing cross-platform tooling and examples (e.g., Azure CLI, REST API).
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-portal.md ...icles/cloud-services-extended-support/deploy-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page primarily describes deployment using the Azure portal, which is cross-platform. However, in the 'Related content' section, alternative deployment methods are listed as Azure PowerShell, ARM template, and Visual Studio, with PowerShell and Visual Studio being Windows-centric tools. PowerShell is mentioned before ARM templates, and there is no explicit mention of Linux CLI or Bash examples, nor are Linux-native tools highlighted. This ordering and tool selection suggest a Windows-first bias and a preference for Windows tools.
Recommendations
  • Include Azure CLI (cross-platform, Linux-friendly) as an alternative deployment method in the 'Related content' section.
  • Provide explicit Bash or Linux shell examples where applicable.
  • Mention Visual Studio Code (cross-platform) alongside Visual Studio for deployment and management.
  • Ensure that deployment instructions and examples are not limited to Windows-specific tools and are presented in a platform-neutral order (e.g., CLI, PowerShell, ARM template, Visual Studio).
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md ...tended-support/cloud-services-guestos-update-matrix.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation is exclusively focused on Windows Server-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1). There is no mention of Linux-based Guest OSes, nor any examples, configuration strings, or update processes for Linux. Windows development tools (Visual Studio, .NET Framework) are referenced, and no Linux equivalents or cross-platform SDKs are discussed. The page assumes all Azure Cloud Services Guest OSes are Windows, and all instructions, terminology, and recommendations are Windows-centric.
Recommendations
  • Add information about Linux-based Guest OS releases if supported, including configuration strings, update processes, and compatibility matrices.
  • Include examples and instructions for managing Linux-based Cloud Services, if available, such as update procedures, patching, and SDK compatibility.
  • Reference Linux development tools (e.g., VS Code, JetBrains Rider, or command-line tools) and frameworks (e.g., .NET Core, Python, Java) where appropriate.
  • Clarify in the introduction whether Azure Cloud Services supports Linux Guest OSes, and if not, provide a link to equivalent Linux documentation (such as Azure Virtual Machines or App Services).
  • Ensure parity in update and retirement policy explanations for both Windows and Linux platforms, if Linux is supported.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/configure-scaling.md ...s/cloud-services-extended-support/configure-scaling.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by prioritizing Windows-centric tools and workflows. Examples include referencing PowerShell and Visual Studio as deployment options before mentioning cross-platform alternatives, and linking to queue storage documentation with Windows-specific environment variable tabs. There are no explicit Linux or CLI examples for scaling configuration, and the guidance assumes use of the Azure portal or Windows tooling.
Recommendations
  • Add explicit Azure CLI examples for scaling configuration, highlighting cross-platform usage.
  • Include Linux-specific instructions or screenshots where relevant, especially for deployment and management tasks.
  • Reorder deployment options to list cross-platform tools (e.g., Azure CLI, ARM templates) before Windows-only tools (PowerShell, Visual Studio).
  • Ensure referenced documentation (such as queue storage quickstarts) includes Linux tabs/examples and links to them directly.
  • Clarify that scaling operations can be performed from any OS using supported cross-platform tools.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-prerequisite.md ...cloud-services-extended-support/deploy-prerequisite.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is repeatedly mentioned as a primary automation tool for tasks such as creating virtual networks and key vaults, with no explicit mention of Linux alternatives (e.g., Bash, Azure CLI on Linux) in those contexts. Visual Studio, a Windows-centric IDE, is referenced as a deployment tool, and Windows-specific plugin names are used in configuration examples. Although the Azure portal and ARM templates are mentioned (which are cross-platform), the ordering and emphasis tend to favor Windows tools and patterns first.
Recommendations
  • Include explicit Azure CLI (cross-platform) examples alongside or before PowerShell examples for all resource creation tasks.
  • Mention Linux-compatible deployment tools (such as VS Code, Azure CLI, or Terraform) in parallel with Visual Studio.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide links to relevant documentation.
  • Ensure configuration examples and plugin references are not Windows-specific unless required, and note any platform dependencies.
  • Add a section or note highlighting cross-platform support and best practices for Linux users.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-template.md ...les/cloud-services-extended-support/deploy-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash equivalents. Instructions for resource creation and deployment consistently reference the Azure portal and Azure PowerShell, omitting Linux-friendly tools. The extension profile example focuses on RDP (a Windows protocol) and uses the 'Microsoft.Windows.Azure.Extensions' publisher, further reinforcing Windows-centric patterns. There are no examples or guidance for Linux users or cross-platform tooling.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all resource creation and deployment steps.
  • Explicitly mention Bash and Linux compatibility where relevant, especially for uploading files and deploying templates.
  • Include guidance for using SSH extensions in the extension profile, not just RDP.
  • Ensure that references to tools (e.g., Visual Studio) are balanced with cross-platform alternatives (e.g., VS Code).
  • Reorder instructions so that cross-platform tools (Azure CLI, portal) are mentioned before or alongside Windows-specific tools.
  • Provide links to Linux-specific documentation or troubleshooting guides where appropriate.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-key-vault-virtual-machine.md ...s-extended-support/enable-key-vault-virtual-machine.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on the Key Vault VM extension for Windows, with repeated references to Windows-specific concepts such as the Windows certificate store, 'LocalMachine', and 'My' store names. There are no examples or instructions for Linux VMs, nor any mention of Linux certificate management patterns or tools. The extension is described and demonstrated only in the context of Windows, and all configuration snippets (ARM template, ServiceDefinition.csdef) use Windows-centric terminology.
Recommendations
  • Add explicit information about Linux support: clarify whether the Key Vault VM extension is available for Linux VMs in Azure Cloud Services (extended support).
  • If Linux is supported, provide equivalent examples for Linux, including certificate store locations, relevant settings, and configuration steps.
  • Mention Linux certificate management tools and patterns (e.g., using PEM files, /etc/ssl/certs, or integrating with OpenSSL).
  • If the extension is Windows-only, state this clearly at the beginning of the documentation to avoid confusion.
  • Ensure future documentation covers both Windows and Linux scenarios, or provides parity in examples and guidance.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/in-place-migration-overview.md ...rvices-extended-support/in-place-migration-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell commands as the primary example for resource registration and status checking, listing Windows-centric tools (PowerShell, Visual Studio) for deployment, and omitting explicit Linux/Unix shell (bash/CLI) examples. Windows tools and patterns are mentioned before or instead of Linux equivalents, and there is no parity in example commands or tooling guidance for Linux users.
Recommendations
  • Add Azure CLI (bash) examples alongside PowerShell commands for resource registration and status checking.
  • Include deployment instructions using cross-platform tools (e.g., Azure CLI, VS Code) in addition to Windows-specific tools like Visual Studio.
  • Ensure that all command-line examples are provided for both Windows (PowerShell) and Linux/macOS (bash/CLI) environments.
  • Explicitly mention Linux-compatible workflows and tools in the 'client tools' section, such as Azure CLI and VS Code.
  • Review and update documentation to present Windows and Linux options with equal prominence and detail.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/non-vnet-migration.md .../cloud-services-extended-support/non-vnet-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by focusing exclusively on Azure portal-based migration steps, which are platform-agnostic but typically more familiar to Windows users. In the 'Next steps' section, PowerShell is mentioned explicitly as a migration method, with no mention of Azure CLI or Bash/Linux alternatives. There are no Linux-specific examples, nor are cross-platform command-line tools referenced.
Recommendations
  • Add migration instructions using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include examples or references for Bash scripting or automation for Linux users.
  • Mention both PowerShell and Azure CLI options in the 'Next steps' section, giving equal prominence.
  • Clarify that the Azure portal is accessible from any OS, and provide links to CLI documentation for parity.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/override-sku.md ...ticles/cloud-services-extended-support/override-sku.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell example (which is Windows-centric), referencing Windows tools and patterns (PowerShell cmdlets), and omitting equivalent Linux/Unix shell examples (such as Azure CLI or Bash). The PowerShell example appears before any mention of cross-platform alternatives, and no Linux-native tooling or instructions are provided for users who may not use Windows.
Recommendations
  • Add Azure CLI examples for setting allowModelOverride, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash or shell script samples to demonstrate how Linux users can perform the same operations.
  • Explicitly mention platform compatibility for each method (e.g., PowerShell is available on Windows and Linux, but Azure CLI is natively cross-platform).
  • Reorder examples to present cross-platform solutions (ARM template, Azure CLI) before platform-specific ones (PowerShell).
  • Reference Linux tools and workflows where appropriate, ensuring parity in instructions and examples.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/post-migration-changes.md ...ud-services-extended-support/post-migration-changes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Windows-centric tools in its examples and instructions. PowerShell is repeatedly mentioned as the primary automation and scripting interface, with no equivalent Bash, Azure CLI, or Linux shell examples provided. Visual Studio is referenced as the default IDE for deployment updates, further reinforcing a Windows-first approach. Linux-native tools and workflows are either missing or mentioned only after Windows tools, if at all.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all PowerShell commands and automation steps.
  • Include instructions and examples for updating deployment files and managing resources using Linux/macOS environments.
  • Reference cross-platform editors (e.g., VS Code) alongside Visual Studio, and provide guidance for non-Windows users.
  • Ensure REST API examples include sample requests using curl or similar Linux-native tools.
  • Explicitly mention platform compatibility for all tools and commands, and avoid assuming a Windows environment.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-rdp.md ...articles/cloud-services-extended-support/enable-rdp.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell, a Windows-centric tool, with no mention of Linux equivalents (such as Azure CLI or SSH). The workflow assumes use of RDP, which is primarily a Windows protocol, and does not provide guidance for connecting from Linux or macOS clients. The 'Next steps' section lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, and omits Azure CLI or Linux-native tools.
Recommendations
  • Add Azure CLI examples for managing the Remote Desktop extension, including enabling, updating, and removing it.
  • Include instructions for connecting to role instances using RDP from Linux and macOS clients (e.g., using 'xfreerdp', 'remmina', or 'mstsc' alternatives).
  • Mention SSH as an alternative for Linux-based role instances, if supported.
  • Reorder 'Next steps' to present cross-platform tools (Azure CLI, templates) before Windows-specific tools (PowerShell, Visual Studio).
  • Explicitly state platform requirements and provide parity guidance for non-Windows users.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/extensions.md ...articles/cloud-services-extended-support/extensions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific tools (PowerShell, Windows Defender, Microsoft Antimalware) and providing instructions and examples only for Windows environments. There is no mention of Linux equivalents, nor are Linux-specific extensions, tools, or configuration patterns discussed. The guidance for deploying and managing extensions is centered around Windows technologies, with no parity for Linux users.
Recommendations
  • Add examples and instructions for configuring extensions on Linux-based cloud service roles, including how to automate monitoring, security, and remote access using Linux-native tools.
  • Include information about Linux-compatible diagnostic and monitoring extensions, such as the OMS Agent or Azure Monitor for Linux.
  • Provide parity in deployment instructions, e.g., show how to deploy extensions using Azure CLI or ARM templates, which are cross-platform, alongside PowerShell.
  • Mention Linux security solutions (e.g., ClamAV, Linux Defender integration) where relevant, and clarify which extensions are Windows-only.
  • Explicitly state OS support for each extension and provide links to Linux documentation where available.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/in-place-migration-technical-details.md ...tended-support/in-place-migration-technical-details.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing PowerShell as the primary automation and scripting tool for migration operations, with no mention of Linux shell equivalents or cross-platform CLI usage. PowerShell is suggested for retrying stuck operations and for retrieving deployments, while Linux-friendly alternatives (such as Bash or Azure CLI examples) are not provided. The documentation also lists PowerShell before REST API, and does not offer explicit Linux or cross-platform migration workflows or troubleshooting steps.
Recommendations
  • Add Azure CLI (az) examples alongside or before PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that migration operations (such as abort, commit, validate) can be performed using Azure CLI or Bash scripts, and provide example commands.
  • Include troubleshooting steps and automation guidance for Linux users, such as using Bash, shell scripts, or Azure CLI.
  • Ensure that REST API references are accompanied by sample requests using curl or httpie, which are common on Linux.
  • Review all sections where PowerShell is mentioned and add equivalent instructions for Linux environments.
  • Clarify that the migration tool and processes are supported on both Windows and Linux platforms, if applicable.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/overview.md ...n/articles/cloud-services-extended-support/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows (PowerShell, Visual Studio) and omitting explicit Linux or cross-platform alternatives. Deployment examples and instructions reference PowerShell and Visual Studio, both of which are traditionally associated with Windows environments, without mentioning Azure CLI or other Linux-friendly tools. There are no Linux-specific examples or guidance, and the ordering of deployment options consistently lists Windows tools before more neutral or cross-platform options.
Recommendations
  • Include Azure CLI examples and instructions alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Mention and provide examples for deploying Cloud Services (extended support) from Linux environments.
  • List cross-platform tools (such as Azure CLI and ARM templates) before Windows-specific tools (PowerShell, Visual Studio) when presenting deployment options.
  • Explicitly state that deployment can be performed from Linux, macOS, and Windows, and link to relevant documentation for each platform.
  • Where Visual Studio is mentioned, also mention Visual Studio Code as a cross-platform alternative.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-webrole.md ...loud-services-extended-support/schema-csdef-webrole.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation for Azure Cloud Services (extended support) WebRole schema exhibits a Windows bias. It consistently references Windows technologies (IIS 7, ASP.NET, .NET Framework), Windows-specific concepts (certificate stores like 'CurrentUser' and 'LocalMachine'), and Windows file formats (CMD, batch files in ANSI format). There are no Linux equivalents or examples provided, nor is there any mention of Linux-based deployment, configuration, or runtime environments. The documentation assumes the reader is working in a Windows context and does not address cross-platform scenarios.
Recommendations
  • Add explicit notes about Linux support or lack thereof for WebRole, including any limitations or alternatives.
  • Provide examples or guidance for deploying web applications using Linux-based runtimes (e.g., Apache, Nginx) if supported.
  • Include information about certificate management on Linux (e.g., using PEM files, OpenSSL, or Linux certificate stores) where applicable.
  • Clarify how startup tasks and scripts should be formatted and executed on Linux (e.g., using Bash scripts instead of CMD/batch files).
  • Reference cross-platform .NET (Core/6+) options and how they differ from classic .NET Framework deployments.
  • If WebRole is Windows-only, state this clearly at the beginning and suggest Linux alternatives (such as Azure App Service for Linux or Azure Virtual Machines with Linux).
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-workerrole.md ...d-services-extended-support/schema-csdef-workerrole.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Cloud Services (extended support) WorkerRole schema demonstrates a Windows bias. It references Windows concepts such as certificate stores ('CurrentUser', 'LocalMachine', 'My', 'Root', etc.), environment variables in Windows format (%ROLEROOT%), and startup scripts as CMD/batch files in ANSI format. There are no examples or guidance for Linux equivalents, such as Linux certificate stores, environment variable conventions, or shell script usage. All examples and terminology are Windows-centric, with no mention of Linux or cross-platform considerations.
Recommendations
  • Add explicit guidance and examples for Linux-based WorkerRoles, including how certificate storage and access works on Linux.
  • Document Linux environment variable conventions and how %ROLEROOT% maps to Linux paths.
  • Provide startup script examples using bash/sh for Linux, and clarify file encoding requirements for Linux scripts.
  • Mention differences in remote access, diagnostics, and other modules when running on Linux.
  • Where Windows-specific terms are used (e.g., certificate store names), add notes or tables showing Linux equivalents or stating how these are handled on Linux.
  • Ensure that cross-platform parity is maintained by presenting both Windows and Linux instructions/examples side by side.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/swap-cloud-service.md .../cloud-services-extended-support/swap-cloud-service.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows PowerShell commands (Get-AzRole) as the only CLI example for checking instance status, listing PowerShell and Visual Studio as deployment options, and omitting equivalent Linux CLI (Azure CLI) or shell examples. Windows tools and patterns are mentioned before or instead of Linux alternatives, and there are no explicit Linux or cross-platform command-line instructions.
Recommendations
  • Add Azure CLI (az) examples alongside or before PowerShell commands for checking instance status and performing swaps.
  • Include instructions for deployment using Azure CLI and shell scripts, not just PowerShell and Visual Studio.
  • Explicitly mention cross-platform tooling and provide parity in examples for Linux/macOS users.
  • Reorder deployment options to present cross-platform methods (portal, ARM template, Azure CLI) before Windows-specific tools (PowerShell, Visual Studio).
  • Clarify that all operations can be performed from Linux/macOS environments, not just Windows.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-1-retirement.md ...-support/cloud-services-guestos-family-1-retirement.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is heavily Windows-centric, referencing only Windows Server OS families, using Azure PowerShell for examples, and omitting any mention of Linux-based guest OS options or equivalent Linux tooling. All migration recommendations are for Windows Server versions, and the only script provided is in PowerShell, with no Bash, CLI, or Linux alternative. This creates a strong Windows bias and lacks Linux parity.
Recommendations
  • Include information about Linux-based Guest OS families available in Azure, if supported.
  • Provide equivalent examples using Azure CLI or Bash scripts for users on Linux or macOS.
  • Mention Linux migration paths and supported Linux distributions for cloud services.
  • Clarify whether the retirement notice applies only to Windows-based services or also to Linux-based services.
  • Ensure that documentation for cloud service management covers both Windows and Linux administration tools and patterns.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/non-vnet-migration.md .../cloud-services-extended-support/non-vnet-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses exclusively on migration procedures using the Azure portal and references PowerShell for further migration steps, without mentioning or providing examples for Linux tools, CLI commands, or Bash scripts. The 'Next steps' section lists PowerShell before any Linux/CLI alternatives, and there are no Linux-specific instructions or parity for command-line migration.
Recommendations
  • Add Azure CLI (cross-platform) instructions and examples for migration steps alongside or before PowerShell references.
  • Include Bash script examples for automation of migration tasks to support Linux users.
  • Explicitly mention Linux compatibility and provide guidance for performing migration on Linux systems.
  • Ensure that references to PowerShell are balanced with equivalent Azure CLI or REST API documentation.
  • Review screenshots and UI instructions to clarify any OS-specific requirements or alternatives.
GitHub Create Pull Request
← Previous Page 5 of 10 Next →