---
title: How to Install SHIELD
slug: how-to-install-shield
docTags: 
createdAt: 2026-08-24T13:15:10.792Z
---

:::hint{type="note"}
SHIELD is the data collection and processing layer that powers **Microsoft Insights**. If your organization plans to use Microsoft Insights, SHIELD must be installed and configured in your Azure environment using this installation guide. If you need help at any point, contact your IT or cloud team, or reach out to your SHI representative. For more details, see [Microsoft Insights](docId:4xqqX1w-YjA7vfNI0OL3-).
:::

# Overview

SHIELD is a self-hosted application deployed in a user's Azure App Service tenant. SHIELD collects and processes all necessary data exclusively within the organization's environment, then returns only abstracted and fully anonymized results back to SHI for reporting. This guide explains the installation prerequisites, how to install the SHIELD - Desktop application, and run your first scan.

***

# Installation Video

::embed[]{url="https://youtu.be/JEQB7EC4RTM?si=FakypykSh8Ufxcad"}

***

# Installation Prerequisites

## Pricing

:::hint{type="info"}
ℹ️ The table below provides estimated costs for the Azure resources required to deploy SHIELD. SHI does not control or manage these prices. The charges are based on the active time of the Azure App Service. However, SHIELD can be disabled post run to save cost. For more information, see [How to Uninstall SHIELD](docId\:J-hIgl0yHHTREtdZgvPD4).
:::

**Azure Cost Estimate associated (As of 9/25/2026)**

| **User Count**  | **Premium v4 Service Plan** | **vCPU(s)** | **RAM** | **Storage** | **Pay as you go** | **1 year savings plan**              | **3 year savings plan**              | **1 year reserved**                  | **3 year reserved**                  |
| --------------- | --------------------------- | ----------- | ------- | ----------- | ----------------- | ------------------------------------ | ------------------------------------ | ------------------------------------ | ------------------------------------ |
| \< 10,000 Users | P0v4                        | 1           | 4 GB    | 250 GB      | **$53.29**/month  | **$36.771**/month<br />\~31% savings | **$24.514**/month<br />\~54% savings | **$31.420**/month<br />\~41% savings | **$20.251**/month<br />\~62% savings |
| > 10,000 Users  | P1v4                        | 2           | 8 GB    | 250 GB      | **$106.58**/month | **$73.541**/month<br />\~31% savings | **$49.027**/month<br />\~54% savings | **$62.919**/month<br />\~41% savings | **$40.501**/month<br />\~62% savings |

***

## Disable Network Traffic Inspection

Network traffic inspection must be turned off for SHIELD and Microsoft endpoints on the device installing SHIELD. Major cloud service providers do not allow network traffic inspection of their services and SHIELD relies on Microsoft Azure networking. If inspection is not disabled, SHIELD will not install or function properly.

Every organization uses different equipment and processes, so the steps to disable inspection will vary.

**How to Proceed**:

- If you’re not sure how to disable network traffic inspection, please contact your networking team, security team, or the person in charge of information technology at your organization.
- You can also share the following network endpoints with your networking team to have the addresses excluded from inspection:
  - `https://api.shilab.com`
  - `https://url.shilab.com`
  - `https://*.azurewebsites.net` - *Your specific deployment URL (generated after deployment)*

**Common Network Traffic Inspection Technologies**

- **Firewalls** (Palo Alto, Fortinet, Cisco)
- **Secure Web Gateways (SWG) & Proxies** (Zscaler, ProxySG)
- **Cloud Access Security Brokers** (Netskope, Microsoft Defender for Cloud Apps)
- **Data Loss Prevention (DLP)** (Microsoft Purview DLP, Symantec DLP)
- **WAN Acceleration and Optimization** (Riverbed, Cisco WAAS, nginx caching)
- **VPN & Traffic Redirection** (VPN gateways, SASE platforms)

