Azure CDN profiles and endpoints - Step-by-Step Execution

Process Flow - Azure CDN profiles and endpoints

Create CDN Profile

↓

Create CDN Endpoint

↓

Associate Endpoint with Profile

↓

Configure Endpoint Settings

↓

Deploy CDN Endpoint

↓

Serve Content via CDN

↓

Monitor and Update as Needed

This flow shows creating a CDN profile, adding endpoints, configuring them, deploying, and serving content.

Execution Sample

Azure

az cdn profile create --name myProfile --resource-group myGroup --location westus
az cdn endpoint create --name myEndpoint --profile-name myProfile --resource-group myGroup --origin www.example.com

Creates a CDN profile and an endpoint linked to an origin server.

Process Table

Step	Action	Resource Created/Modified	Result/State
1	Create CDN profile 'myProfile'	CDN Profile	Profile 'myProfile' created in resource group 'myGroup' at location 'westus'
2	Create CDN endpoint 'myEndpoint' linked to 'myProfile'	CDN Endpoint	Endpoint 'myEndpoint' created with origin 'www.example.com'
3	Associate endpoint with profile	CDN Profile and Endpoint	Endpoint 'myEndpoint' is part of profile 'myProfile'
4	Configure endpoint settings (e.g., caching rules)	CDN Endpoint	Settings applied to 'myEndpoint'
5	Deploy CDN endpoint	CDN Endpoint	Endpoint 'myEndpoint' deployed and ready to serve content
6	Serve content via CDN endpoint	CDN Endpoint	Content served from 'myEndpoint' caching origin content
7	Monitor and update endpoint as needed	CDN Endpoint	Endpoint status monitored and updated if required

💡 All steps completed; CDN profile and endpoint are active and serving content.

Status Tracker

Resource	Initial State	After Creation	After Configuration	After Deployment	Final State
CDN Profile 'myProfile'	Not exist	Created	N/A	Active	Active
CDN Endpoint 'myEndpoint'	Not exist	Created	Configured	Deployed	Serving content

Key Moments - 3 Insights

Why do we need both a CDN profile and an endpoint?

The profile is like a container for endpoints; endpoints define where and how content is delivered. Step 3 shows the association.

What happens if the endpoint is not deployed after creation?

Content won't be served via CDN. Step 5 shows deployment is necessary before serving content.

Can one profile have multiple endpoints?

Yes, a profile can have many endpoints to serve different origins or regions. This is implied in step 3 where endpoints associate with profiles.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the CDN endpoint configured?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Check the 'Action' column for configuration details.

According to the variable tracker, what is the state of 'myProfile' after creation?

A Active

B Configured

C Created

D Not exist

💡 Hint

Look at the 'After Creation' column for 'myProfile'.

If the endpoint is not deployed, what will be the final state of 'myEndpoint'?

A Serving content

B Configured

C Created

D Deployed

💡 Hint

Refer to step 5 and the variable tracker final states.

Concept Snapshot

Azure CDN uses profiles as containers for endpoints.
Endpoints define origins and delivery settings.
Create profile first, then add endpoints.
Configure and deploy endpoints to serve content.
Profiles can have multiple endpoints.
Deployment activates the endpoint for use.

Full Transcript

This visual execution traces the creation and deployment of Azure CDN profiles and endpoints. First, a CDN profile is created as a container. Then, an endpoint is created and linked to the profile, specifying the origin server. The endpoint is configured with caching and delivery settings. Deployment activates the endpoint, allowing it to serve content cached from the origin. Monitoring and updates ensure continued performance. Variables track the state changes of profile and endpoint from non-existence to active serving status.