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 2101-2125 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/resource-files.md
...azure-docs/blob/main//articles/batch/resource-files.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only C# code examples and does not include any platform-specific command-line instructions. However, it implicitly exhibits bias by omitting Linux- or cross-platform shell examples (e.g., Bash, CLI, or scripting) and does not mention any Linux tools or patterns for handling resource files on Batch VMs. There are no references to Windows-specific tools, but the lack of Linux parity in examples and guidance is a notable gap.
Recommendations
- Add Bash or shell script examples for creating and managing resource files, especially for common Linux scenarios.
- Include Azure CLI commands for uploading files to storage containers and generating SAS tokens, as these are cross-platform.
- Mention how resource files can be accessed and used on Linux VMs, including any differences in file paths or permissions.
- Provide guidance or links for Linux users on installing and using Azure SDKs or tools relevant to Batch resource files.
- Ensure that any references to application installation or file usage on VMs include both Windows and Linux approaches.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/business-process-tracking/includes/logic-apps-sku-standard.md
...s-process-tracking/includes/logic-apps-sku-standard.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 Linux at all. This absence could be seen as a lack of Linux parity if the page is part of a larger set where Windows is the default or only platform referenced elsewhere.
Recommendations
- If platform-specific instructions are needed, ensure both Windows and Linux examples are provided.
- Explicitly mention platform compatibility, including Linux, if relevant.
- Review related documentation to ensure Linux users are not excluded or left without guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-purge-endpoint.md
...ure-docs/blob/main//articles/cdn/cdn-purge-endpoint.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation only describes how to purge an Azure CDN endpoint using the Azure Portal (web UI) and does not provide any command-line examples. There are no references to Windows-specific tools, but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash, PowerShell) or REST API command examples are provided. This omission can disadvantage users who prefer or require command-line or automation approaches, which are common in Linux environments.
Recommendations
- Add examples for purging a CDN endpoint using the Azure CLI (az cdn endpoint purge ...), which works cross-platform (Windows, Linux, macOS).
- Include REST API example requests (e.g., using curl) to demonstrate purging via HTTP, which is platform-agnostic.
- If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided and presented together or with Linux-first parity.
- Explicitly mention that the Azure CLI and REST API approaches are supported on all major operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-pop-list-api.md
...azure-docs/blob/main//articles/cdn/cdn-pop-list-api.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or tooling, but it also does not include any command-line examples or scripts at all. There are no Windows/Powershell examples, but also no Linux/bash examples. However, the absence of any Linux-specific guidance or parity checks (such as curl, wget, or bash scripting for retrieving the POP IP list) may disadvantage Linux users who are common in DevOps roles.
Recommendations
- Add example commands for retrieving the POP IP list using common Linux tools (e.g., curl, wget, jq).
- If providing scripts or automation, ensure both PowerShell (Windows) and bash (Linux) examples are included.
- Explicitly mention that the process is platform-agnostic if no OS-specific steps are required.
- Link to cross-platform tools or scripts (e.g., Python) where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cdn/cdn-sas-storage-support.md
...ocs/blob/main//articles/cdn/cdn-sas-storage-support.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific examples or tooling instructions, but it also does not include any command-line examples or scripts for generating SAS tokens or interacting with Azure Storage. As a result, there is no explicit Windows bias (such as PowerShell commands or references to Windows tools), but there is a lack of parity because no Linux (or cross-platform) command-line examples are given at all.
Recommendations
- Add example commands for generating SAS tokens using cross-platform tools such as Azure CLI (az), which works on Windows, Linux, and macOS.
- If scripting examples are provided in the future, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are included.
- Reference cross-platform tools (like Azure CLI or REST API) before or alongside any platform-specific tools.
- Explicitly mention that the steps can be performed from any OS using the Azure Portal or cross-platform tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/using-the-shell-window.md
...b/main//articles/cloud-shell/using-the-shell-window.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains cross-platform neutrality, but in the 'Copy and paste' section, Windows instructions are presented first, followed by macOS and then Linux. No section is missing Linux examples or tools, and both Bash and PowerShell environments are mentioned equally. There is no exclusive use of Windows tools or patterns.
Recommendations
- Present copy/paste shortcuts in a neutral order (e.g., alphabetical: Linux, macOS, Windows) or group them together without prioritizing one OS.
- Where possible, ensure that instructions for all platforms are given equal prominence and detail.
- Consider adding a brief statement at the start of relevant sections to reinforce parity, such as 'The following instructions apply to Windows, macOS, and Linux users.'
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/cloud-shell/new-ui-shell-window.md
...blob/main//articles/cloud-shell/new-ui-shell-window.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and neutral, but in the 'Copy and paste' section, Windows instructions are listed first, followed by macOS and then Linux. No other significant Windows bias (such as exclusive use of PowerShell, Windows-only tools, or missing Linux examples) is present.
Recommendations
- Rotate the order of platform-specific instructions (e.g., sometimes list Linux first, or use alphabetical order) to avoid implicit prioritization.
- Where possible, provide parallel detail and clarity for all platforms in shortcut and usage instructions.
- Continue to avoid Windows- or PowerShell-specific tools or terminology unless directly relevant to the feature being described.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/call-automation/azure-communication-services-azure-cognitive-services-integration.md
...nication-services-azure-cognitive-services-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild 'windows_first' bias by linking to the 'Create an Azure Communication Services resource' quickstart with the 'windows' tab selected in the URL parameters. No explicit Windows-only tools, PowerShell, or command-line examples are present, and the rest of the instructions are platform-neutral, focusing on the Azure portal UI. There are no Linux-specific examples or mentions, but also no Windows-exclusive commands or screenshots.
Recommendations
- Update quickstart links to use a platform-neutral default or provide both Windows and Linux/macOS tabs in the URL parameters.
- Where relevant, clarify that the steps are the same across operating systems, or provide explicit notes about cross-platform parity.
- If command-line or scripting examples are added in the future, ensure both Windows (PowerShell/Command Prompt) and Linux/macOS (Bash/CLI) examples are included side-by-side.
- Consider adding a brief statement at the start of the prerequisites or instructions to reassure users that all steps are cross-platform unless otherwise noted.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/voice-video-calling/includes/user-facing-diagnostics-ios.md
...-video-calling/includes/user-facing-diagnostics-ios.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is generally platform-neutral and focused on iOS, but there is a reference to 'device manager' in the mitigation steps for microphone issues, which is a Windows-specific tool. There are no Linux-specific examples or tools mentioned, and no Linux parity guidance is provided.
Recommendations
- Replace or supplement references to 'device manager' with equivalent instructions for macOS (e.g., 'System Preferences > Sound > Input') and Linux (e.g., using 'alsamixer', 'pavucontrol', or system settings).
- Where platform-specific troubleshooting is mentioned, provide parallel steps for Linux and macOS users.
- Audit all mitigation steps and ensure they do not assume Windows-only tools or terminology.
- Add a table or section listing platform-specific steps for common issues (e.g., enabling microphone, checking permissions) for Windows, macOS, and Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/mute-participants-how-to-java.md
...l-automation/includes/mute-participants-how-to-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by linking to resource creation instructions with a '?tabs=windows' parameter, which defaults users to Windows-specific instructions. There are no explicit Linux or cross-platform command-line examples, but the technical content (Java, Maven) is inherently cross-platform and does not otherwise favor Windows tools or patterns.
Recommendations
- Update all resource links (such as 'Create an Azure Communication Services resource') to either use a neutral tab (e.g., '?tabs=none') or explicitly mention both Windows and Linux options.
- If quickstart or prerequisite links default to Windows, add a note or alternative link for Linux/macOS users.
- Review all referenced quickstarts and ensure Linux parity in instructions and screenshots.
- Consider adding a short section or note clarifying that all Java/Maven commands work on Linux, macOS, and Windows, and provide any OS-specific caveats if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-java.md
...call-automation/includes/play-audio-quickstart-java.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 an Azure Communication Services resource includes a 'tabs=windows' query parameter, suggesting Windows as the default or primary platform. However, the rest of the documentation uses platform-neutral Java and Maven commands, and does not provide Windows-specific tools, PowerShell commands, or examples that would exclude Linux users.
Recommendations
- Update prerequisite links to use platform-neutral or explicit multi-platform tabs (e.g., 'tabs=linux', 'tabs=mac', or a selector), or clarify that instructions apply to all platforms.
- Wherever possible, avoid defaulting to Windows in URLs or documentation pivots unless Windows-specific instructions are truly required.
- If there are platform-specific steps (e.g., for setting up the environment), provide equivalent instructions for Linux and macOS alongside Windows.
- Explicitly state that all terminal/command instructions are cross-platform, or provide notes if there are differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md
...w-tos/call-automation/includes/play-audio-how-to-js.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 an Azure Communication Services resource uses a URL parameter '?tabs=windows', and the word 'windows' appears in the path, suggesting that Windows is the default or primary platform. There are no explicit Linux or cross-platform instructions or references, but there are also no Windows-specific commands or tools (e.g., PowerShell) used in the examples. All code and CLI examples are platform-agnostic JavaScript/Node.js commands.
Recommendations
- Update prerequisite links to use a neutral or platform-agnostic tab (e.g., '?tabs=browser' or remove the tab parameter if not needed).
- Explicitly mention that the instructions and examples apply equally to Windows, Linux, and macOS environments.
- If platform-specific steps exist, provide equivalent instructions for Linux (and macOS) alongside Windows, or clarify when steps are universal.
- Review all quickstart and resource links to ensure they do not default to Windows-specific tabs or content.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md
...s/call-automation/includes/play-audio-how-to-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation displays a mild Windows bias by presenting the Windows virtual environment activation command before the Unix equivalent in the setup instructions. Additionally, the link to creating an Azure Communication Services resource includes a 'tabs=windows' parameter, suggesting Windows as the default or primary platform. However, both Windows and Unix activation commands are present, and the rest of the guide is platform-agnostic Python code.
Recommendations
- Present Unix and Windows commands in parallel or in alphabetical order (e.g., Unix first, then Windows) to avoid implying a platform preference.
- Remove or balance 'tabs=windows' in documentation links, or provide a direct link to a platform-neutral or Linux-specific tab.
- Explicitly state that all instructions and code samples are cross-platform unless otherwise noted.
- Where platform-specific steps are required, ensure equal detail and prominence for both Windows and Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/recognize-how-to-js.md
...ow-tos/call-automation/includes/recognize-how-to-js.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild Windows bias by linking to resource creation instructions with a URL parameter that defaults to the Windows tab (e.g., '?tabs=windows'), and by referencing a quickstart with a similar Windows tab default. However, all code and command-line examples are cross-platform (Node.js, JavaScript, npm, node), and there are no PowerShell, CMD, or Windows-specific tools or patterns shown. No Linux-specific examples or instructions are missing, but the documentation does not explicitly mention or show parity for Linux/macOS environments.
Recommendations
- Avoid using '?tabs=windows' in documentation links unless Windows is truly the only supported platform. Use neutral or platform-agnostic links, or provide explicit tabs for Windows, Linux, and macOS.
- Where possible, mention that the npm and Node.js commands work on Windows, Linux, and macOS to reassure non-Windows users.
- If there are any platform-specific steps (such as environment variable setup, file paths, or permissions), provide examples for both Windows and Linux/macOS.
- Consider adding a note in the prerequisites or setup sections stating that the instructions are cross-platform, or provide links to platform-specific quickstarts if differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/play-audio-with-ai-java.md
...os/call-automation/includes/play-audio-with-ai-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a 'windows_first' bias in the prerequisites section, where the link to creating an Azure Communication Services resource explicitly uses the 'windows' tab in its URL. No Linux-specific instructions, examples, or tools are mentioned, but the rest of the content is platform-neutral and uses Java and Maven commands that work cross-platform. There are no explicit Windows-only tools, PowerShell commands, or missing Linux examples, but the default to Windows in links may suggest a preference.
Recommendations
- Ensure all quickstart and resource creation links use a neutral or platform-agnostic tab (e.g., remove '?tabs=windows' or provide a Linux tab as well).
- Explicitly mention that all Java and Maven commands work on both Windows and Linux, or provide example terminal commands for both platforms if there are any differences.
- Where platform-specific instructions are necessary, provide parallel guidance for both Windows and Linux users.
- Audit other linked documentation for similar 'windows' tab defaults and update to present Linux parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/recognize-action-quickstart-java.md
...utomation/includes/recognize-action-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias. In the prerequisites, links to resource creation use a 'tabs=windows' query parameter and reference 'windows' in the URL, suggesting Windows as the default or primary platform. However, the rest of the content (Java code, Maven commands) is cross-platform and does not show Windows-specific tooling or instructions. There are no explicit PowerShell, CMD, or Windows-only tool references, and no missing Linux examples for the provided commands.
Recommendations
- Update prerequisite links to use a neutral or platform-agnostic default (e.g., remove '?tabs=windows' or provide both Windows and Linux/macOS tabs).
- Explicitly state that the Java/Maven commands work on all platforms (Windows, Linux, macOS) to reinforce cross-platform compatibility.
- If platform-specific steps are necessary, provide parallel instructions for Linux/macOS and Windows, or clarify when steps are universal.
- Review other linked quickstarts to ensure Linux/macOS parity in referenced documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/recognize-how-to-python.md
...os/call-automation/includes/recognize-how-to-python.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by presenting Windows-specific instructions (for activating a Python virtual environment) before their Unix/Linux equivalents. The resource creation link also defaults to a Windows tab, but otherwise, Linux and Windows are both mentioned. All code examples are platform-agnostic Python, and no Windows-only tools or PowerShell commands are used.
Recommendations
- Present activation instructions for Python virtual environments for Windows and Unix/Linux in parallel (side-by-side or with equal prominence), or alternate which comes first.
- Avoid using Windows as the default tab or example in resource creation links; provide a neutral or platform-agnostic default, or highlight both platforms equally.
- Explicitly state that all Python code examples are cross-platform to reassure Linux/macOS users.
- If there are any platform-specific caveats or requirements, document them clearly for both Windows and Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-web.md
...s/closed-captions/closed-captions-teams-interop-web.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias, as seen in the prerequisite section where the link to creating an Azure Communication Services resource uses a Windows-specific tab and platform pivot by default. However, the rest of the documentation is platform-neutral, focusing on TypeScript code samples and not referencing any OS-specific tools or commands.
Recommendations
- Update prerequisite links to use a neutral or multi-platform default (e.g., avoid '?tabs=windows&pivots=platform-azp' unless contextually necessary).
- Explicitly mention support for Linux and macOS where applicable, especially in setup or quickstart links.
- If platform-specific instructions are required, provide parallel examples for Windows, Linux, and macOS.
- Review all quickstart and resource links to ensure they do not default to Windows unless the content is genuinely Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/mqtt-configure-private-endpoints.md
...rticles/event-grid/mqtt-configure-private-endpoints.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes configuration steps using the Azure Portal GUI, with no command-line examples provided. 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 can disadvantage Linux users or those who prefer or require automation and scripting.
Recommendations
- Add equivalent Azure CLI command-line instructions for all major steps (creating private endpoints, managing connections, approving/rejecting/removing endpoints).
- Explicitly mention that the Azure CLI can be used from Windows, Linux, or macOS, and provide Bash-compatible examples.
- Where screenshots are used, consider including CLI output examples for parity.
- If PowerShell is relevant, provide both PowerShell and Bash/Azure CLI examples side by side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-android.md
...osed-captions/closed-captions-teams-interop-android.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild '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. However, the rest of the documentation is platform-neutral, using Java code examples that are not specific to any operating system and do not reference Windows- or Linux-specific tools or patterns.
Recommendations
- Update prerequisite links to use a platform-neutral or user-selectable tab (e.g., remove '?tabs=windows' or provide both Windows and Linux options).
- Ensure that quickstart and resource creation guides referenced in prerequisites are equally accessible for Linux, macOS, and Windows users.
- If platform-specific instructions are necessary, present them in parallel (e.g., with tabs or side-by-side examples) and do not default to Windows.
- Review all referenced quickstarts and ensure Linux parity in instructions and tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/router-sdk/subscribe-events.md
...cation-services/how-tos/router-sdk/subscribe-events.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions 'cmd, PowerShell, or Bash' as possible consoles for running .NET CLI commands, listing Windows shells before Bash. However, all provided code and command-line examples are cross-platform (using dotnet CLI), and there are no Windows-specific tools or PowerShell scripts. No Linux-specific instructions or examples are missing, but the ordering of shell examples gives Windows environments priority.
Recommendations
- List Bash (or 'terminal') before cmd/PowerShell, or use neutral phrasing such as 'in a terminal or command prompt (e.g., Bash, PowerShell, or cmd)'.
- Explicitly state that all dotnet CLI commands work identically on Windows, Linux, and macOS.
- Where appropriate, include example output from both Windows and Linux terminals to reinforce cross-platform parity.
- If referencing shell environments, consider mentioning Linux/macOS shells first or equally.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-net.md
...nced-messaging/whatsapp/includes/common-setting-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides only C# code examples and references to the Azure portal, with no mention of platform-specific tools or commands. There are no explicit Windows or PowerShell examples, but there is also no Linux-specific guidance or parity in examples. The lack of platform-specific command-line or scripting examples means Linux users are not directly excluded, but they are also not supported with tailored content.
Recommendations
- Add equivalent code examples in other popular languages used on Linux (e.g., Python, Java, or Node.js) if relevant to the SDK.
- If any command-line steps are required (such as setting environment variables or retrieving connection strings), provide both Windows (PowerShell/CMD) and Linux (bash) examples.
- Clarify that the steps are platform-agnostic if that is the case, or explicitly mention any platform dependencies.
- Include screenshots or instructions for accessing the Azure portal from different operating systems if there are any differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/templates/template-messages-list-templates-net.md
...udes/templates/template-messages-list-templates-net.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only a C# code example without any platform-specific instructions, but it also lacks any mention of how to run or set up the example on different operating systems. There are no explicit Windows tools or PowerShell commands, but the absence of Linux (or cross-platform) context or examples may hinder non-Windows users.
Recommendations
- Add instructions for running the C# example on both Windows and Linux (e.g., using .NET CLI commands).
- Include notes about any OS-specific prerequisites or environment setup.
- If relevant, provide example commands for both Windows (PowerShell/cmd) and Linux (bash) to ensure parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/call-automation/includes/recording-byos-private-csharp.md
...l-automation/includes/recording-byos-private-csharp.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a C# code example for configuring Azure blob storage as external storage for call recording, but does not include any platform-specific commands or instructions. However, it lacks any mention of Linux-specific considerations, tools, or examples, and does not address cross-platform usage or parity.
Recommendations
- Add notes clarifying that the C# example is cross-platform and works on both Windows and Linux environments if applicable.
- Include Linux-specific setup or troubleshooting steps if there are any differences (e.g., authentication, environment variables, file system permissions).
- If there are any platform-specific dependencies or requirements, document them explicitly for both Windows and Linux.
- Consider providing examples or references for using the Azure SDK in other languages commonly used on Linux (e.g., Python, Java) if relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/chat/includes/chat-az-cli.md
...tion-services/quickstarts/chat/includes/chat-az-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild 'windows_first' bias in the environment variable setup sections. Windows instructions and commands are presented before macOS and Linux, and the Azure CLI installation link defaults to the Windows installation page. However, Linux and macOS instructions are present and complete, and all operational examples use cross-platform Azure CLI commands.
Recommendations
- Present operating system tabs in a neutral or rotating order (e.g., Linux, macOS, Windows) rather than always listing Windows first.
- Link to the general Azure CLI installation page or provide links for all major platforms, not just Windows.
- Ensure parity in detail and clarity across all OS-specific instructions.
- Consider including a brief note that all Azure CLI commands work identically across Windows, Linux, and macOS to reinforce cross-platform support.