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 151-175 of 234 flagged pages
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-file.md ...s/cloud-services-extended-support/schema-csdef-file.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\<version>\schemas) and mentioning the Azure SDK in the context of Windows installation. There are no Linux or cross-platform installation paths, nor are there any examples or notes for Linux users. All tooling and directory references are Windows-centric.
Recommendations
  • Include Linux and macOS installation paths for the Azure SDK and schema files, or clarify if the SDK/tools are Windows-only.
  • Add notes or sections explaining how to work with csdef files on Linux (e.g., file locations, compatible editors, or CLI tools).
  • If relevant, provide cross-platform command-line examples (e.g., using Azure CLI, bash, or PowerShell Core) instead of only referencing Windows tools or directories.
  • Explicitly state platform support and any differences in workflow for Linux/macOS 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: 2025-07-13 21:37
Reviewed by: Unknown
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 PowerShell as a primary method for creating Key Vaults, omitting equivalent Linux/CLI examples. The certificate format required is .PFX, which is most commonly associated with Windows environments. Deployment options prioritize Windows-centric tools (PowerShell, Visual Studio) and do not provide parity for Linux users (e.g., Azure CLI, Bash scripts). There are no examples or instructions for Linux users on how to generate, upload, or manage certificates.
Recommendations
  • Include Azure CLI examples alongside PowerShell for creating and managing Key Vaults and certificates.
  • Provide instructions or references for generating .PFX certificates on Linux (e.g., using OpenSSL).
  • List Linux-friendly deployment options (e.g., Bash, Azure CLI) alongside or before Windows tools.
  • Add explicit Linux/macOS command-line examples for uploading and referencing certificates.
  • Clarify that .PFX files can be generated and used cross-platform, and provide guidance for non-Windows environments.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/states.md ...ain/articles/cloud-services-extended-support/states.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a Windows bias in the 'Next steps' section, where deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and PowerShell is mentioned before any cross-platform or Linux-native options. There is no mention of Azure CLI or Bash scripting, which are commonly used on Linux and macOS. No Linux-specific examples or tools are provided.
Recommendations
  • Include Azure CLI and Bash scripting examples alongside or before PowerShell examples.
  • Mention cross-platform tools (e.g., Azure CLI) in the 'Next steps' deployment options.
  • Provide links to Linux/macOS deployment guides or documentation.
  • Ensure that Visual Studio Code (cross-platform) is mentioned if an IDE is referenced, not just Visual Studio (Windows-only).
  • Balance the order of tool mentions so that Windows-specific tools do not always appear first.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-alerts.md ...icles/cloud-services-extended-support/enable-alerts.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (PowerShell, Visual Studio) before any Linux or cross-platform alternatives, and by omitting explicit Linux CLI examples. The 'Next steps' section prioritizes PowerShell and Visual Studio, both of which are traditionally Windows-focused, and does not mention Azure CLI or Bash scripting, which are more common in Linux environments.
Recommendations
  • Include Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Mention deployment options using Bash or shell scripts where appropriate.
  • List cross-platform tools (e.g., Azure CLI, ARM templates) before Windows-specific tools (PowerShell, Visual Studio) to avoid the appearance of Windows-first bias.
  • Explicitly state that the Azure portal and Azure CLI are supported on all major operating systems.
  • Provide links to Linux-specific documentation or guides where relevant.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing PowerShell and Windows-centric tools exclusively when discussing command-line or automation options. There are no examples or explicit mentions of Linux shell equivalents, Bash, or cross-platform scripting. PowerShell is mentioned as the primary or only automation tool, and no Linux-specific guidance or parity is provided for key migration steps.
