Azure Custom Resource Providers Retiring

The Azure Custom Resource Providers (CuRP) service will be retired on Oct. 31, 2026. After July 31, 2026, new custom resource providers will not be allowed, and existing custom resource providers will no longer be modifiable. Certain partner ISVs, such as those that offer Azure managed applications, will still be allowed to build custom resource providers by working directly with Microsoft. CuRP, which entered preview in 2018 and never reached general availability, allows customers to extend the Azure Resource Manager deployment framework to include custom resources that can be deployed alongside Azure’s native resources, such as VMs and Azure Storage instances. Custom resources could be used to manage customer-built apps using the same processes and governance that are used for native resources. CuRP is likely being retired because of low adoption, support complexity, and security considerations. Alternatives to creating a custom resource provider include creating triggerable custom processes using offerings such as Azure Functions with Azure Resource Manager Deployment Scripts; working with Bicep extensions; and building custom workflows with Logic Apps and Azure API Management. The CuRP retirement notice and documentation are at “Azure Custom Resource Providers Overview” (Microsoft).