> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/azure.md).

# Azure & DNS management

## Azure

We have credits for the Microsoft Azure cloud through their [non-profit program](https://nonprofit.microsoft.com/register). We use Azure resources for our projects if necessary / requested by the project team.

#### Admin&#x20;

* Billing page in azure portal: <https://portal.azure.com/#view/Microsoft_Azure_GTM/ModernBillingMenuBlade/~/Overview>
* Page that shows how much is left + usage breakdown: <https://www.microsoftazuresponsorships.com>&#x20;
* FAQs on nonprofit offer: <https://www.microsoft.com/en-us/nonprofits/faq#primaryR6>&#x20;

Azure has to be renewed every year (around February). We will receive instructions one month before expiry to <info@correlaid.org> (see FAQs).

## DNS management

DNS records are managed through Hetzner. Jonas or Leo can help you when you need to have a subdomain such as obs.correlaid.org pointing at your project / site or other DNS records (A, MX, CNAME, ...).

## FAQ

See [FAQ](/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/faq.md#cloud).


---

# 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.correlaid.org/~/revisions/T8G3F1S1kUWJiGQZsj4F/wiki/infrastructure/azure.md?ask=<question>&goal=<user_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.