Recommendations
  • Include Azure CLI (az) command examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that all migration operations (validate, prepare, commit, abort) can be performed using Azure CLI, and provide sample commands.
  • When referencing automation or scripting, avoid assuming PowerShell as the default; instead, provide both PowerShell and Bash/Azure CLI equivalents.
  • Add a section or callout for Linux/macOS users, clarifying that the migration process is fully supported from non-Windows environments and linking to relevant cross-platform tooling documentation.
  • Review all troubleshooting steps to ensure that Linux users are not directed solely to PowerShell, and provide REST API or Azure CLI alternatives 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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric: it only references the Key Vault VM extension for Windows, describes certificate handling in terms of the Windows certificate store, and provides no mention of Linux support or Linux-specific instructions. All examples and configuration snippets (such as certificate store location and names) are tailored to Windows environments, and there is no guidance for Linux users.
Recommendations
  • Clarify in the introduction whether the Key Vault VM extension is available for Linux VMs in Azure Cloud Services (extended support). If not, explicitly state this limitation.
  • If Linux support exists, add equivalent instructions and configuration examples for Linux, including how certificates are handled and where they are stored.
  • Provide parallel documentation sections or notes for Linux users, including any differences in authentication, certificate management, and extension installation.
  • Avoid using Windows-specific terminology (such as 'certificate store location', 'LocalMachine', 'My') without Linux equivalents or explanations.
  • Include links to Linux-specific Key Vault VM extension documentation if available.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-file.md ...s/cloud-services-extended-support/schema-cscfg-file.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing only Windows file paths (e.g., C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK), mentioning Visual Studio and .NET SDK tools exclusively, and omitting any Linux or cross-platform equivalents for SDK installation, file locations, or tooling. There are no Linux-specific instructions, examples, or references, which may hinder Linux users' ability to follow the documentation.
Recommendations
  • Include Linux file path examples for SDK schema locations, such as /usr/local/share/azure-sdks or similar, alongside the Windows paths.
  • Mention cross-platform or Linux-compatible tools for schema validation and editing, such as VS Code, Azure CLI, or open-source XML editors.
  • Clarify whether the Azure SDK and related tools are available for Linux, and provide installation instructions or references for Linux users.
  • Avoid assuming Visual Studio or .NET SDK as the only tooling; reference cross-platform alternatives where possible.
  • Add a note or section explicitly addressing Linux/macOS users, outlining any differences or parity in the workflow.
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: 2025-07-13 21:37
Reviewed by: Unknown
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 Azure PowerShell examples for resource creation and deployment, referencing Visual Studio (a Windows-centric tool), and omitting any CLI or Linux-native instructions. Steps for creating resources and deploying templates consistently mention the Azure portal and PowerShell, with no mention of Azure CLI or Bash equivalents. The only deployment command shown is in PowerShell, and the extension profile example is for RDP (a Windows protocol), further reinforcing the Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource creation and deployment steps, alongside or before PowerShell examples.
  • Include Linux/Bash shell examples for uploading files to storage and deploying ARM templates.
  • Reference cross-platform tools (such as Azure CLI and VS Code) in addition to or instead of Windows-only tools like Visual Studio.
  • Provide extension profile examples relevant to Linux (e.g., SSH extension) in addition to RDP.
  • Ensure that all instructions and links are platform-neutral or provide parity for Linux/macOS users.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exclusively references Windows Server OS families, provides only Azure PowerShell scripts for discovery, and recommends Windows-centric tools (Visual Studio, .NET Framework). There are no examples, guidance, or references for Linux-based guest OSes or management tools, and the migration recommendations are entirely Windows-focused.
