Skip to content

Commit 42b7d80

Browse files
authored
Added async operation status check change
1 parent aa6ca0f commit 42b7d80

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

changelogs/api-management-service.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,9 @@
2929

3030
---
3131

32-
### ⚠️ Change
32+
### ⚠️ Changes
3333
- You may need to **associate a workspace with a workspace gateway** before managing resources in that workspace. [More info](https://learn.microsoft.com/en-us/azure/api-management/breaking-changes/workspaces-breaking-changes-march-2025)
34+
- We've updated how the state of asynchronous operations is tracked in the Microsoft.ApiManagement resource provider in all API version. Going forward, responses will include an `Azure-AsyncOperation` header, in addition to the Location header. This header contains a URL following the format below, which can be used to monitor the operation status: `https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group}/providers/Microsoft.ApiManagement/service/{service-name}/tenant/operationResults/{operation-id}`. To check the status of an operation, customers using [built-in roles](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#integration) don't need to take any action. However, **custom reader roles must be updated** to allow the `Microsoft.ApiManagement/service/tenant/*/read` action. [Learn more.](https://learn.microsoft.com/azure/azure-resource-manager/management/async-operations)
3435

3536
---
3637

0 commit comments

Comments
 (0)