Document Details
Create Front Door Template
❌
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
Bias Types:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for deploying the ARM template, referencing PowerShell-specific cmdlets, and showing PowerShell output screenshots. While it briefly mentions that Azure CLI and REST API are alternative options, it does not provide any Linux-friendly (Bash/Azure CLI) examples or instructions, nor does it mention or show Linux terminal usage. The step-by-step deployment and cleanup instructions are exclusively tailored to Windows/PowerShell users.
Recommendations:
- Add equivalent Azure CLI (az) command examples for all deployment and cleanup steps, using Bash syntax.
- Include screenshots or output examples from Azure CLI/Bash terminals alongside PowerShell examples.
- Present both PowerShell and CLI examples in parallel, or provide a tabbed interface for users to select their preferred environment.
- Explicitly mention that the steps work on both Windows and Linux, and provide clear guidance for Linux/macOS users.
- Avoid using only PowerShell-specific cmdlets and terminology; ensure parity in instructions and explanations for both Windows and Linux users.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
Wait until you see the prompt from the console.
1. Select **Copy** from the previous code block to copy the PowerShell script.
1. Right-click the shell console pane and then select **Paste**.
1. Enter the values.
The template deployment creates an Azure Front Door with a web app as origin.
The resource group name is the project name with **rg** appended.
> [!NOTE]
> **frontDoorName** needs to be a globally unique name for the template to deploy successfully. If deployment fails, start over with Step 1.
It takes a few minutes to deploy the template. When completed, the output is similar to:
:::image type="content" source="./media/quickstart-create-front-door-template/front-door-standard-premium-template-deployment-powershell-output.png" alt-text="Azure Front Door Resource Manager template PowerShell deployment output":::
Azure PowerShell is used to deploy the template. In addition to Azure PowerShell, you can also use the Azure portal, Azure CLI, and REST API. To learn other deployment methods, see [Deploy templates](../azure-resource-manager/templates/deploy-portal.md).
## Validate the deployment
1. Sign in to the [Azure portal](https://portal.azure.com).
1. Select **Resource groups** from the left pane.
1. Select the resource group that you created in the previous section. The default resource group name is the project name with **rg** appended.
1. Select the Azure Front Door you created previously and you'll be able to see the endpoint hostname. Copy the hostname and paste it into the address bar of a browser. Press enter and your request will automatically get routed to the web app.
:::image type="content" source="./media/create-front-door-portal/front-door-web-app-origin-success.png" alt-text="Screenshot of the message: Your web app is running and waiting for your content.":::
## Clean up resources
When you no longer need the Azure Front Door service, delete the resource group. This will remove the Azure Front Door and all related resources.
To delete the resource group, call the `Remove-AzResourceGroup` cmdlet: