Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 2126-2150 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/add-multiple-senders-net.md
...quickstarts/email/includes/add-multiple-senders-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line tools or PowerShell usage, but it does lack explicit Linux parity. The only command-line example is 'dotnet add package', which is cross-platform, and all code samples are in C# (which is also cross-platform). However, there are no examples or notes about running these commands or setting environment variables on Linux or macOS, nor are there shell-specific instructions or examples for non-Windows users.
Recommendations
- Add explicit instructions or examples for setting environment variables on Linux/macOS (e.g., export AZURE_CLIENT_ID=...) alongside any Windows-specific instructions (e.g., set AZURE_CLIENT_ID=...).
- Clarify that 'dotnet' commands are cross-platform and can be run on Linux, macOS, and Windows.
- If referencing the Azure Portal, note that it is accessible from any OS.
- Consider providing code samples or command-line snippets in Bash or other popular shells where relevant, especially for environment setup.
- Add a note or section confirming that all steps are supported on Linux and macOS, not just Windows.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-dot-net.md
...ludes/create-custom-managed-domain-resource-dot-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of command-line tooling, PowerShell usage, or Windows-specific instructions. However, it lacks explicit Linux/macOS parity in key areas: there are no terminal or shell examples for retrieving environment variables or authenticating via CLI, and all instructions for obtaining the Azure Subscription ID reference the Azure Portal UI, which is platform-agnostic but omits CLI alternatives often preferred by Linux users. All code samples are in C#, which is cross-platform, but the documentation does not clarify or demonstrate usage on Linux systems.
Recommendations
- Add examples for obtaining the Azure Subscription ID using the Azure CLI (e.g., `az account show --query id -o tsv`), and mention that the Azure CLI is available on Windows, Linux, and macOS.
- Where environment variables are referenced (e.g., AZURE_SUBSCRIPTION_ID), provide both Windows (set in CMD/PowerShell) and Linux/macOS (export in bash/zsh) syntax.
- Explicitly state that all .NET and SDK instructions are cross-platform, and provide any Linux/macOS-specific notes if there are known differences.
- If authentication or SDK usage differs on Linux/macOS (e.g., device login flows, credential storage), document those differences.
- Consider including a short section or note confirming that all steps are supported on Linux/macOS, and link to any relevant cross-platform setup guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-import-export-portal.md
...main//articles/dns/private-dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both Windows DNS and BIND as sources for zone files, but the Windows DNS instructions (including the default file path and UI details) are mentioned before BIND. There are no command-line or tool-specific examples for either platform, but the ordering gives Windows DNS precedence. No PowerShell or Windows-only tools are used for import/export, and the portal and Azure CLI are presented as cross-platform solutions. No Linux-specific tools or commands are omitted, but the mention order shows a mild 'windows_first' bias.
Recommendations
- List BIND (Linux/Unix) and Windows DNS sources in parallel or alternate the order to avoid implicit prioritization.
- Provide example commands for obtaining zone files from both Windows DNS (e.g., file path) and BIND (e.g., typical Linux file path or command to copy the file).
- Explicitly state that the Azure portal and Azure CLI are cross-platform and suitable for both Windows and Linux users.
- If possible, add a note or example for exporting a zone file from BIND using standard Linux commands (e.g., cp, scp) to match the detail given for Windows DNS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-email-resource-dot-net.md
...starts/email/includes/create-email-resource-dot-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation is focused exclusively on .NET/C# SDK usage and does not provide any OS-specific command-line examples or instructions. However, it implicitly assumes a cross-platform environment by referencing the .NET Core SDK 'for your operating system' and avoids explicit Windows-only tools or PowerShell commands. There are no CLI, shell, or scripting examples for Linux or macOS users, nor are there any references to Linux-specific workflows or tools.
Recommendations
- Add explicit instructions or examples for setting environment variables on both Windows (e.g., setx) and Linux/macOS (e.g., export in bash).
- Include Azure CLI examples for common tasks (e.g., retrieving subscription ID, creating resource groups) alongside SDK code.
- Mention how to authenticate using the Azure CLI on Linux/macOS, and clarify that the .NET SDK and authentication methods work cross-platform.
- If referencing the Azure portal, clarify that it is web-based and OS-agnostic.
- Consider providing bash/zsh shell snippets where relevant, especially for environment setup and scripting.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/events/includes/create-event-subscription-az-cli.md
...ts/events/includes/create-event-subscription-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows a mild Windows bias by linking to the Windows-specific Azure CLI installation instructions in the prerequisites, without mentioning or linking to Linux or macOS installation guides. However, all command-line examples use the cross-platform Azure CLI and are not inherently Windows-specific.
Recommendations
- In the prerequisites, provide links to Azure CLI installation instructions for all supported platforms (Windows, Linux, macOS), or link to the general installation page that covers all OSes.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS to reassure non-Windows users.
- If possible, include a note or section confirming cross-platform compatibility of the CLI commands shown.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-dot-net.md
...cludes/create-azure-managed-domain-resource-dot-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only C#/.NET code examples and does not include any OS-specific command-line instructions or tooling. However, in the 'Prerequisites' section, it references the .NET Core SDK 'for your operating system' and does not show bias toward Windows or Windows-specific tools. There are no PowerShell, Command Prompt, or Windows-only tool references. However, there is a lack of parity in showing how to set environment variables or run the code on Linux/macOS, which may leave Linux users without clear guidance.
Recommendations
- Add explicit instructions or examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside any Windows instructions (if provided).
- If any command-line authentication or Azure CLI steps are referenced, ensure both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) examples are included.
- Clarify that the C#/.NET code is cross-platform and can be run on Linux and macOS as well as Windows.
- If referencing the Azure portal or tools, note that these are OS-agnostic.
- Consider adding a short section or note for Linux/macOS users on how to install the .NET SDK and run the examples.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-privatednszone.md
.../blob/main//articles/dns/private-dns-privatednszone.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally avoids overt platform bias, but in the 'Next steps' section, the PowerShell (Windows-centric) guide is listed before the Azure CLI guide, subtly prioritizing the Windows tool. No Linux-specific tools or examples are missing, but the ordering suggests a slight Windows-first bias.
Recommendations
- List Azure CLI and Azure PowerShell guides in parallel or alternate their order in different documentation pages to avoid implicit prioritization.
- Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide links to installation/use on both Windows and Linux.
- Where possible, include Bash or Linux-native command examples alongside PowerShell, or clarify that Azure CLI examples work on both Windows and Linux.
- Review documentation templates to ensure that Windows tools are not always listed first by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp-oauth.md
...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create a new C# application. However, the rest of the instructions and code samples are cross-platform and do not rely on Windows-only tools or patterns.
Recommendations
- List Bash (or 'terminal') before or alongside 'cmd' and 'PowerShell' when referring to console windows, e.g., 'In a terminal or command window (such as Bash, cmd, or PowerShell)...'
- Explicitly mention that all .NET CLI commands and MailKit code samples work identically on Linux, macOS, and Windows.
- Consider including a brief note or example for Linux/macOS users if there are any OS-specific considerations (e.g., package installation, environment variables).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-advanced/includes/prepend-python.md
...s/email/send-email-advanced/includes/prepend-python.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Windows-style commands for activating the Python virtual environment ('.\Scripts\activate') and does not include the equivalent Linux/macOS command ('source ./bin/activate'). No other explicit Windows tools or patterns are present, but the omission of Linux/macOS instructions may hinder cross-platform usability.
Recommendations
- Include both Windows and Linux/macOS commands for activating the Python virtual environment. For example, show: - Windows: .\Scripts\activate - Linux/macOS: source ./bin/activate
- Use tabbed or side-by-side examples for platform-specific commands where appropriate.
- Review all setup and prerequisite steps to ensure parity for Linux/macOS users, especially for file paths and terminal commands.
- Explicitly state that the instructions apply to both Windows and Linux/macOS, or provide platform-specific notes where differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-azcli.md
...nd-email-advanced/includes/inline-attachments-azcli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a 'windows_first' bias in the environment variable setup section, where Windows instructions are presented before macOS and Linux. However, the rest of the content is cross-platform, using Azure CLI commands that are applicable to all operating systems, and provides separate tabs for Windows, macOS, and Linux where relevant. There are no exclusive Windows tools, PowerShell-specific examples, or missing Linux examples.
Recommendations
- Present environment variable setup instructions in a neutral order (e.g., Linux/macOS first, alphabetical, or randomized) to avoid implying Windows primacy.
- Consider combining macOS and Linux instructions where they are identical, or explicitly state that the instructions apply to all Unix-like systems.
- Ensure that any references to editors or IDEs (e.g., Visual Studio) are balanced with cross-platform alternatives (e.g., VS Code, JetBrains IDEs) or generic terms.
- Continue to provide explicit, parallel examples for all supported platforms to maintain parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/rooms/manage-rooms-call.md
...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is generally cross-platform, providing code samples for C#, Java, JavaScript, and Python, which are not inherently Windows-specific. However, there is a subtle Windows bias in the 'For more information' link for enabling PSTN dial-out, which includes '?tabs=windows&pivots=platform-azcli' in the URL, suggesting that Windows is the default or primary platform. No PowerShell, Windows-only tools, or CLI commands are present, and all code samples are platform-agnostic SDK usage.
Recommendations
- Review all cross-referenced links (such as the PSTN dial-out quickstart) to ensure that Linux/macOS tabs are available and not defaulted to Windows.
- Avoid using query parameters in documentation links that default to Windows unless there is a clear reason; instead, link to a neutral or platform-agnostic tab.
- Explicitly mention in the introduction or prerequisites that all SDK operations are supported on Windows, Linux, and macOS where applicable.
- If there are any platform-specific steps (e.g., for callback endpoints or phone number provisioning), provide equivalent instructions for Linux/macOS environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-net.md
...ity/includes/active-directory/service-principal-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by listing Windows terminal options (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. However, all command-line instructions use cross-platform .NET CLI commands, and there are no PowerShell-specific scripts or Windows-only tools. No Linux-specific examples or troubleshooting are provided, but no Linux functionality is missing.
Recommendations
- List terminal options in a neutral or Linux-first order, e.g., 'Bash, Command Prompt, or PowerShell'.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Add a note or section confirming that the .NET SDK and Azure SDKs are cross-platform, with links to installation instructions for Linux and macOS.
- Provide troubleshooting tips or environment setup notes for Linux users if there are known differences (e.g., environment variable configuration for DefaultAzureCredential).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-az-cli.md
...identity/includes/access-tokens/access-token-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions for Windows, macOS, and Linux, but consistently lists Windows instructions first in each section. All command-line examples use the cross-platform Azure CLI, and both Windows and Unix-like systems are covered for environment variable configuration. No Linux or macOS examples are missing, and no Windows-specific tools or PowerShell commands are used.
Recommendations
- Rotate the order of OS tabs or use a neutral default (e.g., detect user's OS or list Linux/macOS first in some sections) to avoid always privileging Windows.
- Explicitly mention that Azure CLI commands are cross-platform to reassure non-Windows users.
- Consider combining macOS and Linux instructions where they are identical, or clarify differences only when necessary.
- Ensure parity in post-setup instructions (e.g., mention restarting editors/IDEs for all OSes, not just Windows).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-az-cli.md
.../quickstarts/rooms/includes/rooms-quickstart-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides environment variable setup instructions with Windows listed first, followed by macOS and Linux. The Azure CLI installation link points to the Windows-specific instructions by default. However, all command-line examples use the cross-platform Azure CLI, and Linux/macOS are included in environment variable setup, so the bias is limited to ordering and default linking.
Recommendations
- Present environment variable setup instructions in a neutral order (e.g., Linux/macOS first, or alphabetical order), or use a tabbed interface with no default selection.
- Link to the general Azure CLI installation page or provide links for all supported platforms, not just Windows.
- Ensure that any references to editors or IDEs (e.g., Visual Studio) are accompanied by cross-platform alternatives (e.g., VS Code, JetBrains Rider) where appropriate.
- Continue to provide explicit Linux/macOS instructions wherever Windows-specific steps are given.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/sms/includes/send-sms-az-cli.md
...n-services/quickstarts/sms/includes/send-sms-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform instructions, but in the section about setting the environment variable, the Windows instructions are presented first, followed by macOS and Linux. There are no missing Linux examples or exclusive use of Windows tools, but the ordering may subtly prioritize Windows users.
Recommendations
- Present OS-specific instructions in a neutral or rotating order (e.g., Linux, macOS, Windows) or group them under expandable tabs without a default 'first' tab.
- Ensure that links to Azure CLI installation instructions are equally visible for all operating systems, not just Windows.
- Consider adding a brief statement at the start clarifying that all major platforms are supported equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/tutorial-public-dns-zones-child.md
.../main//articles/dns/tutorial-public-dns-zones-child.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a complete absence of CLI-based instructions (such as Azure CLI or Bash), which are commonly used on Linux and cross-platform environments. This omission may disadvantage Linux users or those who prefer automation and scripting.
Recommendations
- Add equivalent instructions using the Azure CLI (az), which is cross-platform and widely used on Linux, macOS, and Windows.
- Provide sample commands for creating and managing child DNS zones via the CLI, including resource creation, verification, and cleanup.
- Include notes or links to relevant Azure CLI documentation for further reference.
- Ensure that any screenshots or examples that are platform-specific are balanced with text-based, platform-agnostic alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-javascript.md
...includes/closed-captions/closed-captions-javascript.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a 'windows_first' bias in the prerequisites section, where the link to creating an Azure Communication Services resource includes a '?tabs=windows' query parameter, suggesting Windows as the default or primary platform. No explicit Linux or cross-platform guidance is provided, but the rest of the page is platform-neutral and focuses on JavaScript code.
Recommendations
- Update prerequisite links to either be platform-neutral or explicitly include Linux/macOS tabs or pivots.
- Ensure that quickstart and resource creation links do not default to Windows, or provide equal visibility for Linux instructions.
- Review all referenced documentation to confirm Linux users can easily find relevant setup steps.
- Consider adding a note clarifying that the JavaScript SDK and features are cross-platform and supported on Linux, macOS, and Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/custom-teams-endpoint/voice-video-calling-cte-ios.md
...s/custom-teams-endpoint/voice-video-calling-cte-ios.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is focused on getting started with Azure Communication Services Calling SDK for iOS. While the main content is appropriately Mac/iOS-centric, there is a notable instance of Windows bias in the prerequisites section: the link to creating a Communication Services resource uses a URL with '?tabs=windows&pivots=platform-azp', suggesting Windows as the default or primary platform. There are no Linux-specific instructions or parity considerations, but since the SDK is for iOS, this is not a major omission. However, the presence of 'windows' in the resource creation link may confuse or alienate users on non-Windows platforms.
Recommendations
- Update the 'Create a Communication Services resource' link to either a neutral/default tab or provide explicit options for Mac/Linux users, not just Windows.
- Ensure that any referenced Azure portal or CLI instructions include parity for Mac and Linux users (e.g., Azure CLI commands that work cross-platform, not just Windows PowerShell or Windows-specific tools).
- Audit all quickstart and prerequisite links for platform-specific query parameters or content, and provide clear guidance for non-Windows environments where applicable.
- Consider adding a note clarifying that the SDK and instructions are platform-specific (iOS/Mac), but resource creation and management can be performed from any OS using the Azure Portal or cross-platform CLI tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/local-preview-mirroring.md
...kstarts/voice-video-calling/local-preview-mirroring.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides platform-specific instructions for Windows, Android, and iOS, but omits Linux entirely. There are no Linux examples or guidance, which may leave Linux users unsupported.
Recommendations
- Add a Linux-specific section or pivot alongside Windows, Android, and iOS.
- If the feature is not available on Linux, explicitly state this to inform users.
- If Linux is supported via a web client or another method, provide instructions or a link.
- Ensure parity in documentation structure and detail for all supported platforms, including Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/voice-video-calling/includes/video-calling/video-calling-ios.md
...eo-calling/includes/video-calling/video-calling-ios.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias: in the prerequisites, the link to creating a Communication Services resource uses a URL parameter '?tabs=windows', and the phrase 'tabs=windows&pivots=platform-azp' suggests that Windows is the default or primary platform for resource creation. However, the rest of the page is focused on iOS development and does not provide Windows-specific tools, PowerShell, or Windows-only examples. There are no Linux-specific instructions or examples, but the context is iOS/macOS development, which is inherently Apple-centric.
Recommendations
- In the prerequisite step for creating a Communication Services resource, ensure that links do not default to Windows tabs or pivots. Instead, use a neutral or platform-agnostic link, or provide explicit options for Windows, Linux, and macOS.
- If the Azure CLI is used (as in the token generation step), clarify that it is cross-platform and provide installation links or instructions for both Windows and Linux/macOS.
- Audit all documentation links for platform-specific query parameters (like '?tabs=windows') and ensure parity by either removing them or offering equivalent Linux/macOS options.
- If any resource creation steps differ between platforms, provide side-by-side instructions or a platform selector for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/calling-widget/calling-widget-js-tutorial.md
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias by listing Windows/Command Prompt instructions before macOS/Terminal equivalents when creating the project directory. However, all other instructions and code samples are cross-platform and use standard tools (Node.js, VS Code, npx http-server) that work on both Windows and Linux/macOS. There are no PowerShell-specific commands, Windows-only tools, or missing Linux examples.
Recommendations
- Present platform-specific instructions in parallel or alphabetical order (e.g., Linux/macOS first, or both together) to avoid implying Windows primacy.
- Explicitly mention Linux alongside macOS in terminal instructions, as most commands are identical.
- Where possible, use phrasing like 'In your terminal (Windows Command Prompt, PowerShell, macOS Terminal, or Linux shell)...' to reinforce cross-platform applicability.
- If any platform-specific issues are known (e.g., file permissions on Linux), add notes to address them.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/tutorials/migrating-to-azure-communication-services-calling.md
...s/migrating-to-azure-communication-services-calling.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle 'windows_first' bias. In the feature comparison table, links to installation and authentication instructions use URLs with the 'uwp' (Universal Windows Platform) and 'windows' tabs or pivots as defaults, even for web, iOS, and Android platforms. There are no explicit Linux or cross-platform CLI examples or references. However, the page does not provide any PowerShell-specific commands, nor does it mention Windows-only tools or patterns directly.
Recommendations
- Ensure that installation and authentication links default to cross-platform or neutral pivots (e.g., 'dotnet', 'cli', or 'bash') where possible, rather than 'uwp' or 'windows'.
- Where platform-specific instructions are needed, provide parity by including Linux/macOS examples or links alongside Windows ones.
- Audit all quickstart and how-to links to verify that Linux users are not directed to Windows-specific instructions by default.
- Consider adding a section or note clarifying cross-platform support and pointing to Linux/macOS setup guides if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/confidential-computing/attestation.md
...b/main//articles/confidential-computing/attestation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any platform-specific examples or instructions, but it also does not mention or illustrate any Windows-specific tools, commands, or patterns. However, there is a lack of explicit Linux examples or references, which could leave Linux users uncertain about platform compatibility or usage.
Recommendations
- Add explicit examples or references for both Windows and Linux environments, especially for common attestation workflows.
- Clarify whether the attestation process and tools are platform-agnostic or if there are OS-specific considerations.
- Include links or references to Linux-specific tools or sample code, if available.
- If sample code is provided elsewhere, ensure parity between Windows and Linux in those samples and link to both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/dotnet-overview.md
.../blob/main//articles/container-apps/dotnet-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples, but it also does not mention or demonstrate Linux-specific tools, commands, or workflows. There is a lack of explicit Windows bias (such as PowerShell commands or Windows-first instructions), but the absence of Linux-specific guidance or parity checks (e.g., Docker commands for Linux, file system notes, or CLI usage examples) may leave Linux users underserved.
Recommendations
- Add explicit examples of building and running .NET containers using Linux-based Docker commands and shell syntax.
- Clarify that Azure Container Apps is OS-agnostic, and note any differences in containerization or deployment steps between Windows and Linux hosts if applicable.
- Include references or links to Linux development environments and tools (such as VS Code on Linux, or CLI-based workflows) alongside Visual Studio.
- Mention file system considerations (e.g., case sensitivity, path formats) that may differ between Windows and Linux containers.
- Provide troubleshooting tips or common issues for Linux-based .NET container deployments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/container-apps/microservices-dapr-pubsub.md
...//articles/container-apps/microservices-dapr-pubsub.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform instructions, especially for Python, where both Windows and Linux command variants are shown side by side. However, in the Python section, the Windows tab is presented before the Linux tab, which may subtly prioritize Windows. For Node.js and C#, the commands are platform-agnostic and use Bash syntax, which is compatible with both Windows (via WSL or Git Bash) and Linux. There are no exclusive references to Windows tools, PowerShell, or missing Linux examples. The documentation avoids Windows-specific tools and patterns, but the ordering of tabs in the Python section demonstrates a mild 'windows_first' bias.
Recommendations
- Present Linux and Windows command tabs in a neutral or randomized order, or default to Linux first to reflect the prevalence of Linux in cloud-native/containerized environments.
- Explicitly state that Bash commands can be run on Windows using WSL or Git Bash to ensure clarity for Windows users.
- Ensure that all language sections consistently provide both Windows and Linux command variants where differences exist.
- Consider adding a brief note in the prerequisites about cross-platform compatibility and recommended terminal environments for each OS.