Integration · Identity

HailBytes + Microsoft Entra ID

Single sign-on and automated user lifecycle from your existing Azure AD tenant.

What you get

  • Enterprise SSO via OIDC or SAML 2.0 on both HailBytes SAT and ASM — users sign in with their existing corporate credentials, with your Conditional Access policies applying as normal.
  • SCIM 2.0 auto-provisioning. Create, update, and deactivate users automatically from the Entra directory, with group push mapped onto HailBytes RBAC roles.
  • Leavers actually leave. For security awareness training this matters more than usual — a stale roster means campaigns sent to departed employees and completion rates that misreport the workforce you actually have.
  • Per-tenant identity boundary. On multi-client MSP deployments each tenant brings its own IdP configuration.

Supported on both AWS and Azure Marketplace deployments. Both products run single-tenant in your own cloud account, so the Entra connection is between your directory and your instance — no third-party hop.

Also available on the Microsoft side: Sentinel for detection, Teams for notifications, and the Outlook Phish Reporter add-in for one-click user reporting.

SCIM recipe → SSO recipe → All identity integrations →