![]() ![]() You can also attempt to access the static website hostname directly. If you see a different error page, wait a few minutes and try again. ![]() The hostname is emitted as an output from the deployment - the output is named frontDoorEndpointHostName. You can then access the Front Door endpoint. Once you have deployed the Azure Resource Manager template, wait a few minutes before you attempt to access your Front Door endpoint to allow time for Front Door to propagate the settings throughout its network. You can click the "deploy to Azure" button at the beginning of this document or follow the instructions for command line deployment using the scripts in the root of this repo. The following diagram illustrates the components of this sample. Note that you can use either the standard or premium Front Door SKU for this sample.Front Door profile, endpoint, origin group, origin, and route to direct traffic to the static website.This script only executes on the initial deployment of the template. A deployment script enables static website hosting on the storage account account.The following resources are deployed as part of the solution: Azure Storage However, if you need traffic flows to be restricted so that requests must come through Front Door, consider using the 201-front-door-premium-storage-blobs-private-link sample instead. If you are only using Front Door for features like caching and compression then this is not likely to be a concern. Note that in this sample, the storage account will still accept requests directly to the static website. This sample template creates an Azure Storage static website and a Front Door profile. This template deploys a Front Door Standard/Premium with an Azure Storage static website origin, using the public endpoint for the Azure Storage static website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |