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 501-525 of 656 flagged pages
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/hmac-header-csharp.md ...tion-services/tutorials/includes/hmac-header-csharp.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by listing Windows tools (cmd, PowerShell) before Bash when describing how to run commands, and by recommending Visual Studio as the IDE without mentioning Linux alternatives. There are no Linux-specific instructions or examples, and the prerequisites and setup steps assume a Windows-centric development environment.
Recommendations
  • List Bash first or equally alongside cmd and PowerShell when describing console usage.
  • Mention cross-platform IDEs such as VS Code or JetBrains Rider as alternatives to Visual Studio.
  • Include explicit instructions for installing .NET SDK and running commands on Linux (e.g., using apt-get, yum, or snap).
  • Add notes about running the sample code on macOS and Linux, including any platform-specific considerations.
  • Clarify that the instructions are cross-platform and provide links to .NET documentation for Linux/macOS environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/contact-center.md ...les/communication-services/tutorials/contact-center.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in its example links and tab defaults. References to quickstarts and tutorials consistently use 'windows' or 'uwp' tabs, and there are no explicit Linux or cross-platform examples provided. The documentation does not mention Linux tools, patterns, or provide parity for Linux developers, focusing instead on Microsoft-centric technologies and workflows.
Recommendations
  • Add explicit Linux examples and tabs to quickstart links, ensuring parity with Windows instructions.
  • Include references to Linux-compatible SDKs, tools, and deployment patterns where applicable.
  • Provide cross-platform guidance for setting up and running Azure Communication Services, including CLI and scripting examples for Linux environments.
  • Ensure that documentation tables and code samples do not default to Windows or UWP, but offer equal visibility to Linux and web platforms.
  • Mention any platform-specific limitations or requirements for Linux users to avoid confusion.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/chat-hero-sample.md ...les/communication-services/samples/chat-hero-sample.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Windows-specific terminals (PowerShell, Windows Terminal, Command Prompt) first and exclusively in the instructions for opening a terminal to clone the repository. There is no explicit mention of Linux or macOS equivalents (such as Bash, Terminal, or iTerm), nor are there any Linux-specific setup notes or examples. The instructions and tooling references assume a Windows environment, which may confuse or exclude Linux users.
Recommendations
  • Explicitly mention Linux and macOS terminal options (e.g., Bash, Terminal, iTerm) alongside Windows terminals.
  • Add a note clarifying that all commands (git, npm, Azure CLI) work on Linux and macOS, and provide any OS-specific caveats if necessary.
  • Include Linux/macOS-specific instructions or screenshots where relevant, especially for file paths and environment setup.
  • Use neutral language such as 'Open a terminal (PowerShell, Command Prompt, Bash, Terminal, etc.)' instead of listing only Windows tools.
  • Ensure that prerequisites and steps do not assume Windows-only tooling or patterns.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page does not provide explicit Windows or PowerShell command-line examples, nor does it mention Windows-specific tools. However, there is a subtle 'windows_first' bias in the sense that the only SDK code examples provided are for C# (.NET) and JavaScript, with C# (a language most strongly associated with Windows development) presented first. There are no Linux-specific or cross-platform command-line examples (such as Bash, curl, or Python), and the SDK parity table shows Python and Java SDKs as 'coming soon' without offering alternative guidance for Linux users. The provisioning and operational instructions are entirely portal- and SDK-based, with no mention of CLI or automation approaches that are common in Linux environments.
Recommendations
  • Add Linux-friendly command-line examples (e.g., using curl or Bash) for sending SMS via the API, especially in the 'SMS SDK Tutorial' section.
  • Provide Python SDK examples as soon as the SDK is available, and consider including sample code for other cross-platform languages (e.g., Java, Go).
  • Mention and provide Azure CLI or REST API instructions for provisioning and sending messages, as these are commonly used in Linux and automation scenarios.
  • Explicitly state that all features are available cross-platform and clarify any platform-specific requirements or limitations.
  • Ensure that future updates include parity in documentation and examples for both Windows and Linux development environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/events-playbook.md ...es/communication-services/tutorials/events-playbook.md
