Integrations

Connecting Microsoft 365

Microsoft 365 is a deep integration and one of the three highest-leverage first connections. One OAuth approval lights up identity, email, and collaboration evidence at once.

What you get

Once M365 is connected, Radius360 receives:

  • User and license inventory. Every user with their license, sign-in activity, and MFA status.
  • Conditional Access policies. What policies exist, who they apply to, and what they enforce.
  • Secure Score. Microsoft's overall security score broken down by control area, pulled into the Posture Score.
  • Exchange Online. Transport rules, anti-phish configuration, DKIM and DMARC posture.
  • SharePoint and OneDrive. External sharing settings, sensitivity labels, DLP policies.
  • Teams. External access, meeting policies, app permissions.
  • Intune. Device compliance, disk encryption coverage, OS patch state (if Intune-managed).

Framework controls addressed:

  • SOC 2 CC6.1, CC6.6, CC6.7 (logical access, external protection, data in motion)
  • ISO 27001:2022 A.5 (Organizational), A.8 (Technological) — access management, communications security
  • NIST CSF 2.0 PR.AA (Identity & Access), PR.DS (Data Security), PR.PS (Platform Security)
  • HIPAA 164.308, 164.312 (for tenants handling PHI)

Prerequisites

  • Microsoft 365 Global Admin or Security Admin role
  • M365 Business Premium, E3, or E5 (some signals require E5; the integration tells you which)
  • About 5 minutes

Connecting Microsoft 365

  1. 1
    Open Integrations, find Microsoft 365, click Connect.
  2. 2
    You are redirected to Microsoft's consent screen. Review the requested scopes (all read-only) and click Accept. You must be signed in as a Global Admin or Security Admin to grant tenant-wide consent.
  3. 3
    After consent you are redirected back. The integration status goes to Syncing. First sync is typically 5 to 10 minutes.
  4. 4
    Once Connected, open the Evidence Vault and filter Source to Microsoft 365. You will see a batch of evidence artifacts tagged with the specific controls they satisfy.

Grant consent at the tenant level, not per user

The Accept button has two options on many screens: "Consent on behalf of your organization" and a user-level option. Pick the tenant-level option. Otherwise only your own account data flows through, not the whole tenant.

Entra (Azure AD) vs M365

Radius360 has two Microsoft integrations: Microsoft 365 and Microsoft Entra (the new name for Azure AD). They overlap but focus on different data.

Microsoft 365 is focused on productivity: Exchange, SharePoint, OneDrive, Teams, Secure Score, Intune. It includes basic identity signals through Graph API.

Microsoft Entra is focused on identity: users, groups, Conditional Access, sign-in logs, risky users, risky sign-ins, Privileged Identity Management.

If you want the full picture, connect both. They do not conflict. Entra handles identity risks; M365 handles collaboration and email evidence.

Troubleshooting

Consent screen denied. The signing-in user does not have the admin role required. Sign in as a Global Admin and retry.

Some data is missing (e.g., risky sign-ins). Requires an M365 license that includes Azure AD Premium P2. Upgrade the license or use what is available on your current tier.

Secure Score is 0. Microsoft computes Secure Score on a delay after tenant creation. For new tenants, give Microsoft 24 to 48 hours to populate, then re-sync.

For connection issues, email support@radius360.co or ask the GRC Assistant.