> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/azure-cdn-configuration-guide.md).
# Azure CDN Configuration Guide
### Implementation steps
#### Step 1:
Go to your website Front Door configuration
***
#### Step 2:
Choose origin groups → Add origin
***
#### Step 3:
Set any name, uncheck Enable health probes
***
#### Step 4:
Select Add an origin
***
#### Step 5:
Fill in origin details:
1. Set any name
2. Set Origin type = Custom
3. Set Hostname as following: hash of the JENTIS container as subdomain + . + website domain, e.g. [hash.yourwebsitedomain.com](http://hash.yourwebsitedomain.com/)
4. Press Add
***
#### Step 6:
Go to Rule Sets → Add Routing Rule:
1. Set name
2. Set Condition: if Request URL Value Contains /hash (hash of the JENTIS container)
3. Set Action: Overwrite origin group = Yes, Origin group you created in the previous step, Forwarding protocol = Match the incoming request, Caching = Disabled
4. Save
***
#### Step 7:
Go to Front Door configuration panel and choose edit the website route
***
#### Step 8:
Add the rule from the previous step and press Update
{% hint style="danger" %}
After enabling Cookie lifetime extender, the DCP will give a proxy code that is expected to be setup on `https://domain.*/hash` however, if it is set up on `https://www.domain.*/hash` it will cause a CORS Error on the Cookie Lifetime Extender Requests.
For more details on WWW configuration follow this [guide](https://docs.jentis.com/key-features/cookie-lifetime-extender/configure-your-tracking#www-configuration-guide-optional).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/azure-cdn-configuration-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
