Cloud Services Extended Support

45
Total Pages
16
Linux-Friendly Pages
29
Pages with Bias
64.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (40)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/available-sizes.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell examples for retrieving VM sizes, referencing Windows-centric tools (PowerShell, Visual Studio), and omitting equivalent Linux/CLI/bash examples. The deployment options also list PowerShell and Visual Studio before mentioning templates, with no mention of Azure CLI or Linux-native workflows.
Recommendations:
  • Add equivalent Azure CLI (az) and/or Bash examples alongside PowerShell scripts for listing available VM sizes.
  • Explicitly mention and provide examples for Linux users, such as using Azure CLI on Linux or macOS.
  • In the 'Next steps' section, list cross-platform tools (e.g., Azure CLI, ARM/Bicep templates) before or alongside Windows-specific tools like PowerShell and Visual Studio.
  • Where possible, clarify that the service definition file and deployment process are OS-agnostic, and provide links to Linux/macOS documentation if available.
  • Consider including a table or section that maps common Windows tools/workflows to their Linux equivalents for Azure 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 [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily Windows-centric, focusing exclusively on Windows Server OS families, Windows-based configuration files, and PowerShell scripts. There are no references to Linux-based guest OS families, tools, or migration paths. All examples and recommendations assume a Windows environment, with no parity for Linux users.
Recommendations:
  • Include information about Linux-based guest OS families, if supported by Azure Cloud Services, and clarify if this retirement notice is Windows-only.
  • Provide equivalent command-line examples using Azure CLI (cross-platform) or Bash scripts, not just Azure PowerShell.
  • Mention migration or support options for Linux workloads, if applicable, or explicitly state that the guidance is only relevant for Windows-based services.
  • Balance references to development tools (e.g., mention VS Code or cross-platform SDKs, not just Visual Studio for Windows).
  • Clarify in the introduction whether Linux users are affected or not, to avoid confusion.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Only Windows Tools Missing Linux Example
Summary:
The documentation page exclusively covers Windows Server-based Guest OS families (Windows Server 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 SP1) and their release history for Azure Cloud Services. There is no mention of Linux-based Guest OSes, no Linux configuration strings, and no Linux-specific guidance or parity. All references, examples, and recommendations (e.g., Visual Studio, .NET Framework, RDP) are Windows-centric, with no acknowledgment of Linux alternatives or support.
Recommendations:
  • Clearly state in the introduction whether Linux-based Cloud Services Guest OSes are supported or not. If not, explain why.
  • If Linux-based Guest OSes are supported for Cloud Services, add equivalent release tables, configuration strings, and update processes for major Linux distributions (e.g., Ubuntu, CentOS, Red Hat).
  • Provide Linux-specific guidance for SDK compatibility, update processes, and management tools (e.g., using Azure CLI, SSH, Linux package managers).
  • Include references to Linux tools and patterns (such as SSH instead of RDP, or using VS Code/JetBrains IDEs in addition to Visual Studio).
  • If only Windows is supported, make this explicit at the top of the page to avoid confusion for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-file.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/certificates-and-key-vault.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/states.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-alerts.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/in-place-migration-technical-details.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-key-vault-virtual-machine.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-file.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-2-3-4-retirement.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/override-sku.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/available-sizes.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/certificates-and-key-vault.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-family-1-retirement.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/states.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-microsoft-security-response-center-releases.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-guestos-update-matrix.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/cloud-services-model-and-package.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/configure-scaling.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/swap-cloud-service.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-prerequisite.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-sdk.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/deploy-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-alerts.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-key-vault-virtual-machine.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-rdp.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/enable-wad.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and commands for applying the Azure diagnostics extension. All command-line examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The configuration file examples reference Windows-style performance counters and patterns. There are no Linux-specific instructions, examples, or troubleshooting notes, and the documentation does not address how to perform these tasks from a Linux or cross-platform environment.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell script examples for downloading and managing configuration files.
  • Document any differences or considerations when applying the diagnostics extension to Linux-based cloud service roles, if supported.
  • Mention and link to Linux tools or documentation where relevant, such as using curl/wget for file downloads or jq for JSON manipulation.
  • Ensure that references to performance counters or monitoring patterns include Linux equivalents (e.g., CPU/memory metrics as reported by Linux).
  • Clearly state platform limitations or differences if the extension or process is Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/extensions.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows-centric bias by focusing on Windows-specific tools (such as PowerShell and Windows Defender), mentioning Windows Server versions, and omitting Linux equivalents or examples. All extension descriptions and configuration instructions assume a Windows environment, with no guidance for Linux-based cloud service roles or alternative tools for Linux users.
Recommendations:
  • Provide equivalent instructions and examples for Linux-based roles, including how to configure and use extensions on Linux VMs.
  • Mention and link to Linux-compatible monitoring and security tools (e.g., Azure Monitor Agent, Linux antivirus solutions) where applicable.
  • Include Linux command-line examples (such as Azure CLI or bash scripts) alongside or before PowerShell examples.
  • Clarify which extensions and features are Windows-only and which are cross-platform, and provide guidance for Linux users where features are not available.
  • Avoid assuming the use of Visual Studio or Windows-specific deployment tools; mention cross-platform alternatives like VS Code or ARM/Bicep templates.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/in-place-migration-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only command-line example shown, and PowerShell is mentioned before CLI in the provider registration step. Visual Studio is listed as a deployment tool, but no Linux-native tools or workflows are highlighted. There are no explicit Linux/Unix shell (bash/az CLI) examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations:
  • Provide Azure CLI (az) command examples alongside or before PowerShell for all command-line operations, especially for resource provider registration and status checking.
  • Include deployment instructions and examples using cross-platform tools such as Azure CLI, ARM templates, and VS Code, not just Visual Studio.
  • Explicitly mention Linux/macOS compatibility and provide guidance for users on those platforms.
  • Balance the order of tool presentation (e.g., list CLI before or alongside PowerShell) to avoid implying Windows is the default or preferred platform.
  • Where possible, add bash shell script examples or references for common migration tasks.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/in-place-migration-technical-details.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary or sole scripting interface for management tasks (e.g., retrieving deployments, retrying operations, abort/commit actions). There are no explicit Linux or cross-platform CLI examples, and PowerShell is mentioned before or instead of Azure CLI in most cases. This may make the documentation less accessible or immediately actionable for Linux or cross-platform users.
Recommendations:
  • Provide Azure CLI examples alongside or before PowerShell examples for all management tasks, especially for operations like retrieving deployments, aborting/committing migrations, and interacting with Key Vault.
  • Explicitly mention that Azure CLI is cross-platform and supported on Linux, macOS, and Windows.
  • Where PowerShell is referenced, add equivalent Bash/Azure CLI command snippets and links to relevant Azure CLI documentation.
  • Avoid language that implies PowerShell is the default or only supported tool; use neutral phrasing such as 'using Azure CLI or PowerShell'.
  • Add a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-networkconfiguration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page references 'PowerShell deployments' as a method for specifying reserved IP allocation, but does not mention or provide examples for Linux-based tools or workflows (such as Azure CLI or ARM templates used from Linux). There are no Linux-specific examples or parity in tooling references, and the only deployment tool mentioned is PowerShell, which is primarily associated with Windows environments.
Recommendations:
  • Include references and examples for Azure CLI commands, which are cross-platform and commonly used on Linux.
  • When mentioning PowerShell, also mention Azure CLI or Bash scripting as alternatives for Linux users.
  • Provide at least one example of configuring the NetworkConfiguration schema using Linux-friendly tools or workflows.
  • Avoid implying that PowerShell is the only or primary way to deploy or configure these settings; clarify that multiple tools are supported.
  • Add a section or note on how Linux users can achieve the same configuration, possibly linking to relevant Azure CLI or ARM template documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/non-vnet-migration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page focuses exclusively on the Azure portal for migration steps and, in the 'Next steps' section, lists PowerShell as the only command-line automation example. There are no references to Linux tools, Bash, Azure CLI, or cross-platform scripting options. This presents a Windows-first and PowerShell-heavy bias, with missing Linux or cross-platform examples.
Recommendations:
  • Include Azure CLI examples alongside or before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and widely used on Linux.
  • Add explicit instructions or links for performing the migration using Bash or shell scripting where possible.
  • Ensure that screenshots and UI references clarify that the Azure portal is platform-agnostic, and consider mentioning that all steps can be performed from any OS.
  • Where automation is discussed, provide parity between PowerShell and Azure CLI/Bash examples to support Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Deployment methods are listed as PowerShell, Portal, and Visual Studio, all of which are primarily Windows-based, with no mention of Azure CLI, Bash, or Linux-native tooling. There are no Linux or cross-platform examples or instructions, and PowerShell is referenced as the primary scripting method. This may make it less accessible or intuitive for Linux users or those working in cross-platform environments.
Recommendations:
  • Include Azure CLI examples and instructions alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention and provide examples for deploying Cloud Services (extended support) using Bash scripts or shell environments common on Linux.
  • List deployment options in a neutral or cross-platform order (e.g., Azure CLI, PowerShell, Portal, Visual Studio) rather than Windows-first.
  • Reference cross-platform tools and editors (such as VS Code) in addition to Visual Studio.
  • Explicitly state Linux support where applicable and provide parity in documentation for both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/post-migration-changes.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by prioritizing PowerShell and Visual Studio in its examples and instructions. PowerShell is mentioned as a primary tool for retrieving deployment files and managing updates, with no explicit mention or examples of equivalent Bash, Azure CLI, or Linux-native workflows. Visual Studio, a Windows-centric IDE, is referenced for update processes, and there is a lack of Linux-specific guidance or parity in automation/script examples. Azure CLI is mentioned once, but not as prominently as PowerShell.
Recommendations:
  • Provide explicit Azure CLI and Bash examples alongside PowerShell for all operations, especially for retrieving deployment files and managing updates.
  • Include instructions or references for using cross-platform tools (e.g., Azure CLI, REST API via curl) for Linux and macOS users.
  • Add a section or callouts for Linux users, highlighting any differences or additional steps required.
  • When mentioning Visual Studio, also reference cross-platform alternatives (e.g., VS Code, command-line deployment) and provide guidance for non-Windows environments.
  • Ensure that all automation and scripting recommendations are platform-agnostic or have clear Linux equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-cscfg-file.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 without Linux equivalents, and omitting any Linux-specific instructions or examples. There are no references to Linux file paths, tools, or usage patterns, and no guidance for users working on non-Windows platforms.
Recommendations:
  • Include Linux file path examples for schema locations, such as '/usr/local/share/azure-sdks/schemas' or similar, alongside Windows paths.
  • Mention cross-platform tools (e.g., Azure CLI, VS Code) and provide instructions for both Windows and Linux environments.
  • Clarify whether the .cscfg schema and related SDKs are available and supported on Linux, and if so, provide installation and usage guidance for Linux users.
  • Avoid assuming Visual Studio or .NET SDK usage is exclusive to Windows; reference cross-platform alternatives where possible.
  • Add explicit Linux examples or notes in sections discussing file locations, tools, or configuration steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-file.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates Windows bias by referencing only the Windows file path for the Azure Diagnostics configuration schema file location (C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\<version>\schemas) and does not mention Linux or cross-platform equivalents. There are no Linux or macOS-specific instructions or examples, and the documentation implicitly assumes a Windows development environment.
Recommendations:
  • Include the equivalent file path or installation instructions for Linux and macOS environments, if available.
  • Explicitly state whether the Azure SDK and related tools are supported on non-Windows platforms, and provide relevant guidance.
  • Add cross-platform notes or examples to ensure parity for developers using Linux or macOS.
  • Avoid referencing only Windows-specific tools or locations unless absolutely necessary; if so, provide alternatives or clarifications for other platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-webrole.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation for Azure Cloud Services (extended support) WebRole schema demonstrates a Windows bias. It exclusively references Windows technologies (IIS 7, ASP.NET, .NET Framework), Windows file paths and environment variables (e.g., %ROLEROOT%), and Windows-centric configuration concepts (certificate stores, CMD scripts). There are no examples or mentions of Linux-based web roles, alternative web servers, or cross-platform scripting. All examples and descriptions assume a Windows environment.
Recommendations:
  • Add explicit statements about Linux support or lack thereof for Cloud Services (extended support) web roles. If Linux is unsupported, clarify this early in the documentation.
  • If Linux support exists, provide parallel examples and schema explanations for Linux-based web roles, including references to Linux web servers (e.g., Apache, Nginx), Linux file paths, and environment variables.
  • Include information about how startup tasks and scripts should be formatted and executed on Linux (e.g., using shell scripts instead of CMD files).
  • Mention Linux certificate storage and management equivalents if applicable.
  • Where possible, use neutral or dual-platform terminology and examples (e.g., 'web server' instead of 'IIS', or provide both IIS and Nginx/Apache scenarios).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cloud-services-extended-support/schema-csdef-workerrole.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by referencing Windows-specific concepts and tools (such as certificate store locations like 'CurrentUser' and 'LocalMachine', store names like 'My', 'Root', etc., and the use of CMD/batch files for startup tasks) without mentioning Linux equivalents or alternatives. There are no examples or guidance for Linux-based deployments, and terminology assumes a Windows environment (e.g., .NET Framework, environment variables like %ROLEROOT%).
Recommendations:
  • Add explicit documentation or notes for Linux-based worker roles, including how certificates, environment variables, and startup tasks are handled on Linux.
  • Provide Linux-specific examples for startup tasks (e.g., using shell scripts instead of CMD files) and clarify file encoding requirements for Linux.
  • Document how certificate management works on Linux (e.g., using PEM files or Linux certificate stores), and provide equivalent instructions.
  • Clarify whether environment variables like %ROLEROOT% are available or mapped differently on Linux, and provide examples using $ROLEROOT or similar syntax.
  • Include guidance for cross-platform compatibility, highlighting any differences or limitations when deploying worker roles on Linux VMs.