IoT Central

The tutorial exclusively uses Azure CLI commands and shell scripting syntax that is compatible with Bash (Linux/macOS) and PowerShell (Windows), but all examples are shown in Bash syntax. There is no explicit mention of Windows-specific tools (like PowerShell), nor are there any examples tailored for Windows users. However, the documentation does not provide any Linux/macOS-specific notes or troubleshooting, nor does it clarify cross-platform nuances (such as environment variable syntax differences). The Azure CLI is cross-platform, but the documentation assumes Bash shell usage, which may create friction for Windows users who use PowerShell or CMD.

• Add explicit notes clarifying that Azure CLI works on Windows, Linux, and macOS.
• Provide example commands in both Bash and PowerShell syntax, or add a toggle/switch for shell type.
• Include troubleshooting tips for common cross-platform issues (e.g., environment variable syntax differences).
• Mention that Windows users may need to use PowerShell or CMD and provide equivalent commands.

The documentation page demonstrates a mild Windows bias. While most instructions are platform-agnostic, code blocks are labeled as 'cmd/sh' but contain only cross-platform commands (git, npm) without explicit Linux/macOS terminal examples. The sample output shown in the terminal references 'Windows_NT', and the workflow assumes usage of VS Code and F5 for debugging, which is more common on Windows. There are no explicit Linux/macOS instructions, screenshots, or troubleshooting notes.

• Provide explicit Linux/macOS terminal examples or clarify that the commands work cross-platform.
• Show sample terminal output from a Linux or macOS environment, or note that output may differ.
• Mention alternative editors or debugging methods for Linux/macOS users (e.g., running 'npm start' or 'node device.js' instead of F5 in VS Code).
• Clarify that the sample code and workflow are cross-platform and provide troubleshooting tips for non-Windows users if needed.

The documentation provides example commands for Azure CLI and Azure PowerShell, with PowerShell examples included as a dedicated tab. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its inclusion as a first-class example may suggest a Windows-centric approach. There are no explicit Linux/macOS-specific instructions, and the ordering of examples (portal, CLI, then PowerShell) is neutral but the presence of PowerShell examples may create a slight Windows bias.

• Clarify that Azure CLI works on Linux/macOS and provide installation instructions for those platforms.
• Explicitly mention that PowerShell Core is available on Linux/macOS if relevant, or provide Bash shell examples for Linux users.
• Add troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, package managers).
• Ensure screenshots and UI references are not Windows-specific.
• Consider adding a Bash script example for resource creation to demonstrate Linux parity.

The documentation provides parallel examples for Azure portal, Azure CLI, and Azure PowerShell throughout, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is presented in dedicated tabs and code blocks. There is no explicit mention of Linux/macOS alternatives to PowerShell, nor any guidance for users who may not have PowerShell available. In some sections, PowerShell is referenced for tasks that could be completed with cross-platform tools, and the presence of 'ms.custom: devx-track-azurepowershell' suggests a PowerShell focus. However, Azure CLI examples are present and shown before PowerShell, mitigating the bias somewhat.

• Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
• Add notes clarifying that PowerShell examples are primarily for Windows users, and suggest Bash or shell scripting alternatives for Linux/macOS.
• Where PowerShell is used for role assignments or resource queries, provide equivalent Bash/CLI commands.
• Review and minimize references to Windows-specific tools unless necessary; ensure parity in example depth and clarity for CLI and PowerShell.
• Consider adding a section or FAQ for Linux/macOS users outlining recommended tools and installation steps.

The documentation references PowerShell and Azure CLI together in multiple places, and lists PowerShell before CLI, which may suggest a Windows-first orientation. There are no explicit Linux/macOS examples or tool recommendations, and PowerShell is highlighted as a primary tool for administration. No Linux-specific instructions or parity notes are provided.

• Provide explicit Linux/macOS examples alongside PowerShell, especially for command-line tasks.
• List Azure CLI before PowerShell, or present both equally, to avoid Windows-first impression.
• Mention that Azure CLI is cross-platform and provide installation/use guidance for Linux/macOS.
• Add notes or sections clarifying tool availability and usage on non-Windows platforms.
• Include screenshots or walkthroughs for Linux/macOS environments where relevant.