Azure Managed Applications
An Azure service that enables managed service providers, independent software vendors, and enterprise IT teams to deliver turnkey solutions through the Azure Marketplace or service catalog.
Hello,Welcome to Microsoft Q&A,
Microsoft is deprecating CuRP in 2026, and there’s no announced, like-for-like replacement for the “portal buttons & custom resources” experience that Managed Applications got by wiring viewDefinition → custom provider actions. You can still customize the Overview and Metrics blades with viewDefinition.json, but anything in commands, CustomResources, or Associations that depends on CuRP will be impacted on the dates below.
What’s officially changing
- CuRP deprecation timeline (from Microsoft Docs):
- Feb 24, 2026: “scream test.”
- Jul 31, 2026: creates/updates/patches/actions for CuRP blocked (read/delete only).
- Oct 31, 2026: retired. Microsoft suggests alternatives (depending on what you used CuRP for): Deployment Scripts, Bicep Extensions, or Azure Functions. There’s also a deprecation contact (curpdeprecation@microsoft.com).
- https://free.blessedness.top/en-us/azure/azure-resource-manager/custom-providers/overview
Today, viewDefinition’s Commands / CustomResources / Associations are explicitly defined to call custom provider actions or types. Without CuRP, those specific constructs won’t have a backend to call. There’s no public doc that introduces a new portal API to replace those action hooks. (If that changes, the CuRP page is the one Microsoft will update first.)
Please upvote and accept the answer if it helps!!