Medium Priority View Details →
Scanned: 2025-08-24 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently refers to the 'Teams Client (Web or Desktop)' without specifying OS, but elsewhere, when referencing Azure Communication Services quickstarts and resource creation, the documentation uses tabs or pivots defaulting to 'windows' (e.g., '?tabs=windows'). There are no explicit Linux or cross-platform CLI examples, and no mention of Linux-specific tools or instructions. This may create the impression that Windows is the primary or only supported environment, and Linux users may not find clear guidance.
Recommendations
  • Ensure that all quickstart and resource creation links use neutral or cross-platform pivots/tabs (e.g., avoid '?tabs=windows' unless also providing '?tabs=linux' or '?tabs=mac').
  • Explicitly mention that Teams clients and Azure Communication Services SDKs are cross-platform where applicable, and provide installation or usage instructions for Linux and macOS alongside Windows.
  • Add Linux-specific examples or command-line instructions (e.g., using Bash, curl, or Azure CLI on Linux) where setup or configuration steps are described.
  • Where UI or SDK pivots are shown, ensure Linux and macOS are first-class citizens in the documentation, not just Windows.
  • Review all referenced quickstarts and ensure parity of examples and screenshots for Linux environments.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/trusted-service-js.md ...tion-services/tutorials/includes/trusted-service-js.md
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references Visual Studio Code and Azure Functions workflows, which are cross-platform, but all instructions and linked quickstarts are tailored to Visual Studio Code usage patterns. There is no mention of Linux-specific command-line workflows, nor are there examples for running or deploying the function outside of Visual Studio Code. The documentation implicitly assumes the user is using Visual Studio Code, which, while available on Linux, is not the default editor for many Linux users. There is also no mention of alternative editors, terminal-based workflows, or Linux-specific deployment/testing instructions.
Recommendations
  • Add explicit instructions for setting up and running the function using command-line tools (e.g., Azure Functions Core Tools, npm, and the Azure CLI) on Linux.
  • Include examples for deploying and running the function using only the terminal, without relying on Visual Studio Code.
  • Mention and provide links to Linux-specific documentation or quickstarts for Azure Functions.
  • Clarify that Visual Studio Code is optional and that all steps can be performed on Linux using alternative editors and terminal commands.
  • Provide troubleshooting tips or notes for common Linux environments (e.g., Ubuntu, Fedora) where paths, permissions, or dependencies may differ.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-08-21 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of Azure Portal screenshots and step-by-step instructions, which implicitly assume a graphical, Windows-centric workflow. All code examples are provided only for C# (.NET) and JavaScript SDKs, with no CLI, Bash, or Linux-native tooling shown. There are no references to Linux command-line tools, nor are there instructions for provisioning or sending SMS via cross-platform or Linux-friendly methods (such as Azure CLI, REST API via curl, or PowerShell alternatives for Linux). The developer experience and tutorials focus on GUI and SDKs typical for Windows environments, omitting Linux-specific guidance.
Recommendations
  • Add examples using Azure CLI and REST API (e.g., curl) for provisioning and sending SMS, which are platform-agnostic and widely used on Linux.
  • Include screenshots or instructions for accessing Messaging Connect via the Azure Portal on Linux (e.g., using a browser on Ubuntu) or mention that the portal is accessible from any OS.
  • Provide Bash and PowerShell (cross-platform) scripts for common tasks, such as authentication and sending SMS, to ensure parity for Linux users.
  • Explicitly state that all features and workflows are supported on Linux and macOS, not just Windows, and link to relevant cross-platform SDK documentation.
  • Add troubleshooting and setup notes for Linux environments, such as installing SDKs or dependencies on Ubuntu, Fedora, etc.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md ...s/concepts/voice-video-calling/calling-sdk-features.md
