Remote Rendering
81
Total Pages
48
Linux-Friendly Pages
33
Pages with Bias
40.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
51 issues found
Showing 26-50 of 51 flagged pages
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/session-rest-api.md
.../articles/remote-rendering/how-tos/session-rest-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell scripts and Windows-centric tools for interacting with the REST API. There are no examples or mentions of Linux or cross-platform command-line tools (such as curl or bash scripts), and PowerShell is presented as the primary scripting interface. SDKs for .NET (commonly associated with Windows) are mentioned before Java, and there is no mention of Linux-native workflows.
Recommendations
- Provide equivalent Linux/bash script examples for interacting with the REST API, such as using curl or httpie.
- Mention cross-platform tools and workflows alongside PowerShell, ensuring parity in documentation.
- List SDKs in a neutral or alphabetical order, and include information about their cross-platform compatibility.
- Add explicit guidance or links for Linux and macOS users, including setup instructions and sample scripts.
- Reference platform-agnostic tools (e.g., REST clients, Postman) for interacting with the API.
Create Pull Request
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/performance-tracing.md
...ticles/remote-rendering/how-tos/performance-tracing.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily Windows-centric, introducing Windows tools (WPR, WPA, ETW) first and in detail, with step-by-step instructions and screenshots. Linux and Android tracing is only briefly mentioned via Perfetto, with no equivalent depth or parity in instructions or tooling for Linux desktop environments. There are no Linux (non-Android) examples, and PowerShell is referenced for command execution, even for Android/Quest tracing. The documentation assumes Windows as the default environment for both tracing and analysis.
Recommendations
- Provide equivalent step-by-step instructions for capturing and analyzing traces on Linux desktop environments, not just Android/Quest.
- Include Linux-native tools (e.g., perf, sysprof, trace-cmd, or LTTng) and show how to use them for client-side performance tracing.
- Offer examples of analyzing Perfetto traces on Linux desktops, not just via the web UI.
- Avoid referencing PowerShell for cross-platform tasks; use platform-neutral shell commands or provide both PowerShell and Bash equivalents.
- Reorganize the documentation to present Windows and Linux/Android tracing options in parallel, rather than Windows-first.
- Add screenshots and workflow descriptions for Linux tools and environments where possible.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/unity/install-remote-rendering-unity-package.md
...ow-tos/unity/install-remote-rendering-unity-package.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-specific tools (Mixed Reality Feature Tool), providing PowerShell scripts as the only automation example, and omitting Linux/macOS equivalents or instructions. All command-line examples and tooling references assume a Windows environment, with no mention of cross-platform alternatives or guidance for non-Windows users.
Recommendations
- Provide explicit instructions for Linux and macOS users, including how to download and install the package using standard shell commands (e.g., bash) and compatible tools.
- Offer cross-platform scripts (e.g., bash or Python) alongside PowerShell scripts for automation.
- Clarify whether the Mixed Reality Feature Tool is available for non-Windows platforms, and if not, suggest alternative manual installation steps for those users.
- When presenting command-line examples, include both Windows (cmd/PowerShell) and Unix shell (bash/zsh) syntax.
- Add a section or callout addressing platform compatibility and any known limitations or workarounds for Linux/macOS environments.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/unity/holographic-remoting.md
...remote-rendering/how-tos/unity/holographic-remoting.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on Windows-specific tools and scenarios (HoloLens 2, Windows Mixed Reality VR headset) without mentioning Linux or cross-platform alternatives. There are no examples or instructions for Linux users, and Windows tools are presented as the default or only option.
Recommendations
- Include information on whether Holographic Remoting and Azure Remote Rendering are available or supported on Linux platforms.
- If Linux is not supported, explicitly state this to inform users.
- If there are Linux-compatible alternatives or workflows (e.g., using Unity play mode on Linux), provide examples and instructions.
- Avoid assuming the presence of Windows-specific hardware; mention platform requirements up front.
- Where possible, provide parity in documentation by including both Windows and Linux usage scenarios or clarifying platform limitations.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/overview/features/late-stage-reprojection.md
...rendering/overview/features/late-stage-reprojection.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows Mixed Reality (WMR), Windows-specific APIs, and Direct3D (D3D11) graphics bindings. All examples and configuration instructions are tailored to Windows environments, with no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, tools, or code samples, and Windows terminology and tools are presented as the default or only option.
Recommendations
- Add equivalent instructions and examples for Linux platforms, including how to configure LSR modes and pose modes in Unity and native applications on Linux.
- Reference cross-platform APIs (such as Vulkan or OpenGL) alongside Direct3D, and provide code samples for these APIs where possible.
- Mention and document any differences or limitations when using LSR features on Linux, including supported hardware and drivers.
- Clarify whether the described features are Windows-only or if there is Linux support, and if not, provide a roadmap or alternatives for Linux users.
- Ensure terminology and instructions are inclusive of both Windows and Linux users, avoiding Windows-specific paths, tools, or settings as the default.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/concepts/graphics-bindings.md
...rticles/remote-rendering/concepts/graphics-bindings.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows-specific graphics APIs and tools, such as Direct3D 11 (D3D11), Windows Mixed Reality, and HoloLens 2. All code examples and setup instructions assume the use of Windows technologies, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for Linux users, and the documentation does not acknowledge the absence of Linux support or provide any roadmap for parity.
Recommendations
- Explicitly state platform support at the beginning of the documentation, clarifying if Linux is unsupported or if there are plans for future support.
- If Linux support is not available, provide a section explaining this and suggest possible workarounds or alternatives for Linux developers.
- If partial Linux support exists (e.g., via OpenXR or Vulkan), add equivalent Linux setup and code examples.
- When introducing APIs or tools, mention cross-platform alternatives where possible (e.g., Vulkan for graphics binding) and provide guidance for non-Windows environments.
- Structure the documentation to avoid assuming Windows as the default platform; instead, organize by platform or provide parallel instructions for each supported OS.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/frontend-apis.md
...ain/articles/remote-rendering/how-tos/frontend-apis.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 Windows-specific APIs and tools (such as ShellExecuteA and Windows.System.Launcher), providing C# and C++ code that assumes Windows environments, and linking to PowerShell scripts without mentioning Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or notes about running the SDK or tools on Linux or macOS.
Recommendations
- Add Linux/macOS equivalents for launching files (e.g., using xdg-open or open commands) in the 'Connect to ARR inspector' section.
- Include Bash or shell script examples alongside PowerShell scripts, or provide cross-platform scripting guidance.
- Explicitly mention cross-platform compatibility (or limitations) for the SDK and APIs, and provide guidance for Linux/macOS users where relevant.
- Avoid using Windows-specific APIs (like ShellExecuteA) in C++ examples, or provide alternative code for other platforms.
- Add a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/overview/system-requirements.md
...icles/remote-rendering/overview/system-requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all system requirements, setup instructions, and tooling references are exclusively for Windows environments. There are no Linux (or macOS) equivalents or examples provided, and Windows-specific tools and workflows (e.g., Visual Studio, Windows SDK, Microsoft Store, HEVC codec installation, UWP, DX11) are mentioned throughout without alternatives. Even cross-platform tools like Git are only referenced generically, with no Linux-specific installation or usage guidance.
Recommendations
- Clearly state if Linux (or macOS) is unsupported, or provide a roadmap for cross-platform support if planned.
- If Linux support is possible, add equivalent instructions for Linux (and macOS) environments, including supported distributions, required dependencies, and installation steps.
- Provide Linux alternatives for Windows-specific tools (e.g., suggest VS Code or JetBrains Rider for development, and clarify if Visual Studio is required only for Windows).
- For codec and driver requirements, include instructions for checking/installing on Linux (e.g., using ffmpeg, vdpauinfo, or relevant package managers).
- If certain features/tools (like UWP, DX11, or Microsoft Store codecs) are Windows-only, explicitly note this and suggest any possible Linux workarounds or alternatives.
- Include Linux-specific troubleshooting steps and links to relevant resources.
- Ensure parity in example commands, screenshots, and terminology for all supported platforms.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/deploy-to-desktop.md
...cles/remote-rendering/quickstarts/deploy-to-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing primarily on Windows-specific deployment targets (Windows Standalone and UWP), referencing Windows tools (Visual Studio, .exe files, Start menu), and omitting explicit instructions or examples for Linux or Mac, despite mentioning 'PC, Mac & Linux Standalone' in Unity. There are no Linux- or Mac-specific build, deployment, or launch instructions.
Recommendations
- Provide explicit build, deployment, and launch instructions for Linux and Mac platforms, including relevant screenshots and file extensions (e.g., .x86_64 for Linux).
- Mention and give examples for common Linux and Mac development tools (such as MonoDevelop, JetBrains Rider, or command-line execution) alongside Visual Studio.
- When referencing platform selection in Unity, show how to set and build for Linux and Mac, not just Windows.
- Include notes on how to run the built application on Linux (e.g., using terminal commands, setting executable permissions) and Mac (e.g., handling .app bundles).
- Avoid assuming the user is on Windows when describing post-build steps (e.g., 'find it from the Start menu'); provide equivalent instructions for Linux (e.g., desktop environment menus or terminal launch) and Mac.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/render-model.md
.../articles/remote-rendering/quickstarts/render-model.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows development. All prerequisites and instructions assume a Windows environment, requiring Windows SDK, Visual Studio (Windows-only), and Visual Studio tools for Mixed Reality. The command-line instructions use Windows-specific tools (cmd, PowerShell), and there are no Linux or cross-platform alternatives provided. There is no mention of Linux support, nor are any Linux-specific instructions or tools referenced.
Recommendations
- Explicitly state platform support (Windows-only or cross-platform) at the start of the documentation.
- If Linux is supported, provide equivalent instructions for Linux users, including installation steps for required tools (e.g., Unity, git, git-lfs) on Linux.
- Replace or supplement Windows-specific commands (cmd, PowerShell) with cross-platform alternatives (e.g., bash scripts, shell commands).
- Mention and provide guidance for using cross-platform IDEs (such as Rider or VS Code) if possible.
- Clarify any features or steps that are Windows-exclusive, and suggest workarounds or alternatives for Linux users where feasible.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/deploy-to-hololens.md
...les/remote-rendering/quickstarts/deploy-to-hololens.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes deployment using Windows-specific tools and workflows, such as Visual Studio, Universal Windows Platform (UWP), and the Windows Device Portal. There are no instructions or examples for performing these steps from Linux or macOS, nor are any cross-platform alternatives mentioned. The instructions assume the user is on Windows from the outset.
Recommendations
- Explicitly state platform requirements at the beginning, clarifying if Windows is mandatory or if alternatives exist.
- If possible, provide instructions for deploying to HoloLens from Linux or macOS, or clarify that such workflows are unsupported.
- Mention and, if available, provide cross-platform tools or command-line alternatives for building and deploying Unity projects to HoloLens.
- If Visual Studio is required, note whether Visual Studio Code or other IDEs can be used on non-Windows platforms for any part of the workflow.
- Include a section addressing Linux/macOS users, even if only to explain current limitations and suggest workarounds or future plans for support.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/convert-model.md
...articles/remote-rendering/quickstarts/convert-model.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. It provides detailed instructions and examples exclusively for PowerShell scripts and Windows file paths, with no mention of Linux or cross-platform alternatives. The only provided automation script is a PowerShell (.ps1) script, and all path examples use Windows-style backslashes. There are no Linux shell (bash) or cross-platform CLI examples, nor any mention of how to perform the same tasks on non-Windows systems.
Recommendations
- Provide equivalent instructions and examples for Linux users, including bash shell commands and Linux file path conventions.
- Offer a cross-platform script (e.g., in Python or bash) for model conversion, or document how to use the REST API directly from the command line (e.g., with curl or az CLI).
- Explicitly mention OS compatibility for the provided PowerShell script and note any prerequisites for running it on Linux (such as PowerShell Core).
- Include Linux/macOS-specific guidance for installing required tools (e.g., Azure CLI or PowerShell Core) and uploading files to Azure Blob Storage.
- Present examples for both Windows and Linux side by side, or clarify when instructions are Windows-specific.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/native-cpp/hololens/deploy-native-cpp-openxr-tutorial.md
...tive-cpp/hololens/deploy-native-cpp-openxr-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows, focusing exclusively on Windows tools (Visual Studio, Windows SDK), Windows-specific workflows, and command prompts. There are no Linux (or macOS) equivalents or instructions, and all examples and tool recommendations are Windows-centric.
Recommendations
- Add instructions for building and deploying the sample on Linux (and/or macOS) if supported by the toolchain (e.g., using CMake, cross-platform compilers, or VS Code).
- Include Linux equivalents for command-line operations (e.g., using bash instead of cmd).
- Mention cross-platform alternatives to Visual Studio, such as VS Code or CLion, and provide guidance for setting up the project on those IDEs.
- Clarify in the prerequisites if the workflow is only supported on Windows, or explicitly state platform limitations.
- If PowerShell scripts are referenced, provide bash or shell script alternatives where possible.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/reference/vm-sizes.md
...b/main/articles/remote-rendering/reference/vm-sizes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. While the main code examples are in C# and C++ (which are cross-platform), the only scripting example and explicit configuration reference is to PowerShell scripts and arrconfig.json, with no mention of Linux shell, Bash, or cross-platform CLI tools. The 'Next steps' and in-text references also highlight PowerShell scripts as the primary automation/scripting method, and there is no mention of Linux-specific workflows or examples.
Recommendations
- Add equivalent Bash or shell script examples for Linux users, or reference cross-platform CLI tools if available.
- Include a note clarifying whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS, or provide alternative instructions for Linux environments.
- In the 'Next steps' section, add links to Linux or cross-platform automation/script samples if available.
- When referencing configuration files (like arrconfig.json), provide context or examples for editing and using them in Linux environments.
- Consider including a short section or callout on cross-platform support, explicitly mentioning Linux compatibility and tooling.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/unity/security/security.md
.../remote-rendering/tutorials/unity/security/security.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by referencing and providing examples for Windows-specific tools and workflows, such as the use of PowerShell scripts (Conversion.ps1) and deployment instructions tailored for HoloLens (a Windows-based device). There are no equivalent instructions or examples for Linux or macOS users, such as using Bash scripts or cross-platform command-line tools. The documentation assumes a Windows development environment throughout, with no mention of how to perform key steps (like model conversion or deployment) on non-Windows platforms.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell scripts, such as Bash scripts or cross-platform CLI commands.
- Include explicit instructions or notes for performing model conversion and deployment steps on Linux and macOS.
- When referencing scripts (e.g., Conversion.ps1), mention and link to cross-platform alternatives if available, or provide guidance for running them with PowerShell Core on non-Windows systems.
- Ensure that any tooling or workflow described (such as file paths, build steps, or deployment) is either cross-platform or that platform-specific differences are clearly documented.
- Add a section or callouts for non-Windows users, highlighting any prerequisites, limitations, or workarounds needed to achieve parity.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/native-cpp/hololens/deploy-native-cpp-tutorial.md
...arts/native-cpp/hololens/deploy-native-cpp-tutorial.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows, focusing exclusively on Windows tools (Visual Studio, Windows SDK), Windows-specific workflows (cmd, Visual Studio UI), and HoloLens (a Windows device). There are no Linux or cross-platform alternatives mentioned for building, deploying, or managing sessions. Even command-line instructions are given only for Windows (cmd), and session management references a PowerShell script. No Linux equivalents or instructions are provided.
Recommendations
- Add a section clarifying platform support (e.g., if only Windows is supported, state this explicitly at the top).
- If possible, provide Linux/macOS alternatives for cloning, building, and deploying (e.g., using CMake, cross-compilation, or alternative IDEs).
- Include Linux/macOS command-line examples alongside Windows (e.g., bash equivalents for git commands).
- Reference cross-platform session management tools or REST API usage directly, rather than only PowerShell scripts.
- If the workflow is inherently Windows-only (due to HoloLens or UWP), explain why and suggest any possible cross-platform development or testing options.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/native-cpp/hololens/integrate-remote-rendering-into-holographic-app.md
...ens/integrate-remote-rendering-into-holographic-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows development. All instructions, tools, and examples assume the use of Windows, Visual Studio, and Windows-specific SDKs and APIs. There are no mentions of Linux or cross-platform alternatives, and the workflow is tightly coupled to the Windows ecosystem, including UWP, DirectX11, and HoloLens, with no guidance for Linux users.
Recommendations
- Add a section clarifying platform support and, if possible, provide equivalent instructions for Linux (e.g., using CMake, GCC/Clang, and cross-platform graphics APIs like OpenGL or Vulkan).
- Include Linux-compatible project setup instructions, such as using CMake or Makefiles instead of Visual Studio project wizards.
- If Remote Rendering is not supported on Linux, explicitly state this early in the documentation.
- Provide alternative debugging and status feedback mechanisms that do not rely on Visual Studio or Windows-only tools.
- Mention and, if possible, provide code samples for cross-platform development environments or tools.
- List any platform limitations or requirements up front, so Linux/macOS developers know what to expect.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/reference/network-requirements.md
...les/remote-rendering/reference/network-requirements.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools (WifiInfoView, PsPing), providing only PowerShell script examples and screenshots, and omitting Linux (or macOS) equivalents for network testing and session management. The guidance and tooling are tailored to Windows users, with no mention of cross-platform or Linux-native alternatives.
Recommendations
- Include Linux (and macOS) equivalents for all mentioned tools, such as using 'iwlist', 'nmcli', or 'wavemon' for Wi-Fi scanning, and 'hping3', 'nping', or 'tcping' for TCP/UDP latency testing.
- Provide example commands and screenshots for Linux terminals alongside PowerShell examples.
- Reference cross-platform or open-source tools where possible (e.g., 'speedtest-cli' for speed tests, 'mtr' for latency/path analysis).
- Avoid assuming the user is on Windows; use neutral language and structure examples so that Linux/macOS instructions are presented equally and not as an afterthought.
- Add a section or table summarizing tool options for Windows, Linux, and macOS users for each recommended network test.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/resources/tools/arr-inspector.md
...cles/remote-rendering/resources/tools/arr-inspector.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 Windows-specific tools (such as the Windows Device Portal for HoloLens), using Windows-style file paths (User Folders\LocalAppData\...), and omitting any mention of Linux or cross-platform equivalents for accessing files or running the ArrInspector. There are no examples or instructions for Linux users, nor is there guidance for non-Windows environments.
Recommendations
- Provide instructions for accessing the generated StartArrInspector.html file on Linux and macOS systems, including typical file locations and access methods.
- Use cross-platform or platform-neutral file path notation (e.g., use forward slashes or clarify both Windows and Unix-style paths).
- If the ArrInspector tool is usable from non-Windows environments, explicitly state this and provide relevant steps.
- If certain features (like HoloLens integration) are Windows-only, clearly indicate this and, if possible, suggest alternatives or workarounds for Linux users.
- Include screenshots or examples from Linux or macOS environments where applicable.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/unity/commercial-ready/commercial-ready.md
...g/tutorials/unity/commercial-ready/commercial-ready.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific diagnostic tools (ETW, ETL, Windows Device Portal) without mentioning Linux equivalents or cross-platform alternatives. The examples and tool recommendations focus on Windows environments, and there is a lack of Linux or cross-platform guidance for diagnostics and performance tracing. This may hinder Linux developers or those deploying on non-Windows platforms from fully leveraging the documentation.
Recommendations
- Include Linux and cross-platform equivalents for diagnostics, such as using 'perf', 'strace', or Azure Monitor's cross-platform agents.
- When referencing tools like ETW or Windows Device Portal, also mention or link to Linux-compatible alternatives or Azure-native diagnostics that work across OSes.
- Provide example commands or workflows for both Windows (PowerShell, ETW) and Linux (Bash, Linux tracing tools) where relevant.
- Review all sections for implicit Windows-first assumptions and ensure parity in recommendations and troubleshooting steps for Linux environments.
- Explicitly state platform requirements or limitations when a feature or tool is Windows-only, and suggest alternatives for other platforms.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/resources/troubleshoot.md
...in/articles/remote-rendering/resources/troubleshoot.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias, particularly in troubleshooting codec issues, file system limitations, and Unity build problems. Solutions are described using Windows-specific tools (PowerShell, Windows Explorer, registry commands), and file system constraints reference only Windows. There are no Linux or cross-platform equivalents provided for these steps, and Linux/macOS users are not addressed in troubleshooting or example commands.
Recommendations
- Provide Linux/macOS equivalents for PowerShell and Windows Explorer steps, such as using terminal commands (e.g., ls, chmod, chown) and file managers.
- When discussing file system limitations, mention relevant Linux/macOS constraints and provide guidance for those platforms.
- For registry or Windows-specific configuration steps, clarify if these are required only for Windows users and offer alternatives or note irrelevance for other platforms.
- Include cross-platform troubleshooting steps and explicitly state when a step is only applicable to Windows.
- Add Linux/macOS examples for common tasks, such as checking codec installation, managing file permissions, and troubleshooting Unity projects.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/unity/manipulate-models/manipulate-models.md
...tutorials/unity/manipulate-models/manipulate-models.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Windows-centric tools and frameworks such as Visual Studio, Unity, and the Mixed Reality Toolkit (MRTK), which are primarily developed and supported on Windows. There are no examples or instructions for Linux users, and no mention of Linux-compatible alternatives for development, debugging, or interaction. The documentation assumes the user is working in a Windows environment, particularly with references to Visual Studio error messages and Windows-specific links (e.g., /windows/mixed-reality/mrtk-unity).
Recommendations
- Add explicit notes about Linux support for Unity and Azure Remote Rendering, including any known limitations or requirements.
- Provide alternative instructions for Linux users, such as using Rider or VS Code instead of Visual Studio, and clarify how to resolve or ignore similar errors in those environments.
- Include Linux-specific setup steps or troubleshooting tips, especially for installing dependencies and running Unity projects.
- Reference cross-platform or Linux-friendly alternatives to MRTK or clarify MRTK's compatibility with Linux.
- Where possible, use neutral language (e.g., 'your IDE' instead of 'Visual Studio') and avoid linking only to Windows-specific documentation.
- If certain features are Windows-only, clearly state this and suggest workarounds or alternatives for Linux users.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/tutorials/unity/view-remote-models/view-remote-models.md
...torials/unity/view-remote-models/view-remote-models.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. It lists Windows SDK and Visual Studio as required prerequisites, and all platform-specific instructions and screenshots are for Windows (Universal Windows Platform, Windows icons, HoloLens, etc.). There are no Linux or macOS equivalents provided for setup, tooling, or build instructions, and no mention of cross-platform alternatives or limitations. The workflow assumes a Windows development environment throughout.
Recommendations
- Clearly state platform support at the top (e.g., 'This tutorial is for Windows only' or 'Linux/macOS support is limited').
- If Linux/macOS are supported, provide equivalent setup instructions (e.g., required SDKs, compatible IDEs like Rider or VS Code, Unity setup for those platforms).
- Include notes or sections for non-Windows users, outlining any limitations or alternative steps.
- Avoid assuming the use of Windows-specific features (e.g., Universal Windows Platform, HoloLens) unless the product is truly Windows-exclusive.
- Where possible, provide cross-platform code and configuration examples, or explicitly mention when a step is Windows-only.
- Add Linux/macOS-specific troubleshooting or caveats if certain features are unavailable.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/how-tos/conversion/configure-model-conversion.md
...ering/how-tos/conversion/configure-model-conversion.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits a mild Windows bias, primarily through the exclusive mention of Windows-specific texture compression formats (BC1/BC7) and a direct link to Microsoft's Windows Direct3D documentation. There are no explicit Linux or cross-platform alternatives or references. However, the rest of the documentation is generally platform-agnostic, focusing on JSON configuration and 3D model concepts.
Recommendations
- When referencing texture compression formats, mention cross-platform equivalents (such as OpenGL/GL_EXT_texture_compression_s3tc or Khronos documentation) alongside or instead of Windows/Direct3D links.
- Clarify whether the described conversion process and file formats are supported equally on Linux, macOS, and Windows, or note any platform-specific considerations.
- If there are command-line tools or scripts involved in the broader workflow, provide both Windows (PowerShell/CMD) and Linux (bash) examples.
- Avoid linking exclusively to Windows-specific documentation when discussing general concepts; provide neutral or cross-platform references where possible.
Remote Rendering
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/remote-rendering/quickstarts/deploy-to-quest.md
...ticles/remote-rendering/quickstarts/deploy-to-quest.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation implicitly assumes a Windows environment by instructing users to 'open a command prompt' without mentioning Linux or macOS terminals. No Linux-specific instructions or examples are provided, and there is no mention of platform differences in using adb or setting environment variables.
Recommendations
- Explicitly mention that the instructions apply to Windows, and add equivalent instructions for Linux (and optionally macOS), such as 'open a terminal' instead of 'open a command prompt'.
- Provide example adb commands for Linux, and note any differences in path handling or permissions.
- Include instructions for setting environment variables on Linux (e.g., editing .bashrc or .profile) as well as Windows.
- Use cross-platform language (e.g., 'terminal or command prompt') and clarify any OS-specific steps.