For more information about traffic inspection, see <u>[Network Traffic Inspection](https://url.shilab.com/network-traffic-inspection)</u>.

***

## Create a Dedicated Azure Subscription

1. Sign in to your Azure portal.
   - **Enterprise**: <u>[https://portal.azure.com/](https://portal.azure.com/)</u>
   - **Government**: <u>[https://portal.azure.us/](https://portal.azure.us/)</u>
2. Navigate to **Subscriptions** and click **+ Add**.
3. If applicable, choose an offer type from the options provided. **Enterprise Agreement (EA) customers** typically do not have to select an offer type.
4. Enter a name for the subscription (e.g., "SHIELD – Production") or similar.
5. **Enterprise Agreement (EA) customers**: Assign a billing account and confirm creation.

## Permissions

:::hint{type="info"}
**Installing User**: The user installing SHIELD must be a **Global Administrator** in order to grant Microsoft Graph application permissions via admin consent.

**Application**: SHIELD Desktop must be granted `Application.ReadWrite.All` and `AppRoleAssignment.ReadWrite.All` permissions by the user installing SHIELD or another admin.  For more information about permissions, see <u>[Application Permissions](https://url.shilab.com/application-permissions)</u>.
:::

1. Sign in to your Entra ID admin center.
   - **Enterprise**: <u>[https://entra.microsoft.com/](https://entra.microsoft.com/)</u>
   - **Government**: <u>[https://entra.microsoft.us/](https://entra.microsoft.us/)</u>
2. Navigate to **Roles & admins**.
3. Search for and click on the **Global Administrator** role.
4. If the user deploying SHIELD is already assigned the **Global Administrator** role, no additional action is required. If a user needs to be assigned the **Global Administrator** role, follow the steps below:
   - At the top, click **+ Add Assignments**.
   - Click the link under **Select member(s)**.
   - Check the box next to the desired user and click **Select**. You can also use the search bar if needed.
   - Select your desired settings. We recommend the following:
     - Assignment type: **Active**
     - Permanently eligible: Uncheck
     - Assignment duration: 24-48 hours
   - Click **Assign**.

***

## Azure Subscription Owner

Make sure the user installing SHIELD is the **Owner** on the Azure subscription in order to deploy resources.

1. Sign in to your Azure portal.
   - **Enterprise**: <u>[https://portal.azure.com/](https://portal.azure.com/)</u>
   - **Government**: <u>[https://portal.azure.us/](https://portal.azure.us/)</u>
2. Navigate to **Subscriptions** and select the subscription to be used with SHIELD.
3. Click **Access control (IAM)** in the left navigation bar.
4. Click on the **Role assignments** tab.
5. If the user deploying SHIELD is already assigned the **Owner** role of the subscription, no additional action is required. If a user needs to be assigned the **Owner** role, follow the steps below:
   - At the top, click **+ Add** and click **Add role assignment** in the drop-down menu.
   - Click on the **Privileged administrator** roles tab.
   - Click on the **Owner** role so it is highlighted and click **Next**.
   - Click **+ Select members**, click on the desired user account, and click **Select**.
   - Click **Next**.
   - Select **Allow user to assign all roles (highly privileged)**.
   - Click **Next**.
   - If applicable, select your desired Assignment type settings. We recommend the following:
     - Assignment type: **Active**
     - Assignment duration: **Permanent**
   - Once finalized, click **Review + assign**.
   - (Optional) Confirm the role appears in the **Role assignments** tab.

***

# Install and Deploy SHIELD

:::hint{type="info"}
**SHIELD Installation Has Changed**

The **SHIELD - Desktop** application is now the preferred method, for faster and easier installation.

**Why?** The desktop application automates most steps, making setup much simpler.
:::

1. Run the installer to set up SHIELD automatically using the following link: <u>[https://url.shilab.com/shield-install](https://url.shilab.com/shield-install)</u>
   - **Note**: The download will not work if network traffic inspection is enabled, especially in Microsoft/Azure environments.
2. After installation, launch the SHIELD - Desktop application.
3. Log in using the account manager in the top right corner. Be sure to log in with the account that has the necessary **Owner** and **Global Administrator** permissions in Azure. These are required to grant the necessary permissions for deployment.
4. After you are successfully logged in, click on the **Installer** module.
   - **Note**: An additional tab may open, and another log in may be required.
5. Select the **Azure Subscription** that is dedicated for SHIELD.
6. Select your desired **Azure Region** from the drop-down menu. **West US 3** is recommended, but other regions can be selected depending on company policy.
7. Click on the toggle switch to display **Advanced Options**.
8. For **Operation Mode**, select **Discover** from the drop-down menu.
9. Click on the **Deploy** button for the SHIELD installer to begin the installation process.
   - **Note**: An additional tab may open, and another log in may be required.
10. The installer will do the following:
    - Download the SHIELD Deploy ZIP file
    - Create a SHIELD App Service and managed identity in Azure
    - Upload and configure the SHIELD application, including permissions and security settings such as disabling basic auth, enabling encryption, and setting quantum-resistant cryptography.
11. After deployment, grant the following required permissions to the SHIELD managed identity in Azure:
    - `Application.ReadWrite.All`
    - `AppRoleAssignment.ReadWrite.All`
12. Lastly, assign the **Read and Write Everything** role to the user who will run SHIELD scans via the "SHIELD End User Login" enterprise app in Entra.
    - Sign in to your Entra ID admin center.
      - **Enterprise**: <u>[https://entra.microsoft.com/](https://entra.microsoft.com/)</u>
      - **Government**: <u>[https://entra.microsoft.us/](https://entra.microsoft.us/)</u>
    - Navigate to **Enterprise apps** in the navigation bar.
    - Clear out the **Enterprise Applications** filter.
    - Search for 'SHIELD End User Login' and click on the name of the application.
    - Click **Users and groups** in the left navigation bar.
    - Click **+ Add user/group**.
    - Click the link under **Users and groups**.
    - Check the box next to the desired user and click **Select**. You can also use the search bar if needed.
    - Click on the link under **Select a role**.
    - Search for 'Read and Write Everything', click on the name of the role, and click **Select**.
    - Click **Assign**.

***

# Running the SHIELD Web Instance

1. Sign in to your Azure portal.
   - **Enterprise**: <u>[https://portal.azure.com/](https://portal.azure.com/)</u>
   - **Government**: <u>[https://portal.azure.us/](https://portal.azure.us/)</u>
2. Navigate to **Subscriptions** and select the subscription dedicated to SHIELD.
3. Click **Resource groups**.
4. Click **SHIELD**.
5. Click on the App Service that starts with "shield-xxxxxxxxx" (the x's are a random set of lower-case letters and numbers).
   - **Deactivate Health Check (One time only)**
     1. Click on the link next to **Health Check**.
     2. Uncheck the box next to **Health Check** and click **Apply**.
     3. Click **Save**.
6. Click **Overview&#x20;**&#x69;n the left navigation bar.
7. In the top right corner, click on the **Default domain** link.
   - **Example**: shield-xxxxxx-xxxxxxxx.eastus-01.azurewebsites.net
8. Log in to the SHIELD web instance with the account that has the necessary Azure permissions.
9. Click on **Discover Module**.
10. Click **Start Report Collection** to start scanning the tenant environment.
11. Once the scan is complete, reports are available on the SHIELD web instance.
    - Click **Discover** in the left navigation pane and click **Overview**.

***

# Advanced Settings

## Azure Resource Tagging

Some Azure environments enforce governance policies requiring tags such as project, department, environment, etc. If required tags are missing, Azure rejects resource creation. SHIELD creates Azure resources during installation that must comply with these policies.&#x20;

- Installation failures related to Azure Policy may be caused by missing required tags. Verify your Azure tagging policies if your deployment fails.&#x20;
- Subscriptions with mandatory tagging policies must prepare required tag key-value pairs before installation, using the steps below. You will not be able to add resource tags after installation.

### Configure Tags in SHIELD Desktop

1. In the SHIELD - Desktop application, log in to the account that manages your Azure environment.
2. Click on the **SHIELD** **Installer&#x20;**&#x6D;odule. You can also click **Installer&#x20;**&#x69;n the left navigation pane. If you do not see the left navigation pane, click on the three horizontal lines in the top left corner.&#x20;
3. Navigate to **Advanced Settings&#x20;**&#x62;elow the **Deploy&#x20;**&#x62;utton and use the toggle to display **Advanced Options**.
4. Add a **Tag Key&#x20;**&#x61;nd the corresponding **Tag Value**.
5. Click on the + **Add Resource Tag&#x20;**&#x62;utton.&#x20;
6. Add additional key-value pairs as needed. You can also delete key-value pairs by clicking on the trash can icon if needed.&#x20;

**Note**: All tags entered are automatically applied to all Azure resources created by SHIELD.

**Example Table**

| **Tag Key** | **Tag Value** |
| ----------- | ------------- |
| project     | shield        |
| environment | production    |
| department  | security      |
| owner       | it-admin      |

