One Integration hub
Configure Slack workspace and Microsoft Teams side by side under Admin → Integrations.
Teams & Slack
Connect Orqit With Microsoft Teams & Slack
Configure per-tenant Microsoft Teams and Slack in the Orqit Integration hub—channel notifications for both platforms, with deeper Slack workspace collaboration (DMs, commands, and interactive approvals) where your team lives in Slack.
Overview
Microsoft Teams and Slack are Orqit collaboration surfaces inside the Enterprise Operations Platform—configured from Admin → Integrations. Orqit remains the system of record for tickets, assets, approvals, and audit; chat tools carry awareness and, on Slack, selected self-service actions.
Audience
Who this is for
- IT helpdesk agents who need faster awareness of assignments and approvals
- IT administrators configuring tenant integrations
- IT operations teams watching incidents and SLA events
- Team leads and approvers who work primarily in chat
- Employees mentioned on tickets or waiting on request decisions
Challenges
Problems we address
-
Missed notifications Service updates stay inside the ITSM console while people are in chat.
-
Context switching Agents jump between Orqit and Teams or Slack to learn what changed.
-
Delayed responses Assignments and approvals wait until someone opens the right queue.
-
Poor visibility Channel stakeholders cannot see operational events without a separate login.
-
Manual communication People copy ticket links into chat by hand—slow and easy to miss.
Context
How Orqit approaches this
Employees collaborate in Teams or Slack while IT work lives in Orqit. The Integration hub connects both chat platforms so operational signals reach people where they already work—without inventing a second helpdesk inside chat.
Capabilities
Platform capabilities
Bring Orqit IT service notifications and Slack collaboration into the chat tools your employees already use.
Channel notifications (Teams & Slack)
Incoming Webhooks deliver plain-text operational messages to subscribed channels for both providers.
Slack workspace OAuth
Per-tenant Slack app OAuth with bot scopes for chat, DMs, users, commands, and app mentions.
Slack personal DMs
Linked users can receive Block Kit–oriented DMs for assignments, mentions, approvals, and SLA events.
Slack commands & Events API
Slash commands, Events API, and interactivity endpoints power the personal assistant and approval buttons.
Slack interactive approvals
Approvers can act on approval notifications from Slack when interactive actions are enabled.
Slack user mapping
Sync and map Orqit users to Slack identities for DM delivery and command authorization.
Microsoft Teams OAuth setup
Per-tenant Azure app Client ID/secret, redirect URI, and Azure AD tenant for workspace connection.
Workflow
How it works in practice
-
1
Open Integration hub
In Orqit Admin → Integrations, open Integration hub to configure Slack and Microsoft Teams.
-
2
Connect each workspace
Save OAuth credentials, enable OAuth, and connect Slack and/or Teams for the tenant.
-
3
Configure notifications
Set Incoming Webhooks and hub subscriptions for channel delivery; on Slack, enable personal assistant and broadcasts as needed.
-
4
Work from chat + Orqit
Teams receive channel awareness; Slack users can also get DMs and complete selected actions—then open Orqit for full context.
Outcomes
Results teams care about
Faster awareness
Assignments, comments, and approvals surface in chat without waiting for inbox refresh.
Helpdesk focus
Agents see what needs attention while staying in their collaboration tool.
Tenant-scoped setup
Each Orqit tenant configures its own Slack app and Azure/Teams credentials.
Orqit remains system of record
Tickets, SLAs, assets, and audit trails stay in Orqit—chat does not replace the console.
Use cases
Where teams apply this
Notify channels about incidents and updates
Hub subscriptions and Incoming Webhooks post operational text to Slack or Teams channels.
Slack DM on assignment
Linked assignees can receive personal Slack notifications for incident, task, or asset assignment.
Approval awareness (and Slack action)
Approval-required events can notify Slack users; interactive Slack actions support approve/reject where configured.
SLA breach and escalation awareness
Slack personal notifications include SLA breached and SLA escalation events for linked recipients.
Comment mention in Slack
Mentioned users can receive Slack DMs so they see the conversation without hunting the ticket.
Governance & security
Built for audit and least-privilege
- Slack and Teams are configured per tenant in Admin → Integrations (Integration hub).
- Channel hub broadcasts are gated by Slack workspace broadcast settings for the tenant—confirm broadcast enablement when expecting channel delivery.
- Microsoft Teams channel delivery today uses Incoming Webhooks (plain text). Adaptive Cards, Bot Framework bots, and Graph DM delivery are not marketed as shipped on this page.
- Slack supports Events API signature verification, encrypted secrets, and user mapping for personal assistant authorization.
- Visual workflow send_slack / send_teams actions are not claimed as production-wired triggers on this page.
Analytics
Operational visibility
Administrators connect Slack and Microsoft Teams workspaces, enable OAuth where required, configure Incoming Webhooks and hub subscriptions, and—for Slack—toggle personal assistant and broadcast settings.
Details
In depth
The problem
Employees work in Microsoft Teams or Slack all day. IT service activity—incidents, requests, assignments, approvals, SLA pressure—lives in a separate ITSM platform.
That split creates:
- Missed notifications
- Constant context switching
- Delayed responses
- Poor visibility for stakeholders in chat
- Manual “paste the ticket link into the channel” communication
Orqit connects both chat platforms from one Integration hub so awareness (and, on Slack, selected actions) meet people where they already work—while Orqit stays the system of record.
How it works
1. Connect in the Integration hub
Administrators configure each provider under Admin → Integrations → Integration hub, including OAuth credentials and webhook destinations.
Shared path (Teams & Slack)
- Orqit domain event
- Integration hub subscriptions
- Incoming Webhook (plain text)
- Teams channel or Slack channel
2. Collaborate in Slack with the Orqit agent
On Slack, mapped users can message the Orqit agent (for example show my tickets) and receive Block Kit–oriented replies with ticket status, priority, and follow-up actions—without leaving the chat.
Slack collaboration path (deeper)
- Orqit domain event
- Personal notification service (Slack)
- Bot DM (Block Kit–oriented) to mapped user
- Optional slash commands / Events API / interactive buttons
Slack workspace OAuth enables bot messaging, DM history scopes, user read, commands, and app mentions. Signing secret verifies Events API and interactivity callbacks.
What Teams is today
Microsoft Teams in Orqit is configured with a per-tenant Azure app (Client ID, client secret, redirect URI, Azure AD tenant) for workspace connection, plus Incoming Webhook channel notifications.
This page does not claim Teams Adaptive Cards, Bot Framework bots, Graph-powered DMs, or Slack-feature parity for interactive approvals.
Capabilities by platform
| Capability | Slack | Microsoft Teams |
|---|---|---|
| Integration hub configuration | Yes | Yes |
| Per-tenant OAuth app setup | Yes (Slack app) | Yes (Azure app) |
| Channel Incoming Webhook notifications | Yes | Yes |
| Hub event subscriptions | Yes | Yes |
| Personal DMs to mapped users | Yes | Not claimed |
| Slash commands / Events API | Yes | Not claimed |
| Interactive approve/reject buttons | Yes | Not claimed |
| User sync / DM channel sync | Yes | Not claimed |
| Personal assistant toggles | Yes | Slack-oriented settings in hub |
| ChatOps HTTP API for integrators | Yes | Yes (key-authenticated API; not a Teams client UI) |
ITSM connection
Orqit ITSM remains the system of record. Chat integrations surface operational awareness around service work:
| Area | How chat connects (verified) |
|---|---|
| Incidents / tickets | Channel webhook text for created/updated/comment/assignment-oriented hub events; Slack DMs for assignment |
| Service / request approvals | Slack personal notifications for approval-required / request-approval; Slack interactive approve/reject |
| Comments | Channel comment events via hub; Slack DM on comment mention |
| SLA | Slack personal DM for SLA breached and SLA escalation; channel delivery when subscribed/formatted |
| Assets / tasks | Slack personal DM on asset or task assignment |
| Change | Not marketed as a dedicated Teams/Slack change module on this page—use Orqit ITSM for change records |
Orqit does not replace the agent workspace with chat. Deep investigation, device context, and full ticket history stay in Orqit—including IT Service Management and Operations Center when endpoints are involved.
Workflow automation
Visual workflow actions such as `send_slack` / `send_teams` and chat message triggers are not claimed as production-wired on this page. Use the Integration hub notification paths documented above for chat delivery today. See Workflow Automation for Orqit’s broader automation product.
Administration
From Admin → Integrations → Integration hub, administrators can:
Slack workspace
- Client ID, client secret, redirect URI (for example `/integrations/slack/workspace/callback`)
- Signing secret (Events API and interactivity verification)
- OAuth enabled toggle, Save, Connect / Disconnect
- User sync, DM channel sync, manual user mapping
- Personal assistant and broadcasts toggles; test DM
- Legacy/channel Incoming Webhook URL and event checkboxes
- Hub notification subscriptions
Microsoft Teams
- Client ID, client secret, redirect URI (for example `/integrations/teams/workspace/callback`)
- Azure AD tenant (commonly `common`)
- OAuth enabled toggle, Save, Connect / Disconnect
- Incoming Webhook URL and event checkboxes
- Hub notification subscriptions with Teams as provider
Permission to administer integrations is controlled by Orqit admin integration access—not by sharing secrets in marketing materials.
Security (verified controls)
- Per-tenant configuration — Slack and Teams credentials are scoped to the Orqit tenant
- OAuth — Slack workspace OAuth; Microsoft identity OAuth for Teams Azure app connection
- Encrypted secrets — client secrets, tokens, and webhook destinations are stored via Orqit’s secret handling
- Slack request verification — signing secret HMAC verification on Slack Events / interactions
- User mapping & authorization — Slack personal commands and actions require linked users and authorization checks
- Admin permission — Integration hub is an administrator surface
We do not claim “zero trust,” “enterprise-grade” as a slogan, or “100% secure.”
Who benefits
- IT helpdesk — faster assignment and approval awareness
- IT administrators — one hub for Slack and Teams configuration
- IT operations — channel visibility for operational events
- Approvers & team leads — Slack DM/actions when mapped
- Employees — less waiting on manually forwarded ticket updates
Related products
FAQ
Common questions
What is the Orqit Microsoft Teams & Slack integration?
It is the Integration hub connection that lets each Orqit tenant configure Slack and Microsoft Teams for collaboration around IT service activity—channel webhook notifications for both, with deeper Slack workspace features (OAuth bot, DMs, commands, and interactive approvals).
What can Orqit send to Microsoft Teams?
Orqit can post plain-text messages to Teams via Incoming Webhooks and hub subscriptions for operational events (for example ticket created/updated, comments, and assignment-oriented patterns configured in the hub). Personal Teams DMs and Adaptive Cards are not claimed here.
What can Orqit send to Slack?
Slack supports channel Incoming Webhooks plus personal DMs for events such as incident/task/asset assignment, approval required, request approval, comment mention, SLA breached, and SLA escalation—using Block Kit–oriented messages where mapped.
Can Orqit send ticket notifications to Teams?
Yes—via Teams Incoming Webhook / hub subscription channel delivery for configured operational events. This is channel text notification, not a full two-way Teams helpdesk.
Can users create tickets from Microsoft Teams?
Orqit does not ship a native Teams Bot Framework ticket-creation UI in this product surface. A separate ChatOps HTTP API exists for integrators; it is not the same as creating tickets from the Teams client UI.
Can users create tickets from Slack?
Yes—when the Slack personal assistant / ChatOps paths are enabled and the user is mapped, Slack supports creating incidents and related commands through the Slack events and slash-command integration.
Can users approve requests from Teams?
Interactive approve/reject buttons are implemented for Slack interactions. Native Teams Adaptive Card approvals are not claimed as shipped.
Can users approve requests from Slack?
Yes—approval notifications can include interactive approve/reject actions handled by Orqit’s Slack interactions endpoint, subject to mapping and authorization.
Can Orqit notify Teams about SLA events?
SLA-related events can be formatted for hub channel delivery. Slack also delivers SLA breached and SLA escalation as personal DM events to linked users. Confirm your subscription and broadcast settings.
Does Orqit support Microsoft 365 authentication for Teams?
Teams workspace connection uses a per-tenant Azure app (Client ID, client secret, redirect URI, Azure AD tenant such as common) with Microsoft identity OAuth. That is integration OAuth for the Teams connection—not a claim that every Orqit login uses Microsoft 365 SSO.
How do administrators configure the integration?
Open Admin → Integrations → Integration hub. Save Slack Client ID/secret, redirect URI, and signing secret; save Teams Client ID/secret, redirect URI, and Azure AD tenant; enable OAuth; connect workspaces; configure webhooks, subscriptions, and Slack personal-assistant / broadcast toggles.
Does the integration support Teams channels?
Yes—Teams channel notifications are delivered through Incoming Webhooks configured for the tenant/subscription.
Does the integration support direct messages?
Direct messages are implemented for Slack (bot DMs to mapped users). Teams Graph/chat DM delivery is not claimed as shipped on this page.
Is Slack equal to Microsoft Teams in Orqit today?
No. Both share the Integration hub and channel webhook notifications. Slack currently has the deeper interaction surface (Events API, slash commands, Block Kit DMs, interactive approvals, user sync).
Next step
Ready to modernize IT operations?
Launch a pilot workspace or book a walkthrough — with estimated seat savings versus legacy suites, plus 24/7 support.
Entity graph