> For the complete documentation index, see [llms.txt](https://xedex.gitbook.io/internalpentest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xedex.gitbook.io/internalpentest/cloud-pentesting/azure/definitions-and-fundamentals.md).

# Definitions and fundamentals

**What is Microsoft Azure ?**

Microsoft Azure is a cloud computing platform by Microsoft. It's a combination of interoperable cloud computing services that include open-source and standards-based technologies. Most important of all, the Microsoft Azure platform also includes many proprietary solutions from Microsoft as well as other companies. 

**What does it offer ?**

In essence, it helps you build, deploy and manage applications.

**How does it work ?** 

Well,  Azure uses a technology known as **virtualization.** It separates the close coupling between a computer’s CPU or server and its operating system by means of an abstraction layer called a hypervisor. The hypervisor emulates all the functions of a real computer or server and its CPU in a virtual machine. You can run multiple virtual machines at the same time and each virtual machine can run any compatible operating system such as Windows or Linux.

**Azure** takes this virtualization technology and rethinks it on a massive scale in **Microsoft** data centres around the world. Therefore, the cloud is a set of physical servers in one or several data centres that run virtualized hardware on behalf of clients.

Each **server** includes a hypervisor to run multiple virtual machines.

A network switch provides connectivity to the servers. A server in each rack runs a special software called **Fabric Controller**. In turn, Each Fabric Controller is connected to another special piece of software known as the orchestrator.

**The orchestrator is responsible for managing everything that happens in Azure**, including responding to user requests. It assigns services, monitors the maintenance of the server and the services that run on it, and returns the servers to normal when an error occurs. Each instance of the **Fabric Controller** connects to another set of servers running orchestration software in the cloud, commonly known as a front-end. The front-end hosts the web services, the RESTful API and the internal **Azure** databases used for all functions that the cloud carries out.

**Azure services ?**

Here's a big-picture view of the available services and features in Azure.

![](/files/-MPVC29p5vNutGgU7WUp)

As we can see a lot of services are proposed.

If you want to know more about it, refer to the following link :

{% embed url="<https://docs.microsoft.com/en-us/learn/modules/intro-to-azure-fundamentals/tour-of-azure-services>" %}

If you also want to explore Azure cloud a little bit, you can sign up to a free acount, it includes:

* Free access to popular Azure products for 12 months.
* A credit to spend for the first 30 days.
* Access to more than 25 products that are always free.


---

# 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://xedex.gitbook.io/internalpentest/cloud-pentesting/azure/definitions-and-fundamentals.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.