Skip to content
AscendCore
Back to Runbook Library
Provisioning Live in production

Device Enrollment Assignment

Approve a user into the Intune enrollment group from Slack or Teams so their devices can enroll into management, with current devices reported, audited.

Integrates with

Entra IDIntune

The problem

New hardware is only useful once the user's devices can enroll into management and pull the right configuration. When the enrollment group is managed by hand, the device shows up unmanaged and the new hire waits on IT.

What AscendCore does

A requester names the user in Slack or Teams. AscendCore resolves them in Microsoft Entra ID and proposes the grant to an approver. On approval the user is added to the Intune enrollment group (resolved fresh at execution time), and their existing managed devices are reported alongside for context. The report is informational and never blocks the grant. The decision and per-step outcomes are recorded in the audit chain.

Status

Live in production. Executes against real Microsoft Entra ID tenants today from Slack and Teams, with per-step outcomes in the audit chain. The managed-device report runs where Intune is licensed.

Runbook source preview

Versioned, deterministic, auditable

Every runbook is defined as a versioned YAML manifest with explicit triggers, steps, and approval policies. The runbook itself is the audit-ready record of what AscendCore can and will do. Chat is just the interface that triggers it.

name: device-enrollment-assignment
trigger:
  channels: [slack, teams]
  commands: [device-enroll]
steps:
  - resolve_target_user         # Entra ID
  - admin_approval
  - add_to_enrollment_group     # group resolved at execute time
  - report_managed_devices      # informational, never blocks the grant
approval:
  required: true
  approvers: [it-admins]
Ready to deploy

Run device enrollment assignment from Teams or Slack today

AscendCore deploys in days, not months for Slack + Okta or Teams + Entra stacks. See your first automated resolution the same day.