> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blindsight.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Intune

> Let the console read your Microsoft Intune tenant to see which devices run the agent, and optionally deploy, update and remove the agent from the console.

Connect Intune links a Microsoft Intune tenant to your workspace. It does two
separate things, each behind its own approval in Microsoft:

| Tier | What it does | Who approves it in Microsoft |
| - | - | - |
| **Read** | Lists the Windows and Mac devices Intune manages, matches each to a Blindsight device, and shows which ones do not run the agent yet. Changes nothing in your tenant. | A Global Administrator or Privileged Role Administrator |
| **Deploy** | Creates one app in your Intune, assigns it to groups you choose, and later updates it or sets it to uninstall. Needs read first. | A Global Administrator or Privileged Role Administrator |

You find it at **Endpoint → Configurations → Intune**. The page has two tabs,
**Devices** and **Configuration**. Deploy lives on the **Configuration** tab.

For the same rollout without the connection, see
[Deploying with Intune](https://docs.blindsight.io/endpoint/fleet-rollout.md#deploying-with-intune), which
covers the `.intunewin` package and the manual app.

## Who can do what

| Permission | Lets the user |
| - | - |
| `endpoint.devices.view` | See the Intune page, the device list and the rollout figures. |
| `endpoint.intune.manage` | Connect and disconnect the tenant, ask for a sync, change how the tenant is read, and build the `.intunewin` package. The package carries an enrollment token, so building it also needs `endpoint.devices.manage`. |
| `endpoint.intune.deploy` | Approve deploy access, search groups, and deploy, update, retry or remove the app. |

The `admin` and `endpoint-admin` roles hold both Intune permissions. See
[Endpoint permissions](https://docs.blindsight.io/endpoint/permissions.md).

> [!NOTE]
>
> Connecting and deploying do not ask for a two-factor code in Blindsight.
> Access is the signed-in session and the permission. Connecting, setting
> changes, deploys, updates and removals are written to the
> [audit trail](https://docs.blindsight.io/compliance/audit-trail.md).

## The two Microsoft applications

Blindsight reaches your tenant through two Microsoft Entra applications that
Blindsight owns. Both are multitenant and **publisher-verified**, so Microsoft's
consent screen shows a verified publisher and no "unverified" warning.

| Application | Graph application permissions |
| - | - |
| **Blindsight Endpoint for Intune** (read) | `DeviceManagementManagedDevices.Read.All`, `DeviceManagementApps.Read.All`, `DeviceManagementConfiguration.Read.All` |
| **Blindsight Endpoint for Intune (deploy)** | `DeviceManagementApps.ReadWrite.All`, `GroupMember.Read.All` |
| **Blindsight Intune fixes** | `DeviceManagementConfiguration.ReadWrite.All`. Asked for only when you use a [policy fix](#policy-fixes-for-the-wintun-block). |

* **No client secret exists.** Blindsight proves itself to Microsoft with a
  certificate. The private key is held in AWS KMS and only the separate runner
  service can use it. The API never signs.
* **One tenant per workspace.** Consent is pinned to the tenant that signed in,
  and a tenant can be linked to one Blindsight workspace at a time. If yours is
  already linked to another workspace, the page says so and gives a support
  reference.
* **The deploy application only ever touches the app it created.** It cannot
  list, change or delete any other app.

Install status needs `DeviceManagementApps.Read.All`. Without it the device list
still works and the install column reads **Not read yet**.

`DeviceManagementConfiguration.Read.All` lets Blindsight read your device
installation policies, so it can tell whether one blocks the Wintun adapter.
It reads policies and changes nothing. A tenant connected before this
permission existed approves it once with
[Approve more access](#approve-more-access). Until then the policy check reads
**Cannot check** and the rest of the page works as before.

### What Blindsight reads

* Device name, operating system and version.
* Serial number and Entra device ID, to match a device to its Blindsight agent.
* The user assigned to the device, only where the workspace names its people.
* When the device last checked in with Intune.
* Whether the Blindsight app is installed on each device, from Intune's app
  install status. Blindsight lists your Win32 apps by name and publisher and
  keeps only its own.

## Connect the tenant

**1. Open the Intune page**

**Endpoint → Configurations → Intune**, then **Connect Intune**. You need
`endpoint.intune.manage`.

**2. Sign in with an account from your tenant**

Microsoft's sign-in opens in the same tab. This proves which tenant you are
connecting. Use an account that belongs to the tenant, not a personal
Microsoft account.

**3. Wait a few seconds**

Blindsight shows **Checking your Microsoft sign-in** and then sends you on to
Microsoft's permissions page for the tenant you signed in to. You are not
asked to sign in again.

**4. Approve read access**

A Global Administrator or Privileged Role Administrator approves the read
application once. Blindsight shows **Recording the approval** and returns to
the Intune page.

**5. Wait for the first sync**

The Intune page shows the four stops, **Sign in**, **Approve**, **Read
devices** and **Roll out**, and the steps of the first read: **Permissions
verified**, **First sync**, **Matching**, **Install status**, **Ready**. You
can leave the page. It continues by itself.

> [!WARNING]
>
> **Only two Microsoft roles can approve.** Microsoft lets a Global
> Administrator or a Privileged Role Administrator grant tenant-wide consent
> for Microsoft Graph application permissions. An Intune Administrator, an
> Application Administrator or a Cloud Application Administrator cannot, and
> Microsoft's screen then asks for an administrator.

### Connecting with one Microsoft approval

When one approval is available for your workspace, the steps above shrink to a
single Microsoft screen. **Connect Intune** opens Microsoft's permissions page
once. After the administrator approves, Blindsight confirms the tenant with a
quiet sign-in in the background, shows **Confirming with Microsoft**, and then
connects. If Microsoft finishes that sign-in as a different account, the page
offers one more sign-in with the right account. The roles that can approve, the
approval by email and the page's wording for a sign-in that does not finish are
the same as above. A tenant that is already connected is not asked again.

### If you are not one of the two roles

Sign in with your own account anyway. Blindsight proves the tenant, and
Microsoft refuses the approval for your account. The page then shows **Approval
needed from a Microsoft administrator** and says that a Global Administrator or
Privileged Role Administrator approves it once. Nothing is connected. Select
**Try again with another account**, or ask an administrator to connect.

### A sign-in that does not finish

* **You left Microsoft's page open or closed the tab.** The Intune page shows
  **Finish signing in to Microsoft**, and after two minutes **Sign-in not
  finished**. Select **Continue in Microsoft** or **Start again**. A person
  without the Intune permission is told that someone who manages Intune can
  continue it.
* **You selected Cancel at Microsoft.** The page reads **Sign-in was cancelled.
  Nothing was connected.** and offers **Connect Intune**.
* **You approved in a different tenant than you signed in to.** Nothing is
  connected. Select **Start again**.
* **The connection took longer than 10 minutes.** Nothing is connected. Select
  **Start again**.
* **Another administrator started a connection.** The page says who and when.
  Select **Take over** to replace their attempt with yours.

### Approval by email

**Approval needed** also offers **Send the request** and **Copy the link**. They
let you pass the approval to a Global Administrator or Privileged Role
Administrator who does not use Blindsight:

* The approver needs no Blindsight account and no two-factor code in Blindsight.
* The address must be on your tenant's verified domain or on a domain your
  workspace already uses. Free mailbox domains do not count.
* The link works once and expires after 24 hours.
* **Cancel request** withdraws a request that has not been approved yet.

### Approve more access

Blindsight adds a read permission now and then. A tenant connected earlier keeps
working without it, and the **Microsoft Graph** section on the **Configuration**
tab lists each permission as **Granted**, **Not granted** or **Not checked**.
When an optional permission is **Not granted**, **Approve more access** appears
next to the list. Select it, and a Global Administrator or Privileged Role
Administrator approves the missing permission at Microsoft. Existing tenants
approve `DeviceManagementConfiguration.Read.All` this way, once, to enable policy
checks. Nothing already granted is removed, and the page updates by itself when
Microsoft passes the approval on. Needs `endpoint.intune.manage`.

## Read the tenant

### Sync

Blindsight reads the device list every four hours by default. Choose 1, 4, 12 or
24 hours on the **Configuration** tab, or start a sync from the page. While a
deployment is running the page reads every 15 minutes.

### Settings under Reading devices

| Setting | Choices | What it does |
| - | - | - |
| **Devices** | Every managed device, or devices matching a filter | The filter is an OData expression, for example `startswith(deviceName,'LT-')`. Microsoft checks it before Blindsight uses it. |
| **Sync interval** | 1, 4, 12, 24 hours | How often Blindsight reads Intune. |
| **Device owner** | Primary user, Last signed-in user, Not matched | How a device is linked to a person. Last signed-in user needs one more Microsoft permission and is unavailable until then. |
| **Removed devices** | Delete after 30 days, Delete right away, Keep until disconnect | What happens to a device Intune no longer lists. Applies at the next complete sync. |
| **Include personal devices** | Off or on | Off by default: only company-owned devices are expected to run Blindsight. |

### Matching and the figures

A device matches strongly by its Entra device ID or its serial number. It matches
by host name only when the name is unique on both sides, and the match then reads
**Weak, by hostname only**.

| Figure | Meaning |
| - | - |
| **Devices** | Windows and Mac devices Intune manages. |
| **Matched to people** | Devices Blindsight can link to a person. |
| **Fully protected** | Blindsight is running with full protection now. |
| **Protection reduced** | The Blindsight agent is running, but part of its protection is off. The reason is on each device. |
| **No agent or not reporting** | In Intune, with no Blindsight agent, or an agent that is not reporting. |

The three lower figures add up to **Devices**. A device is counted once.

The sentence at the top of the page says which group needs you first. For example
"2 devices in Intune have no agent or are not reporting." If every device is fine
it reads "Every device Intune lists is fully protected." Under it, a line puts the
groups in words: "7 of 10 devices are fully protected. 1 has reduced protection
(device installation is blocked by policy). 2 have no agent or are not reporting
(1 is offline, 1 of those last reported full protection)."

The group of devices with no agent or not reporting includes agents that are
offline. An offline agent is never called "no agent". **Deploy to N devices
without Blindsight** reaches only the devices that have no agent. When the exact
targets are not known, the button reads **Deploy to N devices with no agent or not
reporting**.

When there are devices with reduced protection, the page offers **Review N devices
with reduced protection**. It opens the **Devices** tab on that group, with the
reason on each row.

A workspace that has not received the three-way split from the platform yet shows
two figures, **Fully protected** and **Not fully protected**, in place of the three.
**Not fully protected** is everything that is not fully protected.

A figure that cannot be read reads as withheld, or as unavailable with a date,
never as 0.

The **Devices** tab filters by **All**, **Fully protected**, **Protection reduced**,
**No agent or not reporting**, **Not fully protected**, **Not reporting**,
**Removed** and **Personal**, and sorts by device name or last check-in. The agent
column reads **Running**, **Protection reduced**, **Not reporting** or **Missing**. In a
workspace that shows only counts, a figure for a group of fewer than five is
withheld. See [Who is named in the console](https://docs.blindsight.io/endpoint/who-is-named.md).

> [!NOTE]
>
> Reading changes nothing in your tenant. **Disconnect** sits at the top of the
> Intune page, in the status line of the connection, and asks you to confirm. It
> removes access on the Blindsight side. To finish, delete the Blindsight
> application under **Enterprise applications** in your own Microsoft tenant. The
> page links there.

## Every change is previewed first

Blindsight never writes to your Intune until you have seen exactly what it will
write. Deploy, update, uninstall, remove, retry and a policy fix each open the
preview in place before the button that confirms. The preview lists:

* What Blindsight **creates, uploads, changes, assigns or removes**, one line per
  change, with its details and the groups it targets.
* The **tenant** it writes to.
* **Not touched**: what stays as it is, such as assignments you added in Intune.
* **Undo**: how to take the change back.
* **Show the requests sent to Microsoft**, which opens the requests as they are
  sent.

The confirmation covers that exact plan. If anything Blindsight would write
changes after you read the preview, nothing is written. The page shows the new
preview and you confirm that one. The plan you confirmed is kept in the
[audit trail](https://docs.blindsight.io/compliance/audit-trail.md).

## Deploy the agent

Deploying is a second approval, shown only when read access works. It lets
Blindsight create, assign, update and remove one app in your Intune.

**1. Approve deploy access**

On the **Configuration** tab, under **Deploy with Intune**, select **Approve
deploy access**. Like connecting, it runs in the same tab: Microsoft's sign-in,
then its permissions page, then back to the deploy section of the
**Configuration** tab. A Global Administrator or Privileged Role Administrator
approves the deploy application in Microsoft. If Microsoft does not give
approval, the section says so. Needs `endpoint.intune.deploy`.

**2. Choose a pilot group**

Search your security groups by name (two letters or more). The list shows
each group's device and user counts. Pick a **device** group: the install
needs no one signed in, and shared hosts such as multi-session Azure Virtual
Desktop take device assignments only. Start with a small pilot group.

**3. Confirm**

The dialog names the group and its device count. Confirming creates the app
**Blindsight Endpoint** in your Intune and assigns it as **Required**. The
agent enrols with a token of its own, named `Intune deploy, <group>` in the
token list, where you can revoke it.

**4. Watch the rollout**

The page follows each step as it runs, then every device in the group.

Each device reads one of these words:

| Word | Meaning |
| - | - |
| **Waiting for Intune** | Targeted, Intune has not started. |
| **Installing** | Intune is running the installer. |
| **Installed, not enrolled** | The app is on the device and the agent has not enrolled yet. |
| **Enrolled** | The agent enrolled with this deployment's token. |
| **Protected** | Enrolled and inspecting. |
| **Already protected** | The device ran Blindsight before the deployment. It is counted in the heading line (for example "6 devices targeted, 2 already protected") and is not counted as enrolled by the deployment. |
| **Failed** | Intune reports an error. The row gives the code and its meaning. |
| **Removed as intended** | Uninstalled by an undeploy. |

### Update

**Update** publishes the current installer as a new content version of the same
app, refreshes its detection rules and description, and assigns it again. Tick
**Also issue a new enrollment token** to replace the token. The old one is revoked
once the update is live.

The agent also updates itself, so Update is not what keeps the fleet current. It
raises the version the detection rule asks for. A device on an older agent reads
as not installed and Intune updates it. A device that already updated itself stays
detected and is left alone.

> [!NOTE]
>
> An app created before the October 2026 release keeps its old return codes,
> disk-space floor and information links until you remove it and deploy again.
> Update refreshes only the detection rules, the description and the content.

### Uninstall or remove

Select **Uninstall or remove**. There are two choices:

* **Uninstall from devices.** Changes the assignment to **Uninstall** for the
  group. Intune runs `uninstall.cmd` on each device. The app stays in Intune
  until you remove it. For this assignment the detection rule becomes the
  registry key alone, so a device on an old agent, or with a half-old install, is
  uninstalled too.
* **Remove the app only.** Deletes the app Blindsight created. Devices that
  already have the agent keep it. The deployment's enrollment token is revoked.

When the workspace [requires an uninstall code](https://docs.blindsight.io/endpoint/uninstall.md#uninstall-codes),
Intune cannot supply one and every device would report the uninstall as failed.
Authorize the devices first (**Endpoint → Devices**, select them, **Authorize
removal**), then tick the box in the dialog to confirm you understand.

**Withdraw deploy access** stops Blindsight from deploying, updating or removing
anything. Reading stays connected. A Microsoft administrator then deletes the
deploy application from the tenant.

### Assignments you added in Intune are kept

Intune's assign call replaces every assignment of an app, so Blindsight reads the
current assignments first and sends them all back. On deploy, update and undeploy
it changes only the groups you chose in Blindsight:

* Groups you added in Intune, exclusion groups, all-devices assignments and their
  own settings go back as they were.
* Assignment filters are kept. Blindsight reads the assignments through the
  Microsoft Graph beta endpoint for this, and that is switched on. If the beta
  endpoint is ever off, a filter you added in Intune is neither seen nor kept, so
  check the assignment in Intune after an update if you rely on filters.
* If Blindsight cannot read the assignments, the step stops with
  `assignments_unreadable` and sends nothing.
* If you change the intent of the group Blindsight manages, Blindsight sets it
  back to **Required**, or to **Uninstall** on an undeploy. An exclusion of the
  same group Blindsight includes is refused by Intune, and the step fails with
  Intune's message.

## The app Blindsight creates

| Field | Value |
| - | - |
| Name and publisher | **Blindsight Endpoint**, publisher `Blindsight` |
| Install command | `install.cmd`, a plain cmd script in the package |
| Uninstall command | `uninstall.cmd` |
| Install behavior | **System** |
| Device restart behavior | Determine behavior based on return codes. The install uses `/norestart`. |
| Operating system | Windows 10 version 1809 or later |
| Architecture | x64. The same app installs on Windows 11 on ARM64, which runs x64 programs. It was applicable and installed on a real ARM64 device. |
| Free disk space | 2 GB (2048 MB). A device with less reads **Not applicable** in Intune. |
| Information and privacy links | `https://docs.blindsight.io` and `https://blindsight.io/privacy` |
| Enrollment token | Inside the package, never in the install command |

### Detection

Intune requires every manual detection rule to be met. The app has two:

1. File `C:\Program Files\Blindsight\BlindsightAgent.exe`, **String (version)**,
   greater than or equal to the version being deployed, not associated with a
   32-bit app on 64-bit clients.
2. Registry key
   `HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\UpgradeCodes\EB2308B1879234F408A2A3011B6815F5`
   exists, not associated with a 32-bit app.

The version rule means a broken or half-updated install reads as not detected and
Intune runs the install again, which repairs it. The key rule means files left by a
broken uninstall do not read as installed. Detection never uses the ProductCode,
which changes with every version.

### Return codes

| Code | Intune treats it as | What it means |
| - | - | - |
| `0` | Success | Installed or removed. |
| `1707` | Success | Windows Installer reports success. |
| `3010` | Soft reboot | The install is done and Windows reports a restart as pending. No restart is forced. Some upgrades with files held open return it although the install is complete. |
| `1641` | Hard reboot | The installer started a restart. The command line uses `/norestart`, so this is rare. |
| `1618` | Retry | Another installation was running. Intune tries again. |
| `7001` | Failed | The platform refused the enrollment token (expired, revoked or unknown). `install.cmd` waits up to 120 seconds after the installer returns for the agent to say whether it enrolled, and exits `7001` in about 40 seconds when it was refused. Update with **Also issue a new enrollment token**. |

Any other code is a failure, because Intune treats a code it has no rule for as one.
The usual one is `1603`: a downgrade, a disk that is full, an uninstall that needs a
code, or an uninstall attempted in the three minutes a new uninstall mode takes to
apply. See [Uninstalling the agent](https://docs.blindsight.io/endpoint/uninstall.md).

## Before you deploy

On managed machines, prepare these first. Each is covered on
[Fleet rollout](https://docs.blindsight.io/endpoint/fleet-rollout.md):

* [App Control and AppLocker allow rules](https://docs.blindsight.io/endpoint/fleet-rollout.md#locked-down-powershell-and-app-control)
  for the Blindsight signer and its issuing authority.
* [Device installation restrictions](https://docs.blindsight.io/endpoint/fleet-rollout.md#device-installation-restrictions)
  that allow the Wintun adapter.
* [Outbound access and proxies](https://docs.blindsight.io/endpoint/fleet-rollout.md#firewalls-proxies-and-tls-inspection),
  including the switch **Inspect traffic through a company proxy** on proxy networks.
* [Upgrades](https://docs.blindsight.io/endpoint/install.md#upgrades) briefly pause protection, so deploy
  outside working hours.

## Troubleshooting

| What you see | Why | What to do |
| - | - | - |
| **Approval needed from a Microsoft administrator** | Your account cannot grant tenant-wide consent. Nothing is connected. | Select **Send the request** or **Copy the link** for a Global Administrator or Privileged Role Administrator, or **Try again with another account**. |
| **This Microsoft tenant is already linked to another Blindsight workspace** | A tenant connects to one workspace only. | Disconnect it in the other workspace first, or contact support. |
| Microsoft asks you to pick an account twice | Microsoft shows its picker again on the approval step. Expected. | Pick the same account both times. |
| **Sign-in not finished** | The Microsoft tab was left open or closed. | Select **Continue in Microsoft** or **Start again**. An unfinished attempt expires by itself. |
| **Sign-in was cancelled. Nothing was connected.** | Cancel was selected at Microsoft. | Select **Connect Intune** again. |
| Someone else is connecting Intune | Another administrator has an attempt in progress. | Wait, or select **Take over**. |
| The approval link no longer works | It was used, is older than 24 hours, or the request was cancelled. | Send a new request from the Intune page. |
| The request cannot be sent to that address | The address is not on your tenant's verified domain or a domain your workspace uses. | Use the administrator's work address on one of those domains. |
| Devices missing or figures look low | Personal devices are left out by default, or a device filter excludes them. | Turn on **Include personal devices** or mark them corporate in Intune, check the filter, then start a sync. |
| Deploy access is not offered | Read access is not working yet, or your role lacks `endpoint.intune.deploy`. | Fix read access first, or ask an owner or admin. |
| Deploy fails with return code `7001` | The enrollment token in the app was refused: expired, revoked or unknown. | Select **Update** with **Also issue a new enrollment token**. |
| Agent installed but the device is not **protected** | A network or policy issue on the device, not Intune. | Read the reason on the device row and find it in [Device states](#device-states). |

### Device states

The **Intune** column on **Endpoint → Devices**:

| State | What it means | What to do |
| - | - | - |
| **Managed and installed** | Intune reports the Blindsight app installed. | Nothing. |
| **Pending** | Intune is still installing. | Wait. To speed it up, sync the device from Intune. |
| **Install failed** | Intune reports an error, with its code. The detail panel gives the meaning. | `7001`: select **Update** with **Also issue a new enrollment token**. `1618`: another install was running; Intune retries by itself. Other codes: check free disk space (2048 MB) and [Before you deploy](#before-you-deploy), then retry from the page. |
| **Managed** | Intune manages the device but reports nothing for the app. | Check the device is in an assigned group, then wait for the next sync. |
| **Not in Intune** | Intune lists no device with this Entra device ID or serial number. | Enroll the device in Intune, or start a sync if it enrolled recently. |

The **Protection** column:

| State | What it means | What to do |
| - | - | - |
| **Protected** | Every AI request on the device is inspected. | Nothing. |
| **Partly protected** | Some AI traffic is inspected, some is not. The row gives a one-line reason. | Find the reason in the table below. |
| **Not protected** | AI traffic goes around Blindsight. The row gives a one-line reason. | Find the reason in the table below. |
| **Starting** | The agent just enrolled or restarted and has not reported yet. | Wait a few minutes. |
| **offline** | No heartbeat for five minutes. | Check the device is on and can reach the Blindsight hosts on port 443. |
| **tampered** | The service was stopped, disabled or removed, or agent files changed. | Review the tamper event, then reinstall with **Update**. |

The words **Partly protected** and **Not protected** replace **degraded** and
**bypassed**. They are the same words the agent's own window shows.

The one-line reason on the row is short. The full sentence is in the row's
detail, in its tooltip and in the notices on the page. The reasons that have a
line of their own:

| Line on the row | Full reason |
| - | - |
| **Wintun blocked by policy** | Device installation is blocked by policy, so the network adapter whole-device protection needs cannot be installed. |
| **Adapter driver needed repair** | The agent tried to repair the network adapter driver. |
| **Whole-device protection down** | Whole-device protection is down, most likely because of VPN or other network software on the device. |
| **Company proxy bypasses inspection** | A company proxy setting sends AI sites around Blindsight. |
| **Unknown certificate issuer** | AI sites are re-signed by an issuer neither the device nor Blindsight trusts. |
| **Issuer not accepted yet** | AI sites are re-signed by an issuer the device trusts but Blindsight does not accept yet. |
| **Installed, not inspecting** | The agent reported it is installed but not inspecting, with no reason given. |
| **Protection impaired** | The agent reported impaired protection, with no reason given. |
| **Report out of date** | The agent claims protected, but the claim is older than the reachability window. |

### Why a device is not protected

The reason on the device row starts with one of these:

| Reason on the row | What it means | What to do |
| - | - | - |
| Device installation is blocked by policy | An Intune or Group Policy device installation restriction refuses the Wintun network adapter, so whole-device protection cannot start. | Allow the device ID `Wintun`. If a Prevent rule also matches it, turn on the layered order setting. See [Device installation restrictions](https://docs.blindsight.io/endpoint/fleet-rollout.md#device-installation-restrictions). The agent checks again when the policy changes, or within an hour. |
| AI sites are sent around Blindsight by a company proxy | A proxy is in the path and **Inspect traffic through a company proxy** is off. | Turn it on at **Endpoint → Policies → Default policy**. See [Proxies](https://docs.blindsight.io/endpoint/fleet-rollout.md#proxies). |
| A TLS inspector re-signs AI sites and its root is not trusted | A TLS inspection product sits in the path. The row names its issuer. | Put the inspector's root in the machine certificate store, or exempt the AI hosts from inspection. |
| Traffic into the tunnel is blocked (firewall rule, error 10013) | A firewall rule or a VPN kill switch refuses the agent's traffic. | Allow `BlindsightAgent.exe` in the firewall policy, or exclude it from the kill switch. |
| Windows will not load the network driver | Microsoft's vulnerable-driver blocklist, on by default in Windows 11, refuses the packet driver. Browsers and system-proxy apps are still inspected. | Keep the blocklist on. Allow the Wintun adapter so the whole-device lane covers the rest. |
| Network adapter driver needed repair; restart the device | The agent repaired the Wintun adapter. | Restart the device. |
| Network adapter driver needs repair, another product is using it | Another VPN or product holds the adapter. | Disconnect that product, then restart the device. |
| Network adapter driver needed repair and the repair did not hold | The repair failed. | Reinstall with **Update**. If it returns, send the device's diagnostics to support. |
| the whole-device tunnel helper is not running | Only apps that use the proxy settings are inspected until it restarts. | It restarts by itself. If the reason stays, restart the device. |
| the interceptor is not accepting on 127.0.0.1:47325 | The agent cannot listen on its local port. | Check no other program uses port 47325, then restart the device. |
| nothing is intercepting on this device | The agent is running but inspecting nothing. | Restart the device. If it stays, reinstall with **Update**. |
| agent files were modified on this device | Something changed the agent's installed files. | Review the tamper event, then reinstall with **Update**. |
| Scans are rate limited | The platform limited the device's scans. | Wait. If it continues, contact support. |

### The Wintun policy block notice

When devices are blocked by a device installation policy, the console shows one
notice for all of them. It appears on the Intune **Devices** tab and on
**Endpoint → Devices**, and draws nothing when the count is zero or unknown.

The notice has:

* A headline, for example "3 devices: Windows is blocking the Wintun adapter".
  Devices whose agent is not online right now are counted from their last report
  and named: "(1 not online right now, as last reported)".
* The exact setting to change. In Intune, open **System → Device Installation →
  Device Installation Restrictions** and add the hardware ID `Wintun` to **Allow
  installation of devices that match any of these device IDs**. A copy button
  copies `Wintun`.
* The layered order note, for when a **Prevent** rule also matches Wintun.
* That the devices recover on their own within the hour once the policy allows
  it. No reinstall is needed.
* A link to the steps in [Device installation restrictions](https://docs.blindsight.io/endpoint/fleet-rollout.md#device-installation-restrictions).

Devices that were revoked are not counted. In a workspace that shows only
counts, the figure is withheld when a group is smaller than five.

### Policy fixes for the Wintun block

Under the Wintun notice, **Check and fix from Intune** can check one group of your
deployment and, where one allow entry would change the result, create a single
separately named policy for it. The policy is added in your Intune and nowhere
else.

**1. Check a group**

Pick a group of your deployment and select **Check this group**. Blindsight
reads your device installation policies and says whether Windows blocks the
Wintun adapter on that group. It reads only. This needs the read permission
`DeviceManagementConfiguration.Read.All`; see
[Approve more access](#approve-more-access).

**2. Read the preview**

When a fix would help, the preview shows the policy it would create, its one
setting and value, and the group it is assigned to. **Your own policies, All
users and All devices are not touched.** When a fix would not help, the page
says why and writes nothing.

**3. Approve once**

The first time, you approve **Blindsight Intune fixes** at Microsoft and come
back to the same preview. Later fixes reuse the approval.

**4. Apply**

Confirming creates the policy and assigns it to the chosen group. Devices
take it at their next Intune sync, usually within the hour. Select **Check
again** afterwards to see the result.

An applied fix stays listed on the page with **Undo** after the devices recover and
the notice is gone, so you can still remove it later. If Blindsight could not write
the policy, the card says so and offers **Check again**.

**Undo and remove the policy** shows the exact removal in place first, and the
button there confirms it. The application behind the fixes can only manage the
policies Blindsight created. If its approval is withdrawn while a policy stands,
approve it again to undo the policy or to disconnect Intune. Where policy fixes
are not offered for your workspace, the notice shows the manual steps only.

## Known limits

* A seat stays used after an uninstall from Intune until the device has been quiet
  for 30 minutes, or until you revoke it. See
  [Retiring devices](https://docs.blindsight.io/endpoint/fleet-rollout.md#retiring-devices).
* Deploy options such as exclusion groups, an install deadline and user
  notifications are not set from the console yet. Set them in Intune. Exclusions
  and settings you add there are kept.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.