Medium Priority View Details →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by listing Windows as a primary supported platform (with a dedicated .NET SDK), while Linux is only mentioned in the context of browser support for the JavaScript SDK. There are no Linux-native SDKs, tools, or examples provided, and Linux is not included as a first-class platform in feature tables or SDK links. Linux users are limited to using the web SDK in supported browsers, with no mention of parity for native development or guidance for Linux environments.
Recommendations
  • Explicitly mention Linux support (or lack thereof) in the SDK links and feature tables, clarifying options for Linux developers.
  • If native Linux SDKs are unavailable, provide guidance or workarounds for Linux users (e.g., using the Web SDK in Electron or other cross-platform frameworks).
  • Add Linux-specific examples or notes where relevant, especially in sections discussing platform support, installation, and development environments.
  • Ensure that Linux is not only mentioned as a secondary browser platform but is considered in parity with Windows and macOS in all relevant documentation tables and sections.
  • If Windows-specific features exist, clearly document their absence or alternatives for Linux.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/event-grid/view-events-request-bin.md ...services/how-tos/event-grid/view-events-request-bin.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to the Windows-specific Azure CLI installation instructions in both the pre-requisites and configuration steps, without mentioning or linking to Linux or macOS equivalents. There are no Linux-specific examples or guidance, and the documentation does not acknowledge cross-platform usage for the Azure CLI.
Recommendations
  • Provide links to Azure CLI installation instructions for Linux and macOS alongside the Windows link, or use a generic cross-platform link.
  • Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS.
  • Include a note or section about verifying Azure CLI installation on Linux/macOS.
  • Ensure screenshots and instructions are not Windows-specific, or provide Linux/macOS alternatives where relevant.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/video-calling/video-calling-javascript.md ...ing/includes/video-calling/video-calling-javascript.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation exhibits a mild Windows bias in the prerequisites section, where the Node.js installation is suggested via the MSI installer (a Windows-specific method), and the link to creating a Communication Services resource uses a 'platform-azp' pivot with a 'windows' tab by default. However, the rest of the guide uses cross-platform tools (Node.js, npm, Azure CLI) and generic terminal commands, making it largely platform-agnostic.
Recommendations
  • In the prerequisites, mention cross-platform installation methods for Node.js (e.g., using package managers like apt, yum, brew, or direct downloads for macOS/Linux) alongside the MSI installer.
  • Ensure that links to Azure portal/resource creation do not default to Windows-specific pivots or tabs; provide clear parity for Linux and macOS users.
  • Explicitly state that all terminal/console commands work on Windows, Linux, and macOS, and clarify any platform-specific differences if they exist.
  • Wherever a tool or pattern is mentioned (such as 'command window'), use neutral terms like 'terminal' or 'command-line interface'.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/includes/user-facing-diagnostics-android.md ...eo-calling/includes/user-facing-diagnostics-android.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally platform-neutral and focused on Android, but there is a notable Windows bias in the mitigation steps for the 'noMicrophoneDevicesAvailable' diagnostic, which references enabling a microphone from the 'device manager'—a Windows-specific tool. There are no Linux-specific tools, commands, or mitigation steps mentioned, and no Linux examples are provided for device troubleshooting.
Recommendations
  • When referencing device troubleshooting steps, provide Linux equivalents alongside Windows instructions. For example, suggest checking microphone availability using 'arecord -l' or verifying permissions in ALSA/PulseAudio on Linux.
  • Avoid referencing Windows-specific tools (like 'device manager') without mentioning alternatives for other platforms.
  • Include links or brief instructions for common Linux desktop environments (e.g., GNOME, KDE) on how to enable or troubleshoot audio devices.
  • Where possible, use platform-agnostic language or provide parallel steps for Windows, Linux, and macOS.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-provisioning.md .../interop/tpe/teams-phone-extensibility-provisioning.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page describes Teams Phone extensibility provisioning and authorization but implicitly assumes a Windows-centric environment. It references 'cmdlet' usage for provisioning, which is typically associated with PowerShell on Windows, and does not provide equivalent Linux or cross-platform command-line examples. There are no explicit Linux or macOS instructions, nor are cross-platform tools or patterns mentioned.
