Merge pull request #312802 from guywi-ms/patch-873148

Revise API transition details in what's new section

Author: prmerger-automator[bot]

articles/sentinel/ci-cd-custom-content.md

@@ -137,7 +137,7 @@ These options are available through a feature of the PowerShell deployment scrip
 For information on managing Microsoft Sentinel repositories using the API, see the [Source Control](/rest/api/securityinsights/source-control) and [Source Controls](/rest/api/securityinsights/source-controls) actions in the Microsoft Sentinel REST API.
 
 > [!IMPORTANT]
-> Starting **May 1, 2026**, older API versions used by Microsoft Sentinel repositories will no longer be supported. If you are using APIs to create and manage repository connections, transition to API version **2025-09-01**, **2025-06-01**, or **2025-07-01-preview** before June 1, 2026 to avoid service disruption. Existing repository connections aren't affected. 
+> Starting **June 1, 2026**, older API versions used by Microsoft Sentinel repositories will no longer be supported. If you are using APIs to create and manage repository connections, transition to API version **2025-09-01**, **2025-06-01**, or **2025-07-01-preview** before June 1, 2026 to avoid service disruption. Existing repository connections aren't affected. 
 
 ## Next steps
 

articles/sentinel/whats-new.md

@@ -30,7 +30,7 @@ The retired API versions will no longer be supported, and requests using them wi
 
 **Required action**
 
-If you're using APIs to create or manage repository connections, transition to API version **2025-06-01** or **2025-07-01-preview** before May 1, 2026 to avoid service disruption.
+If you're using APIs to create or manage repository connections, transition to API version **2025-09-01**, **2025-06-01**, or **2025-07-01-preview** before June 1, 2026 to avoid service disruption.
 
 **Affected API versions**