NG-Key
NG-Key
Identity cloud

Entra-ready joins plus M365 visit machinery — without parallel IAM theatre

Tenants configure Microsoft Entra ID beside day‑two automation: the same Microsoft ecosystem that provisions users can feed visitor workflows and API‑driven sync — so IT, reception, and physical security stop reconciling four exports every Monday.

Administrator‑guided Entra connection flows live under tenant integrations — credentials rotate through proper OAuth semantics instead of long‑lived passwords pasted into spreadsheets.

Microsoft 365 visit integrations expose status and sync triggers through the tenant API — automation can refresh calendar‑anchored visitor posture without an operator clicking through admin screens.

Workspace grants inherit cohort semantics you already curate for buildings and schedules — directory drift becomes visible in policy layers instead of surprising you at the reader.

Guest and contractor journeys stay distinguishable from employee posture — mixed‑mode campuses keep separation without duplicate guest databases.

When investigators ask “why was this person eligible then?”, answers trace through tenant identifiers readers already emitted — not reconstructed from screenshots.

Spotlight

What lands in product — not slideware

  • Microsoft Entra ID — first‑class tenant settings for directory alignment with governed connection and test flows.
  • Microsoft 365 visits API — integration status plus programmatic sync for calendar‑bound visitor programmes.
  • Group‑aware grants — facility areas and schedules inherit cohort intent operators recognise from IdP membership.
  • Lifecycle realism — joiners, movers, and leavers shrink stale door rights because identifiers stay coupled to workspace objects.
  • Audit‑friendly lineage — physical events and visitor projections share vocabulary with ledger‑adjacent exports.
  • Tenant isolation — integration scopes respect boundaries; surprises surface in automation logs instead of silent cross‑tenant bleed.
Abstract enterprise directory nodes linking to access surfaces — NG-Key integrations marketing tile

Depth

Capability depth buyers validate

Entra directory alignment

Connect Entra ID using tenant‑scoped settings — operators test connectivity before trusting automated joins.

M365 visits & automation hooks

Trigger and observe Microsoft 365 visit sync through permissioned tenant API endpoints — pair with reception workflows instead of shadow calendars.

People & cohort coupling

Project directory cohorts into grants and facility scopes — fewer spreadsheets naming “who counts as staff” per building.

Schedules + physical policy

Combine roster shifts with reader‑eligible windows — overtime and contractor exceptions stay narratable.

Governed overrides

Time‑bound exceptions carry rationale — reducing endless badge hacks stored outside the platform.

Evidence friendly exports

Align visitor rows, identity identifiers, and reader audits for investigations without reconstructing timelines manually.

Motion

Rollout operators recognise

01

Connect Entra

Validate tenant linkage, consent, and tests — prove directory reads before enabling automation.

02

Shape cohorts

Decide which directory groups drive facility scopes, contractor lanes, and visitor separation.

03

Wire M365 visits

Pilot calendar‑anchored visitor flows — observe API sync health before campus‑wide activation.

04

Observe drift

Review integration diagnostics weekly — fix roster drift before it appears as unexplained denials.

Outcomes procurement and IT defend jointly

Fewer reconciliation wars between HR directories, visitor desks, and physical security.

Automation replaces brittle scheduled CSV imports for identity‑adjacent workflows.

Regulators and insurers hear coherent identity narratives tied to reader evidence.

Security operations spend less time proving “which system was authoritative” after incidents.

Related reading

Continue in neighbouring hubs

Deep dives that pair naturally with this integration chapter.

Facility · Visitors

Reception and visitor chapters that benefit when Microsoft 365 visits stay aligned with indoor routing.

Open Workspace · Identity

People, vehicles, and cohorts once directory truth reaches NG‑Key grants.

Open Platform · Deployment & scale

Tenants, environments, and rollout discipline as integrations multiply across campuses.

Open

Product preview

Chapter walkthrough

Short cinematic clip for this integrations chapter — muted, looped in-page players follow your motion preferences elsewhere on the site.

Integrations hub

Every integration chapter at a glance

Open a chapter for full narrative and product video — identity cloud, smart-building bridges, and developer APIs.

Identity cloud

Identity cloud

Entra ID joins, Microsoft 365 visit API automation, and cohort semantics that match grants — no parallel IAM theatre.

Open
Smart building

Smart building

OT bridges, building signals, and edge gateways with explicit segmentation discipline.

Open
Developer APIs

Developer APIs

Tenant API v1 — OpenAPI, Postman, device provisioning, edge commands, and M365 visit sync with granular scopes.

Open

Continue exploring

Open workspace identity, facility topology, or ledger exports — or return to the platform core.

Platform core Workspace Ledger