> For the complete documentation index, see [llms.txt](https://docs.intuneassistant.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intuneassistant.cloud/intune-assistant/security-insights/worker-setup.md).

# Setup

## What it does

Security Insights needs two things before it is complete, and this page walks you through both.

1. **Access in your tenant.** The checks read your tenant with your own sign-in (users, administrator roles, domains, policies, Secure Score). An administrator has to approve that once for the whole tenant. This part is independent of the Worker, and the checks you start yourself need it too.
2. **Your Worker.** The scheduled check, the Exchange controls and the Devices page are collected by your Worker. This part shows whether the Security Insights package has reached your Worker, which permissions the Worker still needs, and gives you the script to assign them.

The page updates by itself, so you can leave it open while you work through the steps.

## How to use it

1. Open **Customer Settings** from your name in the menu, choose the **Modules** tab and open **Security Insights**, or select **Setup** in Security Insights. If a Worker of this tenant is not ready yet, a banner on every Security Insights page links here as well. See [Modules](https://docs.intuneassistant.cloud/intune-assistant/modules.md) for the overview of all your modules.
2. At the top, **Approve access in your tenant** shows the permissions Security Insights reads with. If it says *Needs approval*, choose **Approve access**. A Microsoft page opens where a Global Administrator (or Privileged Role Administrator) approves them. Come back to this page: the card checks again by itself when you return, and **Check again** does it right away.
3. Pick your Worker if you have more than one. The first one that still needs attention is selected for you.
4. Follow the step you are on:

| Step            | What you see                                                                           | What to do                                                                                                                                                                                                                                               |
| --------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Entitlement** | Security Insights is not active for this tenant                                        | Nothing here yet. Once the service is active, the page continues by itself                                                                                                                                                                               |
| **Worker**      | *Installing*, *Waiting for release*, *Worker update needed* or *Install failed*        | Wait about a minute for *Installing*. For *Worker update needed*, update the Worker. For *Install failed*, read the reason shown                                                                                                                         |
| **Permissions** | A list of roles, each *Granted*, *Missing* or *Assigned, not active yet*, and a script | Copy the script, save it as `grant-module-permissions.ps1` and run it with your tenant ID and the name of your Worker App Service. It opens a browser to sign you in, grants only what is missing and can be run again. Nothing else to do on the Worker |
| **Verify**      | *Assigned, not active yet*                                                             | Wait. A Worker keeps the access token it already has for up to 24 hours, and a restart does not renew it, so a new permission can take up to a day to show. The page updates by itself                                                                   |
| **Done**        | *Ready*                                                                                | Open Security Insights. The first scheduled check runs on the Worker; you can also start one yourself                                                                                                                                                    |

## What you will see

The roles are grouped by where they are granted: **Microsoft Graph**, **Office 365 Exchange Online** and **WindowsDefenderATP** (Defender for Endpoint). Each role shows its own state, so you can see exactly what is still missing after you ran the script. The page checks again every 15 seconds while it is open, and **Check again** does it right away.

## Requirements

* Security Insights is active for the tenant you have selected. If you manage several customers, the page shows the Workers of the customer you selected.
* A Global Administrator or Privileged Role Administrator to approve the access in your tenant (once per tenant).
* A Worker that is connected, approved and running.
* An administrator who may assign application roles: Application Administrator or Global Administrator. The script signs in by itself and installs the `Microsoft.Graph.Authentication` module for you if it is missing.
* For the Exchange controls the Worker's identity also needs the **Exchange Administrator** role in Entra ID.

## Common questions

**Where do I see whether my Worker has all the permissions it needs?** On the Worker itself. Its dashboard has a *Permissions* panel and a **Check Permissions** button, and the Worker tells the portal what it finds: under **Worker** a Worker with a gap gets a **Permissions** flag, and its detail page lists the roles. The Worker checks the roles of its own jobs and of the services it runs, such as Security Insights.

**The Security Insights overview says some data sources could not be read and that consent is required.** The access in your tenant has not been approved yet (or not for every permission). Open **Setup** and approve it in the first card. The next check reads the data.

**The script says "Assigned" but the page still shows the roles as not active.** That is expected for a while. The roles are assigned, but the Worker keeps the token it already has. Until the Worker's access token is renewed (up to 24 hours, and a restart does not speed it up) the page can show them as *Assigned, not active yet* or even *Missing*. It moves on by itself once the token is renewed.

**Which package does my Worker have?** The page shows the installed package version for each Worker, next to its state (*Installing*, *Install failed*, *Ready*). The Worker version is shown there too, and it follows the Worker as soon as it has restarted or updated.

**Can I use Security Insights without a Worker?** Yes. A check you start yourself reads with your own rights and needs no Worker. The Worker adds the scheduled check and the data only it can read.

**Do I have to change a setting on the Worker?** No. A Worker release contains what it needs to install Security Insights. It only installs the package while Security Insights is active for your tenant, and removes it again when the service ends.

**The page says "Waiting for release".** The package has not reached your update ring yet. Nothing to do on your side.
