updating release note

Author: evachen96

articles/healthcare-apis/azure-api-for-fhir/release-notes-2026.md

@@ -21,7 +21,6 @@ Azure API for FHIR® provides a fully managed deployment of the Microsoft FHI
 
 ## March 2026
 ### FHIR service
-
 **Bulk Export cancellation behavior update**: Added updates to align the FHIR server to support [Bulk Data Access 2.0](https://hl7.org/fhir/uv/bulkdata/STU2/export.html#bulk-data-delete-request). This includes a change to bulk export cancellation behavior. Previously, cancellation request of an already completed, cancelled, or failed export job returned "200 OK." The behavior is now updated to return more informative operation outcomes:
   - Cancelling an already-cancelled export job returns "404 Job Not Found."
   - Cancelling a completed or failed export job returns "404 Job Not Found" if the job has already been cancelled or failed; otherwise returns "202 Accepted."
@@ -30,6 +29,8 @@ Azure API for FHIR® provides a fully managed deployment of the Microsoft FHI
 
 
 #### Bug fixes:
+**Added validation for search parameter URL length**:There was an issue where custom search parameter URLs that were longer than the 128-character limit were allowed into the FHIR server and truncated, resulting in faulty search parameter behavior. This issue has been fixed by adding a validation for search parameter URL length. If the URL length exceeds the limit, the validation will fail and return an error: "Search Parameter URL exceeds the maximum length limit of 128".
+
 **Fix for versioning configuration issue**:  On 10 March 2026, a release rolled out that fixed a bug that prevented the resource versioning policy default setting from being honored in the FHIR server. This fix revealed another bug involving a bad configuration setting value that resulted in some requests failing with 500 errors. The issue was fixed on 10 March 2026.
 
 ## February 2026

articles/healthcare-apis/release-notes-2026.md

@@ -19,7 +19,6 @@ Release notes describe features, enhancements, and bug fixes released in 2026 fo
 
 ## March 2026
 ### FHIR service
-
 **Token search behavior update**: After 2 March 2026, the Azure FHIR service was updated so that token values longer than 128 characters are no longer truncated during indexing. If your workspace is affected, you may notice changes in the number of resources returned for token-based queries, along with improved overall query performance. The goal for this update is to improve search behavior accuracy and strengthen service reliability. An Azure service notification was sent to affected accounts with more details.
 
 **Bulk Export cancellation behavior update**: Added updates to align the FHIR server to support [Bulk Data Access 2.0](https://hl7.org/fhir/uv/bulkdata/STU2/export.html#bulk-data-delete-request). This includes a change to bulk export cancellation behavior. Previously, cancellation request of an already completed, canceled, or failed export job returned "200 OK." The behavior is now updated to return more informative operation outcomes:
@@ -29,6 +28,8 @@ Release notes describe features, enhancements, and bug fixes released in 2026 fo
   - Trying to get the status of a user-requested canceled job returns "404 Job Not Found."
 
 #### Bug fixes:
+**Added validation for search parameter URL length**: There was an issue where custom search parameter URLs that were longer than the 128-character limit were allowed into the FHIR server and truncated, resulting in faulty search parameter behavior. This issue has been fixed by adding a validation for search parameter URL length. If the URL length exceeds the limit, the validation will fail and return an error: "Search Parameter URL exceeds the maximum length limit of 128".
+
 **Fix for token search with system values only**: A regression was introduced in the 12 March 2026 release where searches for token search parameters that only included a system value, and not a code, were returning incorrect results. The  issue was fixed on 14 March 2026.
 
 **Fix for versioning configuration issue**:  On 10 March 2026, a release rolled out that fixed a bug that prevented the resource versioning policy default setting from being honored in the FHIR server. This fix revealed another bug involving a bad configuration setting value that resulted in some requests failing with 500 errors. The issue was fixed on 10 March 2026.