Recommendations
  • Provide cross-platform command-line examples, such as using Azure CLI or Microsoft Graph API via curl or other REST tools, alongside any PowerShell/cmdlet instructions.
  • Clarify whether the provisioning steps (e.g., cmdlet usage) can be performed on Linux/macOS, and if so, provide the necessary commands or scripts.
  • Explicitly mention any platform dependencies or prerequisites, and offer alternatives for non-Windows environments.
  • Include notes or links to documentation for cross-platform tools (e.g., Azure CLI, Microsoft Graph API) where appropriate.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-ios.md .../calling-sdk/includes/capabilities/capabilities-ios.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation refers specifically to 'Windows' in the introductory sentence for using the capabilities call feature, but all code examples are in Swift (suggesting iOS/macOS context), and there are no Linux-specific instructions or examples. There is no mention of Linux or its equivalents, nor any cross-platform guidance.
Recommendations
  • Remove or clarify the 'for Windows' phrasing if the feature is not Windows-specific, or provide equivalent instructions/examples for Linux.
  • Add explicit Linux (and macOS, if relevant) usage notes or examples, especially if the SDK is cross-platform.
  • Ensure introductory and instructional text is platform-neutral unless a feature is truly platform-specific.
  • If the feature is not available on Linux, state this explicitly to avoid confusion.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-js.md ...l-automation/includes/audio-streaming-quickstart-js.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation exhibits a subtle Windows bias by referencing Windows-specific resources and presenting Windows as the default environment. For example, the link to creating an Azure Communication Services resource includes a '?tabs=windows' parameter, and the documentation for WebSockets refers to a Windows Azure Web Sites blog post. There are no explicit Linux or cross-platform instructions or examples, and Windows is implied as the primary platform.
Recommendations
  • Provide explicit Linux and macOS instructions or links alongside Windows-specific ones, especially in setup and resource creation steps.
  • Replace or supplement Windows-specific documentation links (such as the WebSockets on Windows Azure Web Sites blog) with cross-platform or Linux-focused resources.
  • Ensure that all code samples and setup instructions are clearly cross-platform, and mention any platform-specific considerations if they exist.
  • Use neutral language and tabs or pivots to allow users to select their operating system, rather than defaulting to Windows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-action-quickstart-csharp.md ...omation/includes/recognize-action-quickstart-csharp.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to resource creation instructions with a Windows-specific tab and parameter (e.g., '?tabs=windows'), and does not provide any explicit Linux or cross-platform examples for setup or usage. While the .NET SDK is cross-platform, the documentation does not clarify or illustrate usage on Linux or macOS, nor does it mention or show Linux-specific commands, tools, or environment considerations.
Recommendations
  • Ensure all links to Azure resource creation or setup guides default to a neutral or cross-platform tab, or explicitly mention both Windows and Linux options.
  • Add explicit instructions or notes for Linux users, such as confirming that the dotnet CLI commands work identically on Linux/macOS and providing any relevant prerequisites (e.g., installing .NET on Ubuntu).
  • Where possible, include example terminal commands or environment setup steps for Linux (e.g., using bash instead of PowerShell, if relevant).
  • Clarify in the prerequisites and setup sections that the SDK and instructions are cross-platform, and provide links to platform-specific installation guides for .NET.
  • Audit all quickstart and reference links to ensure Linux parity and avoid defaulting to Windows-specific documentation.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-java.md ...automation/includes/recognize-ai-action-how-to-java.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias, particularly in the prerequisites section where links and instructions default to Windows (e.g., resource creation link with '?tabs=windows'). There are no explicit Linux or cross-platform instructions or examples, and no mention of Linux-specific considerations, despite the Java/Maven workflow being inherently cross-platform. This may leave Linux users uncertain about parity or specific steps.
Recommendations
  • Update prerequisite links to use neutral or cross-platform tabs, or provide both Windows and Linux (and macOS, if relevant) options.
  • Explicitly state that all Java/Maven commands are cross-platform and can be run on Linux, macOS, or Windows.
  • If any platform-specific steps exist (e.g., file paths, environment variables), provide Linux/macOS equivalents alongside Windows instructions.
  • Include a note or section confirming Linux support and mentioning any known differences or additional requirements for Linux users.
  • Avoid using Windows-specific query parameters (like '?tabs=windows') in documentation links unless also providing Linux/macOS alternatives.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/reactions.md ...ommunication-services/how-tos/calling-sdk/reactions.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page demonstrates a subtle Windows bias by only listing 'Windows' as a supported platform in the SDKs table, without mentioning Linux or macOS. There are no code examples, but the absence of Linux (or cross-platform) support information and the explicit mention of Windows may give the impression that Linux is unsupported or less important.
