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 601-625 of 656 flagged pages
Communication Services
Quickstart - Manage a room call
...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by linking to quickstarts and conceptual documentation with Windows-specific tabs or pivots first (e.g., 'tabs=windows' in URLs), and by not providing any explicit Linux or cross-platform command-line examples or instructions. All code samples are SDK-based and platform-neutral, but supporting links and references prioritize Windows. There are no PowerShell-heavy examples or exclusive mentions of Windows tools, but Linux parity is not addressed.
Recommendations
- Ensure that all referenced quickstarts and conceptual documentation include Linux tabs or pivots alongside Windows, and avoid defaulting to Windows in URLs (e.g., use 'tabs=linux' or provide both).
- Add explicit notes or sections clarifying cross-platform compatibility of SDKs and APIs, including any OS-specific caveats for Linux users.
- Where relevant, provide Linux-specific setup or usage examples (e.g., CLI commands, environment configuration) in addition to Windows instructions.
- Audit all linked documentation for similar bias and update to ensure Linux parity in examples, instructions, and screenshots.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates minor Windows bias by listing Windows terminals (cmd, PowerShell) before Bash when instructing users to run commands. However, all commands and instructions are cross-platform, and no Windows-specific tools or patterns are used. Linux/macOS users can follow the guide without friction.
Recommendations
- List Bash (or 'terminal') before Windows-specific shells (cmd, PowerShell) to avoid implying Windows primacy.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Add a note clarifying that the instructions are platform-agnostic and provide troubleshooting tips for common Linux/macOS issues (e.g., environment variable setup).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows-specific console environments (Command Prompt, PowerShell) before Bash, suggesting a Windows-first perspective. However, all command-line instructions use cross-platform .NET CLI commands, and there are no Windows-only tools or examples. No Linux/macOS-specific instructions or troubleshooting are provided.
Recommendations
- List Bash (Linux/macOS) before or alongside Windows consoles to signal equal support.
- Explicitly state that all CLI commands work on Linux/macOS terminals.
- Add a note or troubleshooting section for Linux/macOS users (e.g., .NET installation, file paths).
- Include a screenshot or example of running the commands in a Linux/macOS terminal.
Communication Services
Access a user's Teams Phone separate from their Teams client
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a mild Windows bias. The only platform-specific tool mentioned is the MicrosoftTeams PowerShell cmdlet (Get-CsOnlineApplicationInstance) for retrieving the ObjectId, with no Linux/macOS alternative or cross-platform guidance. The user enablement instructions reference the Microsoft 365 admin center UI, which is web-based and not platform-specific, but the PowerShell reference is Windows-centric. No Linux or macOS command-line equivalents (such as Azure CLI, Graph API, or bash scripts) are provided for key steps, and the PowerShell method is mentioned before any REST or programmatic alternatives.
Recommendations
- Provide Linux/macOS-friendly alternatives for retrieving ObjectId, such as using Azure CLI or direct Graph API calls.
- Explicitly mention that REST API operations can be performed from any OS, and provide example commands using curl or similar cross-platform tools.
- Where PowerShell is referenced, add equivalent instructions for bash or other common Linux/macOS shells.
- Clarify that the Microsoft 365 admin center is accessible via browser on any OS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a minor Windows bias by listing Windows-specific shells (PowerShell, Windows Terminal, Command Prompt) first when instructing users to open a terminal for cloning the repository. The phrase 'or equivalent' does acknowledge other platforms, but no explicit mention of Linux/macOS terminals (e.g., Bash, Terminal.app) is made. All other instructions and tooling (Node.js, npm, VS Code, Azure CLI) are cross-platform and do not exhibit Windows bias.
Recommendations
- Explicitly mention Linux/macOS terminal options (e.g., Bash, Terminal.app, iTerm) alongside Windows shells.
- Provide a brief note confirming that all commands work on Linux/macOS terminals.
- Consider listing terminal options in a platform-neutral order or grouping (e.g., 'Open a terminal (PowerShell, Command Prompt, Bash, Terminal.app, etc.)').
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by instructing users to open a PowerShell window to run the application, without mentioning Linux/macOS terminal usage or providing equivalent instructions. Additionally, some prerequisite links default to Windows tabs, suggesting Windows-first orientation.
Recommendations
- Update the 'Run the application' section to mention using a terminal or command prompt on Linux/macOS, not just PowerShell.
- Provide explicit instructions or notes for Linux/macOS users, e.g., 'Open a terminal window (PowerShell on Windows, Terminal on Linux/macOS)'.
- Ensure prerequisite links and resource setup instructions do not default to Windows tabs, or provide clear parity for Linux/macOS.
- Add a note clarifying that the sample works cross-platform and that commands are the same on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows mild Windows bias by linking to resource creation instructions with a 'tabs=windows' parameter and mentioning PowerShell and command prompt before Unix terminal when describing how to run the Python application. However, most instructions and examples are cross-platform, and Linux/macOS users can follow along without significant friction.
Recommendations
- Update resource creation links to default to a neutral or Linux tab, or provide explicit instructions for Linux/macOS users.
- When listing command-line options, alternate or equally mention Unix terminal and PowerShell/command prompt.
- Add explicit notes or examples for Linux/macOS users where platform-specific differences may exist.
Communication Services
Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation shows a minor Windows bias by presenting Windows command prompt instructions before macOS terminal equivalents when creating the project directory. However, all other instructions, examples, and tooling are cross-platform (Node.js, VS Code, http-server), and Linux is implicitly supported, though not explicitly mentioned.
Recommendations
- Present platform-specific instructions in parallel or grouped together, rather than listing Windows first.
- Explicitly mention Linux in platform support and provide Linux-specific command examples where relevant.
- Clarify that all terminal commands work on Linux as well as macOS, or provide a Linux example alongside the macOS example.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation refers to opening 'PowerShell, Windows Terminal, Command Prompt or equivalent' as the first step for cloning the repository, listing Windows tools first and not mentioning Linux/macOS terminals by name. No explicit Linux/macOS examples or terminal instructions are provided, though the commands themselves are cross-platform.
Recommendations
- Explicitly mention Linux/macOS terminal applications (e.g., 'Terminal on macOS or Linux') alongside Windows tools.
- Rephrase instructions to be platform-neutral, such as 'Open your terminal application (PowerShell, Windows Terminal, Command Prompt, Terminal on macOS or Linux)'.
- Consider providing any platform-specific notes if there are differences in setup or troubleshooting steps for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates mild Windows bias by listing Windows terminal options (Command Prompt, PowerShell) before Bash when instructing users to open a terminal. All code examples are platform-neutral (C#/.NET) and use the dotnet CLI, which works on both Windows and Linux. No explicit PowerShell scripts, Windows-only tools, or missing Linux examples are present, but the ordering of terminal options subtly prioritizes Windows environments.
Recommendations
- List Bash (or 'terminal') before Command Prompt and PowerShell to avoid implying Windows-first workflows.
- Explicitly state that all commands and steps work on Linux, macOS, and Windows.
- Where relevant, provide platform-specific notes (e.g., how to install .NET SDK on Linux) to ensure parity.
- Include a short section or note confirming cross-platform compatibility for the quickstart.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits mild Windows bias by mentioning Windows command-line tools (cmd, PowerShell) before Bash when instructing users to run commands. However, all command-line examples use 'dotnet' CLI, which is cross-platform, and there are no PowerShell-specific commands or Windows-only tools used. No Linux-specific examples or instructions are provided, but the instructions are generally applicable to both Windows and Linux environments.
Recommendations
- List Bash (Linux/macOS) before Windows command prompts (cmd, PowerShell) when mentioning command-line options, or mention all platforms equally.
- Explicitly state that all commands work on Windows, Linux, and macOS, and provide any platform-specific caveats if applicable.
- Include example screenshots or outputs from Linux/macOS terminals to demonstrate parity.
- Add a note or section for Linux/macOS users with tips for common environment setup differences (e.g., setting environment variables, file path conventions).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally avoids strong Windows bias, as it references cross-platform tools (dotnet CLI) and mentions Bash alongside cmd and PowerShell. However, in the 'Create a new C# application' section, it lists 'cmd, PowerShell, or Bash' in that order, which may subtly prioritize Windows environments. There are no Linux-specific examples or troubleshooting notes, and no mention of Linux package managers or shell environments beyond Bash.
Recommendations
- When listing console environments, alternate the order or explicitly state that all commands work on Windows, Linux, and macOS.
- Include a note clarifying that the dotnet CLI and examples are fully cross-platform.
- Add Linux/macOS-specific troubleshooting tips or environment notes if any platform-specific issues are known.
- Where relevant, mention Linux/macOS equivalents for tools (e.g., Terminal instead of just Bash), or provide a table showing command usage across platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a slight Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when instructing users to create a new C# application. However, all commands shown are cross-platform and no PowerShell-specific syntax or Windows-only tools are used. Linux examples are not missing, but Windows consoles are mentioned first.
Recommendations
- List Bash (or 'terminal') before Windows-specific consoles (cmd, PowerShell) to avoid implying Windows primacy.
- Explicitly state that all commands work on Linux, macOS, and Windows.
- Consider including a note or examples for common Linux/macOS editors (e.g., nano, vim) when instructing users to edit files, if relevant.
- Ensure parity in references to command-line environments, e.g., 'In a terminal or command window (such as Bash, cmd, or PowerShell)...'
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions 'Command Prompt, PowerShell, or Bash' as possible console windows, listing Windows shells before Bash (commonly used on Linux). However, all command-line examples use the cross-platform 'dotnet' CLI and do not use Windows-specific tools or commands. There are no PowerShell-specific scripts, nor are there Windows-only tools or patterns. No Linux-specific instructions or examples are missing, but the ordering of shell examples puts Windows first.
Recommendations
- List Bash before Command Prompt and PowerShell when mentioning console windows, or use neutral phrasing such as 'in a terminal window (such as Bash, PowerShell, or Command Prompt)'.
- Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform parity.
- If possible, add a note or example showing the commands running on Linux/macOS to reassure non-Windows users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run Maven commands, which may subtly prioritize Windows environments. However, all command-line instructions and tooling (Maven, Java) are cross-platform, and no Windows-specific tools or examples (such as PowerShell scripts) are used. There are no missing Linux examples, and no Windows-only patterns or tools are referenced.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when describing command-line usage, or simply state 'any terminal' to avoid platform prioritization.
- Explicitly mention that all commands work on Linux, macOS, and Windows to reinforce cross-platform compatibility.
- If relevant, provide troubleshooting notes for common platform-specific issues (e.g., file permissions on Linux/macOS, path differences) to ensure parity.
- Avoid mentioning Windows-specific shells unless providing equivalent instructions for Linux/macOS.
Communication Services
Quickstart - Manage a room call
...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle Windows bias by linking to quickstart and concept pages with Windows-specific tabs or pivots (e.g., '?tabs=windows', '?pivots=platform-azcli'), and by referencing Windows in URLs before Linux alternatives. However, the code samples themselves are cross-platform (C#, Java, JavaScript, Python) and do not use Windows-only tools or PowerShell. There are no explicit Linux examples, nor are Linux-specific instructions or tools mentioned.
Recommendations
- Ensure that linked quickstart and concept pages provide Linux-specific tabs or pivots, and reference them equally or before Windows alternatives.
- Add explicit notes or examples for Linux users where platform-specific setup or commands may differ, especially in related quickstarts.
- Review all cross-references to ensure parity in guidance for Linux and macOS users, not just Windows.
- Where platform-specific prerequisites or instructions exist, provide them side-by-side (e.g., CLI commands for both Windows and Linux).
Communication Services
Using ACS UI library JavaScript bundles with Teams Call Queues and Auto Attendants
...tutorials/calling-widget/calling-widget-js-tutorial.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation demonstrates a mild Windows bias by presenting Windows command prompt instructions before macOS equivalents when creating the project directory. However, all other instructions and examples (Node.js, VS Code, running the app) are cross-platform and do not favor Windows-specific tools or patterns. There are no PowerShell-heavy examples, exclusive use of Windows tools, or missing Linux examples.
Recommendations
- Present platform instructions in parallel or grouped together, rather than listing Windows first.
- Explicitly mention Linux in platform-specific instructions (e.g., 'For Linux/macOS, use this command...').
- Include a Linux-specific example for creating directories, if any differences exist.
- Clarify that all steps are applicable to Linux unless otherwise noted.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits mild Windows bias by listing Windows command-line environments ('cmd', 'PowerShell') before Linux ('Bash') when describing how to run commands. All examples use cross-platform .NET CLI commands, and there are no PowerShell-specific scripts or Windows-only tools. However, the ordering of environments may subtly suggest Windows as the primary platform.
Recommendations
- List command-line environments in alphabetical or platform-neutral order (e.g., 'Bash, cmd, or PowerShell') to avoid implying Windows primacy.
- Explicitly state that all commands and code samples work equally on Windows, Linux, and macOS.
- Add a brief section or note highlighting any platform-specific considerations (if any), or confirming there are none.
- Where possible, include screenshots or output examples from both Windows and Linux terminals to reinforce cross-platform parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation refers to 'Command Prompt, PowerShell, or Bash' when describing the console window, listing Windows shells before Bash (commonly used on Linux/macOS). However, all command-line examples use the cross-platform 'dotnet' CLI, and there are no Windows-specific tools or PowerShell-only examples. No Linux-specific instructions or examples are missing, but the ordering of shells suggests a subtle Windows-first bias.
Recommendations
- List Bash before Command Prompt and PowerShell when mentioning console windows, or use neutral phrasing such as 'in a terminal window (such as Bash, PowerShell, or Command Prompt)'.
- Explicitly state that the instructions and examples work on Windows, Linux, and macOS.
- If possible, include a note or section confirming parity and any OS-specific considerations for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing how to run commands, which may subtly prioritize Windows environments. However, all code and tooling instructions are platform-agnostic (Java, Maven), and there are no PowerShell-specific examples, Windows-only tools, or missing Linux equivalents.
Recommendations
- List Bash (Linux/macOS) before Windows consoles (cmd, PowerShell) when mentioning terminal options, or present them in alphabetical order.
- Explicitly state that all instructions and commands work equally on Linux, macOS, and Windows.
- Where relevant, provide any OS-specific notes (e.g., environment variable setup, file paths) to ensure parity and clarity for Linux users.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a slight Windows bias by listing Windows-specific console environments (cmd, PowerShell) before Bash when instructing users to create a new C# application. However, all commands given (dotnet CLI) are cross-platform and no examples are exclusive to Windows or PowerShell. No Windows-only tools or patterns are used, and Linux users are not excluded from any steps.
Recommendations
- List Bash (or 'terminal') before Windows-specific environments (cmd, PowerShell) when mentioning console windows, or use neutral phrasing such as 'in a terminal or command window (e.g., Bash, cmd, PowerShell)'.
- Explicitly mention that all steps and commands work on Linux, macOS, and Windows.
- Consider adding a note or section for Linux/macOS users, such as recommended editors or troubleshooting tips specific to those platforms.
- Ensure parity in any future troubleshooting or environment setup instructions, avoiding Windows-first language or examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-net.md
...ts/identity/includes/access-tokens/access-token-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows command-line tools (cmd, PowerShell) before Bash when instructing users to open a command prompt window. However, all command-line instructions use the cross-platform 'dotnet' CLI and do not provide Windows-specific examples or tools. No PowerShell-specific commands or Windows-only patterns are present, and Linux users are not excluded from any steps.
Recommendations
- List Bash before or alongside cmd and PowerShell when mentioning command prompt options to avoid implicit Windows prioritization.
- Explicitly state that all commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- Consider adding a note or section confirming Linux/macOS compatibility, especially for environment variable setup and text editor usage.
- If any platform-specific steps exist (e.g., setting environment variables), provide both Windows and Linux/macOS instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/send-sms-net.md
...tion-services/quickstarts/sms/includes/send-sms-net.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when describing where to run commands. However, all commands shown are cross-platform (dotnet CLI), and there are no exclusive Windows tools or missing Linux examples. The documentation does not provide explicit Linux-specific instructions or mention Linux editors or patterns.
Recommendations
- List Bash (Linux/macOS) first or equally alongside cmd and PowerShell when mentioning console windows.
- Explicitly state that all commands work on Windows, Linux, and macOS.
- Provide examples of opening and editing files using common Linux tools (e.g., nano, vim) in addition to generic instructions.
- Mention cross-platform compatibility in the prerequisites and setup sections.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/manage-rooms-call.md
...cation-services/quickstarts/rooms/manage-rooms-call.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows a subtle Windows bias in its cross-references and quickstart links. For example, the link to enabling PSTN dial-out capability for a room points to a quickstart with '?tabs=windows', suggesting Windows as the default or primary platform. However, all code samples are provided in cross-platform languages (C#, Java, JavaScript, Python) and do not use Windows-specific tools or PowerShell, nor do they reference Windows-only patterns or utilities. There are no explicit examples missing for Linux, but the navigation and tab defaults favor Windows.
Recommendations
- Ensure that quickstart and concept links do not default to Windows tabs; provide parity for Linux/macOS tabs or CLI where relevant.
- Where platform-specific instructions are referenced (e.g., enabling PSTN dial-out), offer clear guidance for Linux/macOS users, such as Azure CLI or Bash examples.
- Audit all cross-references and tab defaults to avoid implicit prioritization of Windows; consider using platform-neutral defaults or highlighting all supported platforms equally.
- If there are platform-specific prerequisites or setup steps, document them for both Windows and Linux/macOS environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-java.md
...es/quickstarts/rooms/includes/rooms-quickstart-java.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows consoles (cmd, PowerShell) before Bash when describing where to run commands, which may subtly prioritize Windows environments. However, all commands and examples are cross-platform (Java/Maven), and there are no Windows-specific tools, PowerShell scripts, or missing Linux examples.
Recommendations
- List Bash before cmd/PowerShell, or use 'such as Bash, cmd, or PowerShell' to avoid Windows-first ordering.
- Explicitly state that all commands work on Linux, macOS, and Windows.
- Add a note confirming Maven and Java are cross-platform and provide links to installation guides for Linux/macOS as well as Windows.
- If any troubleshooting or environment setup is required, include Linux/macOS steps alongside Windows.