> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-cloud-service-providers-in-delivery-shield/azure-server.md).

# Azure Server

Azure Server (Microsoft Azure Virtual Machines and server resources) provides scalable compute infrastructure for hosting, running, and managing applications and workloads in the cloud.

#### Usage of Azure in Delivery Shield

* Delivery Shield connects to Azure servers to assess the security posture of hosted workloads, identifying vulnerabilities, outdated packages, and insecure configurations on running instances.
* Servers are mapped to the applications and pipelines that deploy to them, so findings can be traced back to the services and releases they affect.
* Scan results feed into the overall security score and appear on the unified dashboard, giving teams a single view of risk across their Azure-hosted environments.

#### To Manage Azure Server:

1. Navigate to **Setup** > **Integrations**.
2. In the **Source** panel, click **Azure Server**.

<figure><img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FZBeYleEVPUfX0kVdKrPF%2Fazure%20server%20.png?alt=media&amp;token=5afa69a3-e288-4fdb-961c-033e0c6fd4bf" alt=""><figcaption></figcaption></figure>

3. The Azure integration page is displayed. Click **+New Account**.
4. In the popup that appears, enter the following details:

<figure><img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FKbmLe6hbYyo2V3Q7aRRV%2Fazure%20server%202.png?alt=media&amp;token=9ae40804-11f5-4690-981d-ca809be5c87e" alt=""><figcaption></figcaption></figure>

5. Enter the **Account Name, Host URL**, **Collection Name**, **Access Level, Auth Type** and **Token** values of your Azure Server account.
6. Select the **Teams** and the corresponding **Environments** from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can select up to 5 teams for the integration to be displayed.</p></div>

   * An example is given below for reference:

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuMZQzZsZQuulVdW9B9OuffNPoEXqbcpcAkYtKVyb7YiTQxbVIt1L4Gh-zshqX2J9MFKIat8x4oWFIGxdg3j1XVagyUNhUAlD_52soyMyd1cy53p6XiYi0LsTjIBfHcybRWl61?key=D9EXoOdGF7oYOBvYaW2GnRWJ" alt=""><figcaption></figcaption></figure>

   * In the example above,
     * If **Team 1**, **Team 2**, and **Team 3** are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as **Team 4**, will not have access to this account.
     * Even if the user who created this account is also an admin for **Team 4**, the integration account remains restricted and is not available for **Team 4**.
     * Access to the account is strictly limited to the specified **Teams** and **Environments** selected during account creation.
   * **For Organization Admins:**
     * When an **Organization Admin** creates an account without selecting specific **Teams** and **Environments**, the account will be universally applicable, granting access to **all teams** and **all environments** by default.
   * **For Team Admins with Multiple Teams:**
     * If a **Team Admin** who manages multiple teams creates an account without specifying particular **Teams** and **Environments**, the account will only be accessible to the teams for which the logged-in user holds admin privileges.
7. Click **Save**. The tool is connected.
8. To edit the entered values, click on the three dots provided in the **Actions** column. In the dropdown select **Edit**.
9. Re-enter the new values and click **Update**.

The new values get updated.