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 301-325 of 656 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-powershell.md
...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and code examples using PowerShell and the Send-MailMessage cmdlet, which are native to Windows. There are no examples or guidance for sending email via SMTP from Linux or cross-platform environments, nor are alternative tools (such as sendmail, mailx, or Python scripts) mentioned. This creates a Windows-centric bias and limits accessibility for users on Linux or macOS.
Recommendations
- Add equivalent SMTP email sending examples for Linux, such as using the 'mail' or 'sendmail' command-line utilities.
- Provide a cross-platform example using a language like Python (e.g., with smtplib), which works on both Windows and Linux.
- Explicitly mention that the provided PowerShell example is Windows-specific, and guide users to alternative tools for other operating systems.
- Include troubleshooting notes or links for common Linux SMTP tools and how to install/configure them.
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-javascript.md
...o-calling/includes/teams-user/teams-user-javascript.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a subtle Windows bias. In the prerequisites, enabling Teams Phone for users references a PowerShell-based process and links to a PowerShell-specific guide, with no mention of Linux or cross-platform alternatives. There are no explicit Linux instructions or examples, and the only referenced tooling for Teams user enablement is Windows-centric. However, the main code and web app instructions are platform-agnostic.
Recommendations
- Provide Linux/macOS alternatives or clarify if the PowerShell steps can be performed using cross-platform PowerShell Core.
- Explicitly mention that the web app and SDK instructions are platform-independent.
- If possible, link to Teams user enablement instructions that are not Windows-specific, or clarify the requirements for Linux users.
- Add a note about how to perform prerequisite steps on non-Windows systems, or state if they must be done from a Windows environment.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/manage-teams-identity.md
...nication-services/quickstarts/manage-teams-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias in several ways: it provides only PowerShell commands for administrative tasks (such as creating a service principal), assumes the use of Windows tools (PowerShell, Install-Module), and does not mention or provide equivalent instructions for Linux or macOS environments. There are no CLI or cross-platform alternatives for key steps, and the troubleshooting guidance is Windows-centric.
Recommendations
- Provide equivalent Azure CLI or Microsoft Graph CLI commands for all PowerShell examples, ensuring Linux and macOS users can follow the same steps.
- Explicitly mention cross-platform alternatives where PowerShell is referenced (e.g., 'You can also use Azure CLI or Microsoft Graph CLI on Linux/macOS').
- Add notes or sections for Linux/macOS users, including installation and usage instructions for required tools.
- Where possible, use platform-agnostic language and avoid assuming the user is on Windows.
- Include troubleshooting steps for non-Windows environments, such as how to install required modules or authenticate using CLI tools on Linux/macOS.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-csharp.md
...cludes/call-recording-samples/call-recording-csharp.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on .NET and C# code samples, which are most commonly associated with Windows development environments. There are no examples or instructions for Linux or cross-platform usage, such as using the Azure Communication Services SDK in other languages (e.g., Python, Java, Node.js) or on non-Windows operating systems. Additionally, the prerequisite to download the .NET SDK and the lack of mention of Linux-specific tools or shell commands further reinforce a Windows-centric bias.
Recommendations
- Provide equivalent code samples in other popular languages supported by Azure Communication Services SDK (e.g., Python, Java, JavaScript/Node.js) to demonstrate cross-platform compatibility.
- Include instructions or notes on how to set up the .NET SDK and run the samples on Linux and macOS, not just Windows.
- Mention and provide examples of using CLI tools (such as Azure CLI) and shell commands that work across platforms, rather than focusing solely on C# and .NET.
- Explicitly state the cross-platform nature of the SDKs and provide troubleshooting or environment setup tips for Linux users.
- If possible, add a section or callout highlighting any platform-specific considerations or differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/includes/telemetry-app-insights-net.md
...ces/quickstarts/includes/telemetry-app-insights-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash, and by not providing any Linux- or macOS-specific instructions or examples. All terminal commands are generic, but there is no explicit mention of Linux or macOS environments beyond the brief mention of Bash. There are no Linux-specific troubleshooting tips, environment variable setup instructions, or editor recommendations, and the documentation implicitly assumes familiarity with Windows patterns.
Recommendations
- Explicitly mention Linux and macOS as supported platforms wherever relevant, not just in passing.
- Provide Linux/macOS-specific instructions for setting environment variables (e.g., export VAR=VALUE) alongside Windows (set VAR=VALUE or $env:VAR=VALUE in PowerShell).
- List Bash (or other Unix shells) first or equally when mentioning console options, e.g., 'in a console window (such as Bash, cmd, or PowerShell)'.
- Include notes on using popular Linux/macOS editors (e.g., nano, vim, VS Code) for editing files, not just generic 'text editor'.
- Add troubleshooting tips or notes for common Linux/macOS issues (e.g., permissions, .NET SDK installation differences).
- Ensure all screenshots, if any, are cross-platform or provide both Windows and Linux/macOS examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/get-started/get-started-unity.md
...ideo-calling/includes/get-started/get-started-unity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by emphasizing Windows-specific tools and workflows, such as recommending the Universal Windows Platform workload for Unity, referencing the Windows tab in Unity Editor, and suggesting the Mixed Reality Feature Tool (a Windows-only tool). There is no mention of Linux or macOS compatibility, nor are alternative instructions or notes provided for non-Windows users. This may hinder Linux developers from following the guide or understanding platform-specific requirements.
Recommendations
- Explicitly state platform compatibility for the SDK and sample (e.g., Windows, Linux, macOS).
- Provide alternative instructions for Linux and macOS users, such as how to install Unity and required workloads on those platforms.
- Replace or supplement references to Windows-only tools (e.g., Mixed Reality Feature Tool) with cross-platform alternatives or clarify their platform limitations.
- Avoid phrases like 'found under the Windows tab' without noting the equivalent on other platforms, or clarify if a feature is Windows-only.
- If certain features are only available on Windows, clearly document this and provide workarounds or alternatives for Linux/macOS where possible.
- Include troubleshooting notes or links for Linux/macOS users, especially for steps that may differ from Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-net.md
...ces/quickstarts/rooms/includes/rooms-quickstart-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions Bash alongside cmd and PowerShell as possible consoles, it consistently uses Windows-centric terminology and tools first (e.g., 'cmd, PowerShell, or Bash'), and all command-line examples use the generic 'dotnet' CLI without clarifying any Linux-specific differences. There are no explicit Linux or macOS-specific instructions, troubleshooting, or environment notes, and no mention of package managers or shell conventions common to Linux users. The documentation assumes parity but does not verify or illustrate it.
Recommendations
- Explicitly state that all commands work on Windows, Linux, and macOS, and provide any OS-specific caveats if they exist.
- When listing console options, rotate or randomize the order (e.g., 'Bash, cmd, or PowerShell') or mention that any terminal is supported.
- Add Linux/macOS-specific notes where appropriate (e.g., file path conventions, permissions, or dependency installation).
- Include at least one example of running commands in a Linux terminal (e.g., screenshots or explicit Bash prompt).
- Mention how to install .NET Core on Linux and macOS, including links to official documentation for those platforms.
- If there are any known differences in behavior or troubleshooting steps for Linux/macOS, document them explicitly.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-javascript.md
...eams-auto-attendant/teams-auto-attendant-javascript.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Teams Admin Center (a web interface but often associated with Windows-centric workflows), providing resource creation links with a 'tabs=windows' parameter, and omitting any explicit Linux-specific instructions or examples. There are no mentions of Linux tools, terminal differences, or alternative admin methods (e.g., CLI, PowerShell vs. Bash). The setup and run instructions use generic commands but do not clarify cross-platform considerations, and all admin steps assume familiarity with Microsoft/Windows-centric environments.
Recommendations
- Provide explicit instructions or notes for Linux users, especially for steps involving resource creation (remove or supplement 'tabs=windows' links with Linux/CLI equivalents).
- Mention and link to cross-platform or Linux-friendly tools (e.g., Azure CLI, Microsoft Graph CLI) for tasks like finding Object IDs, rather than only referencing web portals.
- Clarify that all terminal/console commands are cross-platform, or provide platform-specific notes if there are differences.
- Where possible, include screenshots or examples from Linux environments or clarify that the instructions are not Windows-specific.
- Avoid defaulting to Windows-centric terminology or links; ensure parity in documentation structure and examples for both Windows and Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/references/how-to-collect-browser-verbose-log.md
...lling/references/how-to-collect-browser-verbose-log.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides instructions and command-line examples for collecting verbose logs on Windows, referencing Windows file paths, executables, and omitting any mention of Linux or macOS equivalents. There are no examples or guidance for users on non-Windows platforms.
Recommendations
- Add equivalent instructions and command-line examples for Linux and macOS, including typical executable paths (e.g., /usr/bin/google-chrome, /Applications/Google Chrome.app/Contents/MacOS/Google Chrome).
- Explain where log files are stored on Linux and macOS, and provide example file paths.
- Mention platform-specific differences in launching browsers with command-line arguments.
- Present Windows, Linux, and macOS instructions in parallel sections or tables to ensure parity and clarity for all users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/speaker-issue.md
...ting/voice-video-calling/audio-issues/speaker-issue.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides troubleshooting steps for audio issues but specifically mentions Windows tools (volume mixer, app volume settings) and includes a screenshot of the Windows volume mixer. There are no equivalent instructions or screenshots for Linux or macOS systems, nor are cross-platform differences discussed. This results in a Windows-first bias and a lack of Linux parity.
Recommendations
- Add equivalent troubleshooting steps for Linux (e.g., checking PulseAudio or ALSA mixer settings) and macOS (e.g., Sound preferences, per-app volume controls).
- Include screenshots of audio settings/mixers from Linux desktop environments (such as GNOME, KDE) and macOS alongside the Windows example.
- Explicitly mention that app-specific volume controls and system mixers exist on other platforms, and provide guidance or links for those systems.
- Rephrase instructions to address all major platforms equally, rather than focusing on Windows first.
- Where platform-specific limitations exist (e.g., browser support for output device selection), clarify which platforms are affected.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-android.md
.../includes/teams-call-queue/teams-call-queue-android.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing Microsoft Teams Admin Center, Microsoft Graph Explorer, and other Microsoft-centric tools, all of which are primarily web-based or Windows-oriented. There are no mentions of Linux-compatible alternatives or command-line options for Linux users. Additionally, the documentation assumes familiarity with Microsoft 365 administration patterns, which are more common in Windows environments. No Linux-specific instructions or examples are provided for managing Teams resources or interacting with Graph API.
Recommendations
- Provide CLI-based alternatives (such as using Azure CLI, Microsoft Graph CLI, or curl commands) for steps like retrieving the Call Queue Object ID, so Linux users can follow along without relying on web portals.
- Explicitly mention that the Teams Admin Center and Graph Explorer are web-based and accessible from any OS, but also provide guidance for users who prefer or require command-line tools.
- Include Linux-friendly instructions for all administrative steps, such as using PowerShell Core (which is cross-platform) or bash scripts where applicable.
- Add a section or callout for Linux/macOS users, clarifying any platform-agnostic steps and highlighting any differences or additional requirements.
- Ensure parity in tooling recommendations by listing both Windows and Linux options side-by-side where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/chat-interop/includes/meeting-interop-features-inline-image-receiving-csharp.md
...meeting-interop-features-inline-image-receiving-csharp.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on C# and .NET, which are traditionally Windows-centric technologies. There are no examples or guidance for Linux or cross-platform development environments. The code samples and instructions assume the use of Windows tools and patterns (such as Dispatcher, CoreDispatcherPriority, BitmapImage, and running from an IDE), with no mention of Linux equivalents or how to adapt the tutorial for non-Windows platforms.
Recommendations
- Provide equivalent code samples for Linux environments, such as using .NET Core/5+/6+ on Linux, and clarify any platform-specific dependencies.
- Mention and demonstrate how to run the sample code on Linux (e.g., using VS Code, JetBrains Rider, or command-line dotnet CLI) and not just an IDE typically associated with Windows.
- Replace or supplement Windows-specific UI elements (e.g., BitmapImage, Dispatcher) with cross-platform alternatives or explain how to handle image rendering in Linux-friendly frameworks (such as Avalonia, Gtk#, or MAUI).
- Explicitly state platform requirements and, if possible, provide Docker or container-based instructions for maximum portability.
- Add a note or section on any differences in behavior or setup when running on Linux versus Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/ui-maui.md
...les/communication-services/samples/includes/ui-maui.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows and Mac (Visual Studio) workflows, mentioning Windows-specific tools (GitBash, WSL) for running shell scripts, and omitting explicit instructions or support for running the sample on native Linux environments. There are no Linux-specific setup or run instructions, and the guidance assumes Visual Studio as the primary IDE, which is not natively available on Linux.
Recommendations
- Add explicit instructions for running the sample on native Linux environments, including required dependencies and compatible IDEs (e.g., VS Code, JetBrains Rider).
- Provide Linux-specific alternatives for running shell scripts (e.g., bash in a Linux terminal) instead of only referencing GitBash or WSL on Windows.
- Clarify which steps are cross-platform and which are specific to Windows or Mac, and ensure Linux users are not left out.
- Include troubleshooting tips or notes for Linux users, especially regarding .NET MAUI support and any known limitations.
- Consider referencing cross-platform tools and editors before or alongside Windows-specific ones.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/email-resource-management.md
...nication-services/samples/email-resource-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing multiple PowerShell-specific examples for resource cleanup, referencing Windows command-line conventions (e.g., 'PS C:\>'), and omitting equivalent Linux/bash commands. Azure CLI is mentioned, but PowerShell commands are more prominent and appear first for some tasks. There is no explicit Linux/bash example for deleting Email Communication Services or Domain resources.
Recommendations
- Provide equivalent bash/Azure CLI commands for all resource management and cleanup tasks, especially for deleting Email Communication Services and Domain resources.
- Ensure that examples are presented in a platform-neutral order or grouped by platform, rather than prioritizing Windows/PowerShell.
- Avoid using Windows-specific command prompts (e.g., 'PS C:\>') unless also providing bash equivalents (e.g., '$').
- Explicitly mention Linux/macOS compatibility where possible, and provide guidance for non-Windows users.
- Consider adding a table or section summarizing commands for each platform (PowerShell, Azure CLI on bash, Python, etc.) to improve parity and discoverability.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/chat-app-teams-embed.md
...mmunication-services/tutorials/chat-app-teams-embed.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft-centric tools and workflows, such as Visual Studio Code, Microsoft Teams Toolkit, and Azure Functions, without mentioning or providing guidance for Linux environments. There are no examples or instructions for Linux users, and all tooling references assume a Windows or Microsoft ecosystem. This may hinder accessibility for developers working on Linux or non-Windows platforms.
Recommendations
- Include explicit instructions or notes for Linux users, such as how to install and use the Teams Toolkit and Azure Functions CLI on Linux.
- Provide cross-platform command-line examples (e.g., using bash or zsh) alongside any GUI-based instructions.
- Mention alternative editors and development environments (such as VS Code on Linux, or JetBrains IDEs) and clarify that the Teams Toolkit is available cross-platform.
- Add troubleshooting tips or links for common Linux-specific issues (such as permissions, package installation, or environment setup).
- Ensure that all code samples and project setup steps are tested and documented for both Windows and Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/email-resource-management-azurecli-powershell.md
...ludes/email-resource-management-azurecli-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell users. All code samples are written in PowerShell, and the instructions assume the use of PowerShell as the scripting environment. Installation links and prerequisite checks are Windows-centric, and there are no equivalent Bash or Linux shell examples. This makes it difficult for Linux or macOS users to follow the guide without significant adaptation.
Recommendations
- Provide parallel Bash (Linux/macOS) script examples for all PowerShell commands, especially for Azure CLI usage, variable initialization, and scripting logic.
- Include installation instructions and links for Azure CLI and Azure PowerShell for Linux and macOS, not just Windows.
- When referencing command-line environments, mention both Windows (PowerShell/Command Prompt) and Linux/macOS (Bash/Terminal) explicitly.
- Add a section or callouts that highlight any differences or considerations for Linux/macOS users.
- Consider using cross-platform scripting approaches (e.g., pure Azure CLI in Bash) for automation tasks, or at least provide both PowerShell and Bash versions side by side.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
...s/tutorials/includes/twilio-to-acs-chat-js-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias in the prerequisites section by linking only to Windows-specific Azure CLI installation instructions and using a resource creation link with a 'tabs=windows' parameter. There are no Linux or macOS equivalents or instructions provided for these steps, and no mention of cross-platform compatibility for the CLI or resource setup. The rest of the documentation is platform-agnostic JavaScript, but the initial setup is Windows-centric.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows instructions.
- Use neutral or platform-agnostic links for resource creation and CLI installation, or include tabs for all major platforms.
- Explicitly state that the Azure CLI and SDK are cross-platform, and provide guidance for users on Linux and macOS.
- Review all prerequisite steps to ensure parity and clarity for non-Windows users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/tutorials/includes/twilio-to-acs-chat-csharp-tutorial.md
...torials/includes/twilio-to-acs-chat-csharp-tutorial.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation shows evidence of Windows bias, primarily through the use of Windows-specific tools and patterns. The prerequisite section requires Visual Studio (a Windows-centric IDE) and the package installation example uses PowerShell syntax. There are no Linux/macOS equivalents or alternatives mentioned for development environment setup or package installation. The documentation assumes a Windows development environment and does not provide parity for Linux users.
Recommendations
- Include instructions for installing the .NET SDK and the Azure Communication Services Chat SDK using cross-platform tools (e.g., dotnet CLI) and show command-line examples in bash/zsh as well as PowerShell.
- Mention Visual Studio Code as an alternative to Visual Studio, and provide setup steps for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users in the prerequisites, including any required dependencies or differences in environment setup.
- Avoid using PowerShell-specific syntax for generic .NET package installation; prefer the dotnet CLI, which is cross-platform.
- Where possible, provide side-by-side or clearly marked examples for both Windows and Linux/macOS environments.
Communication Services
Automate email resource management
...nication-services/samples/email-resource-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides resource management automation examples primarily using PowerShell, with PowerShell commands shown for deleting Email Communication Services and Domain resources. While an Azure CLI example is given for deleting a Communication Services resource, equivalent CLI commands for Email and Domain resources are missing. The organization and examples favor Windows/PowerShell users, creating friction for Linux/macOS users who may not have access to PowerShell or its Azure modules.
Recommendations
- Add Azure CLI examples for deleting Email Communication Services and Domain resources, ensuring parity with PowerShell commands.
- Clearly indicate which commands are platform-specific and provide alternative instructions for Linux/macOS users.
- Reorganize examples so that cross-platform tools (Azure CLI, Python SDK) are presented before or alongside PowerShell examples.
- Consider including sample scripts for resource cleanup in Python or Bash where possible.
Communication Services
Plan user experience for virtual appointments
...oncepts/interop/virtual-visits/plan-user-experience.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Teams Admin Center and PowerShell as the primary ways to learn and configure Teams meeting settings, without mentioning Linux/macOS equivalents or alternatives. PowerShell is a Windows-centric tool, and its mention without alternatives creates friction for Linux/macOS users. No Linux-specific tools or cross-platform CLI options are discussed.
Recommendations
- Include cross-platform alternatives to PowerShell, such as Azure CLI or Microsoft Graph API, for managing Teams settings.
- Explicitly mention whether Teams Admin Center is accessible via web browser on Linux/macOS.
- Provide examples or links for Linux/macOS users to perform equivalent configuration tasks.
- Clarify which configuration steps can be completed using platform-agnostic tools.
Communication Services
Send an email using SMTP
...s/quickstarts/email/send-email-smtp/send-email-smtp.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides a Powershell example specifically for sending email via SMTP, which is a Windows-centric tool. There is no mention of Linux/macOS command-line alternatives (such as sendmail, mailx, or Python scripts), nor are Linux-specific instructions or examples present. The inclusion of 'Windows Powershell' as a dedicated method and the absence of Linux/macOS equivalents demonstrates a notable Windows bias.
Recommendations
- Add Linux/macOS command-line examples using common tools (e.g., sendmail, mailx, swaks, or Python's smtplib).
- Include instructions for sending email via SMTP from Linux/macOS terminals.
- Ensure parity by presenting cross-platform examples side-by-side, or clearly indicating platform applicability.
- Consider adding a section for macOS users if there are platform-specific nuances.
Communication Services
Register the Event Grid resource provider
...starts/events/includes/register-provider-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are primarily used on Windows. There are no examples for Linux/macOS users, such as Azure CLI or Bash equivalents, and Windows tooling is implicitly prioritized.
Recommendations
- Add Azure CLI examples (e.g., 'az provider register --namespace Microsoft.EventGrid') for cross-platform compatibility.
- Include Bash or shell command alternatives where appropriate.
- Explicitly mention that PowerShell examples are for Windows and provide guidance for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation frequently references Windows-specific tools and patterns, such as PowerShell and Windows terminal, and lists them before mentioning generic or cross-platform alternatives. The instructions for running commands and opening terminals are Windows-centric, with no explicit mention of Linux/macOS equivalents or examples.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, Terminal.app, GNOME Terminal) alongside Windows options.
- Provide command examples using both Windows (PowerShell/CMD) and Linux/macOS (Bash/zsh) syntax where differences exist.
- Clarify that all commands (git, npm, devtunnel) are cross-platform and can be run in any terminal.
- Add notes or sections for Linux/macOS users, including any OS-specific setup steps or troubleshooting tips.
Communication Services
Enable interoperability with Teams
...ices/concepts/interop/enable-interoperability-teams.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively references Windows-centric tools and patterns, such as the PowerShell Set-CsPhoneNumberAssignment cmdlet, without mentioning Linux/macOS alternatives or providing cross-platform guidance. No Linux or macOS command-line equivalents or instructions are given, and the only example is Windows/PowerShell-based.
Recommendations
- Provide equivalent instructions for Linux/macOS users, such as using Microsoft Graph API or Azure CLI where possible.
- Explicitly state platform requirements for the PowerShell cmdlet and offer alternatives for non-Windows environments.
- Include cross-platform examples in all code and command sections.
- Add a section clarifying how Linux/macOS users can perform the same configuration steps.
Communication Services
Teams controls for Teams external user
...ervices/concepts/interop/guest/teams-administration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through the exclusive use of PowerShell for configuration examples and references, and by listing Windows-centric tools (Teams Admin Center, PowerShell) as the only administrative interfaces for tenant and policy management. There is no mention of Linux/macOS equivalents, nor are alternative CLI tools or cross-platform scripting options provided. The order of presentation also places Windows tools first, with no Linux-specific guidance.
Recommendations
- Include cross-platform alternatives to PowerShell, such as Azure CLI or REST API examples, where possible.
- Explicitly state whether PowerShell commands can be run on Linux/macOS (via PowerShell Core), and provide installation/setup instructions for those platforms.
- Add examples or references for managing Teams policies and configurations using Azure CLI, Graph API, or other platform-agnostic tools.
- Clarify which administrative tasks require Windows-only tools and which can be performed from Linux/macOS.
- Consider reordering tool lists to present platform-neutral options first, or group them by OS.