> For the complete documentation index, see [llms.txt](https://docs.arkannis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkannis.net/cloud/azure/courses/az900-course/cloud-models-and-cloud-types/cloud-types.md).

# Cloud Types

## Public cloud

* Azure owns the hardware on their network and infrastructure
* Open for everyone to sign up
* Renting services

## Private cloud

* Looks and acts like a cloud except the customer owns or leases or has exclusive access to the hardware
* Azure Stack - Software that is licensed to use a portal on your own private cloud

## Hybrid cloud

* Combination of public and private clouds
* Scale private infrastructure to the cloud

## Compare and Contrast:

#### Public cloud:

* MSFT owns the hardware and you are leasing services

#### Private cloud:

* Your hardware, more like a traditional on-prem build

#### Hybrid cloud:

* It's a mix between the two

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.arkannis.net/cloud/azure/courses/az900-course/cloud-models-and-cloud-types/cloud-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.