Recommendations
  • Explicitly mention Linux and macOS support (or lack thereof) in the SDKs/platforms table to clarify parity.
  • If Linux is supported, add Linux-specific instructions, examples, or notes alongside Windows.
  • If Linux is not supported, state this clearly to avoid ambiguity.
  • Ensure future documentation includes cross-platform considerations and does not default to Windows-only references.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-with-ai-csharp.md .../call-automation/includes/play-audio-with-ai-csharp.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows a mild Windows bias. In the prerequisites, links and instructions reference Windows first (e.g., resource creation link includes '?tabs=windows'), and there is no mention of Linux-specific instructions or examples. All command-line and code examples are platform-neutral, but there are no explicit Linux or cross-platform instructions, and no mention of Linux package managers or shell environments.
Recommendations
  • Provide Linux-specific instructions or ensure parity in quickstart/resource creation links (e.g., include tabs for Linux/macOS).
  • Explicitly mention that the dotnet CLI and SDK are cross-platform, and provide example commands for Linux/macOS if any differences exist.
  • If there are platform-specific steps (such as setting environment variables, file paths, or installing dependencies), include Linux/macOS equivalents alongside Windows.
  • Avoid using Windows-specific query parameters (like '?tabs=windows') in documentation links unless also providing Linux/macOS options.
  • Consider adding a section or note clarifying cross-platform compatibility and any known differences in behavior or setup.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/templates/template-messages-quick-reference-net.md ...des/templates/template-messages-quick-reference-net.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows development environments and tools. All code examples and setup instructions are focused exclusively on .NET and C#, with no mention of Linux-specific instructions, shell commands, or alternative SDKs (such as Python, Java, or Node.js). The 'Run the code' section provides build/run instructions for .NET CLI, Visual Studio, and Visual Studio Code, but omits any Linux-specific guidance or examples (e.g., bash shell, Linux package dependencies, or cross-platform considerations). Visual Studio, a Windows-centric IDE, is mentioned before Visual Studio Code, which is more cross-platform.
Recommendations
  • Add explicit instructions and examples for Linux users, such as installing .NET SDK on Linux, using bash/zsh shell commands, and troubleshooting common Linux-specific issues.
  • Include alternative code samples or references for other supported SDKs (e.g., Python, Java, Node.js) to broaden platform inclusivity.
  • When listing development tools, mention cross-platform editors (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio), and clarify which instructions apply to which OS.
  • Provide guidance on running the code in Linux terminal environments, including any required dependencies or environment variables.
  • Where screenshots or UI references are shown (e.g., Azure Portal), clarify if the experience is the same across OSes or note any differences.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-android.md ...ideo-calling/includes/teams-user/teams-user-android.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references enabling Teams Phone features via PowerShell, a Windows-centric tool, and does not provide Linux/macOS alternatives or mention cross-platform management options. No explicit Linux or cross-platform command-line examples are given for Teams user enablement.
Recommendations
  • When referencing enabling Teams Phone or Enterprise Voice, provide cross-platform alternatives (e.g., Teams Admin Center web UI) or note if PowerShell is available on Linux/macOS.
  • If PowerShell is required, clarify that PowerShell Core is cross-platform and provide instructions for Linux/macOS users.
  • Add a note or link to documentation for managing Teams users from non-Windows environments.
  • Ensure all prerequisite steps are accessible from Linux/macOS, or clearly state any platform limitations.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-az-cli.md ...kstarts/email/includes/create-email-resource-az-cli.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking only to the Windows installation instructions for Azure CLI in the prerequisites section. There are no Linux or macOS installation links or examples, and no mention of cross-platform usage, even though the Azure CLI is cross-platform. All command-line examples use the Azure CLI, which is platform-agnostic, but the installation guidance is Windows-specific.
