Communication Services
1044
Total Pages
900
Linux-Friendly Pages
144
Pages with Bias
13.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
656 issues found
Showing 626-650 of 656 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/voice-routing-sdk-csharp.md
...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation refers to 'Command Prompt, PowerShell, or Bash' when instructing users to open a console window, listing Windows shells before Bash (commonly used on Linux/macOS). However, all command-line examples use the cross-platform 'dotnet' CLI, and there are no OS-specific commands or tools shown. No explicit Linux or macOS bias or omission is present, but the ordering of shells subtly prioritizes Windows environments.
Recommendations
- List Bash (Linux/macOS) before Command Prompt and PowerShell, or mention all shells in alphabetical order to avoid perceived prioritization.
- Explicitly state that all command-line instructions work identically on Windows, Linux, and macOS.
- Consider adding a brief note or table confirming cross-platform compatibility for the .NET SDK and CLI commands.
- If possible, include a screenshot or example from a Linux/macOS terminal as well as Windows to reinforce parity.
Create Pull Request
Communication Services
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 provides both Windows and macOS commands for creating the project directory, but lists Windows (command prompt) instructions before macOS (terminal) instructions. There are no Linux-specific examples or mentions, and Linux terminal usage is not explicitly addressed. All other instructions (Node, VS Code, running the app) use cross-platform commands, but the omission of Linux-specific guidance and the ordering of Windows first indicate a mild Windows bias.
Recommendations
- Add explicit Linux instructions alongside Windows and macOS for terminal commands (e.g., mkdir/cd).
- Use neutral phrasing such as 'In your terminal (Windows, macOS, or Linux)...' rather than listing Windows first.
- Mention Linux as a supported platform for VS Code and Node.js.
- If there are platform-specific caveats (e.g., file permissions, package installation), include notes for Linux users.
- Ensure all command examples are tested and work on Linux shells (bash, zsh, etc.).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/includes/router-quickstart-java.md
.../quickstarts/router/includes/router-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, which subtly prioritizes Windows environments. However, all commands and instructions are cross-platform and do not rely on Windows-specific tools or patterns. No PowerShell-specific examples or Windows-only tools are present, and Linux users are not excluded from any steps.
Recommendations
- List Bash (Linux/macOS) first or equally alongside cmd and PowerShell when referencing console windows.
- Explicitly state that all commands work on Linux, macOS, and Windows to reassure non-Windows users.
- Consider adding a note or section about running the sample on Linux/macOS, including any OS-specific considerations (e.g., environment variables, file paths).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/voice-routing-sdk-csharp.md
...kstarts/telephony/includes/voice-routing-sdk-csharp.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references 'Command Prompt, PowerShell, or Bash' as possible console windows, listing Windows shells before Bash (commonly used on Linux/macOS). However, all commands shown (dotnet CLI) are cross-platform and there are no Windows-specific tools or examples. There are no missing Linux examples, but the ordering subtly prioritizes Windows environments.
Recommendations
- List Bash (Linux/macOS) before Command Prompt and PowerShell, or mention all three in a neutral order (e.g., 'such as Bash, Command Prompt, or PowerShell').
- Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform compatibility.
- If possible, include a brief note or example of running the commands on Linux/macOS terminals to demonstrate parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-net.md
...ts/identity/includes/access-tokens/access-token-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a slight Windows bias by mentioning Windows command-line tools (cmd, PowerShell) before Bash when instructing users to run commands. However, all command-line instructions use 'dotnet' CLI, which is cross-platform, and environment variable usage is shown in a generic way. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
- List Bash (Linux/macOS) before Windows tools (cmd, PowerShell) when mentioning command-line environments, or mention all platforms equally.
- Add explicit notes or examples for setting environment variables on Windows (cmd/PowerShell) and Linux/macOS (Bash) to help users unfamiliar with the differences.
- Ensure that any future instructions involving file paths, environment variables, or shell commands provide both Windows and Linux/macOS syntax where they differ.
Communication Services
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 demonstrates a subtle Windows bias by referencing a 'Rooms quickstart' link with Windows-specific tabs and pivots before mentioning any Linux alternatives. The link uses '?tabs=windows&pivots=platform-azcli', which prioritizes Windows instructions and may imply Windows as the default platform. However, the code samples themselves are cross-platform (C#, Java, JavaScript, Python) and do not use Windows-specific tools or PowerShell commands.
Recommendations
- Ensure that quickstart and concept links include Linux and macOS tabs or pivots, or use a neutral default (e.g., CLI or cross-platform instructions).
- Explicitly mention Linux and macOS support in introductory sections, clarifying that all SDKs and features are available across platforms.
- Where platform-specific setup is required (e.g., for CLI or SDK installation), provide equal visibility and instructions for Linux, macOS, and Windows.
- Review linked documentation (such as the Rooms quickstart) to confirm Linux parity and avoid Windows-first navigation or examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-java.md
...es/quickstarts/rooms/includes/rooms-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles ('cmd, PowerShell') before Linux ('Bash') when describing where to run commands, but otherwise provides platform-neutral instructions and examples. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present. The Java/Maven workflow is cross-platform.
Recommendations
- List Bash (Linux/macOS) before Windows consoles when mentioning command-line environments, or use neutral phrasing such as 'in a terminal window (such as Bash, cmd, or PowerShell)'.
- Explicitly state that all commands and instructions work on Linux, macOS, and Windows.
- Provide troubleshooting notes for platform-specific issues if any exist (e.g., file paths, environment variables).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/send-sms-net.md
...tion-services/quickstarts/sms/includes/send-sms-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when describing how to run commands. However, all commands shown are cross-platform (dotnet CLI), and there are no PowerShell-specific scripts or Windows-only tools. No Linux-specific examples, tools, or troubleshooting are provided, but the instructions are generally applicable to both platforms.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles (cmd, PowerShell) to avoid implying Windows primacy.
- Explicitly mention that all commands work on Linux, macOS, and Windows, and provide any platform-specific notes if needed.
- Include a brief example or screenshot of running the commands in a Linux terminal.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variable setup).
Communication Services
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 bias by presenting Windows command prompt instructions before macOS equivalents when creating the project directory. However, all other instructions (Node.js, VS Code, running the app) use cross-platform commands and tools, and there are no PowerShell-specific examples or exclusive references to Windows-only tools.
Recommendations
- Present platform-specific instructions in parallel or grouped together, rather than listing Windows first.
- Explicitly mention Linux in platform-specific instructions, not just macOS and Windows.
- Include Linux-specific command examples where appropriate (e.g., for creating directories, checking VS Code installation).
- Add a note clarifying that all commands are compatible with Linux unless otherwise stated.
- Ensure parity in troubleshooting steps for all major platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sms/messaging-connect.md
...mmunication-services/concepts/sms/messaging-connect.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of tools, patterns, or terminology. However, it lacks any command-line or shell examples (such as Bash or PowerShell) and only provides SDK code samples in C# and JavaScript. There are no Linux-specific instructions, CLI walkthroughs, or references to Linux environments. The provisioning and usage flows are described entirely via the Azure portal UI and SDKs, with no mention of cross-platform command-line automation or Linux developer workflows.
Recommendations
- Add CLI-based examples using Azure CLI or Bash scripts to demonstrate provisioning and sending SMS, ensuring parity for Linux and cross-platform users.
- Include explicit references to Linux and macOS environments in setup and troubleshooting sections, clarifying that the SDKs and APIs are cross-platform.
- Provide sample Dockerfiles or containerization tips for running Messaging Connect integrations on Linux servers.
- If PowerShell or Windows-specific tools are not needed, explicitly state that all features are available and supported on Linux, macOS, and Windows.
- Expand the SDK tutorial section to include Python and Java examples as soon as those SDKs are available, and clarify their cross-platform compatibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sms/messaging-connect.md
...mmunication-services/concepts/sms/messaging-connect.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias in terms of tools, commands, or PowerShell usage. However, it lacks any platform-specific examples, and all SDK code samples are limited to C# (.NET) and JavaScript, with no Linux- or Unix-specific command-line, shell, or environment examples. There is no mention of Linux tools, shell commands, or cross-platform CLI usage, and the developer workflow is described entirely through the Azure Portal UI and SDKs, which may implicitly favor Windows/.NET developers.
Recommendations
- Add explicit Linux/Unix command-line examples for provisioning and sending SMS, such as using the Azure CLI or cURL.
- Include Python SDK examples as soon as the SDK is available, and mention its roadmap.
- Clarify that the APIs and SDKs are cross-platform and can be used from Linux, macOS, and Windows environments.
- Provide guidance or links for headless/server-side provisioning and sending (e.g., via CLI or REST), not just Azure Portal UI.
- Mention any platform-specific requirements or parity (e.g., if all SDKs work identically on Linux and Windows).
Communication Services
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 displays a subtle Windows bias by referencing Windows in the authentication link (../quickstarts/identity/access-tokens.md?tabs=windows&pivots=platform-azportal) as the default or first tab, rather than providing a cross-platform or Linux example. However, there are no explicit PowerShell-heavy examples, exclusive mention of Windows tools, or missing Linux examples in the main content. The documentation is otherwise platform-neutral and covers web, iOS, and Android parity.
Recommendations
- Ensure that authentication and other platform-neutral features provide Linux and macOS examples or tabs alongside Windows, or default to a cross-platform approach.
- Wherever a link or tab is provided (such as for authentication), offer parity for Linux (e.g., Bash, CLI) and macOS, not just Windows.
- Review all quickstart and how-to links to confirm that Linux users are not required to adapt Windows-specific instructions.
- Explicitly mention cross-platform compatibility in sections that are not inherently OS-specific.
Communication Services
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 exhibits a mild 'windows_first' bias. In the prerequisites section, the link to creating an Azure Communication Services resource uses a URL parameter '?tabs=windows', suggesting Windows as the default or primary platform. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the content (Java, Maven, terminal usage) is generally platform-agnostic.
Recommendations
- Ensure that links to Azure documentation use neutral or cross-platform tabs by default (e.g., '?tabs=linux' or no tab parameter).
- Explicitly mention that the steps work on both Windows and Linux, or provide notes for any platform-specific differences.
- If there are platform-specific quickstart pivots (e.g., for creating resources), provide both Windows and Linux options or clarify that the instructions are cross-platform.
- Review all linked quickstarts to ensure Linux parity and avoid defaulting to Windows in tabbed instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/analytics/logs/call-summary-log-schema.md
...ces/concepts/analytics/logs/call-summary-log-schema.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides sample log data where the only explicit desktop OS mentioned is Windows ("osVersion": "Windows 10.0.17763 Arch: x64"). Other examples include Darwin (macOS) and Android, but there are no Linux examples. Windows is the only desktop OS shown in the P2P call sample, and Linux is not mentioned anywhere. There are no command-line or tool usage examples, so no PowerShell or Windows tool bias is present, but the log samples show a subtle preference for Windows as a desktop environment.
Recommendations
- Include at least one sample log entry where 'osVersion' reflects a Linux distribution (e.g., 'Ubuntu 20.04', 'Linux 5.15.0-60-generic').
- In the data definitions, clarify that 'osVersion' can include Linux, macOS, Windows, Android, and iOS, and provide representative values for each.
- If possible, add a FAQ or note about how logs appear for Linux clients/endpoints.
- Review future documentation and samples to ensure Linux is represented equally alongside Windows and macOS in both log samples and descriptive text.
Communication Services
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 exhibits a mild 'windows_first' bias in the prerequisites section, where the link to creating an Azure Communication Services resource includes a '?tabs=windows' parameter and the word 'windows' in the URL. No explicit Linux or cross-platform instructions or examples are provided, but the rest of the guide is platform-neutral and focused on JavaScript/Node.js, which is inherently cross-platform.
Recommendations
- Ensure that links to Azure resource creation guides either default to a neutral tab or explicitly mention both Windows and Linux options.
- If platform-specific steps exist (e.g., environment setup, file hosting, or CLI usage), provide parallel instructions or notes for Linux/macOS users.
- Review and update any quickstart or referenced documentation to avoid defaulting to Windows tabs or terminology unless necessary.
- Consider adding a note in the prerequisites clarifying that all steps and examples are cross-platform unless otherwise stated.
Communication Services
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 demonstrates a mild Windows bias by referencing Windows first in the link to creating an Azure Communication Services resource, using a URL parameter (?tabs=windows&pivots=platform-azp) that suggests a Windows-centric quickstart. However, the rest of the page uses Java and Maven, which are cross-platform, and does not provide any OS-specific instructions or examples. There are no explicit PowerShell commands, Windows-only tools, or missing Linux equivalents in the main content.
Recommendations
- Update prerequisite links to either be OS-neutral or provide both Windows and Linux/macOS tabs equally, rather than defaulting to Windows.
- Review linked quickstarts to ensure Linux and macOS instructions are as prominent and accessible as Windows instructions.
- Explicitly state that the Java and Maven steps are cross-platform and can be run on Windows, Linux, or macOS.
- If there are any platform-specific steps (e.g., environment variables, file paths), provide examples for both Windows and Linux/macOS.
Communication Services
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 demonstrates a mild Windows bias by presenting Windows-specific instructions (virtual environment activation) before Unix/Linux equivalents. Additionally, some linked quickstarts default to Windows tabs. However, Linux/Unix commands are present where relevant, and the main content is otherwise platform-neutral.
Recommendations
- Present Unix/Linux and Windows instructions side-by-side or in parallel tabs, rather than listing Windows first.
- Ensure that all linked resources and quickstarts do not default to Windows tabs, or clearly indicate how to switch to Linux/Mac instructions.
- Where possible, use platform-agnostic language and examples, or provide equal prominence to both Windows and Linux commands.
- Consider explicitly stating that all features and examples are cross-platform unless otherwise noted.
Communication Services
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# example for configuring Azure blob storage for call recording, but does not include any platform-specific commands or references. However, there are no examples or notes addressing Linux or cross-platform considerations, nor is there any mention of Windows-specific tools or patterns.
Recommendations
- Add explicit notes about cross-platform compatibility, clarifying whether the example applies equally to Windows, Linux, and macOS.
- If there are any platform-specific steps (e.g., authentication with Azure CLI, environment variable setup), provide both Windows (PowerShell/CMD) and Linux (bash) command examples.
- Include a section or note on any dependencies or configurations that may differ between Windows and Linux environments.
Communication Services
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 terminal/command window instructions and virtual environment activation commands only in the Windows format (e.g., .\Scripts\activate), with no equivalent Linux/macOS commands (e.g., source ./bin/activate). This may confuse or hinder users on non-Windows platforms. No explicit Windows tools or PowerShell commands are used, but the lack of Linux/macOS parity is a notable bias.
Recommendations
- For every command-line instruction, provide both Windows and Linux/macOS versions, especially for virtual environment activation (e.g., '.\Scripts\activate' for Windows, 'source ./bin/activate' for Linux/macOS).
- Use tabbed or side-by-side code blocks to show platform-specific commands where they differ.
- Explicitly mention that the instructions apply to both Windows and Linux/macOS, and clarify any platform-specific steps.
- Review the documentation for other subtle Windows-first assumptions, such as path separators or references to 'command window' instead of 'terminal'.
Communication Services
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, it references environment variables and authentication via the Azure SDK, which can have OS-specific nuances, but does not clarify or provide examples for Linux/macOS users. There is no explicit Windows bias (e.g., PowerShell, Windows tools, or Windows-first ordering), but Linux parity is lacking in terms of environment variable setup and authentication instructions.
Recommendations
- Add explicit instructions or examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside any Windows (set AZURE_SUBSCRIPTION_ID=...) examples.
- Clarify that the .NET Core SDK and Azure SDK are cross-platform and provide links or notes for Linux/macOS installation guides.
- If referencing command-line authentication (e.g., az login), provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples.
- Include a note or section confirming that all code samples are cross-platform and highlight any OS-specific considerations, if applicable.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-dot-net.md
...il/includes/create-sender-username-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 tools or command-line instructions, but it lacks explicit Linux parity in its examples and guidance. All code samples are in C# and .NET, which are cross-platform, but there are no shell or environment variable examples for Linux/macOS, nor are there any references to Linux-specific workflows or tools. The instructions for setting environment variables and acquiring the subscription ID are generic and do not mention platform-specific steps.
Recommendations
- Add explicit examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside any Windows (set AZURE_SUBSCRIPTION_ID=...) instructions.
- When referencing the Azure CLI or authentication, provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples.
- Clarify that .NET Core SDK and the code samples are cross-platform, and provide links or notes for Linux/macOS users where appropriate.
- If referencing file paths or shell commands, include both Windows and Linux/macOS formats.
- Consider including a short section or callout for Linux/macOS users to ensure they can follow along without ambiguity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-closed-captions.md
...oice-video-calling/get-started-with-closed-captions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation uses platform-specific pivots for web, Windows, Android, and iOS, but does not mention or provide examples for Linux. Additionally, in the 'Clean up resources' section, the link includes a 'tabs=windows' parameter, suggesting Windows is the default or primary example, with no mention of Linux alternatives.
Recommendations
- Add explicit Linux support or examples if the SDK or service is available for Linux.
- In the 'Clean up resources' section, provide instructions or links for Linux users (e.g., using Azure CLI on Linux, or Bash examples).
- Avoid defaulting to Windows tabs in links; use a neutral or platform-agnostic default, or provide clear options for all supported platforms.
- If Linux is not supported, clearly state this in the documentation to avoid confusion.
Communication Services
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 demonstrates 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 platforms.
- Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS to reassure non-Windows users.
- Consider including a brief note or section for platform-specific considerations, if any, to improve inclusivity.
Communication Services
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 subtle Windows bias by listing Windows command-line environments (cmd, PowerShell) before Bash when instructing users to create a new C# application. No explicit Linux or cross-platform examples are missing, but the ordering implicitly prioritizes Windows environments.
Recommendations
- List Bash before or alongside cmd and PowerShell when mentioning console windows, e.g., 'In a console window (such as Bash, cmd, or PowerShell)...'
- Explicitly state that all commands and code samples work identically on Linux, macOS, and Windows.
- Consider adding a short section or note confirming cross-platform compatibility, especially for Linux users.
- Where relevant, provide example terminal commands using both Windows and Linux conventions (e.g., path separators, environment variable syntax) if differences exist.
Communication Services
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 maintains cross-platform parity, but in the environment variable setup section, 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
- Rotate or randomize the order of OS-specific tabs (Windows, macOS, Linux) to avoid always listing Windows first.
- Explicitly state that all examples are cross-platform unless otherwise noted.
- Ensure that Linux and macOS instructions are as detailed and visible as Windows instructions.
- Consider grouping macOS and Linux together as 'Unix-like' systems where appropriate to reduce repetition and highlight parity.