Document Details
Create Custom Policy Definition
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for discovering policy aliases, but it lists Azure PowerShell after Azure CLI and does not provide any explicit Linux-specific guidance or examples. The use of PowerShell is emphasized, and there are no references to Linux shells or tools, nor is there any mention of platform differences in command usage. The document assumes the reader is comfortable with PowerShell and the Azure Portal, both of which are more familiar to Windows users. There is also no mention of Bash, shell scripting, or Linux-specific environments, and the clean-up instructions are portal-centric, omitting CLI-based deletion steps.
Recommendations
- Include explicit Bash/Linux shell examples alongside PowerShell and Azure CLI, especially for common tasks like discovering aliases or managing policies.
- Clarify that Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide any necessary notes about differences in command syntax or authentication (e.g., az login in Bash).
- Add instructions for deleting policy definitions and assignments using Azure CLI commands, not just via the Azure Portal UI.
- When listing tools or command-line options, avoid always listing PowerShell after CLI, and consider grouping by platform or providing parallel examples.
- Mention that VS Code and Azure CLI are cross-platform, and provide links or notes for Linux/macOS installation if relevant.
- Where possible, provide guidance for users working in Linux environments, such as using Azure Cloud Shell (Bash) or local Bash terminals.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-09-11 00:00 | #108 | completed |
Clean
|
| 2025-08-11 00:00 | #77 | completed |
Clean
|
| 2025-08-10 00:00 | #76 | completed |
Clean
|
| 2025-08-09 00:00 | #75 | completed |
Clean
|
| 2025-08-08 00:00 | #74 | completed |
Clean
|
| 2025-08-07 00:00 | #73 | completed |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
In the results, we see an alias supported by the storage accounts named `supportsHttpsTrafficOnly`. This existence of this alias means we can write the policy to enforce our business requirements! ### Azure PowerShell In Azure PowerShell, the `Get-AzPolicyAlias` cmdlet is used to search for resource aliases. Filter for the `Microsoft.Storage` namespace based on the details we got about the Azure resource earlier.