Recommendations
  • Provide installation links for Azure CLI on Linux and macOS alongside the Windows link, or use a generic Azure CLI installation page that covers all platforms.
  • Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS.
  • Consider adding a note or section confirming cross-platform compatibility for all commands shown.
  • If platform-specific instructions are necessary, present them in parallel (e.g., tabs for Windows, Linux, macOS) rather than only for Windows.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-android.md ...s/teams-auto-attendant/teams-auto-attendant-android.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing the Teams Admin Center (a web-based tool but often associated with Windows-centric workflows) and omitting any mention of Linux or cross-platform alternatives for Teams administration. There are no examples or instructions for managing Teams Auto Attendants or resource accounts using command-line tools (such as PowerShell or CLI) that could be run on Linux. All setup and configuration steps are described using GUI tools or web portals, which may not be ideal or accessible for Linux users.
Recommendations
  • Include instructions for managing Teams Auto Attendants and resource accounts using cross-platform tools, such as Microsoft Graph API or Azure CLI, which can be used on Linux.
  • Provide PowerShell and CLI script examples for relevant steps, and clarify which steps can be performed from any OS.
  • Explicitly state when a step requires a web portal and confirm its accessibility from all major browsers and platforms.
  • Add notes or links to Linux-friendly tools or documentation for Teams administration tasks.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-video-calling.md .../voice-video-calling/get-started-with-video-calling.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. In the 'Clean up resources' section, the link provided includes a 'tabs=windows' parameter, suggesting that Windows instructions are prioritized or shown by default. There is no explicit mention or example for Linux or macOS in this section, and the documentation references Windows tools/patterns without ensuring Linux parity.
Recommendations
  • Ensure that all referenced links and tabs provide clear options for Linux and macOS, not just Windows.
  • Avoid defaulting to Windows-specific instructions or tabs; use a neutral or platform-agnostic default where possible.
  • Explicitly mention and provide examples for Linux (and macOS) in cleanup and resource management sections.
  • Review included content (e.g., video-calling-javascript.md) to ensure cross-platform parity in all code and command-line examples.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-call-web.md ...uickstarts/rooms/includes/rooms-quickstart-call-web.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing the Microsoft Installer (MSI) for Node.js installation as the only installation method, without mentioning Linux alternatives. No explicit Linux or cross-platform installation instructions or examples are provided. However, the rest of the instructions (npm, webpack, JavaScript code) are platform-agnostic.
Recommendations
  • Provide Linux installation instructions for Node.js, such as using package managers like apt, yum, or snap.
  • Mention that Node.js can be installed on macOS and Linux, and provide links or commands for those platforms.
  • Avoid referencing only Windows-specific installers (like MSI) when discussing prerequisites; instead, offer cross-platform guidance.
  • Explicitly state that the sample and commands work on Windows, Linux, and macOS, and note any platform-specific caveats if they exist.
GitHub Create Pull Request
Communication Services https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/prepend-net.md ...arts/email/send-email-advanced/includes/prepend-net.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias by referencing Windows-centric console environments (cmd, PowerShell) before Bash, and by not providing any Linux- or macOS-specific instructions or examples. All terminal commands are generic and cross-platform, but there is no explicit mention or demonstration of Linux-specific steps, such as environment variable setup or file path conventions. There are no PowerShell-specific commands, but the overall framing assumes familiarity with Windows tools and patterns.
Recommendations
  • Explicitly mention Linux and macOS as supported platforms wherever terminal or console instructions are given.
  • When listing console environments, use neutral or rotated orderings (e.g., 'such as Bash, cmd, or PowerShell') or mention all three equally.
  • Provide Linux/macOS-specific notes for setting environment variables (e.g., 'export VAR=VALUE' for Bash) alongside Windows examples ('set VAR=VALUE' for cmd, '$env:VAR="VALUE"' for PowerShell).
  • Include screenshots or references to Linux/macOS terminal usage where appropriate.
  • Ensure that any file path or editor instructions are platform-neutral or provide alternatives for different OSes.
GitHub Create Pull Request
← Previous Page 21 of 27 Next →