Service Desk Integrations and Ticket Outcomes

Key Takeaways

  • A service desk integration can route manual provisioning actions to an external ticket queue and check ticket status.

  • Select the documented VA-based or SaaS connection type for the ticketing system and confirm that the chosen type can reach it.

  • ServiceNow Service Desk supports service requests and incidents. The ServiceNow Service Catalog integration serves a different request-entry purpose.

  • Map the external ticket’s outcomes to SailPoint’s processing states and verify the target change separately.

Last updated: November 2026

Identify where the work happens

A service desk integration sends work that a service desk must carry out to an information technology service management (ITSM) system. In SailPoint’s Service Desk Integration Module (SDIM) for ServiceNow, a manual provisioning action can become a Service Request or Incident. The ticket identifies the work for fulfillment. SailPoint checks the ticket outcome and maps its status back to the provisioning task. An already-created ticket demonstrates that a handoff occurred. Validate the actual change in the system that owns the access when evidence of fulfillment matters.

Distinguish an external ticket from an access request’s entry point. The ServiceNow Service Catalog integration lets users interact with SailPoint access requests from the ServiceNow portal. The Service Desk integration converts SailPoint provisioning activity into tickets. A requirement to submit access requests in the portal and a requirement to create tickets for manual provisioning are different design decisions. An account source that brings ServiceNow users into SailPoint serves another purpose again.

Business requirementIntegration choice
Fulfill a manual change in a private ticketing system with a supported appliance connectionEvaluate the VA-based service desk option and verify the cluster can reach the ticketing endpoint
Route manual work to a supported SaaS ticketing instance with SailPoint-hosted connectivityEvaluate the SaaS service desk option and its endpoint, license and authentication
Integrate with a ticketing product through a configurable supported interfaceEvaluate the Generic Service Desk option and configure ticket creation and status mapping for the actual interface
Let users initiate a SailPoint-governed access request from a ServiceNow portalEvaluate the Service Catalog integration for that request-entry requirement

SailPoint lists ServiceNow Service Desk and Generic Service Desk in VA-based and SaaS-based forms. Platform support is connector-specific. For example, its catalog lists Jira Data Center Service Management in the VA-based group and Jira Cloud in both groups. Check the chosen product and connectivity column together. A private ticketing endpoint can also require network and authentication work even when its integration is listed.

Design and verify a ticket path

  1. Identify the manual provisioning source and the actions that should create tickets. The ServiceNow connector documentation requires a source that generates manual tasks and a ServiceNow user source for requester identity correlation.
  2. Configure connection details, authentication, ticket fields, routing and requester mapping. For applicable Service Requests, choose the ServiceNow catalog item that should represent the action.
  3. Map external statuses to SailPoint states such as Queued, Committed and Failed. In the documented ServiceNow Incident mapping, a configured closure code takes precedence over the incident status.
  4. Test a queued request, a completed request, and one that closes unsuccessfully. Compare the ticket identity, external status read by SailPoint, resulting task state, and actual access on the target.

For example, an engineer retires an entitlement in a legacy application administered through tickets. Approval produces a manual revocation task and SDIM creates an incident. The service desk closes the incident as unsuccessful because the underlying account could not be found. If the integration marks every closed incident as committed, the tenant can display success for an unfinished removal. Configure and test the specific unsuccessful closure code to yield Failed. Confirm the target account state and retain the link between the request and the incident. This case calls for changing the status mapping or confirming which closure code was returned before editing the entitlement or its source connection.

Keep the external reference visible in the incident investigation. SailPoint documents Service Desk connector activity in Search and the identity’s activity view. Correlating those events with the ServiceNow record can show whether the integration created a ticket, received an unsuccessful outcome, or has yet to read a final result.

Now consider a ticket that remains queued while the service desk claims completion. Compare the integration’s tracked ticket type and status field against the record that the operator updated. In ServiceNow, a parent request and a requested item have separate status mappings. Check which record the integration polls and whether item-level tracking is configured before assuming that the polling job is broken.

See SailPoint’s service desk catalog, ServiceNow Service Desk requirements, status mapping, and Service Catalog distinction.

Test Your Knowledge

A team needs SailPoint manual provisioning tasks to create ServiceNow tickets. Which option addresses that requirement?

A

Configure the ServiceNow Service Desk integration for the manual tasks and map ticket statuses

B

Use the ServiceNow Service Catalog only because it defines how all provisioning tasks create incidents

C

Upload a ServiceNow user file each night to create incidents

D

Enable provisioning on the legacy application without setting up a service desk connection

Test Your Knowledge

The ServiceNow Incident is closed with an unsuccessful closure code, but the status is mapped to Committed. Which mapping condition should the engineer check first?

A

Whether the requester’s identity profile uses a lower numeric priority

B

Whether the source schema lists ServiceNow as the Account ID

C

Whether the configured incident closure code maps to Failed, because it takes precedence over incident status

D

Whether the target allows a full entitlement aggregation

Sections you finish are checked off in the contents.