Azure PostgreSQL advisory SJRX-YHZ: how to identify affected API callers, and is 2026-01-01-preview included?

We received Azure Database for PostgreSQL retirement advisory SJRX-YHZ, with a retirement date of 30 January 2027.

The notice lists specific retiring management API versions through 2025-06-01-preview and recommends moving dependencies to 2026-04-01-preview or later.

Our checks so far:

• Service Health shows the advisory but no impacted resources.
• Our PostgreSQL flexible server is healthy.
• A PostgreSQL-provider-filtered Activity Log query covering 90 days returned no entries. We understand that read operations are not normally captured.
• Inspection of our application scripts and scheduled automation has not identified calls using the listed retiring versions.
• An observed server lookup from Azure CLI 2.84.0 uses 2026-01-01-preview.
• A direct read-only server lookup using 2026-10-01 succeeds.

Could Microsoft clarify:

1. Is 2026-01-01-preview affected by this specific retirement? It is absent from the notice’s explicit list but earlier than its recommended migration target.
2. How can customers identify the API version, operation, caller and last-used timestamp that triggered the advisory, particularly for read-only requests?
3. Does receiving this advisory establish that a retiring API was observed in the subscription, or can it be a broader notification?
4. Which Azure CLI release or supported configuration should customers use to move PostgreSQL management calls to the recommended API versions?

This concerns Azure management APIs, not a PostgreSQL engine-version upgrade.