Skip to content

Commit c77b893

Browse files
Update release-notes-2025.md
Further edits
1 parent 5dfea78 commit c77b893

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

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

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,13 @@ Azure API for FHIR® provides a fully managed deployment of the Microsoft FHI
2727

2828
### Enhancement: Improved error handling and validation
2929

30-
HTTP Method Validation for Transaction Bundle Requests:
31-
Added validation to ensure the HTTP method in the Request component of the transaction bundle is a valid HTTPVerb enum value. If the HTTP method is invalid or null, a `RequestNotValidException` is thrown with a `400 Bad Request` status, providing a clearer error message to users.
30+
**HTTP Method Validation for Transaction Bundle Requests**: Added validation to ensure the HTTP method in the Request component of the transaction bundle is a valid HTTPVerb enum value. If the HTTP method is invalid or null, a `RequestNotValidException` is thrown with a `400 Bad Request` status, providing a clearer error message to users.
3231

33-
Partition Size Error Handling: When a partition exceeds 20GB, a `PreconditionFailedException` is raised, replacing the previous HTTP 500 errors with HTTP 400 errors. This indicates to customers that the failure is due to an issue on their end (partition size).
32+
**Partition Size Error Handling**: When a partition exceeds 20GB, a `PreconditionFailedException` is raised, replacing the previous HTTP 500 errors with HTTP 400 errors. This indicates to customers that the failure is due to an issue on their end (partition size).
3433

35-
Transaction Failure Exception: A new FHIR-specific exception type has been introduced to handle Cosmos DB transaction failures, replacing the generic `InvalidOperationExceptions`.
34+
**Transaction Failure Exception**: A new FHIR-specific exception type has been introduced to handle Cosmos DB transaction failures, replacing the generic `InvalidOperationExceptions`.
3635

37-
CMK Error Handling: Improved error handling for operations dependent on customer-managed keys. Users will now see a more specific error message and a link to [Microsoft's troubleshooting guide](../fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
36+
**CMK Error Handling**: Improved error handling for operations dependent on customer-managed keys. Users will now see a more specific error message and a link to [Microsoft's troubleshooting guide](../fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
3837

3938
## Related content
4039

0 commit comments

Comments
 (0)