204 status from Custom Connector, no changes made

IQ 0 Reputation points
2024-11-05T16:31:03.5233333+00:00

Hello,

I created a custom connector to update the "employeeLeaveDateTime" user attribute in Entra. The request succeeds and returns a 204 status code but when I check the changes in MS Graph nothing has changed. Does anyone know why? Should I receive a 200 status instead? Below is a copy of my API definition.

swagger: '2.0'

info:

title: Offboarding Connector

description: API for managing offboarding processes.

version: '1.0'

host: graph.microsoft.com

basePath: /v1.0

schemes:

  • https

consumes:

  • application/json

produces:

  • application/json

paths:

/users/{UID}:

patch:

  responses:

    default:

      description: default

      schema: {}

  summary: Update employeeLeaveDateTime

  parameters:

    - name: UID

      in: path

      required: true

      type: string

      description: The unique identifier of the user

    - name: Prefer

      in: header

      required: false

      type: string

      description: Client preference for response representation

      default: return=representation

    - name: Content-Type

      in: header

      required: true

      type: string

      description: The content type of the request body

      default: application/json

    - name: body

      in: body

      required: true

      schema:

        type: object

        properties:

          employeeLeaveDateTime:

            type: string

            format: date-time

  operationId: Offboard

  x-ms-visibility: important

  description: Update employeeLeaveDateTime

definitions: {}

parameters: {}

responses: {}

securityDefinitions:

oauth2-auth:

type: oauth2

flow: accessCode

tokenUrl: https://login.windows.net/common/oauth2/authorize

scopes: {}

authorizationUrl: https://login.microsoftonline.com/common/oauth2/authorize

security:

  • oauth2-auth: []

tags: []

Microsoft Security | Microsoft Graph
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. IQ 0 Reputation points
    2024-11-07T06:16:01.5133333+00:00

    I figured out that it accepts the value as the trigger for the lifecycle process and returns the value to null if queried. the trigger is still set in the lifecycle process and the actions in the tasks process.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.