Recommendations
  • If Linux-based guest OSes are supported in Azure Cloud Services (classic or extended), include equivalent guidance and examples for identifying and migrating Linux workloads.
  • Provide CLI (az cli) or cross-platform scripting examples (e.g., Bash) in addition to PowerShell, or clarify if only PowerShell is supported.
  • Mention Linux guest OS families, if applicable, and provide parity in recommendations for migration and support.
  • If the service is Windows-only, explicitly state this at the beginning of the documentation to set expectations for Linux users.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for ARM templates, PowerShell, and the .NET SDK (C#), but does not include any Linux-native CLI examples (such as Azure CLI/bash), nor does it mention Linux-specific tools or workflows. The PowerShell example is prominent, and there is no parity for Linux users who may prefer Bash or cross-platform scripting tools.
Recommendations
  • Add an Azure CLI example (az cloud-service ...) demonstrating how to set allowModelOverride, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that the PowerShell example can be run on PowerShell Core on Linux, if applicable.
  • Consider including Bash scripting examples or references for Linux users.
  • Ensure that SDK examples include at least one language commonly used on Linux (e.g., Python or Java), not just C#.
  • Review the documentation for any terminology or tool references that assume a Windows environment and provide Linux equivalents where possible.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
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), and omitting equivalent Linux/CLI examples. The deployment instructions and tooling references prioritize or exclusively mention Windows workflows, with no mention of Azure CLI, Bash, or cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) command examples for listing available VM sizes, suitable for Linux/macOS users.
  • Include Bash or shell script snippets alongside PowerShell to ensure parity.
  • Mention cross-platform tools (e.g., Azure CLI, ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Ensure deployment instructions and next steps reference both Windows and Linux-friendly workflows, such as deploying via Azure CLI or from a Linux environment.
  • Where possible, clarify that the service definition file and repackaging steps can be performed on any platform, not just Windows.
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: 2025-07-08 04:23
Reviewed by: Unknown
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 PowerShell and Windows-centric tools (such as .PFX certificates and Visual Studio) without providing equivalent Linux or cross-platform examples. The instructions and tooling are oriented towards Windows users, and there are no mentions of Linux command-line tools or certificate formats commonly used on Linux. Additionally, PowerShell is mentioned before any other scripting or CLI options, and deployment examples focus on Windows-first workflows.
Recommendations
  • Include Azure CLI examples for certificate and Key Vault operations, as Azure CLI is cross-platform and widely used on Linux.
  • Provide instructions for preparing certificates in PEM format and converting between PEM and PFX, as PEM is common on Linux.
  • Add Linux shell (bash) examples for uploading certificates to Key Vault.
  • Mention and link to documentation for Linux-based deployment tools and editors (e.g., VS Code, ARM templates via CLI).
  • Ensure that all steps referencing PowerShell or Visual Studio are accompanied by Linux-friendly alternatives.
  • Clarify that the process is platform-agnostic where possible, and highlight any Windows-specific steps as such.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows-based operating systems (Windows Server 2008/2012/2012 R2) and provides only Azure PowerShell scripts for determining OS family usage. There are no examples or guidance for Linux-based cloud services, nor are cross-platform tools or CLI alternatives mentioned. The migration recommendations focus solely on Windows OS families and .NET frameworks, omitting any Linux or open-source stack considerations.
Recommendations
  • Include equivalent Azure CLI or Azure Cloud Shell examples, which are cross-platform and can be used on Linux, macOS, and Windows.
  • Explicitly state if the retirement notice only applies to Windows-based cloud services, or clarify the status for Linux-based services if applicable.
  • Provide guidance for users running Linux-based workloads, if supported, or direct them to relevant documentation.
  • Mention cross-platform tools and patterns (such as Azure Resource Manager templates or Bicep) where possible, instead of focusing solely on Windows-centric tools and scripting.
  • If PowerShell is required, note that PowerShell Core is available cross-platform, and provide installation instructions for Linux/macOS users.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/states.md ...ain/articles/cloud-services-extended-support/states.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where deployment options are listed as Azure portal, PowerShell, Template, and Visual Studio. PowerShell and Visual Studio are Windows-centric tools, and there is no mention of Linux-native tools or CLI-based deployment options. No Linux or cross-platform examples are provided, and the ordering places Windows tools before more neutral options.
Recommendations
  • Include Azure CLI deployment instructions and links alongside or before PowerShell to provide a cross-platform alternative.
  • Mention cross-platform editors (such as VS Code) in addition to Visual Studio.
  • Ensure that examples and instructions are provided for both Windows and Linux environments where applicable.
  • Reorder the deployment options to list cross-platform tools (Azure CLI, Templates) before Windows-specific tools (PowerShell, 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-microsoft-security-response-center-releases.md ...es-guestos-microsoft-security-response-center-releases.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows Only Missing Linux Example 🔧 Windows Tools
Summary
This documentation page exclusively lists updates for the Azure Guest OS, which is based on Windows operating systems. All update references, KB articles, and product categories are for Windows components (e.g., .NET Framework, Internet Explorer, Windows Security, Servicing Stack, etc.). There are no references to Linux distributions, Linux update mechanisms, or Linux-specific security advisories. The documentation is entirely Windows-centric, with no mention of Linux guest OSes, their update cadence, or equivalent security patching processes.
Recommendations
  • Add a clear statement at the top clarifying that this page only covers Windows-based Azure Guest OS images, and provide a link to equivalent documentation for Linux-based Azure VM images.
  • Provide a parallel table or section for Linux guest OSes, listing update advisories, CVEs, and patch release dates for supported distributions (e.g., Ubuntu, CentOS, Red Hat, SUSE).
  • Reference Linux update mechanisms (such as apt, yum, zypper) and security advisories (USN, RHSA, etc.) where appropriate.
  • If Azure Guest OS for Linux is not supported in this context, explicitly state this to avoid confusion for Linux users.
  • Ensure future documentation on Azure VM guest OS updates covers both Windows and Linux platforms with parity in detail and update tracking.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively covers Windows-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1) and related .NET Framework versions, with no mention of Linux-based Guest OS options, examples, or parity. All configuration strings, compatibility notes, and update processes are Windows-centric. There are references to Windows-specific tools (Visual Studio, RDP), and the terminology assumes Windows as the only platform. No Linux equivalents, distributions, or instructions are provided.
Recommendations
  • Explicitly state in the introduction whether Linux-based Guest OS options are available for Azure Cloud Services (classic) and, if not, clarify this limitation.
  • If Linux Guest OS support exists or is planned, add equivalent sections for Linux Guest OS families, including release tables, update processes, and compatibility notes.
  • Provide parity in tooling recommendations (e.g., suggest cross-platform tools or Linux alternatives to Visual Studio and RDP where applicable).
  • Include examples or references for managing and updating Linux-based roles if supported, or link to relevant Linux documentation.
  • Review and update terminology to be inclusive of both Windows and Linux where possible, or clearly scope the document to Windows if Linux is not supported.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-model-and-package.md ...s-extended-support/cloud-services-model-and-package.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (such as Visual Studio, CSPack.exe, and the Azure Compute Emulator), providing only Windows command-line examples, and mentioning Windows-specific paths and UI (e.g., Certificates tab in Visual Studio). There are no Linux or cross-platform alternatives or examples provided for packaging, deploying, or managing Azure Cloud Services (extended support).
Recommendations
  • Include explicit instructions and examples for Linux and macOS users, such as how to install and use CSPack or equivalent tools on non-Windows platforms.
  • Clarify whether CSPack and the Azure Compute Emulator are available or supported on Linux/macOS, and if not, suggest alternative workflows (such as using Azure CLI, Azure DevOps, or Docker-based builds).
  • Provide cross-platform command-line examples (e.g., Bash, Azure CLI) alongside Windows CMD/PowerShell examples.
  • Avoid referencing Windows UI elements (like Visual Studio tabs) as the only method for configuration; instead, describe how to perform these actions using cross-platform tools or editors.
  • Add a section or note summarizing the platform support matrix for all tools and steps, and direct Linux/macOS users to relevant resources or workarounds.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell and Visual Studio are mentioned as primary deployment options, with no explicit mention of Linux CLI or cross-platform alternatives. Example links and tabs reference Windows environments, and there are no Linux-specific instructions or screenshots.
Recommendations
  • Include Azure CLI examples for scaling and deployment, as Azure CLI is cross-platform and widely used on Linux.
  • Provide Linux-specific instructions or notes where workflows differ from Windows (e.g., environment variables, shell commands).
  • Add screenshots or terminal examples from Linux environments alongside Windows/portal images.
  • Mention cross-platform tools (e.g., Azure CLI, Bicep, ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Ensure that quickstart and reference links include Linux tabs or alternatives, not just Windows or PowerShell.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows PowerShell commands (e.g., Get-AzRole) as the only CLI example for checking instance status, listing PowerShell and Visual Studio as deployment options without mentioning cross-platform or Linux-native tools, and omitting any Bash, Azure CLI, or Linux-specific instructions. The ordering of deployment options also places Windows-centric tools before cross-platform alternatives.
Recommendations
  • Provide Azure CLI (az) command examples alongside or instead of PowerShell, especially for tasks like checking instance status (e.g., az vm list or az cloud-service role-instance list).
  • Explicitly mention that ARM templates and REST API methods are cross-platform and can be used from any OS.
  • Include Bash or shell script examples where relevant, particularly for Linux users.
  • In the 'Next steps' section, list cross-platform tools (Azure CLI, ARM template) before Windows-specific tools (PowerShell, Visual Studio), or group them by platform.
  • Where PowerShell is mentioned, add a note or link to equivalent Azure CLI documentation for Linux/macOS users.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary automation tool alongside the Azure portal, while Linux-native tools (such as Bash or Azure CLI) are less emphasized or mentioned after PowerShell. Visual Studio, a Windows-centric IDE, is referenced as a deployment tool, and there is no mention of cross-platform alternatives (e.g., VS Code, GitHub Actions). Some instructions and examples focus on Windows tools and patterns, with Linux equivalents either omitted or de-emphasized.
Recommendations
  • Ensure Azure CLI is mentioned equally or before PowerShell in all tool lists and instructions, as it is cross-platform and widely used on Linux.
  • Add explicit Linux/Bash command examples where PowerShell is referenced, especially for key vault creation and virtual network setup.
  • Reference Visual Studio Code or other cross-platform editors in addition to Visual Studio, or clarify when Visual Studio is optional.
  • Where possible, provide ARM/Bicep template examples as the primary automation method, as these are platform-agnostic.
  • Include a note or section on deploying and managing Cloud Services (extended support) from Linux/macOS environments, with links to relevant documentation.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-sdk.md ...articles/cloud-services-extended-support/deploy-sdk.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias, especially in the certificate/key vault steps, where only PowerShell commands are provided for key vault and certificate management. There are no equivalent examples for Linux users (e.g., using Azure CLI or Bash). The use of PowerShell is assumed, and Windows-centric tools and patterns (such as .cspkg packaging and RDP extensions) are referenced without Linux alternatives or guidance. The documentation does not provide parity for Linux users in critical steps.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI (az) or Bash example suitable for Linux/macOS users, especially for key vault and certificate operations.
  • Mention Azure CLI and Bash as supported options in the prerequisites and throughout the guide.
  • Clarify that .cspkg packaging and RDP extensions are Windows-centric, and provide guidance or alternatives for Linux-based deployments if available.
  • Reorder or parallelize instructions so that Windows and Linux approaches are presented together, rather than defaulting to Windows/PowerShell first.
  • Add a note or section addressing Linux/macOS users, highlighting any differences or additional steps they may need.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. Throughout the prerequisites and deployment steps, only Azure PowerShell and Windows-centric tools (such as Visual Studio and RDP) are mentioned or provided as examples. There are no CLI (az) or Bash/Linux shell examples for resource creation, file uploads, or template deployment. The extension profile example is focused on RDP (a Windows-only protocol), and the guidance for certificate/key vault management only references PowerShell and the Azure portal, omitting Linux-friendly alternatives. The deployment command at the end is shown only in PowerShell, with no az CLI or Bash equivalent.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource creation, file upload, and deployment steps, alongside or before PowerShell examples.
  • Include Bash/Linux shell examples for uploading files to storage and managing key vaults.
  • Mention cross-platform tools (such as Azure CLI and VS Code) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Provide extension profile examples that are not Windows-specific (e.g., SSH for Linux), or clarify that the RDP extension is only relevant for Windows workloads.
  • Explicitly state when a step or tool is Windows-only, and offer Linux/macOS alternatives where possible.
  • Update the deployment section to include az deployment group create or az deployment sub create commands as alternatives to New-AzResourceGroupDeployment.
GitHub Create Pull Request
Cloud Services Extended Support https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-alerts.md ...icles/cloud-services-extended-support/enable-alerts.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page primarily focuses on the Azure portal, which is cross-platform, but in the 'Next steps' section, Windows-centric tools (PowerShell, Visual Studio) are mentioned before any Linux-friendly or cross-platform alternatives. There is no mention of Azure CLI or Bash examples, and the deployment options prioritize Windows tools, indicating a subtle Windows-first and PowerShell-heavy bias.
Recommendations
  • Include Azure CLI (az) as a deployment option alongside PowerShell and Visual Studio, and list it before or alongside PowerShell to avoid Windows-first ordering.
  • Provide explicit mention or examples for Linux/macOS users, such as using Bash or cross-platform tools.
  • Balance the order of tool recommendations so that Linux-friendly options are not always listed after Windows tools.
  • If possible, add screenshots or instructions that are not specific to Windows environments.
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: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively discusses the Key Vault VM extension for Windows, with all examples and explanations tailored to Windows environments. There is no mention of Linux support, Linux certificate stores, or Linux-specific configuration steps. The documentation references Windows certificate stores and uses Windows-centric terminology and file paths, indicating a strong Windows bias.
Recommendations
  • Clarify in the introduction whether the Key Vault VM extension is available for Linux VMs in Azure Cloud Services (extended support). If not, explicitly state this limitation.
  • If Linux support exists, provide equivalent instructions and examples for Linux, including details on certificate storage locations and configuration steps.
  • Include Linux-specific code snippets or configuration samples (e.g., for cloud-init or Linux VM extensions).
  • Mention Linux tools and patterns (such as OpenSSL, Linux certificate stores, etc.) alongside Windows tools.
  • Ensure parity in documentation structure and depth for both Windows and Linux platforms, or clearly indicate platform-specific limitations.
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: 2025-07-08 04:23
Reviewed by: Unknown
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 instructions for managing the Remote Desktop extension use PowerShell and the Az.CloudService module, which are Windows-centric tools. There are no examples or guidance for performing equivalent tasks using cross-platform tools such as Azure CLI, Bash, or Linux-native RDP clients. The workflow assumes the use of .rdp files and the Windows Remote Desktop client, with no mention of Linux or macOS alternatives. The 'Next steps' section also lists PowerShell and Visual Studio (both Windows-focused) before mentioning templates, and does not reference Azure CLI or Linux tools.
Recommendations
  • Add equivalent Azure CLI examples for managing the Remote Desktop extension, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include instructions or references for connecting to RDP-enabled instances from Linux and macOS, such as using 'xfreerdp', 'remmina', or 'rdesktop'.
  • When listing deployment options, mention cross-platform tools (e.g., Azure CLI, ARM templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Clarify that .rdp files can be used with RDP clients on Linux and macOS, and provide links to relevant documentation.
  • Where possible, use neutral language and tool-agnostic instructions, or provide parallel examples for both Windows and Linux/macOS users.
GitHub Create Pull Request
← Previous Page 7 of 10 Next →