SolarWinds Service Desk already appears to provide a Microsoft Teams client integration, and the documentation says users can log in, create tickets, view tickets, see ticket details, add comments, resolve tickets, and use live chat with an agent from within Teams. The documentation also states that tickets created through this integration can be identified with Teams as the incident origin.
SolarWinds Service Desk documentation also states that the product includes an open REST API, and the integrations documentation describes process integrations for connecting Service Desk with third-party applications. In addition, SolarWinds documents Microsoft-related integration points such as Microsoft Entra provisioning and a built-in MS Entra ID integration that is listed as being in Labs.
What I have not found in the documentation is a clearly documented, native way for SolarWinds Service Desk ticket data to be exposed as a Microsoft 365 / Copilot-searchable data source for broader ticket lookup, summarization, and contextual reference outside of the current Teams experience.
Requested Enhancement
Please extend the existing Microsoft integration story for SolarWinds Service Desk by adding a native or officially supported Microsoft 365 / Copilot-accessible ticket search and reference capability.
Why this would help
Today, Service Desk already supports ticket activity in Teams and provides API-based integration options, but there does not appear to be a documented feature that exposes ticket data more broadly for Microsoft 365 search and AI-assisted reference workflows. A supported capability here would make ticket history easier to find, summarize, and reference in organizations that work heavily inside Microsoft tools.
Examples of valuable outcomes
- Secure search and reference of Service Desk tickets from Microsoft 365 experiences
- A supported connector for exposing ticket metadata and ticket content to Microsoft search experiences
- A broader Microsoft integration model beyond the currently documented Teams client functionality
- Administrative controls to define which ticket fields are exposed and which remain restricted
Important requirements
- Respect existing SolarWinds permissions and role-based access
- Allow administrators to control which ticket fields are exposed
- Keep internal/private notes separated appropriately
- Support secure authentication and governance expectations already present in enterprise Microsoft environments
Because SolarWinds Service Desk already documents Microsoft Teams integration, API availability, and Microsoft identity-related integration points, this request is intended as an extension of those existing capabilities, not a request for first-time Microsoft integration.
