Skip to main content
Back to the connector catalogue

Connector

Microsoft 365 / Entra ID

OAuth connection, authorised by the client in their own tenant.

Reads multi-factor authentication coverage, account hygiene, and — via Intune/Defender — the fleet of enrolled devices, their compliance, disk encryption and antivirus status.

01

What to create in the tool

The access is created in Microsoft 365 / Entra ID, not in Vigicap.

Where to generate it

The exact path through the vendor's console is not documented here to date. We are not describing it from memory: the vendor's own documentation is the authority.

Minimum role

The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.

02

What to enter in Vigicap

This connector asks for no additional field.

03

Per-client routing

The connection is made client by client: one credential per client, entered on that client's record. Nothing is shared between two clients, and disconnecting one leaves the other untouched.

04

What it does, and what it does not do

ISO 27001 controls covered

This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.

  • 5.9 Inventory of information and other associated assets
  • 5.10 Acceptable use of information and other associated assets
  • 5.11 Return of assets
  • 5.12 Classification of information
  • 5.14 Information transfer
  • 5.15 Access control
  • 5.16 Identity management
  • 5.17 Authentication information
  • 5.18 Access rights
  • 5.34 Privacy and protection of PII
  • 6.5 Responsibilities after termination or change of employment
  • 8.1 User endpoint devices
  • 8.2 Privileged access rights
  • 8.3 Information access restriction
  • 8.5 Secure authentication
  • 8.7 Protection against malware
  • 8.9 Configuration management
  • 8.12 Data leakage prevention
  • 8.19 Installation of software on operational systems
  • 8.23 Web filtering
  • 8.24 Use of cryptography
  • 8.27 Secure system architecture and engineering principles

ReCyF objectives it pre-fills

A reading feeds 4 objectives of the ANSSI ReCyF framework. It PROPOSES them: a level only counts once a consultant has confirmed it.

  • #1 Recensement des systèmes d'informationInventory of information systems
  • #9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code
  • #10 Gestion des identités et des accès des utilisateurs aux systèmes d'informationManagement of user identities and of user access to the information systems
  • #18 Sécurisation de la configuration des ressources des systèmes d'informationSecuring the configuration of information systems resources

Read-only

Vigicap writes nothing to the tool while reading.

How Vigicap handles your credentials.

Scopes requested

The exact scopes requested at authorisation, named as the vendor names them.

  • openid
  • profile
  • offline_access
  • https://graph.microsoft.com/User.Read.All
  • https://graph.microsoft.com/AuditLog.Read.All
  • https://graph.microsoft.com/DeviceManagementManagedDevices.Read.All
  • https://graph.microsoft.com/SecurityEvents.Read.All
  • https://graph.microsoft.com/SecurityAlert.Read.All
  • https://graph.microsoft.com/Policy.Read.All

Verification

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.

What this connector reads, exactly

  • Each account's MFA registration state, through Microsoft Graph — this is where MFA coverage and account hygiene come from.
  • The inventory of devices managed by Intune, and for each one its compliance state and its disk-encryption flag.
  • Defender XDR alerts, with their severity and their resolution status.
  • The tenant's count of conditional access policies, and its Secure Score.

What it does not read

No content. The nine scopes requested include neither Mail.Read, nor Files.Read, nor any access to Teams: a message, an attachment or a document belonging to your client is out of the connector's reach — technically, not merely by undertaking. The four scopes that carry the reading are User.Read.All, AuditLog.Read.All, DeviceManagementManagedDevices.Read.All and SecurityAlert.Read.All; the others serve authentication and policy reading.

What these signals do not prove

  • The compliance state says whether a device meets the policies this tenant configured. A tenant with no policy at all reports every device as compliant, which proves nothing — which is why compliance alone never reaches the top level.
  • Defender fields exist only for Windows devices. Antivirus coverage is therefore computed over the devices that actually reported a state, never over the whole estate: a Mac-heavy fleet would otherwise read as "antivirus missing".
  • Zero alerts is genuinely ambiguous and is treated as such. A quiet month and a tenant with no sensors onboarded are indistinguishable from here, so that case yields a middling level — never 0, which would accuse a clean tenant, never the maximum, which would credit a tenant watching nothing.
  • A count of conditional access policies says access is conditioned. It says nothing about whether the conditions are the right ones, who is excluded from them, or whether the break-glass account everybody creates is in scope.
Is Intune required for this connector to be useful?
No, but half of what it reads depends on it. Without Intune, MFA coverage and account hygiene are read normally; the device inventory, disk encryption and antivirus state stay empty.
Can the connector fix a non-compliance it finds?
No. No write scope is requested: all nine are read scopes, and remediation from Vigicap is impossible even if someone wanted it.
Who grants the access, and how is it withdrawn?
An administrator of your client's tenant, by OAuth consent granted inside that tenant. Revocation happens in Entra ID, without going through us and without telling us.