198
Pages Scanned
23
Pages Flagged
198
Changed Pages
11.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-07 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 198
Files Completed: 198
Problematic Pages
24 issues found
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tooling references are for Visual Studio (Windows), with no mention of Linux/macOS alternatives. PowerShell and Package Manager Console examples are provided, but no equivalent CLI or cross-platform instructions. There are no examples for deploying from Linux/macOS, nor guidance for using cross-platform tools like VS Code, Azure CLI, or dotnet CLI.
Recommendations
- Add instructions and examples for deploying the ASP.NET app using cross-platform tools such as VS Code, Azure CLI, and dotnet CLI.
- Provide guidance for Linux/macOS users, including how to set up the sample project, connect to Azure SQL Database, and manage migrations using CLI tools.
- Include screenshots and steps for VS Code or other cross-platform editors.
- Offer SQL command examples using Azure CLI or sqlcmd for Linux/macOS, not just PowerShell.
- Clarify which steps are Windows-only and provide alternatives where possible.
Create Pull Request
API Management
Add a Custom CA Certificate - API Management | Microsoft Docs
...api-management/api-management-howto-ca-certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI, Bash, or Linux/macOS-compatible methods. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used.
- Mention Bash or shell scripting alternatives where applicable.
- Clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide instructions if so.
- Ensure REST API usage is documented for certificate upload, as REST APIs are platform-agnostic.
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation references enabling DDoS IP Protection via a linked page that is PowerShell-focused, which is typically Windows-centric. There is no mention of Linux/macOS CLI alternatives or parity in the main instructions, and the PowerShell method is referenced before any CLI or portal-based options. However, the primary instructions use the Azure portal, which is cross-platform.
Recommendations
- Add Azure CLI examples for enabling DDoS IP Protection, alongside PowerShell instructions, to ensure Linux/macOS users have clear guidance.
- Explicitly mention that PowerShell commands can be run on Linux/macOS (via PowerShell Core), or provide equivalent Azure CLI commands.
- Where possible, link to documentation that covers both PowerShell and Azure CLI methods, or update the referenced page to include CLI instructions.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides step-by-step instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively features PowerShell examples for CLI-based operations, with no equivalent instructions for Azure CLI (cross-platform) or Bash scripting. PowerShell is presented as the primary scripting tool, and there are no Linux/macOS-specific examples or guidance. This creates friction for users on Linux/macOS who may prefer or require Azure CLI or Bash.
Recommendations
- Add Azure CLI examples alongside PowerShell for all CLI-based operations, such as creating resource groups, managed identities, and API Management instances.
- Explicitly mention that Azure CLI is supported and provide links to relevant Azure CLI documentation.
- Ensure that scripting instructions are not Windows-centric and clarify cross-platform compatibility.
- Consider including Bash script snippets or references for ARM template deployments.
Medium Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section requires installation of Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS alternatives. This creates friction for non-Windows users who wish to use Hybrid Connections for outbound access from Azure App Service.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative outbound connectivity options for Linux/macOS users.
- Add examples or guidance for Linux App Service users, especially in sections where Windows-specific tools are referenced.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows examples (C#, Java) are presented first and in detail, with explicit code for accessing certificates from the Windows certificate store. Linux guidance is less prominent and often deferred to external documentation, especially for non-.NET languages. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are described in depth, while Linux and cross-platform approaches are less thoroughly covered.
Recommendations
- Provide Linux and cross-platform code examples (e.g., Python, Node.js, Java, PHP) for loading certificates, not just C#.
- Present Linux and Windows examples side-by-side or in parallel tabs, rather than Windows-first.
- Expand the 'Load a certificate from a file' section with concrete Linux and containerized app examples, including code for common languages.
- Clarify when guidance is Windows-specific and offer equivalent Linux instructions where possible.
- Reference Linux tools and patterns (e.g., OpenSSL, Linux environment variables) alongside Windows tools.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is evidence of Windows bias: Windows-specific paths (e.g., D:\home) and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS) are mentioned frequently and often before Linux equivalents. Windows terminology and examples (such as referencing Windows time zones, IIS, and .bat files) appear throughout, sometimes without Linux alternatives or with Linux details added as secondary notes. Build automation and logging sections are Windows-centric, with Linux (Oryx) build configuration presented as a separate tab, but less detailed. Some environment variables and explanations are Windows-only, with Linux coverage sometimes limited or appended.
Recommendations
- Ensure Linux examples and paths (e.g., /home) are given equal prominence alongside Windows ones, especially in introductory tables and explanations.
- Where Windows tools (e.g., msbuild, Web Deploy) are referenced, provide Linux equivalents or clarify when features are Windows-only.
- Expand Linux-specific build automation and logging documentation to match the detail provided for Windows/Kudu.
- Avoid presenting Windows terminology (paths, tools, config files) first unless the feature is Windows-only; use neutral or dual-platform language.
- Add explicit Linux/macOS guidance for configuring environment variables and app settings where currently only Windows instructions are given.
Low Priority
View Details â
Detected Bias Types
windows_first
windows_tools
minor_windows_patterns
Summary
The documentation is generally cross-platform, but there are subtle Windows biases. Windows file paths and environment variables (e.g., `%HOME%`, `D:\home\site\wwwroot`) are shown first or exclusively in some examples. The use of Kudu DebugConsole and references to FTP upload methods are described with Windows-style paths. The documentation mentions both Azure CLI and PowerShell for automation, but PowerShell is listed second. Linux equivalents are present (e.g., `/home` directory), but Windows patterns are more prominent.
Recommendations
- Where file paths are shown (e.g., `_backup.filter` location), provide both Windows and Linux examples, such as `D:\home\site\wwwroot\` and `/home/site/wwwroot/`.
- When referencing environment variables, clarify both `%HOME%` (Windows) and `$HOME` (Linux).
- In sections describing access via Kudu or FTP, mention Linux/macOS tools and path conventions.
- Ensure that CLI examples are equally applicable and clarify any OS-specific nuances.
- Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands. However, PowerShell examples are shown immediately after Bash, and the PowerShell formatting is explicitly called out as 'Formatted for PowerShell', which may indicate a slight preference for Windows environments. There is no explicit Linux/macOS bias, but the presence of PowerShell examples and their formatting may create minor friction for non-Windows users.
Recommendations
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows.
- Consider labeling Bash examples as 'Linux/macOS' and PowerShell as 'Windows' for clarity.
- Ensure Bash examples are always shown first to reinforce Linux parity.
- Add a note that Azure CLI works cross-platform and Bash is recommended for Linux/macOS.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files. However, PowerShell (a Windows-centric tool) is featured equally alongside Azure CLI, and PowerShell requirements are mentioned in the prerequisites. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, though it is available on Linux/macOS. The order of examples does not strongly favor Windows, but the inclusion of PowerShell as a primary option may create mild friction for Linux/macOS users.
Recommendations
- Clearly indicate that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, highlighting that Azure CLI works natively and is preferred.
- Consider showing Azure CLI examples first, or adding a brief note about PowerShell's cross-platform availability.
- Ensure that any referenced prerequisites or setup instructions for PowerShell include Linux/macOS guidance if PowerShell is to be used.
API Center
Perform API Linting and Analysis
...ain/articles/api-center/enable-api-analysis-linting.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both bash and PowerShell command examples for Azure CLI operations, but PowerShell syntax is often shown immediately after bash, and Visual Studio Code instructions reference Windows keyboard shortcuts and folder paths first. Output examples use Windows-style paths (e.g., C:\Users\<user>\AppData\Local\Temp), and Visual Studio Code instructions reference Windows conventions. However, all critical steps are cross-platform, and Linux/macOS users can complete the tasks without friction.
Recommendations
- Ensure output examples use generic or cross-platform paths, or provide both Windows and Linux/macOS output samples.
- When referencing Visual Studio Code, include macOS/Linux keyboard shortcuts and clarify folder navigation for all platforms.
- Alternate the order of bash and PowerShell examples, or explicitly state that both are supported equally.
- Add explicit notes about Linux/macOS compatibility for Azure Functions Core Tools and Azure CLI steps.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are consistently shown immediately after Bash, and are explicitly labeled as 'Formatted for PowerShell.' This creates a slight Windows bias, as Linux/macOS users may expect Bash examples to be prioritized or exclusively shown. However, both platforms are covered, and the Azure CLI is cross-platform.
Recommendations
- Clearly label Bash examples as 'Linux/macOS' and PowerShell as 'Windows' to help users identify the relevant section.
- Consider showing Bash examples first, or grouping them together before PowerShell examples, to reinforce Linux parity.
- Add a brief note clarifying that Azure CLI commands work on all platforms, and that Bash is the default shell for Linux/macOS users.
- If possible, provide a toggle or tabbed interface for users to select their preferred shell (Bash or PowerShell), reducing clutter and bias.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template, but PowerShell is mentioned alongside CLI throughout, and the PowerShell example is given equal prominence. There is no explicit Linux/macOS bias, but PowerShell is a Windows-centric tool (though available on Linux/macOS), and the documentation does not mention Bash or shell scripting alternatives. The Azure Cloud Shell is referenced, which is cross-platform, but the focus remains on CLI and PowerShell.
Recommendations
- Clarify that Azure PowerShell is available on Linux/macOS, not just Windows.
- Add Bash or shell scripting examples for template deployment, or explicitly state that Azure CLI commands work on Linux/macOS.
- Mention that Azure Cloud Shell can be used from any OS, and highlight its cross-platform nature.
- Consider providing a table or section that summarizes deployment options for Windows, Linux, and macOS users.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides detailed PowerShell examples for backup and restore operations, with PowerShell shown first in each example section. While Azure CLI and REST API examples are also included, the PowerShell focus and ordering may create friction for Linux/macOS users, as PowerShell is primarily associated with Windows environments. However, Azure CLI and REST API examples ensure Linux parity for all critical operations.
Recommendations
- Consider presenting Azure CLI examples before PowerShell, or at least alternating the order, to avoid implicit Windows-first bias.
- Explicitly note that Azure CLI and REST API methods are fully supported on Linux/macOS, and clarify PowerShell's cross-platform availability if relevant.
- Add a brief section explaining that all operations can be performed on Linux/macOS using Azure CLI or REST, and that PowerShell Core is available cross-platform if users prefer.
- Ensure that any references to installing PowerShell mention PowerShell Core for Linux/macOS, not just Windows PowerShell.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides instructions primarily through the Azure Portal and Azure CLI, with a brief mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI example, and no explicit Windows-only tools or patterns are prioritized. All command-line examples use Azure CLI, which is cross-platform. There are no PowerShell-heavy sections, and Linux parity is generally maintained. However, Azure PowerShell is mentioned before 'other Azure tools', which could be seen as a minor 'windows_first' bias.
Recommendations
- When mentioning Azure PowerShell, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide explicit examples for both Azure CLI and Azure PowerShell only if there are significant differences or if PowerShell is required for certain operations.
- Consider listing Azure CLI as the primary tool for scripting and automation, with PowerShell as an alternative for Windows users.
- Add a note that all Azure CLI commands work on Linux, macOS, and Windows.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides links for creating an Azure Kubernetes cluster using Azure CLI, Azure PowerShell, and Azure portal, with PowerShell (a Windows-centric tool) mentioned before the portal. However, all deployment and operational examples use cross-platform tools (kubectl), and no Windows-specific commands or tools are prioritized or exclusively used. There are no missing Linux/macOS examples, and the workflow is platform-neutral after cluster creation.
Recommendations
- List Azure CLI (cross-platform) before Azure PowerShell in the prerequisites to avoid subtle Windows-first ordering.
- Explicitly note that all kubectl commands work on Linux, macOS, and Windows.
- If possible, provide links to Linux/macOS-specific guidance for AKS cluster creation, or clarify that Azure CLI is recommended for cross-platform use.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all key steps, but PowerShell is featured equally alongside CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific instructions or considerations, and PowerShell examples are given in every section, which may create friction for Linux/macOS users who typically use Azure CLI. However, Azure CLI examples are present and shown first in each case.
Recommendations
- Add a brief note clarifying that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider including a section or callout for Linux/macOS users, highlighting that all CLI commands work natively on those platforms.
- If possible, add links or references to installing Azure CLI on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but Azure PowerShell is most commonly used on Windows.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation is structured to cover both Windows and Linux custom containers in Azure App Service, with clear pivots for each platform. However, in several cross-platform sections, Windows/PowerShell examples are consistently presented before Linux/Bash equivalents, and some advanced configuration and diagnostic sections are more detailed for Windows. PowerShell commands are provided alongside Bash, but often Windows terminology and tools (e.g., C:\home, IIS, .NET Framework) are mentioned first or in more depth. Linux parity is generally good, but the ordering and emphasis may create friction for Linux users.
Recommendations
- In cross-platform sections, alternate the order of Windows and Linux examples, or present Linux examples first where appropriate.
- Ensure that all advanced configuration and troubleshooting topics have equally detailed Linux sections, especially for diagnostics and persistent storage.
- Where possible, avoid Windows-centric terminology in general sections (e.g., refer to '/home' before 'C:\home' in shared storage explanations).
- Add more Linux-specific troubleshooting and best practices, matching the depth provided for Windows.
- Consider using tabs or collapsible sections for command-line examples, so users can easily select their platform.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is largely platform-neutral and does not provide command-line examples or tooling instructions specific to any OS. However, in the 'Related content' section, a link to 'Connect virtual networks from different deployment models using PowerShell' is given, and no equivalent Linux/CLI/Bash example is referenced or prioritized. This subtly prioritizes Windows/PowerShell as the default automation approach.
Recommendations
- In the 'Related content' section, add or prioritize links to equivalent Azure CLI or Bash-based guidance for connecting virtual networks, ensuring Linux/macOS users see their options equally.
- Where PowerShell is referenced, clarify that equivalent steps can be performed using Azure CLI, and provide links or notes to such documentation.
- Review related guidance to ensure Linux/macOS users are not implicitly directed to use Windows/PowerShell tooling for common network tasks.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation is focused on a feature (gateway-required virtual network integration) that is explicitly Windows-only, as stated in the prerequisites. However, the troubleshooting and example commands (e.g., Test-NetConnection, netstat -aon) are Windows/PowerShell-centric, and there are no equivalent Linux/macOS commands or guidance. The use of Windows tools is presented without alternatives, and PowerShell/Windows commands are shown exclusively.
Recommendations
- Clearly state at the top that this feature is Windows-only, which is already done, but consider making this even more prominent.
- In troubleshooting sections, provide equivalent Linux/macOS commands (e.g., use 'nc' or 'telnet' for TCP connectivity, 'ss' or 'netstat' for port checks) where possible, since users may be diagnosing from non-Windows VMs.
- When referencing tools like 'tcpping' or 'Test-NetConnection', mention cross-platform alternatives or note that these are Windows-specific.
- If any steps can be performed from Linux/macOS (e.g., updating routes, checking connectivity from a Linux VM), provide those examples as well.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides example commands for Azure portal, Azure CLI, and Azure PowerShell in all procedural sections. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented alongside CLI and portal examples. In most cases, PowerShell examples are given equal prominence to CLI, but sometimes appear before CLI. There are no Linux-specific tools or shell examples (e.g., Bash, scripting), and no explicit mention of Linux/macOS user experience. However, the documentation does not rely solely on Windows tools, and all critical tasks can be completed using Azure CLI, which is cross-platform.
Recommendations
- Ensure Azure CLI examples are always presented before Azure PowerShell examples, as CLI is cross-platform.
- Explicitly state that Azure CLI works on Linux/macOS and is recommended for non-Windows users.
- Consider adding Bash shell scripting examples for common migration tasks, or clarify that Azure CLI commands can be run in Bash.
- If PowerShell is included, clarify its cross-platform availability (PowerShell Core) or note any limitations for Linux/macOS users.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC role assignment, but PowerShell is featured equally and sometimes before Linux-native tools. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, while Linux tools (OpenSSL) are also included. However, Windows export instructions are more prominent and linked, and PowerShell is given as a primary automation example alongside CLI. The FAQ and automation sections mention PowerShell and CLI, but do not reference Bash or Linux-specific scripting. Overall, Linux users can complete all tasks, but Windows tools and patterns are mentioned first or equally, creating minor friction.
Recommendations
- Include Bash scripting examples for certificate automation alongside PowerShell and CLI.
- Provide explicit instructions for certificate export from macOS/Linux (e.g., using Keychain or OpenSSL), not just Windows tools.
- When listing automation options, mention Azure CLI and Bash first, then PowerShell, to reduce Windows-first bias.
- Add links to Linux/macOS certificate management documentation where Windows tools are referenced.
- Clarify that all steps can be performed on Linux/macOS, and highlight any OS-specific differences.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides a balanced overview of Azure App Service Plans, explicitly supporting both Windows and Linux. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (e.g., PowerShell, RDP, .NET Framework) are described first and exclusively, with clear mention that this feature is Windows-only. No Linux-specific examples or parity features are discussed in this section, but this is appropriate given the feature's current Windows-only status. Elsewhere, the documentation does not show bias; both OS options are referenced equally.
Recommendations
- For the Managed Instance section, clarify upfront that this is a Windows-only feature and that Linux support is not available, which is already done.
- Where possible, provide links or notes about Linux alternatives or roadmap if relevant (e.g., if Managed Instance for Linux is planned).
- Ensure that general sections (outside Windows-only features) continue to reference both Windows and Linux equally, and provide OS-specific guidance where necessary.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides parity for Azure portal, Azure CLI, ARM templates, and programming languages (.NET, JavaScript, Python, Java), but PowerShell examples are prominent and often shown alongside or before CLI examples. PowerShell is a Windows-centric tool, and its heavy inclusion may create friction for Linux/macOS users. Additionally, PowerShell is referenced in some CLI tabs (e.g., az identity create) with 'azurepowershell-interactive' code blocks, which could confuse non-Windows users. However, Azure CLI and ARM template instructions are present throughout, and most critical tasks can be completed cross-platform.
Recommendations
- Ensure all CLI code blocks use the correct 'azurecli-interactive' language tag, not 'azurepowershell-interactive', to avoid confusion.
- Where PowerShell is used, clarify its cross-platform availability (PowerShell Core) or recommend Azure CLI as the primary cross-platform tool.
- Consider showing Azure CLI examples before PowerShell, or explicitly note that PowerShell is optional and CLI is preferred for Linux/macOS.
- Add explicit notes or links for Linux/macOS users if any step is Windows-specific.
- Review and update any PowerShell-heavy sections to ensure CLI parity and clarity.