Skip to main content
Connect Intune links a Microsoft Intune tenant to your workspace. It does two separate things, each behind its own approval in Microsoft: 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, which covers the .intunewin package and the manual app.

Who can do what

The admin and endpoint-admin roles hold both Intune permissions. See Endpoint permissions.
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.

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.
  • 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. 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.
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

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. 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.
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.

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:

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.
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, 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

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

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.

Before you deploy

On managed machines, prepare these first. Each is covered on Fleet rollout:

Troubleshooting

Device states

The Intune column on Endpoint → Devices: The Protection column: 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:

Why a device is not protected

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

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.
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.
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.
  • 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.