PATCH /bookingBusinesses/{id} displayName updates not reflected in GET /bookingBusinesses

We are encountering an inconsistency with the Microsoft Graph API for Bookings. After sending a successful PATCH request to update the displayName of a booking business, the update is correctly reflected in the response of GET /bookingBusinesses/{id}. However, the same change is not reflected in the results of GET /bookingBusinesses, even after a week has passed.

Details:

• PATCH Endpoint Used:
  PATCH https://graph.microsoft.com/v1.0/solutions/bookingBusinesses/{id}
• GET Endpoints Tested:
  • GET https://graph.microsoft.com/v1.0/solutions/bookingBusinesses/{id} ✅ Shows updated displayName
  • GET https://graph.microsoft.com/v1.0/solutions/bookingBusinesses ❌ Still shows old displayName
• Response to PATCH:
  HTTP 204 No Content (successful update)
• Observed Delay:
  Over 7 days, no change observed in list response.
• Expected Behavior:
  GET /bookingBusinesses should return the updated displayName for the business entity.

Trace ID / Request Log Metadata:

"timestamp": "2025-06-13T13:44:41.479Z"

"service": "ms-bookings-business-graph-api-utility"

"xray_trace_id": "1-684c2b46-693da2b57acdbf0c7e9110a1"

"status": 204

Steps to Reproduce:

1. Send a valid PATCH to update displayName on an existing booking business.
2. Confirm GET /bookingBusinesses/{id} reflects the new displayName.
3. Check GET /bookingBusinesses — the displayName remains unchanged.
4. Wait multiple days (in this case, 7+) — still no update observed in the list endpoint.

Impact:

This affects our ability to reliably sync and display updated business data across our systems, particularly where lists are used (e.g., admin interfaces, calendars, reporting). It creates confusion for users expecting to see the latest business names.