Skip to content

Commit 8315064

Browse files
Merge pull request #296135 from dlepow/patch-753301
Update direct-management-api-retirement-march-2025.md
2 parents bcba1c1 + 9da5b6d commit 8315064

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/api-management/breaking-changes/direct-management-api-retirement-march-2025.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66
ms.service: azure-api-management
77
ms.custom: devx-track-arm-template
88
ms.topic: reference
9-
ms.date: 05/16/2024
9+
ms.date: 03/11/2025
1010
ms.author: danlep
1111
---
1212

@@ -22,11 +22,13 @@ A built-in [direct management API](/rest/api/apimanagement/apimanagementrest/api
2222

2323
## What is the deadline for the change?
2424

25-
The direct management API is deprecated. Support for the direct management API will no longer be available after 15 March 2025.
25+
The direct management API is deprecated. Support for the direct management API will no longer be available starting 15 March 2025.
2626

2727
## What do I need to do?
2828

29-
You should no longer use the direct management API. Before the retirement date, update your tools, scripts, and programs to use equivalent operations in the Azure Resource Manager-based REST API instead.
29+
You should no longer use the direct management API and, if it's enabled in your API Management instance, you should disable it. To detect API Management instances that have the direct management API enabled, you can use this [open-source tool](https://github.com/simonkurtz-MSFT/api-management-discover-direct-management-api-status).
30+
31+
Before the retirement date, update your tools, scripts, and programs that call the direct management API endpoint (`https://<service-name>.management.azure-api.net`) to use equivalent operations in the Azure Resource Manager-based REST API instead.
3032

3133
## Help and support
3234

0 commit comments

Comments
 (0)