Communication Services
2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
367 issues found
Showing 201-225 of 367 flagged pages
Communication Services
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias by referencing Windows in resource creation links (e.g., '?tabs=windows') and not providing any Linux-specific or cross-platform examples. All instructions are portal-based with no CLI, PowerShell, or Bash examples, but where platform is mentioned, Windows is referenced first or exclusively. There are no explicit Linux or macOS instructions, nor are there any screenshots or guidance for non-Windows users.
Recommendations
- Remove or supplement Windows-specific links (e.g., '?tabs=windows') with Linux/macOS equivalents or a platform selector.
- Add Azure CLI and/or Bash examples for resource creation and management steps, alongside portal instructions.
- Explicitly state that the instructions are platform-agnostic or provide notes for Linux/macOS users where relevant.
- Include screenshots or references that reflect non-Windows environments if applicable.
- Ensure that any referenced tools or commands (e.g., for role assignments or identity management) have cross-platform guidance.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/call-logs-azure-monitor-access.md
...on-services/concepts/call-logs-azure-monitor-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes accessing logs via the Azure Portal web interface, which is platform-agnostic but implicitly Windows-first due to the lack of command-line or automation examples. There are no examples using cross-platform tools (e.g., Azure CLI, Bash, or PowerShell Core), nor are there instructions for accessing logs from Linux environments.
Recommendations
- Add Azure CLI examples for enabling and accessing logs, which work on both Windows and Linux.
- Include sample Bash scripts for downloading logs from the storage account.
- Mention PowerShell Core (cross-platform) if providing PowerShell examples, and ensure parity with Bash/CLI.
- Explicitly state that the Azure Portal can be accessed from any OS, and provide links to CLI documentation for automation scenarios.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/european-union-data-boundary.md
...tion-services/concepts/european-union-data-boundary.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references a resource management link with a query parameter 'tabs=windows', suggesting that Windows is the default or primary platform for examples. There are no explicit Linux or cross-platform examples or instructions, and no mention of Linux tools or parity. This may unintentionally signal that Windows is the preferred or only supported environment.
Recommendations
- Provide equivalent Linux (and macOS, if relevant) examples or instructions alongside Windows examples.
- Ensure that cross-platform instructions are clearly marked and that platform-specific tabs (e.g., 'tabs=windows', 'tabs=linux') are available where applicable.
- Avoid defaulting to Windows in links or code samples; instead, present platform options equally.
- Review linked quickstarts and ensure Linux parity in resource management and CLI instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/email/email-headers.md
...communication-services/concepts/email/email-headers.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only .NET (C#) code examples and instructs users to run the application using the 'dotnet run' command, which is cross-platform but most commonly associated with Windows development. There are no examples or instructions for Linux-specific tools, shell commands, or alternative SDKs (such as Python or Node.js), and no mention of Linux-specific considerations.
Recommendations
- Add examples using other SDKs (e.g., Python, Node.js) that are popular on Linux.
- Include instructions for running the code on Linux (e.g., using bash, mentioning prerequisites for Linux environments).
- Explicitly state that 'dotnet run' works on Linux and macOS, and provide any Linux-specific troubleshooting tips if applicable.
- Consider adding a section or note about using the Azure Communication Services Email API from Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/includes/identifiers/identifiers-net.md
...vices/concepts/includes/identifiers/identifiers-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides C# code samples and references to .NET APIs, which are most commonly used on Windows. There is no mention of Linux-specific tools, patterns, or alternative SDKs, nor are there any examples for Linux environments or cross-platform usage. The documentation implicitly assumes a Windows/.NET development environment and does not address Linux parity.
Recommendations
- Include examples using cross-platform SDKs (e.g., JavaScript/TypeScript, Python) that run natively on Linux.
- Add explicit notes or sections about Linux compatibility and usage, including any required dependencies or setup steps.
- Reference CLI tools (such as Azure CLI) and REST API usage with curl or other Linux-native tools.
- Clarify that the APIs and SDKs are cross-platform where applicable, and provide guidance for Linux developers.
- Provide sample code that can be executed on Linux (e.g., bash scripts, Python, Node.js) alongside C#/.NET examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/enable-closed-captions.md
...on-services/concepts/interop/enable-closed-captions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by listing 'Windows' before other platforms when describing SDK availability and by referencing Teams policies using PowerShell modules without mentioning Linux or cross-platform alternatives. There are no explicit Linux examples or tools mentioned, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- When listing supported platforms (e.g., SDKs), use a neutral or rotating order, or explicitly mention Linux support if available.
- If referencing Teams policies via PowerShell modules, also mention or link to cross-platform management options (such as Microsoft Graph API or Teams Admin Center web UI), and clarify if PowerShell is required or if alternatives exist.
- Include explicit Linux support statements or examples where relevant, especially for SDK usage or policy management.
- Review the documentation for any implicit assumptions of a Windows environment and add clarifications or alternatives for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/guest/monitor-logs-metrics.md
...ervices/concepts/interop/guest/monitor-logs-metrics.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references Microsoft Teams Admin Center and Teams Call Quality Dashboard as primary tools for log review, which are web-based but are typically associated with Windows-centric administration workflows. There are no explicit examples or instructions for accessing logs or metrics via Linux tools, command-line interfaces, or cross-platform methods. No PowerShell commands are given, but the absence of Linux-specific guidance or CLI/API usage suggests a Windows bias.
Recommendations
- Include examples or instructions for accessing Azure logs and metrics using cross-platform tools such as Azure CLI or REST APIs.
- Mention and provide examples for Linux users on how to retrieve and analyze logs, e.g., using az command-line tool or curl.
- Clarify whether the Teams Admin Center and Call Quality Dashboard are accessible and fully functional from non-Windows platforms.
- Add references to documentation or tools that are platform-agnostic for log analysis.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams administration and provisioning processes that are typically performed using Windows-centric tools (e.g., cmdlets, Teams Admin roles) without providing equivalent Linux or cross-platform examples. There is no mention of Linux-compatible tools, CLI alternatives, or guidance for non-Windows environments, and all procedural descriptions assume the use of Microsoft-centric (often Windows-based) administration interfaces.
Recommendations
- Include examples using cross-platform tools such as Azure CLI, Microsoft Graph API via curl or other Linux-friendly methods, and PowerShell Core (pwsh) where applicable.
- Explicitly mention whether provisioning and authorization steps can be performed from Linux or macOS environments, and provide instructions for those platforms.
- Add sample commands or scripts for Linux environments, such as bash scripts or REST API calls using curl.
- Clarify any platform dependencies for Teams administration tasks and suggest alternatives for non-Windows users.
- Ensure that all referenced tools and processes are accessible from Linux and document any limitations or required workarounds.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/interop/virtual-visits/govern-meeting-experience.md
...ts/interop/virtual-visits/govern-meeting-experience.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Microsoft 365 and Teams administrative tools, which are typically managed via Windows-centric interfaces (such as Teams Admin Center, PowerShell, or Microsoft 365 portal). There are no explicit examples or instructions for Linux users, nor is there mention of cross-platform command-line tools or APIs that could be used from Linux environments. The documentation implicitly assumes a Windows administrative environment.
Recommendations
- Include explicit instructions or references for managing Teams policies and meeting options via cross-platform tools such as the Microsoft Graph API, which can be accessed from Linux.
- If PowerShell is required, mention PowerShell Core (pwsh), which is available on Linux, and provide examples for installing and using it.
- Clarify whether administrative tasks can be performed via web interfaces accessible from Linux browsers, and note any limitations.
- Add Linux-specific notes or examples where relevant, especially for automation or scripting tasks.
- Where possible, provide REST API examples (e.g., using curl or HTTP requests) for policy and meeting management.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is generally cross-platform and Android-focused, but there are subtle Windows biases. Some mitigation steps reference 'device manager' for enabling microphones, which is a Windows-specific tool, without mentioning Linux or macOS equivalents. There are no explicit Linux examples or references to Linux-specific tools or workflows, and the only platform-specific guidance is for Windows and macOS.
Recommendations
- When referencing device management (e.g., enabling microphones), include Linux equivalents such as using 'alsamixer', 'pavucontrol', or relevant system settings.
- Provide parity in troubleshooting steps for Linux (and other platforms) wherever Windows or macOS tools are mentioned.
- Explicitly state if a diagnostic or mitigation step is platform-specific, and offer alternatives for other platforms.
- Consider adding a table or section summarizing how to perform common device management tasks (e.g., enabling/disabling microphones or cameras) on Windows, Linux, and macOS.
- Review all mitigation steps for implicit platform assumptions and generalize or diversify instructions to cover Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/sdk-options.md
...rticles/communication-services/concepts/sdk-options.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows a moderate Windows bias, primarily in the SDK platform support section. Windows platforms and tools (.NET, UWP, WinUI3) are described in greater detail and listed before Linux and macOS equivalents. There is a lack of parity in platform-specific guidance, with Windows-specific deployment and support notes (e.g., unpackaged app not supported) and more granular versioning for Windows. No explicit Linux or macOS examples, troubleshooting, or deployment notes are provided. However, the SDKs themselves are cross-platform and Linux is mentioned as supported for .NET Standard 2.0.
Recommendations
- Add explicit Linux and macOS platform support tables and troubleshooting sections, similar to the detailed Windows/.NET support section.
- Provide Linux/macOS-specific deployment notes, including known issues, best practices, and supported distributions/versions.
- Ensure that any Windows-specific limitations (e.g., unpackaged app support) are matched with equivalent notes for Linux/macOS where relevant.
- Include Linux/macOS examples or references in sections discussing SDK usage, especially where OS-specific behavior or setup may differ.
- Consider listing cross-platform support (Linux, macOS, Windows) together, or in alphabetical order, rather than Windows-first.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/about-call-types.md
...vices/concepts/voice-video-calling/about-call-types.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias in the 'Video quality' section, where Windows is listed as a first-class platform alongside WebJS, iOS, and Android, and is the only desktop OS called out. No Linux desktop support or examples are mentioned, and there is no indication of parity for Linux users. There are no explicit PowerShell or Windows command-line examples, but the omission of Linux as a supported platform or in examples suggests a bias toward Windows environments.
Recommendations
- Explicitly mention Linux support (or lack thereof) in the 'Video quality' table and other relevant sections.
- If Linux is supported, add a column for Linux in the video quality table and provide details.
- If Linux is not supported, clarify this in the documentation to set user expectations.
- Include examples or guidance for Linux users where appropriate, or reference cross-platform SDK usage.
- Review all sections to ensure Linux is considered alongside Windows, especially in platform capability tables.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/concepts/voice-video-calling/network-requirements.md
...s/concepts/voice-video-calling/network-requirements.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a mild Windows bias by listing 'native Windows, Android, and iOS SDKs' bandwidth requirements, but does not mention Linux as a supported native platform or provide Linux-specific guidance. There are no explicit Linux examples, tools, or troubleshooting steps, and Windows is mentioned before other platforms. No PowerShell or Windows-only tools are referenced, but Linux is notably absent from native SDK and optimization discussions.
Recommendations
- Explicitly state Linux support status for native SDKs. If Linux is supported, add Linux to the bandwidth requirements table and provide relevant guidance.
- Include Linux-specific examples or troubleshooting steps where appropriate, especially in sections discussing firewall configuration, NAT, and VPN.
- When listing platforms (e.g., 'native Windows, Android, and iOS SDKs'), use a more inclusive order or clarify why Linux is omitted.
- Reference common Linux tools (e.g., iptables, nftables, systemd-resolved) alongside Windows equivalents in network and firewall configuration sections.
- Provide parity in optimization guidance, such as mentioning Linux VPN clients and Linux QoS configuration tools.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-csharp.md
...tomation/includes/audio-streaming-quickstart-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily by referencing Windows-first resources (e.g., the 'Create an Azure Communication Services resource' link uses '?tabs=windows') and by omitting explicit Linux examples or instructions. All code samples are in C# (cross-platform), but there are no Linux-specific setup steps, troubleshooting notes, or parity in referenced documentation. The only external WebSocket documentation linked is Windows-focused.
Recommendations
- Provide Linux-specific instructions or examples, especially for setting up the WebSocket server and installing dependencies.
- Update prerequisite links to include Linux tabs or provide parity for Linux and macOS users.
- Reference cross-platform or Linux-focused WebSocket documentation in addition to (or instead of) Windows-specific resources.
- Add troubleshooting notes or tips relevant to Linux environments (e.g., common firewall, permissions, or .NET runtime issues).
- Explicitly state that the C# code samples are cross-platform and note any OS-specific considerations.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific resources first and omitting Linux-specific instructions or examples. In the prerequisites, the link to creating an Azure Communication Services resource uses a Windows tab by default, and there is no mention of Linux or cross-platform setup. Additionally, the WebSocket documentation link points to a Windows Azure Web Sites blog post, with no Linux equivalent or general guidance. All code examples are platform-neutral (JavaScript), but supporting instructions and references are Windows-centric.
Recommendations
- Provide Linux-specific or cross-platform instructions and links in the prerequisites, such as a Linux tab for resource creation.
- Include documentation or blog links for setting up WebSocket servers on Linux (e.g., using Node.js on Ubuntu or other distributions).
- Ensure all referenced guides and quickstarts have parity between Windows and Linux, or explicitly mention cross-platform compatibility.
- Add a note clarifying that all JavaScript examples are platform-independent and can be run on both Windows and Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-csharp.md
...ll-automation/includes/play-audio-quickstart-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a subtle Windows bias. In the prerequisites, links and instructions reference Windows first (e.g., resource creation link uses '?tabs=windows'), and there are no explicit Linux-specific instructions or examples. All command-line and SDK usage examples are OS-agnostic, but there are no Linux shell or cross-platform environment setup examples. No mention is made of Linux-specific considerations, tools, or troubleshooting.
Recommendations
- Provide explicit Linux (and macOS) instructions or tabs alongside Windows for resource creation and environment setup.
- Ensure all links that use '?tabs=windows' also have Linux and macOS equivalents, or clarify that instructions are cross-platform.
- Add notes or sections on using the .NET SDK and NuGet on Linux (e.g., using dotnet CLI on Ubuntu, installing dependencies).
- Include troubleshooting tips or common issues for Linux users, if any.
- Review all examples and ensure that none assume a Windows environment (e.g., file paths, shell commands).
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, particularly in the prerequisites section where links and instructions reference Windows tabs and do not provide explicit Linux equivalents. There are no Linux-specific examples or guidance, and the only command-line example is generic (dotnet), but the resource creation links default to Windows. No mention is made of Linux-specific considerations, tools, or troubleshooting.
Recommendations
- Provide explicit Linux instructions and examples alongside Windows, especially for resource creation and setup steps.
- Ensure that documentation links (such as quickstarts) include tabs or pivots for Linux and macOS, not just Windows.
- Mention any Linux-specific requirements or troubleshooting tips, such as installing .NET on Linux, using bash/zsh, or file path conventions.
- Where possible, include screenshots or terminal output from Linux environments to demonstrate parity.
- Review and update all references to ensure that Linux users are equally supported and not required to adapt Windows-centric instructions.
Communication Services
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites section, where links and instructions reference Windows first (e.g., resource creation links with '?tabs=windows' and no mention of Linux/Mac equivalents). There are no explicit Linux-specific instructions or examples, and the documentation does not clarify cross-platform compatibility for commands or tools. However, the main code and build instructions (Java, Maven) are inherently cross-platform.
Recommendations
- Update prerequisite links to include or reference Linux/Mac instructions or ensure the default is platform-neutral.
- Explicitly state that all command-line and Maven instructions are cross-platform, and provide examples of running them on Linux/Mac terminals if any differences exist.
- Where links use '?tabs=windows', either add or point to Linux/Mac tabs, or clarify that the instructions are the same for all platforms.
- Add a note in the prerequisites or setup section confirming support for Linux/Mac and any platform-specific requirements or caveats.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the prerequisites section, where links and instructions reference Windows first (e.g., resource creation links with '?tabs=windows'), and there are no explicit Linux-specific instructions or examples. All command-line and code examples are platform-agnostic (using 'dotnet'), but there is no mention of Linux-specific considerations, nor are there any Linux/macOS terminal screenshots or package manager alternatives. The documentation assumes familiarity with .NET and NuGet, which are cross-platform, but does not provide parity in guidance for Linux users.
Recommendations
- Provide explicit instructions or links for Linux users in the prerequisites, such as resource creation guides with Linux tabs or pivots.
- Include Linux/macOS terminal screenshots or clarify that all 'dotnet' commands work identically on Linux and macOS.
- Mention any Linux-specific dependencies or troubleshooting steps, if applicable.
- Ensure that all links (such as resource creation) default to a neutral or platform-agnostic view, or provide clear tabs for both Windows and Linux.
- If there are any platform-specific behaviors or requirements (e.g., for installing .NET or NuGet), reference official Linux installation guides.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/recognize-ai-action-how-to-csharp.md
...tomation/includes/recognize-ai-action-how-to-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a Windows bias by referencing Windows first in resource creation links (e.g., 'tabs=windows' in quickstart URLs) and does not provide any Linux-specific instructions or examples. All command-line and SDK usage examples are platform-agnostic (using dotnet CLI and C#), but there are no explicit Linux or macOS instructions, troubleshooting notes, or parity checks. The documentation assumes familiarity with Windows-centric patterns and omits Linux equivalents or considerations.
Recommendations
- Update quickstart/resource creation links to include Linux/macOS tabs or clarify that the instructions apply to all platforms.
- Explicitly mention that the dotnet CLI commands work on Linux/macOS and provide any platform-specific prerequisites (e.g., installing .NET SDK on Linux).
- Add troubleshooting notes or environment setup instructions for Linux (e.g., file path formats, permissions, or common issues).
- Ensure that all referenced guides and pivots include Linux/macOS options, not just Windows.
- Consider including a short section or callout for Linux/macOS users to highlight any differences or confirm parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/includes/secure-webhook-endpoint-csharp.md
...-automation/includes/secure-webhook-endpoint-csharp.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides only C#/.NET examples and references to NuGet packages, which are primarily associated with Windows development environments. There are no examples or guidance for validating JWTs in webhook callbacks using Linux-centric tools, languages, or frameworks (e.g., Python, Node.js, Java, or command-line utilities commonly used on Linux).
Recommendations
- Add equivalent JWT validation examples using popular Linux-friendly languages and frameworks such as Python (with PyJWT), Node.js, or Java.
- Mention cross-platform package managers and libraries, not just NuGet.
- Clarify that the JWT validation process is platform-agnostic and provide links or references to Linux/open-source tool documentation.
- If possible, provide command-line or script-based validation examples (e.g., using curl and jq) to demonstrate platform neutrality.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/call-automation/record-every-call.md
...-services/how-tos/call-automation/record-every-call.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a Windows-first bias by linking to Windows-specific Azure CLI installation instructions and not providing explicit Linux/macOS equivalents. All setup and CLI instructions assume parity but do not clarify or provide Linux-specific guidance, which may confuse or hinder Linux users.
Recommendations
- Provide installation links for Azure CLI for all major platforms (Windows, Linux, macOS) in the prerequisites section.
- Explicitly mention that Visual Studio Code and ngrok are cross-platform, and provide any Linux/macOS-specific notes if needed.
- Where commands or tools differ between platforms (e.g., Azure CLI installation, environment variable handling), include platform-specific tabs or notes.
- Review all links and ensure they do not default to Windows-specific documentation unless appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/capabilities/capabilities-android.md
...ling-sdk/includes/capabilities/capabilities-android.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page introduces the capabilities feature for the Azure Communication Services Call API and explicitly states usage 'for Windows' before providing code examples. There are no references to Linux, macOS, or cross-platform usage, nor are there examples or instructions for non-Windows environments. The language and structure suggest a Windows-centric approach, with no parity for Linux users.
Recommendations
- Remove or rephrase 'for Windows' unless the feature is truly Windows-exclusive. If cross-platform, clarify applicability.
- Add explicit examples or instructions for Linux (and macOS, if supported), including any platform-specific setup or code differences.
- Mention platform compatibility in the introduction, and provide guidance for users on non-Windows systems.
- If there are platform-specific limitations, document them clearly and provide alternative approaches or workarounds for Linux.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation explicitly refers to using the capabilities feature 'for Windows' and does not mention Linux or provide Linux-specific examples or guidance. All code examples are platform-neutral (Swift), but the introductory text and context focus solely on Windows, omitting Linux parity.
Recommendations
- Clarify whether the feature is available on Linux and, if so, provide equivalent instructions or examples for Linux.
- Avoid phrasing such as 'for Windows' unless the feature is truly Windows-exclusive; otherwise, use platform-neutral language.
- If the feature is not supported on Linux, explicitly state this to inform users.
- If Linux is supported, add a section or examples demonstrating usage or any platform-specific considerations for Linux.
Communication Services
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias, particularly in the prerequisites section, where links and instructions reference Windows-specific tabs or pivots (e.g., '?tabs=windows') without mention of Linux or cross-platform alternatives. There are no explicit Linux examples or guidance for Linux users, and no mention of Linux-specific tools or considerations, despite the cross-platform nature of Azure Communication Services.
Recommendations
- Update prerequisite links to include Linux (and macOS) tabs or pivots, or provide platform-agnostic instructions where possible.
- Explicitly mention that the SDK and features are cross-platform, and provide confirmation or examples for Linux environments if supported.
- Ensure that all quickstart and resource creation guides referenced are available and linked for Linux users.
- Review and update any referenced documentation to ensure Linux parity in setup and usage instructions.